From megaco-admin@ietf.org  Mon Apr  1 01:27: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 BAA08456
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 01:27: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 BAA03202;
	Mon, 1 Apr 2002 01:01: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 BAA03173
	for <megaco@optimus.ietf.org>; Mon, 1 Apr 2002 01:01:48 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08271
	for <megaco@ietf.org>; Mon, 1 Apr 2002 01:01:45 -0500 (EST)
From: vbajaj@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 g3162A305988;
	Mon, 1 Apr 2002 11:32:10 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B8E.0020E4F0 ; Mon, 1 Apr 2002 11:29:17 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
        megaco@ietf.org
Message-ID: <65256B8E.001ED328.00@sandesh.hss.hns.com>
Date: Mon, 1 Apr 2002 10:15:56 +0530
Subject: RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00.
		txt
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



Tom,
        I think it is absolutely necessary to take this activity as a WG work
item. This area needs
  to be addressed to avoid interoperability issues later.

Rgds,

Vikas Bajaj





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 03/29/2002 09:22:32 PM

To:   "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
      megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00. txt




Could I have opinions from the WG on whether we should be producing a
document on control associations and the signalling associated with control
state transitions as a WG work item?  I assume the work would be Standards
Track because it would specify normative behaviour on the signalling side.
As an alternative, if the impact on the base specification wouldn't be too
large, we could simply add the conclusions to the Implementor's Guide.

-----Original Message-----
From: Jean-Luc.Lecuyer@alcatel.fr [mailto:Jean-Luc.Lecuyer@alcatel.fr]
Sent: Friday, March 29, 2002 4:11 AM
To: megaco@ietf.org
Subject: [Megaco] Status of
draft-hss-megaco-control-state-machine-00.txt




What is the status of the document
"draft-hss-megaco-control-state-machine-00.txt"
which expired in February ?

Thank-you
Jean-Luc
----------------------------------------------------------------------------
----------------
Jean-Luc.Lecuyer :         VND/E10 VS  BU R&D//CCPD Lannion
Full telephone number :                                         33 (0)2 96
04 77 09
Full fax number :                                                        33
(0)2 96 04 72 35
Email :
jean-luc.lecuyer@alcatel.fr
----------------------------------------------------------------------------
-----------------



_______________________________________________
Megaco mailing 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 Apr  1 01:27: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 BAA08468
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 01:27:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA14073
	for megaco-archive@odin.ietf.org; Mon, 1 Apr 2002 01:27: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 BAA03202;
	Mon, 1 Apr 2002 01:01: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 BAA03173
	for <megaco@optimus.ietf.org>; Mon, 1 Apr 2002 01:01:48 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08271
	for <megaco@ietf.org>; Mon, 1 Apr 2002 01:01:45 -0500 (EST)
From: vbajaj@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 g3162A305988;
	Mon, 1 Apr 2002 11:32:10 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B8E.0020E4F0 ; Mon, 1 Apr 2002 11:29:17 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
        megaco@ietf.org
Message-ID: <65256B8E.001ED328.00@sandesh.hss.hns.com>
Date: Mon, 1 Apr 2002 10:15:56 +0530
Subject: RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00.
		txt
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



Tom,
        I think it is absolutely necessary to take this activity as a WG work
item. This area needs
  to be addressed to avoid interoperability issues later.

Rgds,

Vikas Bajaj





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 03/29/2002 09:22:32 PM

To:   "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
      megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00. txt




Could I have opinions from the WG on whether we should be producing a
document on control associations and the signalling associated with control
state transitions as a WG work item?  I assume the work would be Standards
Track because it would specify normative behaviour on the signalling side.
As an alternative, if the impact on the base specification wouldn't be too
large, we could simply add the conclusions to the Implementor's Guide.

-----Original Message-----
From: Jean-Luc.Lecuyer@alcatel.fr [mailto:Jean-Luc.Lecuyer@alcatel.fr]
Sent: Friday, March 29, 2002 4:11 AM
To: megaco@ietf.org
Subject: [Megaco] Status of
draft-hss-megaco-control-state-machine-00.txt




What is the status of the document
"draft-hss-megaco-control-state-machine-00.txt"
which expired in February ?

Thank-you
Jean-Luc
----------------------------------------------------------------------------
----------------
Jean-Luc.Lecuyer :         VND/E10 VS  BU R&D//CCPD Lannion
Full telephone number :                                         33 (0)2 96
04 77 09
Full fax number :                                                        33
(0)2 96 04 72 35
Email :
jean-luc.lecuyer@alcatel.fr
----------------------------------------------------------------------------
-----------------



_______________________________________________
Megaco mailing 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 mailman-owner@ietf.org  Mon Apr  1 06:34: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 GAA19258
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 06: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 GAA09886
	for <megaco-archive@lists.ietf.org>; Mon, 1 Apr 2002 06:34:34 -0500 (EST)
Date: Mon, 1 Apr 2002 06:34:34 -0500 (EST)
Message-Id: <200204011134.GAA09886@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  Mon Apr  1 08:09: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 IAA23934
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 08:09: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 HAA06873;
	Mon, 1 Apr 2002 07:38: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 HAA06830
	for <megaco@optimus.ietf.org>; Mon, 1 Apr 2002 07:38:09 -0500 (EST)
Received: from mxout2.netvision.net.il (mxout2.netvision.net.il [194.90.9.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23318
	for <megaco@ietf.org>; Mon, 1 Apr 2002 07:37:44 -0500 (EST)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout2.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GTW00M7I31LMD@mxout2.netvision.net.il> for megaco@ietf.org;
 Mon, 01 Apr 2002 15:36:57 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <HWZPZ6DZ>; Mon, 01 Apr 2002 15:35:47 +0300
Content-return: allowed
Date: Mon, 01 Apr 2002 15:35:47 +0300
From: Dan Elbert <delbert@radvision.com>
Subject: RE: [Megaco] Megaco 53 Minutes
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B018BBF4A@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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
I don't see in the list of changes for v2 the ability to specifiy topology
per stream.

Dan Elbert
RADVISION

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, March 28, 2002 12:32 AM
To: 'megaco@ietf.org'
Cc: 'Scott Bradner'; 'Allison Mankin'
Subject: [Megaco] Megaco 53 Minutes


Draft Megaco minutes, reported by Tom Taylor.
The charts presented at this meeting are available at
ftp://standards.nortelnetworks.com/megaco/docs/Current/IETF/Megaco53

The Megaco Working Group met Wednesday afternoon from 3:00 to 4:30.  Tom
Taylor <taylor@nortelnetworks.com> chaired.  40 people attended.

1. Agenda
   ======

Accepted without change.

2. Review of new charter, potential new work items
   ===============================================

Tom Taylor presented charts summarizing the new Megaco charter.  The key
point is that the Working Group can only work on enhancing the base
protocol, in cooperation with SG 16.  The Megaco E-mail list does NOT face a
similar constraint, so we can continue new package work and the like there.
We currently have three work items besides H.248v2:
 - a naming patterns package
 - the Megaco MIB
 - an Informational call flows document.

A brief discussion of other possible work items ensued.  Brian Rosen
<brian.rosen@marconi.com> mentioned that he had had requests to resubmit his
draft on packages for ATM.  The Chair noted that others had made submissions
or planned to do so on this topic.  Nevertheless, it seemed doubtful that
the IESG would interpret this work as falling within the scope of the new
charter.  He promised to discuss the matter with Scott Bradner.

Christer Holmberg <christer.holmberg@lmf.ericsson.se> brought up two work
items.  One was to define changes needed to negotiate the use of SDPng
rather than SDP.  He remarked that it was not desirable to indicate SDPng
support through choice of transport address, since this could multiply the
number of ports used.  The other work item is to define SDP for various
transports beyond IP and ATM.

3. Review of SG 16 Results
   =======================

Tom Taylor presented a chart summarizing the outlook for work at Study Group
16.  The three major points covered were the probability of an H.248v3 at
the next full Study Group meeting in October, changes in management of
Question 3/16, and the renumbering of H.248 and its Annexes.  Tom paid
tribute to Glen Freundlich, whose determination had undoubtedly reduced the
time until issuance of H.248v1 by at least half a year.  He explained that
The H.248.x series was being created so that the Annexes could be versioned
independently of the main protocol specification.

Kevin McCandless <KMcCandless@Illuminet.com> expressed his concern about
continued creation of new versions of H.248.  There should not be any more
version of H.248 developed until implementation experience is gained and the
data from that experience is analyzed.  Succeeding versions should be
backwards compatible.  Finally, on the editorial level, each new draft
version of H.248 should separately list the corrections to the previous
version and the new enhancements added.  After several additional comments
from other meeting participants, it was agreed that the Chair would send a
message to SG 16 conveying the Megaco Working Group's strong concern that
the ITU-T not move ahead with further versions until we get deployment
experience.

Tom's presentation also included charts showing the changes to H.248 made at
the Geneva meeting.  These were separated into changes affecting both v1 and
v2, and changes affecting v2 only.  Tom highlighted the largest changes,
most of which had been passed to the Megaco E-mail list for comment before
final approval.

The largest changes affecting both v1 and v2 included
 - modification of the definition of BR signals to make duration irrelevant
 - addition of text in Modify, Subtract, and Move on side-effects of
Multiplex Descriptors, consistent with the text in Add
 - clarification of the effect of omitting a descriptor and individual
properties from a command
 - retention of the restriction that a single session description within a
Local or Remote Descriptor contain no more than one m= line
 - adding the ability to disable the start timer in a digit map by setting
it to 0; applicable to the case where it is necessary to listen for new
tones throughout a call
 - clarification of the disposition of outstanding replies during switchover
 - the idea that when a parameter or property is unspecified the default may
be a specified value or it may be a different behaviour, such as not
executing a procedure in which that parameter or property is used
 - extension of the scope of the TDM package in Annex E to apply also to
non-TDM transport (e.g. ATM AAL 2).

The list of changes affecting v2 only included both changes presented at
IETF 52 and new changes introduced as a result of work in Dublin and in
Geneva itself.  The post-IETF-52 changes include:
 - deprecation of the Modem Descriptor; an appropriate SDP/Annex C attribute
should be used instead
 - Nx64K multiplex type added and described
 - added ability for duration of long tones (Z qualifier) to be overridden
in the digit map
 - added digit buffering after the digit map completion event has completed
 - can have more parameters for digit map completion event (triggering
timer, extra digit)
 - removed section 7.3 -- original content covered in Annex L and earlier in
document
 - protocol version is 2
 - Initial ServiceChange for association always uses version 1 format
 - new sections on profiles
 - corrected examples in Appendix.
 
Taking particular note of changes to digit map operation, Brian Rosen
suggested that Megaco and SG 16 should try to prevent needless divergence
between Megaco/H.248 and MGCP.

4. Control Associations
   ====================

Tom Taylor presented a series of charts concerning control association
states and the use of ServiceChange.  These were provided in the hopes of
continuing the work begun by
draft-hss-megaco-control-association-state-machine-00.txt

At the outset, the proposal that states should be analyzed separately from
the MG and MGC points of view rather than considering a joint association
state met with some agreement.  It was also agreed that a hot switchover is
by definition transparent to the peer and preserves all transactions in
progress, while a warm switchover or reboot results in a Stale state as
defined in the charts.

Tom made the point that it is important for the MGC to know what state an MG
registering with it is in when it registers.  He pointed out that the
existing specification generally does not indicate what ServiceChangeReason
to use when reestablishing a control session, and suggested that this
property is therefore available to indicate the MG's state.  He proposed
that where not otherwise specified the MG use 901 Cold Boot to indicate that
the MG was in Initialized state as defined in the charts, and 902 Warm Boot
to indicate that the MG was in Stale state.

On the MGC side, there is not the same necessity to indicate state to the
peer.

The analysis shown in the charts is incomplete, but it turned out that the
charts provided too much technical detail for the audience to comment upon
and work with on the spot.  It was agreed to adjourn the meeting early
rather than continue in design session.  [Guess I've learned my lesson --
apologies for not making the material available well in advance of the
meeting. PTT]
 
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  Mon Apr  1 08:33: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 IAA25036
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 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 IAA08431;
	Mon, 1 Apr 2002 08:11: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 AAA02310
	for <megaco@optimus.ietf.org>; Mon, 1 Apr 2002 00:49:06 -0500 (EST)
Received: from epygilab.am (araler.epygilab.am [195.151.94.74])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08149
	for <megaco@ietf.org>; Mon, 1 Apr 2002 00:48:53 -0500 (EST)
Received: (apparently) from epygilab.am ([192.168.0.156]) by epygilab.am  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Mon, 1 Apr 2002 09:48:50 +0400
Received: from epygilab.am [192.168.0.32]
	by epygilab.am [192.168.0.156]
	with SMTP (MDaemon.PRO.v5.0.1.R)
	for <megaco@ietf.org>; Mon, 01 Apr 2002 10:47:44 +0500
Message-ID: <3CA8026F.88A92E05@epygilab.am>
Date: Mon, 01 Apr 2002 10:47:11 +0400
From: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: Megaco <megaco@ietf.org>
Subject: Re: [MEGACO] what does list of signals mean?
References: <3CA16702.CC6CB0D4@epygilab.am> <3CA1F936.EDB6B299@lucent.com> <3CA2ED4A.E50A98DB@epygilab.am> <3CA4A166.46829717@lucent.com>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
X-MDRemoteIP: 192.168.0.32
X-Return-Path: Narine.Mossikyan@epygilab.am
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

It is indicated SigID=cg/rt in your sample, in this case cg signal's rt parameter
is simple. My question is if  I have SigID=pt/tl, where tl is tone id list, should
I enumerate tl's parameters too, or not? I mean will the syntax of SigID=pt/tl  be
correct if I will  not use  tl tone list parameters?

thanks for your advice
P.S. "sit" is not a parameter of "g" event. How could you explain the meaning of
g/sit you used in your sample?


Terry L Anderson wrote:

> An example would be
> End of a signal, say an ringtone
>     ObservedEvents = 2345 {20010329T11501000:g/sit{SigID=cg/rt, Meth=TO,
> SLID=NotInServiceAnnouncement}}
> If the signal had been part of a signal list, then the signal list ID is also
> returned as shown, otherwise it would be omitted.
>
> For example, if the signal was started by a signals descriptor like:
> Signals { SignalList = NotInServiceAnnouncement {
>     cg/sit {NotifyCompletion={TimeOut,IntByEvent,OtherReason}},
>     an/apf {an=NotInService, av=English, NotifyCompletion={TimeOut, IntByEvent,
> OtherReason}},
> }}
>
> End of the sit tone would be notified as above.
>
> Narine_Mossikyan wrote:
>
> > Hi ,
> > Thanks for your quick response.
> > I still don't  understand what does observedEventsDescriptor's last parameter
> > mean? Can you give me some examples of observedEventsDescriptor?
> > thanks a lot for your help
> >
> > Terry L Anderson wrote:
> >
> > > The original text was ambiguous and was recently amended to clarify this
> > > parameter.  The change first appeared in the Implementors Guide but was
> > > included in H.248v1 Corrigendum 1 and H.248v2 as consented in Geneva Feb
> > > 2002.  Here is the current text:
> > >
> > > ObservedEvents Descriptor parameters:
> > > Signal Identity
> > > ParameterID:  SigID (0x0001)
> > > This parameter identifies the signal which has terminated. For a signal
> > > that is contained in a signal list the signal list identity parameter
> > > should also be returned indicating the appropriate list.
> > > Type: Binary: octet (string), Text: string
> > > Possible values: a signal which has terminated.  A signal shall be
> > > identified using the pkgdName syntax without wildcarding.
> > >
> > > Narine_Mossikyan wrote:
> > >
> > > > Hi,
> > > > I found the list of signals on the page#139,  RFC 3015 Megaco Protocol
> > > > Version 1.0,  November 2000 , in Section Generic packages , E.1.2.
> > > > Events .
> > > > ObservedEvents Descriptor parameters:
> > > >         Signal Identity
> > > >         ParameterID:  SigID (0x0001)
> > > >         This parameter identifies the signals which have terminated.
> > > >         Type: list
> > > > My question is:
> > > > Should I implement  list of  signals as it is describe in the same RFC,
> > > > page #107 ?
> > > >         signalList           = SignalListToken EQUAL signalListId LBRKT
> > > >                           signalListParm *(COMMA signalListParm) RBRKT
> > > > or the list of signals in ObservedEvents has another meaning?
> > > > thanks for your help
> > > >
> > > > _______________________________________________
> > > > Megaco mailing list
> > > > Megaco@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/megaco
> > >
> > > --
> > >
> > > ------------------------------------------------------------
> > > Terry L Anderson             mailto:tla@lucent.com
> > > Tel:732.949.5628   Fax:732.949.7016
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson             mailto:tla@lucent.com
> Tel:732.949.5628   Fax:732.949.7016
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> 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  Mon Apr  1 08:39: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 IAA25363
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 08:39: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 IAA08764;
	Mon, 1 Apr 2002 08:20: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 IAA08659
	for <megaco@optimus.ietf.org>; Mon, 1 Apr 2002 08:20:03 -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 IAA24164
	for <megaco@ietf.org>; Mon, 1 Apr 2002 08:19:34 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g31DInu12751
	for <megaco@ietf.org>; Mon, 1 Apr 2002 08:18:50 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g31DImU07749
	for <megaco@ietf.org>; Mon, 1 Apr 2002 08:18: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 g31DIhk05380
	for <megaco@ietf.org>; Mon, 1 Apr 2002 08:18:44 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K937N>; Mon, 1 Apr 2002 08:18:45 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A217@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Dan Elbert'" <delbert@radvision.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Megaco 53 Minutes
Date: Mon, 1 Apr 2002 08:18: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'll add that to the minutes.

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Monday, April 01, 2002 7:36 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; 'megaco@ietf.org'
Subject: RE: [Megaco] Megaco 53 Minutes


Hi
I don't see in the list of changes for v2 the ability to specifiy topology
per stream.

Dan Elbert
RADVISION

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, March 28, 2002 12:32 AM
To: 'megaco@ietf.org'
Cc: 'Scott Bradner'; 'Allison Mankin'
Subject: [Megaco] Megaco 53 Minutes


Draft Megaco minutes, reported by Tom Taylor.
The charts presented at this meeting are available at
ftp://standards.nortelnetworks.com/megaco/docs/Current/IETF/Megaco53

The Megaco Working Group met Wednesday afternoon from 3:00 to 4:30.  Tom
Taylor <taylor@nortelnetworks.com> chaired.  40 people attended.

1. Agenda
   ======

Accepted without change.

2. Review of new charter, potential new work items
   ===============================================

Tom Taylor presented charts summarizing the new Megaco charter.  The key
point is that the Working Group can only work on enhancing the base
protocol, in cooperation with SG 16.  The Megaco E-mail list does NOT face a
similar constraint, so we can continue new package work and the like there.
We currently have three work items besides H.248v2:
 - a naming patterns package
 - the Megaco MIB
 - an Informational call flows document.

A brief discussion of other possible work items ensued.  Brian Rosen
<brian.rosen@marconi.com> mentioned that he had had requests to resubmit his
draft on packages for ATM.  The Chair noted that others had made submissions
or planned to do so on this topic.  Nevertheless, it seemed doubtful that
the IESG would interpret this work as falling within the scope of the new
charter.  He promised to discuss the matter with Scott Bradner.

Christer Holmberg <christer.holmberg@lmf.ericsson.se> brought up two work
items.  One was to define changes needed to negotiate the use of SDPng
rather than SDP.  He remarked that it was not desirable to indicate SDPng
support through choice of transport address, since this could multiply the
number of ports used.  The other work item is to define SDP for various
transports beyond IP and ATM.

3. Review of SG 16 Results
   =======================

Tom Taylor presented a chart summarizing the outlook for work at Study Group
16.  The three major points covered were the probability of an H.248v3 at
the next full Study Group meeting in October, changes in management of
Question 3/16, and the renumbering of H.248 and its Annexes.  Tom paid
tribute to Glen Freundlich, whose determination had undoubtedly reduced the
time until issuance of H.248v1 by at least half a year.  He explained that
The H.248.x series was being created so that the Annexes could be versioned
independently of the main protocol specification.

Kevin McCandless <KMcCandless@Illuminet.com> expressed his concern about
continued creation of new versions of H.248.  There should not be any more
version of H.248 developed until implementation experience is gained and the
data from that experience is analyzed.  Succeeding versions should be
backwards compatible.  Finally, on the editorial level, each new draft
version of H.248 should separately list the corrections to the previous
version and the new enhancements added.  After several additional comments
from other meeting participants, it was agreed that the Chair would send a
message to SG 16 conveying the Megaco Working Group's strong concern that
the ITU-T not move ahead with further versions until we get deployment
experience.

Tom's presentation also included charts showing the changes to H.248 made at
the Geneva meeting.  These were separated into changes affecting both v1 and
v2, and changes affecting v2 only.  Tom highlighted the largest changes,
most of which had been passed to the Megaco E-mail list for comment before
final approval.

The largest changes affecting both v1 and v2 included
 - modification of the definition of BR signals to make duration irrelevant
 - addition of text in Modify, Subtract, and Move on side-effects of
Multiplex Descriptors, consistent with the text in Add
 - clarification of the effect of omitting a descriptor and individual
properties from a command
 - retention of the restriction that a single session description within a
Local or Remote Descriptor contain no more than one m= line
 - adding the ability to disable the start timer in a digit map by setting
it to 0; applicable to the case where it is necessary to listen for new
tones throughout a call
 - clarification of the disposition of outstanding replies during switchover
 - the idea that when a parameter or property is unspecified the default may
be a specified value or it may be a different behaviour, such as not
executing a procedure in which that parameter or property is used
 - extension of the scope of the TDM package in Annex E to apply also to
non-TDM transport (e.g. ATM AAL 2).

The list of changes affecting v2 only included both changes presented at
IETF 52 and new changes introduced as a result of work in Dublin and in
Geneva itself.  The post-IETF-52 changes include:
 - deprecation of the Modem Descriptor; an appropriate SDP/Annex C attribute
should be used instead
 - Nx64K multiplex type added and described
 - added ability for duration of long tones (Z qualifier) to be overridden
in the digit map
 - added digit buffering after the digit map completion event has completed
 - can have more parameters for digit map completion event (triggering
timer, extra digit)
 - removed section 7.3 -- original content covered in Annex L and earlier in
document
 - protocol version is 2
 - Initial ServiceChange for association always uses version 1 format
 - new sections on profiles
 - corrected examples in Appendix.
 
Taking particular note of changes to digit map operation, Brian Rosen
suggested that Megaco and SG 16 should try to prevent needless divergence
between Megaco/H.248 and MGCP.

4. Control Associations
   ====================

Tom Taylor presented a series of charts concerning control association
states and the use of ServiceChange.  These were provided in the hopes of
continuing the work begun by
draft-hss-megaco-control-association-state-machine-00.txt

At the outset, the proposal that states should be analyzed separately from
the MG and MGC points of view rather than considering a joint association
state met with some agreement.  It was also agreed that a hot switchover is
by definition transparent to the peer and preserves all transactions in
progress, while a warm switchover or reboot results in a Stale state as
defined in the charts.

Tom made the point that it is important for the MGC to know what state an MG
registering with it is in when it registers.  He pointed out that the
existing specification generally does not indicate what ServiceChangeReason
to use when reestablishing a control session, and suggested that this
property is therefore available to indicate the MG's state.  He proposed
that where not otherwise specified the MG use 901 Cold Boot to indicate that
the MG was in Initialized state as defined in the charts, and 902 Warm Boot
to indicate that the MG was in Stale state.

On the MGC side, there is not the same necessity to indicate state to the
peer.

The analysis shown in the charts is incomplete, but it turned out that the
charts provided too much technical detail for the audience to comment upon
and work with on the spot.  It was agreed to adjourn the meeting early
rather than continue in design session.  [Guess I've learned my lesson --
apologies for not making the material available well in advance of the
meeting. PTT]
 
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  Mon Apr  1 08: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 IAA25377
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 08:39:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA09957
	for megaco-archive@odin.ietf.org; Mon, 1 Apr 2002 08: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 IAA08764;
	Mon, 1 Apr 2002 08:20: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 IAA08659
	for <megaco@optimus.ietf.org>; Mon, 1 Apr 2002 08:20:03 -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 IAA24164
	for <megaco@ietf.org>; Mon, 1 Apr 2002 08:19:34 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g31DInu12751
	for <megaco@ietf.org>; Mon, 1 Apr 2002 08:18:50 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g31DImU07749
	for <megaco@ietf.org>; Mon, 1 Apr 2002 08:18: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 g31DIhk05380
	for <megaco@ietf.org>; Mon, 1 Apr 2002 08:18:44 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K937N>; Mon, 1 Apr 2002 08:18:45 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A217@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Dan Elbert'" <delbert@radvision.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Megaco 53 Minutes
Date: Mon, 1 Apr 2002 08:18: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'll add that to the minutes.

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Monday, April 01, 2002 7:36 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; 'megaco@ietf.org'
Subject: RE: [Megaco] Megaco 53 Minutes


Hi
I don't see in the list of changes for v2 the ability to specifiy topology
per stream.

Dan Elbert
RADVISION

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, March 28, 2002 12:32 AM
To: 'megaco@ietf.org'
Cc: 'Scott Bradner'; 'Allison Mankin'
Subject: [Megaco] Megaco 53 Minutes


Draft Megaco minutes, reported by Tom Taylor.
The charts presented at this meeting are available at
ftp://standards.nortelnetworks.com/megaco/docs/Current/IETF/Megaco53

The Megaco Working Group met Wednesday afternoon from 3:00 to 4:30.  Tom
Taylor <taylor@nortelnetworks.com> chaired.  40 people attended.

1. Agenda
   ======

Accepted without change.

2. Review of new charter, potential new work items
   ===============================================

Tom Taylor presented charts summarizing the new Megaco charter.  The key
point is that the Working Group can only work on enhancing the base
protocol, in cooperation with SG 16.  The Megaco E-mail list does NOT face a
similar constraint, so we can continue new package work and the like there.
We currently have three work items besides H.248v2:
 - a naming patterns package
 - the Megaco MIB
 - an Informational call flows document.

A brief discussion of other possible work items ensued.  Brian Rosen
<brian.rosen@marconi.com> mentioned that he had had requests to resubmit his
draft on packages for ATM.  The Chair noted that others had made submissions
or planned to do so on this topic.  Nevertheless, it seemed doubtful that
the IESG would interpret this work as falling within the scope of the new
charter.  He promised to discuss the matter with Scott Bradner.

Christer Holmberg <christer.holmberg@lmf.ericsson.se> brought up two work
items.  One was to define changes needed to negotiate the use of SDPng
rather than SDP.  He remarked that it was not desirable to indicate SDPng
support through choice of transport address, since this could multiply the
number of ports used.  The other work item is to define SDP for various
transports beyond IP and ATM.

3. Review of SG 16 Results
   =======================

Tom Taylor presented a chart summarizing the outlook for work at Study Group
16.  The three major points covered were the probability of an H.248v3 at
the next full Study Group meeting in October, changes in management of
Question 3/16, and the renumbering of H.248 and its Annexes.  Tom paid
tribute to Glen Freundlich, whose determination had undoubtedly reduced the
time until issuance of H.248v1 by at least half a year.  He explained that
The H.248.x series was being created so that the Annexes could be versioned
independently of the main protocol specification.

Kevin McCandless <KMcCandless@Illuminet.com> expressed his concern about
continued creation of new versions of H.248.  There should not be any more
version of H.248 developed until implementation experience is gained and the
data from that experience is analyzed.  Succeeding versions should be
backwards compatible.  Finally, on the editorial level, each new draft
version of H.248 should separately list the corrections to the previous
version and the new enhancements added.  After several additional comments
from other meeting participants, it was agreed that the Chair would send a
message to SG 16 conveying the Megaco Working Group's strong concern that
the ITU-T not move ahead with further versions until we get deployment
experience.

Tom's presentation also included charts showing the changes to H.248 made at
the Geneva meeting.  These were separated into changes affecting both v1 and
v2, and changes affecting v2 only.  Tom highlighted the largest changes,
most of which had been passed to the Megaco E-mail list for comment before
final approval.

The largest changes affecting both v1 and v2 included
 - modification of the definition of BR signals to make duration irrelevant
 - addition of text in Modify, Subtract, and Move on side-effects of
Multiplex Descriptors, consistent with the text in Add
 - clarification of the effect of omitting a descriptor and individual
properties from a command
 - retention of the restriction that a single session description within a
Local or Remote Descriptor contain no more than one m= line
 - adding the ability to disable the start timer in a digit map by setting
it to 0; applicable to the case where it is necessary to listen for new
tones throughout a call
 - clarification of the disposition of outstanding replies during switchover
 - the idea that when a parameter or property is unspecified the default may
be a specified value or it may be a different behaviour, such as not
executing a procedure in which that parameter or property is used
 - extension of the scope of the TDM package in Annex E to apply also to
non-TDM transport (e.g. ATM AAL 2).

The list of changes affecting v2 only included both changes presented at
IETF 52 and new changes introduced as a result of work in Dublin and in
Geneva itself.  The post-IETF-52 changes include:
 - deprecation of the Modem Descriptor; an appropriate SDP/Annex C attribute
should be used instead
 - Nx64K multiplex type added and described
 - added ability for duration of long tones (Z qualifier) to be overridden
in the digit map
 - added digit buffering after the digit map completion event has completed
 - can have more parameters for digit map completion event (triggering
timer, extra digit)
 - removed section 7.3 -- original content covered in Annex L and earlier in
document
 - protocol version is 2
 - Initial ServiceChange for association always uses version 1 format
 - new sections on profiles
 - corrected examples in Appendix.
 
Taking particular note of changes to digit map operation, Brian Rosen
suggested that Megaco and SG 16 should try to prevent needless divergence
between Megaco/H.248 and MGCP.

4. Control Associations
   ====================

Tom Taylor presented a series of charts concerning control association
states and the use of ServiceChange.  These were provided in the hopes of
continuing the work begun by
draft-hss-megaco-control-association-state-machine-00.txt

At the outset, the proposal that states should be analyzed separately from
the MG and MGC points of view rather than considering a joint association
state met with some agreement.  It was also agreed that a hot switchover is
by definition transparent to the peer and preserves all transactions in
progress, while a warm switchover or reboot results in a Stale state as
defined in the charts.

Tom made the point that it is important for the MGC to know what state an MG
registering with it is in when it registers.  He pointed out that the
existing specification generally does not indicate what ServiceChangeReason
to use when reestablishing a control session, and suggested that this
property is therefore available to indicate the MG's state.  He proposed
that where not otherwise specified the MG use 901 Cold Boot to indicate that
the MG was in Initialized state as defined in the charts, and 902 Warm Boot
to indicate that the MG was in Stale state.

On the MGC side, there is not the same necessity to indicate state to the
peer.

The analysis shown in the charts is incomplete, but it turned out that the
charts provided too much technical detail for the audience to comment upon
and work with on the spot.  It was agreed to adjourn the meeting early
rather than continue in design session.  [Guess I've learned my lesson --
apologies for not making the material available well in advance of the
meeting. PTT]
 
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  Mon Apr  1 09:09: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 IAA23943
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 08:09:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA08319
	for megaco-archive@odin.ietf.org; Mon, 1 Apr 2002 08:09: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 HAA06873;
	Mon, 1 Apr 2002 07:38: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 HAA06830
	for <megaco@optimus.ietf.org>; Mon, 1 Apr 2002 07:38:09 -0500 (EST)
Received: from mxout2.netvision.net.il (mxout2.netvision.net.il [194.90.9.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23318
	for <megaco@ietf.org>; Mon, 1 Apr 2002 07:37:44 -0500 (EST)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout2.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GTW00M7I31LMD@mxout2.netvision.net.il> for megaco@ietf.org;
 Mon, 01 Apr 2002 15:36:57 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <HWZPZ6DZ>; Mon, 01 Apr 2002 15:35:47 +0300
Content-return: allowed
Date: Mon, 01 Apr 2002 15:35:47 +0300
From: Dan Elbert <delbert@radvision.com>
Subject: RE: [Megaco] Megaco 53 Minutes
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B018BBF4A@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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
I don't see in the list of changes for v2 the ability to specifiy topology
per stream.

Dan Elbert
RADVISION

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, March 28, 2002 12:32 AM
To: 'megaco@ietf.org'
Cc: 'Scott Bradner'; 'Allison Mankin'
Subject: [Megaco] Megaco 53 Minutes


Draft Megaco minutes, reported by Tom Taylor.
The charts presented at this meeting are available at
ftp://standards.nortelnetworks.com/megaco/docs/Current/IETF/Megaco53

The Megaco Working Group met Wednesday afternoon from 3:00 to 4:30.  Tom
Taylor <taylor@nortelnetworks.com> chaired.  40 people attended.

1. Agenda
   ======

Accepted without change.

2. Review of new charter, potential new work items
   ===============================================

Tom Taylor presented charts summarizing the new Megaco charter.  The key
point is that the Working Group can only work on enhancing the base
protocol, in cooperation with SG 16.  The Megaco E-mail list does NOT face a
similar constraint, so we can continue new package work and the like there.
We currently have three work items besides H.248v2:
 - a naming patterns package
 - the Megaco MIB
 - an Informational call flows document.

A brief discussion of other possible work items ensued.  Brian Rosen
<brian.rosen@marconi.com> mentioned that he had had requests to resubmit his
draft on packages for ATM.  The Chair noted that others had made submissions
or planned to do so on this topic.  Nevertheless, it seemed doubtful that
the IESG would interpret this work as falling within the scope of the new
charter.  He promised to discuss the matter with Scott Bradner.

Christer Holmberg <christer.holmberg@lmf.ericsson.se> brought up two work
items.  One was to define changes needed to negotiate the use of SDPng
rather than SDP.  He remarked that it was not desirable to indicate SDPng
support through choice of transport address, since this could multiply the
number of ports used.  The other work item is to define SDP for various
transports beyond IP and ATM.

3. Review of SG 16 Results
   =======================

Tom Taylor presented a chart summarizing the outlook for work at Study Group
16.  The three major points covered were the probability of an H.248v3 at
the next full Study Group meeting in October, changes in management of
Question 3/16, and the renumbering of H.248 and its Annexes.  Tom paid
tribute to Glen Freundlich, whose determination had undoubtedly reduced the
time until issuance of H.248v1 by at least half a year.  He explained that
The H.248.x series was being created so that the Annexes could be versioned
independently of the main protocol specification.

Kevin McCandless <KMcCandless@Illuminet.com> expressed his concern about
continued creation of new versions of H.248.  There should not be any more
version of H.248 developed until implementation experience is gained and the
data from that experience is analyzed.  Succeeding versions should be
backwards compatible.  Finally, on the editorial level, each new draft
version of H.248 should separately list the corrections to the previous
version and the new enhancements added.  After several additional comments
from other meeting participants, it was agreed that the Chair would send a
message to SG 16 conveying the Megaco Working Group's strong concern that
the ITU-T not move ahead with further versions until we get deployment
experience.

Tom's presentation also included charts showing the changes to H.248 made at
the Geneva meeting.  These were separated into changes affecting both v1 and
v2, and changes affecting v2 only.  Tom highlighted the largest changes,
most of which had been passed to the Megaco E-mail list for comment before
final approval.

The largest changes affecting both v1 and v2 included
 - modification of the definition of BR signals to make duration irrelevant
 - addition of text in Modify, Subtract, and Move on side-effects of
Multiplex Descriptors, consistent with the text in Add
 - clarification of the effect of omitting a descriptor and individual
properties from a command
 - retention of the restriction that a single session description within a
Local or Remote Descriptor contain no more than one m= line
 - adding the ability to disable the start timer in a digit map by setting
it to 0; applicable to the case where it is necessary to listen for new
tones throughout a call
 - clarification of the disposition of outstanding replies during switchover
 - the idea that when a parameter or property is unspecified the default may
be a specified value or it may be a different behaviour, such as not
executing a procedure in which that parameter or property is used
 - extension of the scope of the TDM package in Annex E to apply also to
non-TDM transport (e.g. ATM AAL 2).

The list of changes affecting v2 only included both changes presented at
IETF 52 and new changes introduced as a result of work in Dublin and in
Geneva itself.  The post-IETF-52 changes include:
 - deprecation of the Modem Descriptor; an appropriate SDP/Annex C attribute
should be used instead
 - Nx64K multiplex type added and described
 - added ability for duration of long tones (Z qualifier) to be overridden
in the digit map
 - added digit buffering after the digit map completion event has completed
 - can have more parameters for digit map completion event (triggering
timer, extra digit)
 - removed section 7.3 -- original content covered in Annex L and earlier in
document
 - protocol version is 2
 - Initial ServiceChange for association always uses version 1 format
 - new sections on profiles
 - corrected examples in Appendix.
 
Taking particular note of changes to digit map operation, Brian Rosen
suggested that Megaco and SG 16 should try to prevent needless divergence
between Megaco/H.248 and MGCP.

4. Control Associations
   ====================

Tom Taylor presented a series of charts concerning control association
states and the use of ServiceChange.  These were provided in the hopes of
continuing the work begun by
draft-hss-megaco-control-association-state-machine-00.txt

At the outset, the proposal that states should be analyzed separately from
the MG and MGC points of view rather than considering a joint association
state met with some agreement.  It was also agreed that a hot switchover is
by definition transparent to the peer and preserves all transactions in
progress, while a warm switchover or reboot results in a Stale state as
defined in the charts.

Tom made the point that it is important for the MGC to know what state an MG
registering with it is in when it registers.  He pointed out that the
existing specification generally does not indicate what ServiceChangeReason
to use when reestablishing a control session, and suggested that this
property is therefore available to indicate the MG's state.  He proposed
that where not otherwise specified the MG use 901 Cold Boot to indicate that
the MG was in Initialized state as defined in the charts, and 902 Warm Boot
to indicate that the MG was in Stale state.

On the MGC side, there is not the same necessity to indicate state to the
peer.

The analysis shown in the charts is incomplete, but it turned out that the
charts provided too much technical detail for the audience to comment upon
and work with on the spot.  It was agreed to adjourn the meeting early
rather than continue in design session.  [Guess I've learned my lesson --
apologies for not making the material available well in advance of the
meeting. PTT]
 
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  Mon Apr  1 09:23: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 IAA25046
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 08:33:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA09795
	for megaco-archive@odin.ietf.org; Mon, 1 Apr 2002 08:33: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 IAA08431;
	Mon, 1 Apr 2002 08:11: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 AAA02310
	for <megaco@optimus.ietf.org>; Mon, 1 Apr 2002 00:49:06 -0500 (EST)
Received: from epygilab.am (araler.epygilab.am [195.151.94.74])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08149
	for <megaco@ietf.org>; Mon, 1 Apr 2002 00:48:53 -0500 (EST)
Received: (apparently) from epygilab.am ([192.168.0.156]) by epygilab.am  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Mon, 1 Apr 2002 09:48:50 +0400
Received: from epygilab.am [192.168.0.32]
	by epygilab.am [192.168.0.156]
	with SMTP (MDaemon.PRO.v5.0.1.R)
	for <megaco@ietf.org>; Mon, 01 Apr 2002 10:47:44 +0500
Message-ID: <3CA8026F.88A92E05@epygilab.am>
Date: Mon, 01 Apr 2002 10:47:11 +0400
From: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: Megaco <megaco@ietf.org>
Subject: Re: [MEGACO] what does list of signals mean?
References: <3CA16702.CC6CB0D4@epygilab.am> <3CA1F936.EDB6B299@lucent.com> <3CA2ED4A.E50A98DB@epygilab.am> <3CA4A166.46829717@lucent.com>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
X-MDRemoteIP: 192.168.0.32
X-Return-Path: Narine.Mossikyan@epygilab.am
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

It is indicated SigID=cg/rt in your sample, in this case cg signal's rt parameter
is simple. My question is if  I have SigID=pt/tl, where tl is tone id list, should
I enumerate tl's parameters too, or not? I mean will the syntax of SigID=pt/tl  be
correct if I will  not use  tl tone list parameters?

thanks for your advice
P.S. "sit" is not a parameter of "g" event. How could you explain the meaning of
g/sit you used in your sample?


Terry L Anderson wrote:

> An example would be
> End of a signal, say an ringtone
>     ObservedEvents = 2345 {20010329T11501000:g/sit{SigID=cg/rt, Meth=TO,
> SLID=NotInServiceAnnouncement}}
> If the signal had been part of a signal list, then the signal list ID is also
> returned as shown, otherwise it would be omitted.
>
> For example, if the signal was started by a signals descriptor like:
> Signals { SignalList = NotInServiceAnnouncement {
>     cg/sit {NotifyCompletion={TimeOut,IntByEvent,OtherReason}},
>     an/apf {an=NotInService, av=English, NotifyCompletion={TimeOut, IntByEvent,
> OtherReason}},
> }}
>
> End of the sit tone would be notified as above.
>
> Narine_Mossikyan wrote:
>
> > Hi ,
> > Thanks for your quick response.
> > I still don't  understand what does observedEventsDescriptor's last parameter
> > mean? Can you give me some examples of observedEventsDescriptor?
> > thanks a lot for your help
> >
> > Terry L Anderson wrote:
> >
> > > The original text was ambiguous and was recently amended to clarify this
> > > parameter.  The change first appeared in the Implementors Guide but was
> > > included in H.248v1 Corrigendum 1 and H.248v2 as consented in Geneva Feb
> > > 2002.  Here is the current text:
> > >
> > > ObservedEvents Descriptor parameters:
> > > Signal Identity
> > > ParameterID:  SigID (0x0001)
> > > This parameter identifies the signal which has terminated. For a signal
> > > that is contained in a signal list the signal list identity parameter
> > > should also be returned indicating the appropriate list.
> > > Type: Binary: octet (string), Text: string
> > > Possible values: a signal which has terminated.  A signal shall be
> > > identified using the pkgdName syntax without wildcarding.
> > >
> > > Narine_Mossikyan wrote:
> > >
> > > > Hi,
> > > > I found the list of signals on the page#139,  RFC 3015 Megaco Protocol
> > > > Version 1.0,  November 2000 , in Section Generic packages , E.1.2.
> > > > Events .
> > > > ObservedEvents Descriptor parameters:
> > > >         Signal Identity
> > > >         ParameterID:  SigID (0x0001)
> > > >         This parameter identifies the signals which have terminated.
> > > >         Type: list
> > > > My question is:
> > > > Should I implement  list of  signals as it is describe in the same RFC,
> > > > page #107 ?
> > > >         signalList           = SignalListToken EQUAL signalListId LBRKT
> > > >                           signalListParm *(COMMA signalListParm) RBRKT
> > > > or the list of signals in ObservedEvents has another meaning?
> > > > thanks for your help
> > > >
> > > > _______________________________________________
> > > > Megaco mailing list
> > > > Megaco@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/megaco
> > >
> > > --
> > >
> > > ------------------------------------------------------------
> > > Terry L Anderson             mailto:tla@lucent.com
> > > Tel:732.949.5628   Fax:732.949.7016
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson             mailto:tla@lucent.com
> Tel:732.949.5628   Fax:732.949.7016
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> 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  Mon Apr  1 10:17: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 KAA01159
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 10:17: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 JAA13637;
	Mon, 1 Apr 2002 09:55: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 JAA13599
	for <megaco@ns.ietf.org>; Mon, 1 Apr 2002 09:55:05 -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 JAA00147
	for <megaco@ietf.org>; Mon, 1 Apr 2002 09:55:03 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g31EsYV10866;
	Mon, 1 Apr 2002 09:54:34 -0500 (EST)
Received: from lucent.com (tla.lra.lucent.com [192.11.63.84])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA00898;
	Mon, 1 Apr 2002 09:55:15 -0500 (EST)
Message-ID: <3CA87493.1584E7D3@lucent.com>
Date: Mon, 01 Apr 2002 09:54:11 -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: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
CC: Megaco <megaco@ietf.org>
Subject: Re: [MEGACO] what does list of signals mean?
References: <3CA16702.CC6CB0D4@epygilab.am> <3CA1F936.EDB6B299@lucent.com> <3CA2ED4A.E50A98DB@epygilab.am> <3CA4A166.46829717@lucent.com> <3CA8026F.88A92E05@epygilab.am>
Content-Type: multipart/mixed;
 boundary="------------47C62E53E769E6543BD013BB"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------47C62E53E769E6543BD013BB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Narine_Mossikyan wrote:

> It is indicated SigID=cg/rt in your sample, in this case cg signal's rt parameter
> is simple. My question is if  I have SigID=pt/tl, where tl is tone id list, should
> I enumerate tl's parameters too, or not? I mean will the syntax of SigID=pt/tl  be
> correct if I will  not use  tl tone list parameters?

We currently have a way to indicate the name of a signal that completed but not the
name of a parameter to that signal.  That would not seem to be a problem when only one
instance of a given signal is active (even if it has a parameter).  In your example, I
don't think there is a problem as a signal
    Signals{tonegen/pt{tl=2,4,6}}
has only one "signal".  That signal is a sequence of tones, but is one signal and so
completion will be notified only after the entire signal (all tones in sequence) are
complete).

But if more than one instance of a signal with varying parameter values are active
there is currently no way to indicate which completed.  That is, if the signal were:
    Signals{
    tonegen/pt{tl=1{Duration=1 } },
    tonegen/pt{tl=3{Duration=2 } }
    }    ; play 1 and 3 simultaneously
There would be no way to indicate in a notify which one completed.  Of course it would
be more usual to play single DTMF tones using the distinct events rather than
tonegen/pt.  If one played the above as
    Signals{
    dg/d1{Duration=1},
    dg/d3{Duration=2}
}
There would be no problem.  However, there may well be useful cases where more than
one instance of a given named signal (with distinct parameter values) is played
simultaneously.  Do folks think we need a way to notify which completed?

> thanks for your advice
> P.S. "sit" is not a parameter of "g" event. How could you explain the meaning of
> g/sit you used in your sample?

I'm sorry, I mistyped.  I meant g/sc event in ObservedEvents.  I did use cg/sit
further down, but did not mean 'sit' in the ObservedEvents.

> Terry L Anderson wrote:
>
> > An example would be
> > End of a signal, say an ringtone
> >     ObservedEvents = 2345 {20010329T11501000:g/sit{SigID=cg/rt, Meth=TO,
> > SLID=NotInServiceAnnouncement}}
> > If the signal had been part of a signal list, then the signal list ID is also
> > returned as shown, otherwise it would be omitted.
> >
> > For example, if the signal was started by a signals descriptor like:
> > Signals { SignalList = NotInServiceAnnouncement {
> >     cg/sit {NotifyCompletion={TimeOut,IntByEvent,OtherReason}},
> >     an/apf {an=NotInService, av=English, NotifyCompletion={TimeOut, IntByEvent,
> > OtherReason}},
> > }}
> >
> > End of the sit tone would be notified as above.
> >
> > Narine_Mossikyan wrote:
> >
> > > Hi ,
> > > Thanks for your quick response.
> > > I still don't  understand what does observedEventsDescriptor's last parameter
> > > mean? Can you give me some examples of observedEventsDescriptor?
> > > thanks a lot for your help
> > >
> > > Terry L Anderson wrote:
> > >
> > > > The original text was ambiguous and was recently amended to clarify this
> > > > parameter.  The change first appeared in the Implementors Guide but was
> > > > included in H.248v1 Corrigendum 1 and H.248v2 as consented in Geneva Feb
> > > > 2002.  Here is the current text:
> > > >
> > > > ObservedEvents Descriptor parameters:
> > > > Signal Identity
> > > > ParameterID:  SigID (0x0001)
> > > > This parameter identifies the signal which has terminated. For a signal
> > > > that is contained in a signal list the signal list identity parameter
> > > > should also be returned indicating the appropriate list.
> > > > Type: Binary: octet (string), Text: string
> > > > Possible values: a signal which has terminated.  A signal shall be
> > > > identified using the pkgdName syntax without wildcarding.
> > > >
> > > > Narine_Mossikyan wrote:
> > > >
> > > > > Hi,
> > > > > I found the list of signals on the page#139,  RFC 3015 Megaco Protocol
> > > > > Version 1.0,  November 2000 , in Section Generic packages , E.1.2.
> > > > > Events .
> > > > > ObservedEvents Descriptor parameters:
> > > > >         Signal Identity
> > > > >         ParameterID:  SigID (0x0001)
> > > > >         This parameter identifies the signals which have terminated.
> > > > >         Type: list
> > > > > My question is:
> > > > > Should I implement  list of  signals as it is describe in the same RFC,
> > > > > page #107 ?
> > > > >         signalList           = SignalListToken EQUAL signalListId LBRKT
> > > > >                           signalListParm *(COMMA signalListParm) RBRKT
> > > > > or the list of signals in ObservedEvents has another meaning?
> > > > > thanks for your help
> > > > >
> > > > > _______________________________________________
> > > > > Megaco mailing list
> > > > > Megaco@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/megaco
> > > >
> > > > --
> > > >
> > > > ------------------------------------------------------------
> > > > Terry L Anderson             mailto:tla@lucent.com
> > > > Tel:732.949.5628   Fax:732.949.7016
> > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson             mailto:tla@lucent.com
> > Tel:732.949.5628   Fax:732.949.7016
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------47C62E53E769E6543BD013BB
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------47C62E53E769E6543BD013BB--


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


From daemon@ns.ietf.org  Mon Apr  1 10:17: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 KAA01170
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 10:17:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA15025
	for megaco-archive@odin.ietf.org; Mon, 1 Apr 2002 10:17: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 JAA13637;
	Mon, 1 Apr 2002 09:55: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 JAA13599
	for <megaco@ns.ietf.org>; Mon, 1 Apr 2002 09:55:05 -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 JAA00147
	for <megaco@ietf.org>; Mon, 1 Apr 2002 09:55:03 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g31EsYV10866;
	Mon, 1 Apr 2002 09:54:34 -0500 (EST)
Received: from lucent.com (tla.lra.lucent.com [192.11.63.84])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA00898;
	Mon, 1 Apr 2002 09:55:15 -0500 (EST)
Message-ID: <3CA87493.1584E7D3@lucent.com>
Date: Mon, 01 Apr 2002 09:54:11 -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: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
CC: Megaco <megaco@ietf.org>
Subject: Re: [MEGACO] what does list of signals mean?
References: <3CA16702.CC6CB0D4@epygilab.am> <3CA1F936.EDB6B299@lucent.com> <3CA2ED4A.E50A98DB@epygilab.am> <3CA4A166.46829717@lucent.com> <3CA8026F.88A92E05@epygilab.am>
Content-Type: multipart/mixed;
 boundary="------------47C62E53E769E6543BD013BB"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------47C62E53E769E6543BD013BB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Narine_Mossikyan wrote:

> It is indicated SigID=cg/rt in your sample, in this case cg signal's rt parameter
> is simple. My question is if  I have SigID=pt/tl, where tl is tone id list, should
> I enumerate tl's parameters too, or not? I mean will the syntax of SigID=pt/tl  be
> correct if I will  not use  tl tone list parameters?

We currently have a way to indicate the name of a signal that completed but not the
name of a parameter to that signal.  That would not seem to be a problem when only one
instance of a given signal is active (even if it has a parameter).  In your example, I
don't think there is a problem as a signal
    Signals{tonegen/pt{tl=2,4,6}}
has only one "signal".  That signal is a sequence of tones, but is one signal and so
completion will be notified only after the entire signal (all tones in sequence) are
complete).

But if more than one instance of a signal with varying parameter values are active
there is currently no way to indicate which completed.  That is, if the signal were:
    Signals{
    tonegen/pt{tl=1{Duration=1 } },
    tonegen/pt{tl=3{Duration=2 } }
    }    ; play 1 and 3 simultaneously
There would be no way to indicate in a notify which one completed.  Of course it would
be more usual to play single DTMF tones using the distinct events rather than
tonegen/pt.  If one played the above as
    Signals{
    dg/d1{Duration=1},
    dg/d3{Duration=2}
}
There would be no problem.  However, there may well be useful cases where more than
one instance of a given named signal (with distinct parameter values) is played
simultaneously.  Do folks think we need a way to notify which completed?

> thanks for your advice
> P.S. "sit" is not a parameter of "g" event. How could you explain the meaning of
> g/sit you used in your sample?

I'm sorry, I mistyped.  I meant g/sc event in ObservedEvents.  I did use cg/sit
further down, but did not mean 'sit' in the ObservedEvents.

> Terry L Anderson wrote:
>
> > An example would be
> > End of a signal, say an ringtone
> >     ObservedEvents = 2345 {20010329T11501000:g/sit{SigID=cg/rt, Meth=TO,
> > SLID=NotInServiceAnnouncement}}
> > If the signal had been part of a signal list, then the signal list ID is also
> > returned as shown, otherwise it would be omitted.
> >
> > For example, if the signal was started by a signals descriptor like:
> > Signals { SignalList = NotInServiceAnnouncement {
> >     cg/sit {NotifyCompletion={TimeOut,IntByEvent,OtherReason}},
> >     an/apf {an=NotInService, av=English, NotifyCompletion={TimeOut, IntByEvent,
> > OtherReason}},
> > }}
> >
> > End of the sit tone would be notified as above.
> >
> > Narine_Mossikyan wrote:
> >
> > > Hi ,
> > > Thanks for your quick response.
> > > I still don't  understand what does observedEventsDescriptor's last parameter
> > > mean? Can you give me some examples of observedEventsDescriptor?
> > > thanks a lot for your help
> > >
> > > Terry L Anderson wrote:
> > >
> > > > The original text was ambiguous and was recently amended to clarify this
> > > > parameter.  The change first appeared in the Implementors Guide but was
> > > > included in H.248v1 Corrigendum 1 and H.248v2 as consented in Geneva Feb
> > > > 2002.  Here is the current text:
> > > >
> > > > ObservedEvents Descriptor parameters:
> > > > Signal Identity
> > > > ParameterID:  SigID (0x0001)
> > > > This parameter identifies the signal which has terminated. For a signal
> > > > that is contained in a signal list the signal list identity parameter
> > > > should also be returned indicating the appropriate list.
> > > > Type: Binary: octet (string), Text: string
> > > > Possible values: a signal which has terminated.  A signal shall be
> > > > identified using the pkgdName syntax without wildcarding.
> > > >
> > > > Narine_Mossikyan wrote:
> > > >
> > > > > Hi,
> > > > > I found the list of signals on the page#139,  RFC 3015 Megaco Protocol
> > > > > Version 1.0,  November 2000 , in Section Generic packages , E.1.2.
> > > > > Events .
> > > > > ObservedEvents Descriptor parameters:
> > > > >         Signal Identity
> > > > >         ParameterID:  SigID (0x0001)
> > > > >         This parameter identifies the signals which have terminated.
> > > > >         Type: list
> > > > > My question is:
> > > > > Should I implement  list of  signals as it is describe in the same RFC,
> > > > > page #107 ?
> > > > >         signalList           = SignalListToken EQUAL signalListId LBRKT
> > > > >                           signalListParm *(COMMA signalListParm) RBRKT
> > > > > or the list of signals in ObservedEvents has another meaning?
> > > > > thanks for your help
> > > > >
> > > > > _______________________________________________
> > > > > Megaco mailing list
> > > > > Megaco@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/megaco
> > > >
> > > > --
> > > >
> > > > ------------------------------------------------------------
> > > > Terry L Anderson             mailto:tla@lucent.com
> > > > Tel:732.949.5628   Fax:732.949.7016
> > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson             mailto:tla@lucent.com
> > Tel:732.949.5628   Fax:732.949.7016
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------47C62E53E769E6543BD013BB
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------47C62E53E769E6543BD013BB--


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



From megaco-admin@ietf.org  Mon Apr  1 11:13: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 LAA03191
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 11: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 KAA17328;
	Mon, 1 Apr 2002 10:55: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 KAA17297
	for <megaco@ns.ietf.org>; Mon, 1 Apr 2002 10:55:43 -0500 (EST)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02507
	for <megaco@ietf.org>; Mon, 1 Apr 2002 10:55:40 -0500 (EST)
Received: from visio ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GTWC4X01.7GA for
          <megaco@ietf.org>; Mon, 1 Apr 2002 23:53:21 +0800 
Message-ID: <001501c1d995$a72d4180$d5190b0a@huawei.com>
From: "Suman Choudhary" <sumanc@huawei.com>
To: <megaco@ietf.org>
Date: Mon, 1 Apr 2002 23:55:31 +0800
Organization: Huawei Technologies
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0012_01C1D9D8.B5381780"
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
Subject: [Megaco] A small query
Sender: megaco-admin@ietf.org
Errors-To: 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_0012_01C1D9D8.B5381780
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,

What is meaning of the below statement as stated in RFC3015
"Multiple signals and sequential signal lists in the same =
SignalsDescriptor shall be played simultaneously."

How can multiple signals be played simultaneously ???

Regards

Suman


------=_NextPart_000_0012_01C1D9D8.B5381780
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.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>What is meaning of the below statement =
as stated in=20
RFC3015</FONT></DIV>
<DIV><FONT size=3D2>
<P>"Multiple signals and sequential signal lists in the same =
SignalsDescriptor=20
shall be played simultaneously."</P>
<P>How can multiple signals be played simultaneously ???</P>
<P><FONT face=3DArial>Regards</FONT></P>
<P><FONT =
face=3DArial>Suman</FONT></P></FONT></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0012_01C1D9D8.B5381780--


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


From daemon@ns.ietf.org  Mon Apr  1 11:13: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 LAA03202
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 11:13:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA18819
	for megaco-archive@odin.ietf.org; Mon, 1 Apr 2002 11:13: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 KAA17328;
	Mon, 1 Apr 2002 10:55: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 KAA17297
	for <megaco@ns.ietf.org>; Mon, 1 Apr 2002 10:55:43 -0500 (EST)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02507
	for <megaco@ietf.org>; Mon, 1 Apr 2002 10:55:40 -0500 (EST)
Received: from visio ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GTWC4X01.7GA for
          <megaco@ietf.org>; Mon, 1 Apr 2002 23:53:21 +0800 
Message-ID: <001501c1d995$a72d4180$d5190b0a@huawei.com>
From: "Suman Choudhary" <sumanc@huawei.com>
To: <megaco@ietf.org>
Date: Mon, 1 Apr 2002 23:55:31 +0800
Organization: Huawei Technologies
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0012_01C1D9D8.B5381780"
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
Subject: [Megaco] A small query
Sender: megaco-admin@ietf.org
Errors-To: 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_0012_01C1D9D8.B5381780
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,

What is meaning of the below statement as stated in RFC3015
"Multiple signals and sequential signal lists in the same =
SignalsDescriptor shall be played simultaneously."

How can multiple signals be played simultaneously ???

Regards

Suman


------=_NextPart_000_0012_01C1D9D8.B5381780
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.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>What is meaning of the below statement =
as stated in=20
RFC3015</FONT></DIV>
<DIV><FONT size=3D2>
<P>"Multiple signals and sequential signal lists in the same =
SignalsDescriptor=20
shall be played simultaneously."</P>
<P>How can multiple signals be played simultaneously ???</P>
<P><FONT face=3DArial>Regards</FONT></P>
<P><FONT =
face=3DArial>Suman</FONT></P></FONT></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0012_01C1D9D8.B5381780--


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



From megaco-admin@ietf.org  Mon Apr  1 11: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 LAA04416
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 11: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 LAA19427;
	Mon, 1 Apr 2002 11: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 LAA19402
	for <megaco@ns.ietf.org>; Mon, 1 Apr 2002 11:24:01 -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 LAA03645
	for <megaco@ietf.org>; Mon, 1 Apr 2002 11:23:58 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g31GNUd26960;
	Mon, 1 Apr 2002 11:23:30 -0500 (EST)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA05012;
	Mon, 1 Apr 2002 11:24:14 -0500 (EST)
Message-ID: <3CA88988.51036971@lucent.com>
Date: Mon, 01 Apr 2002 11:23:36 -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: Suman Choudhary <sumanc@huawei.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] A small query
References: <001501c1d995$a72d4180$d5190b0a@huawei.com>
Content-Type: multipart/mixed;
 boundary="------------048E6841BEF3B788393198E9"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------048E6841BEF3B788393198E9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Simultaneous signals might require mixing the data for output.  If this
is not the desired behavior MGC should use a sequential signal list.
There may be times, however, when simultaneous signals are desired and
so this is permitted.  Also some signals have directionality and so it
may well be desired to play one signal outward and another inward
simultaneously.

Suman Choudhary wrote:

> Hi All, What is meaning of the below statement as stated in
> RFC3015"Multiple signals and sequential signal lists in the same
> SignalsDescriptor shall be played simultaneously."
>
> How can multiple signals be played simultaneously ???
>
> Regards
>
> Suman

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------048E6841BEF3B788393198E9
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------048E6841BEF3B788393198E9--


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


From daemon@ns.ietf.org  Mon Apr  1 11: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 LAA04429
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 11:45:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA21025
	for megaco-archive@odin.ietf.org; Mon, 1 Apr 2002 11:45: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 LAA19427;
	Mon, 1 Apr 2002 11: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 LAA19402
	for <megaco@ns.ietf.org>; Mon, 1 Apr 2002 11:24:01 -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 LAA03645
	for <megaco@ietf.org>; Mon, 1 Apr 2002 11:23:58 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by hoemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g31GNUd26960;
	Mon, 1 Apr 2002 11:23:30 -0500 (EST)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA05012;
	Mon, 1 Apr 2002 11:24:14 -0500 (EST)
Message-ID: <3CA88988.51036971@lucent.com>
Date: Mon, 01 Apr 2002 11:23:36 -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: Suman Choudhary <sumanc@huawei.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] A small query
References: <001501c1d995$a72d4180$d5190b0a@huawei.com>
Content-Type: multipart/mixed;
 boundary="------------048E6841BEF3B788393198E9"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------048E6841BEF3B788393198E9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Simultaneous signals might require mixing the data for output.  If this
is not the desired behavior MGC should use a sequential signal list.
There may be times, however, when simultaneous signals are desired and
so this is permitted.  Also some signals have directionality and so it
may well be desired to play one signal outward and another inward
simultaneously.

Suman Choudhary wrote:

> Hi All, What is meaning of the below statement as stated in
> RFC3015"Multiple signals and sequential signal lists in the same
> SignalsDescriptor shall be played simultaneously."
>
> How can multiple signals be played simultaneously ???
>
> Regards
>
> Suman

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------048E6841BEF3B788393198E9
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------048E6841BEF3B788393198E9--


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



From megaco-admin@ietf.org  Mon Apr  1 12: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 MAA07842
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 12: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 MAA25626;
	Mon, 1 Apr 2002 12:37: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 MAA25596
	for <megaco@ns.ietf.org>; Mon, 1 Apr 2002 12:37:29 -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 MAA07016
	for <megaco@ietf.org>; Mon, 1 Apr 2002 12:37:26 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g31Hara25218
	for <megaco@ietf.org>; Mon, 1 Apr 2002 12:36:53 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g31HapU14131
	for <megaco@ietf.org>; Mon, 1 Apr 2002 12:36: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 g31Haok29741
	for <megaco@ietf.org>; Mon, 1 Apr 2002 12:36:51 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K9VZA>; Mon, 1 Apr 2002 12:36:50 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A21E@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Terry L Anderson'" <tla@lucent.com>,
        Suman Choudhary
	 <sumanc@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] A small query
Date: Mon, 1 Apr 2002 12:36: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

When we originally developed this capability, one example given was that of
playing an announcement superimposed on busy tone, where, for example, the
announcement would offer to deliver a message.

-----Original Message-----
From: Terry L Anderson [mailto:tla@lucent.com]
Sent: Monday, April 01, 2002 11:24 AM
To: Suman Choudhary
Cc: megaco@ietf.org
Subject: Re: [Megaco] A small query


Simultaneous signals might require mixing the data for output.  If this
is not the desired behavior MGC should use a sequential signal list.
There may be times, however, when simultaneous signals are desired and
so this is permitted.  Also some signals have directionality and so it
may well be desired to play one signal outward and another inward
simultaneously.

Suman Choudhary wrote:

> Hi All, What is meaning of the below statement as stated in
> RFC3015"Multiple signals and sequential signal lists in the same
> SignalsDescriptor shall be played simultaneously."
>
> How can multiple signals be played simultaneously ???
>
> Regards
>
> Suman

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
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  Mon Apr  1 12: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 MAA07853
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 12:54:16 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA26823
	for megaco-archive@odin.ietf.org; Mon, 1 Apr 2002 12: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 MAA25626;
	Mon, 1 Apr 2002 12:37: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 MAA25596
	for <megaco@ns.ietf.org>; Mon, 1 Apr 2002 12:37:29 -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 MAA07016
	for <megaco@ietf.org>; Mon, 1 Apr 2002 12:37:26 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g31Hara25218
	for <megaco@ietf.org>; Mon, 1 Apr 2002 12:36:53 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g31HapU14131
	for <megaco@ietf.org>; Mon, 1 Apr 2002 12:36: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 g31Haok29741
	for <megaco@ietf.org>; Mon, 1 Apr 2002 12:36:51 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K9VZA>; Mon, 1 Apr 2002 12:36:50 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A21E@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Terry L Anderson'" <tla@lucent.com>,
        Suman Choudhary
	 <sumanc@huawei.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] A small query
Date: Mon, 1 Apr 2002 12:36: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

When we originally developed this capability, one example given was that of
playing an announcement superimposed on busy tone, where, for example, the
announcement would offer to deliver a message.

-----Original Message-----
From: Terry L Anderson [mailto:tla@lucent.com]
Sent: Monday, April 01, 2002 11:24 AM
To: Suman Choudhary
Cc: megaco@ietf.org
Subject: Re: [Megaco] A small query


Simultaneous signals might require mixing the data for output.  If this
is not the desired behavior MGC should use a sequential signal list.
There may be times, however, when simultaneous signals are desired and
so this is permitted.  Also some signals have directionality and so it
may well be desired to play one signal outward and another inward
simultaneously.

Suman Choudhary wrote:

> Hi All, What is meaning of the below statement as stated in
> RFC3015"Multiple signals and sequential signal lists in the same
> SignalsDescriptor shall be played simultaneously."
>
> How can multiple signals be played simultaneously ???
>
> Regards
>
> Suman

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
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  Mon Apr  1 13:04: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 NAA08369
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 13:04: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 MAA26075;
	Mon, 1 Apr 2002 12:43: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 MAA26039
	for <megaco@ns.ietf.org>; Mon, 1 Apr 2002 12:43:05 -0500 (EST)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07308
	for <megaco@ietf.org>; Mon, 1 Apr 2002 12:43:01 -0500 (EST)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id MAA17886;
	Mon, 1 Apr 2002 12:42:00 -0500 (EST)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2ACALZBC>; Mon, 1 Apr 2002 12:41:59 -0500
Message-ID: <29B5A21C13C8D51190F900805F65B4EC239F82@rndex50.ottawa.mitel.com>
From: "Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM>
To: "'vbajaj@hss.hns.com'" <vbajaj@hss.hns.com>,
        Tom-PT Taylor
	 <taylor@nortelnetworks.com>
Cc: "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
        megaco@ietf.org
Subject: RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00.
	 txt
Date: Mon, 1 Apr 2002 12:41:58 -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 agree this should be a WG item, one way or another -- separate doc or folded in to main protocol, perhaps updates to base protocol doc + an Informational doc.  Its important to correct interop and affects basic use of the protocol.  

Don't think this should be a large task however.  If it gets too large we have likely made it too complicated, and I just don't think it really need to be.  

My $0.02. 
-- Peter Blatherwick

-----Original Message-----
From: vbajaj@hss.hns.com [mailto:vbajaj@hss.hns.com]
Sent: March 31, 2002 23:46
To: Tom-PT Taylor
Cc: 'Jean-Luc.Lecuyer@alcatel.fr'; megaco@ietf.org
Subject: RE: [Megaco] Status of
draft-hss-megaco-control-state-machine-00. txt




Tom,
        I think it is absolutely necessary to take this activity as a WG work
item. This area needs
  to be addressed to avoid interoperability issues later.

Rgds,

Vikas Bajaj





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 03/29/2002 09:22:32 PM

To:   "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
      megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00. txt




Could I have opinions from the WG on whether we should be producing a
document on control associations and the signalling associated with control
state transitions as a WG work item?  I assume the work would be Standards
Track because it would specify normative behaviour on the signalling side.
As an alternative, if the impact on the base specification wouldn't be too
large, we could simply add the conclusions to the Implementor's Guide.

-----Original Message-----
From: Jean-Luc.Lecuyer@alcatel.fr [mailto:Jean-Luc.Lecuyer@alcatel.fr]
Sent: Friday, March 29, 2002 4:11 AM
To: megaco@ietf.org
Subject: [Megaco] Status of
draft-hss-megaco-control-state-machine-00.txt




What is the status of the document
"draft-hss-megaco-control-state-machine-00.txt"
which expired in February ?

Thank-you
Jean-Luc
----------------------------------------------------------------------------
----------------
Jean-Luc.Lecuyer :         VND/E10 VS  BU R&D//CCPD Lannion
Full telephone number :                                         33 (0)2 96
04 77 09
Full fax number :                                                        33
(0)2 96 04 72 35
Email :
jean-luc.lecuyer@alcatel.fr
----------------------------------------------------------------------------
-----------------



_______________________________________________
Megaco mailing 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  Mon Apr  1 13:04: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 NAA08378
	for <megaco-archive@odin.ietf.org>; Mon, 1 Apr 2002 13:04:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA28348
	for megaco-archive@odin.ietf.org; Mon, 1 Apr 2002 13:04: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 MAA26075;
	Mon, 1 Apr 2002 12:43: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 MAA26039
	for <megaco@ns.ietf.org>; Mon, 1 Apr 2002 12:43:05 -0500 (EST)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07308
	for <megaco@ietf.org>; Mon, 1 Apr 2002 12:43:01 -0500 (EST)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id MAA17886;
	Mon, 1 Apr 2002 12:42:00 -0500 (EST)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2ACALZBC>; Mon, 1 Apr 2002 12:41:59 -0500
Message-ID: <29B5A21C13C8D51190F900805F65B4EC239F82@rndex50.ottawa.mitel.com>
From: "Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM>
To: "'vbajaj@hss.hns.com'" <vbajaj@hss.hns.com>,
        Tom-PT Taylor
	 <taylor@nortelnetworks.com>
Cc: "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
        megaco@ietf.org
Subject: RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00.
	 txt
Date: Mon, 1 Apr 2002 12:41:58 -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 agree this should be a WG item, one way or another -- separate doc or folded in to main protocol, perhaps updates to base protocol doc + an Informational doc.  Its important to correct interop and affects basic use of the protocol.  

Don't think this should be a large task however.  If it gets too large we have likely made it too complicated, and I just don't think it really need to be.  

My $0.02. 
-- Peter Blatherwick

-----Original Message-----
From: vbajaj@hss.hns.com [mailto:vbajaj@hss.hns.com]
Sent: March 31, 2002 23:46
To: Tom-PT Taylor
Cc: 'Jean-Luc.Lecuyer@alcatel.fr'; megaco@ietf.org
Subject: RE: [Megaco] Status of
draft-hss-megaco-control-state-machine-00. txt




Tom,
        I think it is absolutely necessary to take this activity as a WG work
item. This area needs
  to be addressed to avoid interoperability issues later.

Rgds,

Vikas Bajaj





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 03/29/2002 09:22:32 PM

To:   "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
      megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00. txt




Could I have opinions from the WG on whether we should be producing a
document on control associations and the signalling associated with control
state transitions as a WG work item?  I assume the work would be Standards
Track because it would specify normative behaviour on the signalling side.
As an alternative, if the impact on the base specification wouldn't be too
large, we could simply add the conclusions to the Implementor's Guide.

-----Original Message-----
From: Jean-Luc.Lecuyer@alcatel.fr [mailto:Jean-Luc.Lecuyer@alcatel.fr]
Sent: Friday, March 29, 2002 4:11 AM
To: megaco@ietf.org
Subject: [Megaco] Status of
draft-hss-megaco-control-state-machine-00.txt




What is the status of the document
"draft-hss-megaco-control-state-machine-00.txt"
which expired in February ?

Thank-you
Jean-Luc
----------------------------------------------------------------------------
----------------
Jean-Luc.Lecuyer :         VND/E10 VS  BU R&D//CCPD Lannion
Full telephone number :                                         33 (0)2 96
04 77 09
Full fax number :                                                        33
(0)2 96 04 72 35
Email :
jean-luc.lecuyer@alcatel.fr
----------------------------------------------------------------------------
-----------------



_______________________________________________
Megaco mailing 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 Apr  2 09: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 JAA16793
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 09:32: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 JAA14268;
	Tue, 2 Apr 2002 09:17: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 BAA19250
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 01:29:48 -0500 (EST)
Received: from epygilab.am (araler.epygilab.am [195.151.94.74])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29469
	for <megaco@ietf.org>; Tue, 2 Apr 2002 01:29:37 -0500 (EST)
Received: (apparently) from epygilab.am ([192.168.0.156]) by epygilab.am  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Tue, 2 Apr 2002 10:29:38 +0400
Received: from epygilab.am [192.168.0.32]
	by epygilab.am [192.168.0.156]
	with SMTP (MDaemon.PRO.v5.0.1.R)
	for <megaco@ietf.org>; Tue, 02 Apr 2002 11:27:55 +0500
Message-ID: <3CA95D5F.69AB75DB@epygilab.am>
Date: Tue, 02 Apr 2002 11:27:27 +0400
From: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>, Megaco <megaco@ietf.org>
Subject: Re: [MEGACO] what does list of signals mean?
References: <3CA16702.CC6CB0D4@epygilab.am> <3CA1F936.EDB6B299@lucent.com> <3CA2ED4A.E50A98DB@epygilab.am> <3CA4A166.46829717@lucent.com> <3CA8026F.88A92E05@epygilab.am> <3CA87493.1584E7D3@lucent.com>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-MDRemoteIP: 192.168.0.32
X-Return-Path: Narine.Mossikyan@epygilab.am
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

Your samples were about Signals Descriptor. Can I say that SigID=tonegen/pt{t1=2,4,5} for
ObservedEvent is useful too?
I mean,
is the following ObservedEvent  syntactical correct?
    ObservedEvents = 2345 {20010329T11501000:g/sc{SigID=tonegen/pt{t1=2,4,5},    Meth=TO
}}
if not, could you give me a correct one?
thanks a lot


Terry L Anderson wrote:

> Narine_Mossikyan wrote:
>
> > It is indicated SigID=cg/rt in your sample, in this case cg signal's rt parameter
> > is simple. My question is if  I have SigID=pt/tl, where tl is tone id list, should
> > I enumerate tl's parameters too, or not? I mean will the syntax of SigID=pt/tl  be
> > correct if I will  not use  tl tone list parameters?
>
> We currently have a way to indicate the name of a signal that completed but not the
> name of a parameter to that signal.  That would not seem to be a problem when only one
> instance of a given signal is active (even if it has a parameter).  In your example, I
> don't think there is a problem as a signal
>     Signals{tonegen/pt{tl=2,4,6}}
> has only one "signal".  That signal is a sequence of tones, but is one signal and so
> completion will be notified only after the entire signal (all tones in sequence) are
> complete).
>
> But if more than one instance of a signal with varying parameter values are active
> there is currently no way to indicate which completed.  That is, if the signal were:
>     Signals{
>     tonegen/pt{tl=1{Duration=1 } },
>     tonegen/pt{tl=3{Duration=2 } }
>     }    ; play 1 and 3 simultaneously
> There would be no way to indicate in a notify which one completed.  Of course it would
> be more usual to play single DTMF tones using the distinct events rather than
> tonegen/pt.  If one played the above as
>     Signals{
>     dg/d1{Duration=1},
>     dg/d3{Duration=2}
> }
> There would be no problem.  However, there may well be useful cases where more than
> one instance of a given named signal (with distinct parameter values) is played
> simultaneously.  Do folks think we need a way to notify which completed?
>
> > thanks for your advice
> > P.S. "sit" is not a parameter of "g" event. How could you explain the meaning of
> > g/sit you used in your sample?
>
> I'm sorry, I mistyped.  I meant g/sc event in ObservedEvents.  I did use cg/sit
> further down, but did not mean 'sit' in the ObservedEvents.
>
> > Terry L Anderson wrote:
> >
> > > An example would be
> > > End of a signal, say an ringtone
> > >     ObservedEvents = 2345 {20010329T11501000:g/sit{SigID=cg/rt, Meth=TO,
> > > SLID=NotInServiceAnnouncement}}
> > > If the signal had been part of a signal list, then the signal list ID is also
> > > returned as shown, otherwise it would be omitted.
> > >
> > > For example, if the signal was started by a signals descriptor like:
> > > Signals { SignalList = NotInServiceAnnouncement {
> > >     cg/sit {NotifyCompletion={TimeOut,IntByEvent,OtherReason}},
> > >     an/apf {an=NotInService, av=English, NotifyCompletion={TimeOut, IntByEvent,
> > > OtherReason}},
> > > }}
> > >
> > > End of the sit tone would be notified as above.
> > >
> > > Narine_Mossikyan wrote:
> > >
> > > > Hi ,
> > > > Thanks for your quick response.
> > > > I still don't  understand what does observedEventsDescriptor's last parameter
> > > > mean? Can you give me some examples of observedEventsDescriptor?
> > > > thanks a lot for your help
> > > >
> > > > Terry L Anderson wrote:
> > > >
> > > > > The original text was ambiguous and was recently amended to clarify this
> > > > > parameter.  The change first appeared in the Implementors Guide but was
> > > > > included in H.248v1 Corrigendum 1 and H.248v2 as consented in Geneva Feb
> > > > > 2002.  Here is the current text:
> > > > >
> > > > > ObservedEvents Descriptor parameters:
> > > > > Signal Identity
> > > > > ParameterID:  SigID (0x0001)
> > > > > This parameter identifies the signal which has terminated. For a signal
> > > > > that is contained in a signal list the signal list identity parameter
> > > > > should also be returned indicating the appropriate list.
> > > > > Type: Binary: octet (string), Text: string
> > > > > Possible values: a signal which has terminated.  A signal shall be
> > > > > identified using the pkgdName syntax without wildcarding.
> > > > >
> > > > > Narine_Mossikyan wrote:
> > > > >
> > > > > > Hi,
> > > > > > I found the list of signals on the page#139,  RFC 3015 Megaco Protocol
> > > > > > Version 1.0,  November 2000 , in Section Generic packages , E.1.2.
> > > > > > Events .
> > > > > > ObservedEvents Descriptor parameters:
> > > > > >         Signal Identity
> > > > > >         ParameterID:  SigID (0x0001)
> > > > > >         This parameter identifies the signals which have terminated.
> > > > > >         Type: list
> > > > > > My question is:
> > > > > > Should I implement  list of  signals as it is describe in the same RFC,
> > > > > > page #107 ?
> > > > > >         signalList           = SignalListToken EQUAL signalListId LBRKT
> > > > > >                           signalListParm *(COMMA signalListParm) RBRKT
> > > > > > or the list of signals in ObservedEvents has another meaning?
> > > > > > thanks for your help
> > > > > >
> > > > > > _______________________________________________
> > > > > > Megaco mailing list
> > > > > > Megaco@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/megaco
> > > > >
> > > > > --
> > > > >
> > > > > ------------------------------------------------------------
> > > > > Terry L Anderson            mailto:tla@lucent.com
> > > > > Tel:732.949.5628   Fax:732.949.7016
> > > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> > >
> > > --
> > >
> > > ------------------------------------------------------------
> > > Terry L Anderson            mailto:tla@lucent.com
> > > Tel:732.949.5628   Fax:732.949.7016
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
>
> --
> -------------------------------------------------------
> Terry L Anderson, DMTS                   tla@lucent.com
> Lucent Technologies /INS/ Voice over IP Access Networks
> Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
> Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
> 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 Apr  2 09:32: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 JAA16806
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 09:32:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA15375
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 09:32: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 JAA14268;
	Tue, 2 Apr 2002 09:17: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 BAA19250
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 01:29:48 -0500 (EST)
Received: from epygilab.am (araler.epygilab.am [195.151.94.74])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29469
	for <megaco@ietf.org>; Tue, 2 Apr 2002 01:29:37 -0500 (EST)
Received: (apparently) from epygilab.am ([192.168.0.156]) by epygilab.am  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Tue, 2 Apr 2002 10:29:38 +0400
Received: from epygilab.am [192.168.0.32]
	by epygilab.am [192.168.0.156]
	with SMTP (MDaemon.PRO.v5.0.1.R)
	for <megaco@ietf.org>; Tue, 02 Apr 2002 11:27:55 +0500
Message-ID: <3CA95D5F.69AB75DB@epygilab.am>
Date: Tue, 02 Apr 2002 11:27:27 +0400
From: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>, Megaco <megaco@ietf.org>
Subject: Re: [MEGACO] what does list of signals mean?
References: <3CA16702.CC6CB0D4@epygilab.am> <3CA1F936.EDB6B299@lucent.com> <3CA2ED4A.E50A98DB@epygilab.am> <3CA4A166.46829717@lucent.com> <3CA8026F.88A92E05@epygilab.am> <3CA87493.1584E7D3@lucent.com>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-MDRemoteIP: 192.168.0.32
X-Return-Path: Narine.Mossikyan@epygilab.am
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

Your samples were about Signals Descriptor. Can I say that SigID=tonegen/pt{t1=2,4,5} for
ObservedEvent is useful too?
I mean,
is the following ObservedEvent  syntactical correct?
    ObservedEvents = 2345 {20010329T11501000:g/sc{SigID=tonegen/pt{t1=2,4,5},    Meth=TO
}}
if not, could you give me a correct one?
thanks a lot


Terry L Anderson wrote:

> Narine_Mossikyan wrote:
>
> > It is indicated SigID=cg/rt in your sample, in this case cg signal's rt parameter
> > is simple. My question is if  I have SigID=pt/tl, where tl is tone id list, should
> > I enumerate tl's parameters too, or not? I mean will the syntax of SigID=pt/tl  be
> > correct if I will  not use  tl tone list parameters?
>
> We currently have a way to indicate the name of a signal that completed but not the
> name of a parameter to that signal.  That would not seem to be a problem when only one
> instance of a given signal is active (even if it has a parameter).  In your example, I
> don't think there is a problem as a signal
>     Signals{tonegen/pt{tl=2,4,6}}
> has only one "signal".  That signal is a sequence of tones, but is one signal and so
> completion will be notified only after the entire signal (all tones in sequence) are
> complete).
>
> But if more than one instance of a signal with varying parameter values are active
> there is currently no way to indicate which completed.  That is, if the signal were:
>     Signals{
>     tonegen/pt{tl=1{Duration=1 } },
>     tonegen/pt{tl=3{Duration=2 } }
>     }    ; play 1 and 3 simultaneously
> There would be no way to indicate in a notify which one completed.  Of course it would
> be more usual to play single DTMF tones using the distinct events rather than
> tonegen/pt.  If one played the above as
>     Signals{
>     dg/d1{Duration=1},
>     dg/d3{Duration=2}
> }
> There would be no problem.  However, there may well be useful cases where more than
> one instance of a given named signal (with distinct parameter values) is played
> simultaneously.  Do folks think we need a way to notify which completed?
>
> > thanks for your advice
> > P.S. "sit" is not a parameter of "g" event. How could you explain the meaning of
> > g/sit you used in your sample?
>
> I'm sorry, I mistyped.  I meant g/sc event in ObservedEvents.  I did use cg/sit
> further down, but did not mean 'sit' in the ObservedEvents.
>
> > Terry L Anderson wrote:
> >
> > > An example would be
> > > End of a signal, say an ringtone
> > >     ObservedEvents = 2345 {20010329T11501000:g/sit{SigID=cg/rt, Meth=TO,
> > > SLID=NotInServiceAnnouncement}}
> > > If the signal had been part of a signal list, then the signal list ID is also
> > > returned as shown, otherwise it would be omitted.
> > >
> > > For example, if the signal was started by a signals descriptor like:
> > > Signals { SignalList = NotInServiceAnnouncement {
> > >     cg/sit {NotifyCompletion={TimeOut,IntByEvent,OtherReason}},
> > >     an/apf {an=NotInService, av=English, NotifyCompletion={TimeOut, IntByEvent,
> > > OtherReason}},
> > > }}
> > >
> > > End of the sit tone would be notified as above.
> > >
> > > Narine_Mossikyan wrote:
> > >
> > > > Hi ,
> > > > Thanks for your quick response.
> > > > I still don't  understand what does observedEventsDescriptor's last parameter
> > > > mean? Can you give me some examples of observedEventsDescriptor?
> > > > thanks a lot for your help
> > > >
> > > > Terry L Anderson wrote:
> > > >
> > > > > The original text was ambiguous and was recently amended to clarify this
> > > > > parameter.  The change first appeared in the Implementors Guide but was
> > > > > included in H.248v1 Corrigendum 1 and H.248v2 as consented in Geneva Feb
> > > > > 2002.  Here is the current text:
> > > > >
> > > > > ObservedEvents Descriptor parameters:
> > > > > Signal Identity
> > > > > ParameterID:  SigID (0x0001)
> > > > > This parameter identifies the signal which has terminated. For a signal
> > > > > that is contained in a signal list the signal list identity parameter
> > > > > should also be returned indicating the appropriate list.
> > > > > Type: Binary: octet (string), Text: string
> > > > > Possible values: a signal which has terminated.  A signal shall be
> > > > > identified using the pkgdName syntax without wildcarding.
> > > > >
> > > > > Narine_Mossikyan wrote:
> > > > >
> > > > > > Hi,
> > > > > > I found the list of signals on the page#139,  RFC 3015 Megaco Protocol
> > > > > > Version 1.0,  November 2000 , in Section Generic packages , E.1.2.
> > > > > > Events .
> > > > > > ObservedEvents Descriptor parameters:
> > > > > >         Signal Identity
> > > > > >         ParameterID:  SigID (0x0001)
> > > > > >         This parameter identifies the signals which have terminated.
> > > > > >         Type: list
> > > > > > My question is:
> > > > > > Should I implement  list of  signals as it is describe in the same RFC,
> > > > > > page #107 ?
> > > > > >         signalList           = SignalListToken EQUAL signalListId LBRKT
> > > > > >                           signalListParm *(COMMA signalListParm) RBRKT
> > > > > > or the list of signals in ObservedEvents has another meaning?
> > > > > > thanks for your help
> > > > > >
> > > > > > _______________________________________________
> > > > > > Megaco mailing list
> > > > > > Megaco@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/megaco
> > > > >
> > > > > --
> > > > >
> > > > > ------------------------------------------------------------
> > > > > Terry L Anderson            mailto:tla@lucent.com
> > > > > Tel:732.949.5628   Fax:732.949.7016
> > > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> > >
> > > --
> > >
> > > ------------------------------------------------------------
> > > Terry L Anderson            mailto:tla@lucent.com
> > > Tel:732.949.5628   Fax:732.949.7016
> > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
>
> --
> -------------------------------------------------------
> Terry L Anderson, DMTS                   tla@lucent.com
> Lucent Technologies /INS/ Voice over IP Access Networks
> Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
> Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
> 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 Apr  2 12:02: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 MAA23154
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 12:02: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 LAA23403;
	Tue, 2 Apr 2002 11:38: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 LAA23372
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 11:38:42 -0500 (EST)
Received: from blaze.hcltech.com ([203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22025
	for <megaco@ietf.org>; Tue, 2 Apr 2002 11:38:38 -0500 (EST)
Received: from rajesh.netlab.hcltech.com (rajesh.hclt-guindy.co.in [192.168.201.84])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id WAA06771
	for <megaco@ietf.org>; Tue, 2 Apr 2002 22:29:17 +0530
Message-Id: <4.3.2.7.1.20020402215335.00cba7f0@192.168.201.1>
X-Sender: nrajesh@192.168.201.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 02 Apr 2002 22:02:06 +0530
To: megaco@ietf.org
From: Rajesh N <nrajesh@netlab.hcltech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Megaco] Local/Remote descriptors and Permanent 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,

Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor".

I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided.

Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from?

Thanks
Regards,
Rajesh N


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


From daemon@optimus.ietf.org  Tue Apr  2 12:02: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 MAA23165
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 12:02:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA26147
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 12:02: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 LAA23403;
	Tue, 2 Apr 2002 11:38: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 LAA23372
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 11:38:42 -0500 (EST)
Received: from blaze.hcltech.com ([203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22025
	for <megaco@ietf.org>; Tue, 2 Apr 2002 11:38:38 -0500 (EST)
Received: from rajesh.netlab.hcltech.com (rajesh.hclt-guindy.co.in [192.168.201.84])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id WAA06771
	for <megaco@ietf.org>; Tue, 2 Apr 2002 22:29:17 +0530
Message-Id: <4.3.2.7.1.20020402215335.00cba7f0@192.168.201.1>
X-Sender: nrajesh@192.168.201.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 02 Apr 2002 22:02:06 +0530
To: megaco@ietf.org
From: Rajesh N <nrajesh@netlab.hcltech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Megaco] Local/Remote descriptors and Permanent 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,

Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor".

I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided.

Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from?

Thanks
Regards,
Rajesh N


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



From megaco-admin@ietf.org  Tue Apr  2 12:11: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 MAA23807
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 12:11: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 LAA24652;
	Tue, 2 Apr 2002 11:57: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 LAA24622
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 11:57:00 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22867
	for <megaco@ietf.org>; Tue, 2 Apr 2002 11:56:54 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g32GuQV20186
	for <megaco@ietf.org>; Tue, 2 Apr 2002 10:56:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g32GtVO22346
	for <megaco@ietf.org>; Tue, 2 Apr 2002 10:55:31 -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 g32GtU723327
	for <megaco@ietf.org>; Tue, 2 Apr 2002 10:55:30 -0600 (CST)
Message-ID: <3CA9E282.66DAA83C@alcatel.com>
Date: Tue, 02 Apr 2002 10:55:30 -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="------------789A87008F484D0825C0E8EB"
Subject: [Megaco] Is ROOT case insensitive?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

   EVERYTHING IN THE ABNF AND TEXT ENCODING IS CASE INSENSITIVE. This
   includes TerminationIDs, digitmap Ids etc. THE SDP IS CASE SENSITIVE
   AS PER RFC2327.

   TerminationID        = "ROOT" / pathNAME / "$" / "*"

Here the "ROOT" does not imply that root has to be ROOT in the Megaco.
It can be Root, root, RoOt, etc.

So in general in the ABNF, the double quote around anything is just an
indication of what it can be
and does not really trying to specify case at all.

Please clairfy

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



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>

<pre></pre>

<pre>&nbsp;&nbsp; EVERYTHING IN THE ABNF AND TEXT ENCODING IS CASE INSENSITIVE. This&nbsp;
&nbsp;&nbsp; includes TerminationIDs, digitmap Ids etc. THE SDP IS CASE SENSITIVE&nbsp;
&nbsp;&nbsp; AS PER RFC2327.&nbsp;
</pre>

<pre>&nbsp;&nbsp; TerminationID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = "ROOT" / pathNAME / "$" / "*"</pre>

<pre></pre>
Here the "ROOT" does not imply that root has to be ROOT&nbsp;in the Megaco.
<br>It can be Root, root, RoOt, etc.
<p>So in general in the ABNF, the double quote around anything is just
an indication of what it can be
<br>and does not really trying to specify case at all.
<p>Please clairfy
<p>Thanks
<br>Chuong
<pre></pre>

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

--------------789A87008F484D0825C0E8EB--


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


From daemon@optimus.ietf.org  Tue Apr  2 12:11: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 MAA23815
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 12:11:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA27537
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 12:11: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 LAA24652;
	Tue, 2 Apr 2002 11:57: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 LAA24622
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 11:57:00 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22867
	for <megaco@ietf.org>; Tue, 2 Apr 2002 11:56:54 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g32GuQV20186
	for <megaco@ietf.org>; Tue, 2 Apr 2002 10:56:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g32GtVO22346
	for <megaco@ietf.org>; Tue, 2 Apr 2002 10:55:31 -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 g32GtU723327
	for <megaco@ietf.org>; Tue, 2 Apr 2002 10:55:30 -0600 (CST)
Message-ID: <3CA9E282.66DAA83C@alcatel.com>
Date: Tue, 02 Apr 2002 10:55:30 -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="------------789A87008F484D0825C0E8EB"
Subject: [Megaco] Is ROOT case insensitive?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

   EVERYTHING IN THE ABNF AND TEXT ENCODING IS CASE INSENSITIVE. This
   includes TerminationIDs, digitmap Ids etc. THE SDP IS CASE SENSITIVE
   AS PER RFC2327.

   TerminationID        = "ROOT" / pathNAME / "$" / "*"

Here the "ROOT" does not imply that root has to be ROOT in the Megaco.
It can be Root, root, RoOt, etc.

So in general in the ABNF, the double quote around anything is just an
indication of what it can be
and does not really trying to specify case at all.

Please clairfy

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



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>

<pre></pre>

<pre>&nbsp;&nbsp; EVERYTHING IN THE ABNF AND TEXT ENCODING IS CASE INSENSITIVE. This&nbsp;
&nbsp;&nbsp; includes TerminationIDs, digitmap Ids etc. THE SDP IS CASE SENSITIVE&nbsp;
&nbsp;&nbsp; AS PER RFC2327.&nbsp;
</pre>

<pre>&nbsp;&nbsp; TerminationID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = "ROOT" / pathNAME / "$" / "*"</pre>

<pre></pre>
Here the "ROOT" does not imply that root has to be ROOT&nbsp;in the Megaco.
<br>It can be Root, root, RoOt, etc.
<p>So in general in the ABNF, the double quote around anything is just
an indication of what it can be
<br>and does not really trying to specify case at all.
<p>Please clairfy
<p>Thanks
<br>Chuong
<pre></pre>

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

--------------789A87008F484D0825C0E8EB--


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



From megaco-admin@ietf.org  Tue Apr  2 12:15: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 MAA24023
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 12:15: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 LAA24587;
	Tue, 2 Apr 2002 11:56: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 LAA24496
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 11:56:14 -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 LAA22812
	for <megaco@ietf.org>; Tue, 2 Apr 2002 11:56:11 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g32GtbK27776;
	Tue, 2 Apr 2002 11:55:37 -0500 (EST)
Received: from lucent.com (tlalap.ho.lucent.com [135.112.32.218])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA22228;
	Tue, 2 Apr 2002 11:56:20 -0500 (EST)
Message-ID: <3CA9E1BD.4D98A452@lucent.com>
Date: Tue, 02 Apr 2002 11:52:13 -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: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
CC: Megaco <megaco@ietf.org>
Subject: Re: [MEGACO] what does list of signals mean?
References: <3CA16702.CC6CB0D4@epygilab.am> <3CA1F936.EDB6B299@lucent.com> <3CA2ED4A.E50A98DB@epygilab.am> <3CA4A166.46829717@lucent.com> <3CA8026F.88A92E05@epygilab.am> <3CA87493.1584E7D3@lucent.com> <3CA95D5F.69AB75DB@epygilab.am>
Content-Type: multipart/mixed;
 boundary="------------7833E99541BFCD425522C8AE"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------7833E99541BFCD425522C8AE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Narine_Mossikyan wrote:

> Your samples were about Signals Descriptor. Can I say that SigID=tonegen/pt{t1=2,4,5} for
> ObservedEvent is useful too?
> I mean,
> is the following ObservedEvent  syntactical correct?
>     ObservedEvents = 2345 {20010329T11501000:g/sc{SigID=tonegen/pt{t1=2,4,5},    Meth=TO
> }}
> if not, could you give me a correct one?
> thanks a lot

no.  tonegen/pt is the signal.  The parameter to sc only takes a signal.  It does not include
any parameters to that signal.  The syntax is specified for text encoding as pkgdName which (
PackageName SLASH ItemID ) The wildcard alternative is not allowed.
But the event would not be sent until the entire signal (all three digits in sequence) is
complete.

>
>
> Terry L Anderson wrote:
>
> > Narine_Mossikyan wrote:
> >
> > > It is indicated SigID=cg/rt in your sample, in this case cg signal's rt parameter
> > > is simple. My question is if  I have SigID=pt/tl, where tl is tone id list, should
> > > I enumerate tl's parameters too, or not? I mean will the syntax of SigID=pt/tl  be
> > > correct if I will  not use  tl tone list parameters?
> >
> > We currently have a way to indicate the name of a signal that completed but not the
> > name of a parameter to that signal.  That would not seem to be a problem when only one
> > instance of a given signal is active (even if it has a parameter).  In your example, I
> > don't think there is a problem as a signal
> >     Signals{tonegen/pt{tl=2,4,6}}
> > has only one "signal".  That signal is a sequence of tones, but is one signal and so
> > completion will be notified only after the entire signal (all tones in sequence) are
> > complete).
> >
> > But if more than one instance of a signal with varying parameter values are active
> > there is currently no way to indicate which completed.  That is, if the signal were:
> >     Signals{
> >     tonegen/pt{tl=1{Duration=1 } },
> >     tonegen/pt{tl=3{Duration=2 } }
> >     }    ; play 1 and 3 simultaneously
> > There would be no way to indicate in a notify which one completed.  Of course it would
> > be more usual to play single DTMF tones using the distinct events rather than
> > tonegen/pt.  If one played the above as
> >     Signals{
> >     dg/d1{Duration=1},
> >     dg/d3{Duration=2}
> > }
> > There would be no problem.  However, there may well be useful cases where more than
> > one instance of a given named signal (with distinct parameter values) is played
> > simultaneously.  Do folks think we need a way to notify which completed?
> >
> > > thanks for your advice
> > > P.S. "sit" is not a parameter of "g" event. How could you explain the meaning of
> > > g/sit you used in your sample?
> >
> > I'm sorry, I mistyped.  I meant g/sc event in ObservedEvents.  I did use cg/sit
> > further down, but did not mean 'sit' in the ObservedEvents.
> >
> > > Terry L Anderson wrote:
> > >
> > > > An example would be
> > > > End of a signal, say an ringtone
> > > >     ObservedEvents = 2345 {20010329T11501000:g/sit{SigID=cg/rt, Meth=TO,
> > > > SLID=NotInServiceAnnouncement}}
> > > > If the signal had been part of a signal list, then the signal list ID is also
> > > > returned as shown, otherwise it would be omitted.
> > > >
> > > > For example, if the signal was started by a signals descriptor like:
> > > > Signals { SignalList = NotInServiceAnnouncement {
> > > >     cg/sit {NotifyCompletion={TimeOut,IntByEvent,OtherReason}},
> > > >     an/apf {an=NotInService, av=English, NotifyCompletion={TimeOut, IntByEvent,
> > > > OtherReason}},
> > > > }}
> > > >
> > > > End of the sit tone would be notified as above.
> > > >
> > > > Narine_Mossikyan wrote:
> > > >
> > > > > Hi ,
> > > > > Thanks for your quick response.
> > > > > I still don't  understand what does observedEventsDescriptor's last parameter
> > > > > mean? Can you give me some examples of observedEventsDescriptor?
> > > > > thanks a lot for your help
> > > > >
> > > > > Terry L Anderson wrote:
> > > > >
> > > > > > The original text was ambiguous and was recently amended to clarify this
> > > > > > parameter.  The change first appeared in the Implementors Guide but was
> > > > > > included in H.248v1 Corrigendum 1 and H.248v2 as consented in Geneva Feb
> > > > > > 2002.  Here is the current text:
> > > > > >
> > > > > > ObservedEvents Descriptor parameters:
> > > > > > Signal Identity
> > > > > > ParameterID:  SigID (0x0001)
> > > > > > This parameter identifies the signal which has terminated. For a signal
> > > > > > that is contained in a signal list the signal list identity parameter
> > > > > > should also be returned indicating the appropriate list.
> > > > > > Type: Binary: octet (string), Text: string
> > > > > > Possible values: a signal which has terminated.  A signal shall be
> > > > > > identified using the pkgdName syntax without wildcarding.
> > > > > >
> > > > > > Narine_Mossikyan wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > > I found the list of signals on the page#139,  RFC 3015 Megaco Protocol
> > > > > > > Version 1.0,  November 2000 , in Section Generic packages , E.1.2.
> > > > > > > Events .
> > > > > > > ObservedEvents Descriptor parameters:
> > > > > > >         Signal Identity
> > > > > > >         ParameterID:  SigID (0x0001)
> > > > > > >         This parameter identifies the signals which have terminated.
> > > > > > >         Type: list
> > > > > > > My question is:
> > > > > > > Should I implement  list of  signals as it is describe in the same RFC,
> > > > > > > page #107 ?
> > > > > > >         signalList           = SignalListToken EQUAL signalListId LBRKT
> > > > > > >                           signalListParm *(COMMA signalListParm) RBRKT
> > > > > > > or the list of signals in ObservedEvents has another meaning?
> > > > > > > thanks for your help
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Megaco mailing list
> > > > > > > Megaco@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/megaco
> > > > > >
> > > > > > --
> > > > > >
> > > > > > ------------------------------------------------------------
> > > > > > Terry L Anderson            mailto:tla@lucent.com
> > > > > > Tel:732.949.5628   Fax:732.949.7016
> > > > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> > > >
> > > > --
> > > >
> > > > ------------------------------------------------------------
> > > > Terry L Anderson            mailto:tla@lucent.com
> > > > Tel:732.949.5628   Fax:732.949.7016
> > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> >
> > --
> > -------------------------------------------------------
> > Terry L Anderson, DMTS                   tla@lucent.com
> > Lucent Technologies /INS/ Voice over IP Access Networks
> > Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
> > Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
> > http://its.lucent.com/~tla  (Lucent internal)
> > http://www.gti.net/tla
> > -------------------------------------------------------

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------7833E99541BFCD425522C8AE
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------7833E99541BFCD425522C8AE--


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


From daemon@optimus.ietf.org  Tue Apr  2 12:15: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 MAA24036
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 12:15:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA28038
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 12:15: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 LAA24587;
	Tue, 2 Apr 2002 11:56: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 LAA24496
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 11:56:14 -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 LAA22812
	for <megaco@ietf.org>; Tue, 2 Apr 2002 11:56:11 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g32GtbK27776;
	Tue, 2 Apr 2002 11:55:37 -0500 (EST)
Received: from lucent.com (tlalap.ho.lucent.com [135.112.32.218])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA22228;
	Tue, 2 Apr 2002 11:56:20 -0500 (EST)
Message-ID: <3CA9E1BD.4D98A452@lucent.com>
Date: Tue, 02 Apr 2002 11:52:13 -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: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
CC: Megaco <megaco@ietf.org>
Subject: Re: [MEGACO] what does list of signals mean?
References: <3CA16702.CC6CB0D4@epygilab.am> <3CA1F936.EDB6B299@lucent.com> <3CA2ED4A.E50A98DB@epygilab.am> <3CA4A166.46829717@lucent.com> <3CA8026F.88A92E05@epygilab.am> <3CA87493.1584E7D3@lucent.com> <3CA95D5F.69AB75DB@epygilab.am>
Content-Type: multipart/mixed;
 boundary="------------7833E99541BFCD425522C8AE"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------7833E99541BFCD425522C8AE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Narine_Mossikyan wrote:

> Your samples were about Signals Descriptor. Can I say that SigID=tonegen/pt{t1=2,4,5} for
> ObservedEvent is useful too?
> I mean,
> is the following ObservedEvent  syntactical correct?
>     ObservedEvents = 2345 {20010329T11501000:g/sc{SigID=tonegen/pt{t1=2,4,5},    Meth=TO
> }}
> if not, could you give me a correct one?
> thanks a lot

no.  tonegen/pt is the signal.  The parameter to sc only takes a signal.  It does not include
any parameters to that signal.  The syntax is specified for text encoding as pkgdName which (
PackageName SLASH ItemID ) The wildcard alternative is not allowed.
But the event would not be sent until the entire signal (all three digits in sequence) is
complete.

>
>
> Terry L Anderson wrote:
>
> > Narine_Mossikyan wrote:
> >
> > > It is indicated SigID=cg/rt in your sample, in this case cg signal's rt parameter
> > > is simple. My question is if  I have SigID=pt/tl, where tl is tone id list, should
> > > I enumerate tl's parameters too, or not? I mean will the syntax of SigID=pt/tl  be
> > > correct if I will  not use  tl tone list parameters?
> >
> > We currently have a way to indicate the name of a signal that completed but not the
> > name of a parameter to that signal.  That would not seem to be a problem when only one
> > instance of a given signal is active (even if it has a parameter).  In your example, I
> > don't think there is a problem as a signal
> >     Signals{tonegen/pt{tl=2,4,6}}
> > has only one "signal".  That signal is a sequence of tones, but is one signal and so
> > completion will be notified only after the entire signal (all tones in sequence) are
> > complete).
> >
> > But if more than one instance of a signal with varying parameter values are active
> > there is currently no way to indicate which completed.  That is, if the signal were:
> >     Signals{
> >     tonegen/pt{tl=1{Duration=1 } },
> >     tonegen/pt{tl=3{Duration=2 } }
> >     }    ; play 1 and 3 simultaneously
> > There would be no way to indicate in a notify which one completed.  Of course it would
> > be more usual to play single DTMF tones using the distinct events rather than
> > tonegen/pt.  If one played the above as
> >     Signals{
> >     dg/d1{Duration=1},
> >     dg/d3{Duration=2}
> > }
> > There would be no problem.  However, there may well be useful cases where more than
> > one instance of a given named signal (with distinct parameter values) is played
> > simultaneously.  Do folks think we need a way to notify which completed?
> >
> > > thanks for your advice
> > > P.S. "sit" is not a parameter of "g" event. How could you explain the meaning of
> > > g/sit you used in your sample?
> >
> > I'm sorry, I mistyped.  I meant g/sc event in ObservedEvents.  I did use cg/sit
> > further down, but did not mean 'sit' in the ObservedEvents.
> >
> > > Terry L Anderson wrote:
> > >
> > > > An example would be
> > > > End of a signal, say an ringtone
> > > >     ObservedEvents = 2345 {20010329T11501000:g/sit{SigID=cg/rt, Meth=TO,
> > > > SLID=NotInServiceAnnouncement}}
> > > > If the signal had been part of a signal list, then the signal list ID is also
> > > > returned as shown, otherwise it would be omitted.
> > > >
> > > > For example, if the signal was started by a signals descriptor like:
> > > > Signals { SignalList = NotInServiceAnnouncement {
> > > >     cg/sit {NotifyCompletion={TimeOut,IntByEvent,OtherReason}},
> > > >     an/apf {an=NotInService, av=English, NotifyCompletion={TimeOut, IntByEvent,
> > > > OtherReason}},
> > > > }}
> > > >
> > > > End of the sit tone would be notified as above.
> > > >
> > > > Narine_Mossikyan wrote:
> > > >
> > > > > Hi ,
> > > > > Thanks for your quick response.
> > > > > I still don't  understand what does observedEventsDescriptor's last parameter
> > > > > mean? Can you give me some examples of observedEventsDescriptor?
> > > > > thanks a lot for your help
> > > > >
> > > > > Terry L Anderson wrote:
> > > > >
> > > > > > The original text was ambiguous and was recently amended to clarify this
> > > > > > parameter.  The change first appeared in the Implementors Guide but was
> > > > > > included in H.248v1 Corrigendum 1 and H.248v2 as consented in Geneva Feb
> > > > > > 2002.  Here is the current text:
> > > > > >
> > > > > > ObservedEvents Descriptor parameters:
> > > > > > Signal Identity
> > > > > > ParameterID:  SigID (0x0001)
> > > > > > This parameter identifies the signal which has terminated. For a signal
> > > > > > that is contained in a signal list the signal list identity parameter
> > > > > > should also be returned indicating the appropriate list.
> > > > > > Type: Binary: octet (string), Text: string
> > > > > > Possible values: a signal which has terminated.  A signal shall be
> > > > > > identified using the pkgdName syntax without wildcarding.
> > > > > >
> > > > > > Narine_Mossikyan wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > > I found the list of signals on the page#139,  RFC 3015 Megaco Protocol
> > > > > > > Version 1.0,  November 2000 , in Section Generic packages , E.1.2.
> > > > > > > Events .
> > > > > > > ObservedEvents Descriptor parameters:
> > > > > > >         Signal Identity
> > > > > > >         ParameterID:  SigID (0x0001)
> > > > > > >         This parameter identifies the signals which have terminated.
> > > > > > >         Type: list
> > > > > > > My question is:
> > > > > > > Should I implement  list of  signals as it is describe in the same RFC,
> > > > > > > page #107 ?
> > > > > > >         signalList           = SignalListToken EQUAL signalListId LBRKT
> > > > > > >                           signalListParm *(COMMA signalListParm) RBRKT
> > > > > > > or the list of signals in ObservedEvents has another meaning?
> > > > > > > thanks for your help
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Megaco mailing list
> > > > > > > Megaco@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/megaco
> > > > > >
> > > > > > --
> > > > > >
> > > > > > ------------------------------------------------------------
> > > > > > Terry L Anderson            mailto:tla@lucent.com
> > > > > > Tel:732.949.5628   Fax:732.949.7016
> > > > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> > > >
> > > > --
> > > >
> > > > ------------------------------------------------------------
> > > > Terry L Anderson            mailto:tla@lucent.com
> > > > Tel:732.949.5628   Fax:732.949.7016
> > > > Lucent Technologies/INS/Voice Over IP Access Networks
> > > > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > > > http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla
> >
> > --
> > -------------------------------------------------------
> > Terry L Anderson, DMTS                   tla@lucent.com
> > Lucent Technologies /INS/ Voice over IP Access Networks
> > Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
> > Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
> > http://its.lucent.com/~tla  (Lucent internal)
> > http://www.gti.net/tla
> > -------------------------------------------------------

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------7833E99541BFCD425522C8AE
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------7833E99541BFCD425522C8AE--


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



From megaco-admin@ietf.org  Tue Apr  2 12:45: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 MAA25523
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 12:45: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 MAA29392;
	Tue, 2 Apr 2002 12:28: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 MAA29366
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 12:28:01 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24637
	for <megaco@ietf.org>; Tue, 2 Apr 2002 12:27: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 g32HRSZ05548
	for <megaco@ietf.org>; Tue, 2 Apr 2002 12:27:29 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0JGQ>; Tue, 2 Apr 2002 12:27:30 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A230@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Rajesh N'" <nrajesh@netlab.hcltech.com>, megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 12:27:28 -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

In general Local and Remote can be provisioned for physical terminations, so
the MGC doesn't have to specify anything for them.  The exception is when
the MG is functioning as a NAS, in which case it needs to know a number of
parameters which are sent in call signalling.

-----Original Message-----
From: Rajesh N [mailto:nrajesh@netlab.hcltech.com]
Sent: Tuesday, April 02, 2002 11:32 AM
To: megaco@ietf.org
Subject: [Megaco] Local/Remote descriptors and Permanent terminations


Hi,

Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor".

I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided.

Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from?

Thanks
Regards,
Rajesh N


_______________________________________________
Megaco mailing list
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 Apr  2 12:45: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 MAA25536
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 12:45:13 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA01217
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 12:45: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 MAA29392;
	Tue, 2 Apr 2002 12:28: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 MAA29366
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 12:28:01 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24637
	for <megaco@ietf.org>; Tue, 2 Apr 2002 12:27: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 g32HRSZ05548
	for <megaco@ietf.org>; Tue, 2 Apr 2002 12:27:29 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0JGQ>; Tue, 2 Apr 2002 12:27:30 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A230@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Rajesh N'" <nrajesh@netlab.hcltech.com>, megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 12:27:28 -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

In general Local and Remote can be provisioned for physical terminations, so
the MGC doesn't have to specify anything for them.  The exception is when
the MG is functioning as a NAS, in which case it needs to know a number of
parameters which are sent in call signalling.

-----Original Message-----
From: Rajesh N [mailto:nrajesh@netlab.hcltech.com]
Sent: Tuesday, April 02, 2002 11:32 AM
To: megaco@ietf.org
Subject: [Megaco] Local/Remote descriptors and Permanent terminations


Hi,

Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor".

I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided.

Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from?

Thanks
Regards,
Rajesh N


_______________________________________________
Megaco mailing list
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 Apr  2 14:30: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 OAA29143
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 14:30: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 OAA06365;
	Tue, 2 Apr 2002 14:04: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 OAA06334
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 14:04:16 -0500 (EST)
Received: from caduceus.fm.intel.com ([192.55.52.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28242
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:04:14 -0500 (EST)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39])
	by caduceus.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.37 2002/04/01 17:50:55 root Exp $) with ESMTP id g32J35L20904
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:03:05 GMT
Received: from fmsmsxvs043.fm.intel.com (fmsmsxv043-1.fm.intel.com [132.233.48.128])
	by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.15 2002/04/01 17:51:48 root Exp $) with SMTP id g32J4dL25343
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:04:39 GMT
Received: from fmsmsx28.fm.intel.com ([132.233.42.28])
 by fmsmsxvs043.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002040211023127106
 for <megaco@ietf.org>; Tue, 02 Apr 2002 11:02:31 -0800
Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <HKXH3WA7>; Tue, 2 Apr 2002 11:03:26 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D5018748111@FMSMSX37>
From: "Kaul, Bharat" <bharat@trillium.com>
To: Megaco <megaco@ietf.org>
Date: Tue, 2 Apr 2002 11:03:22 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Megaco] Annex M.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

Please point me to the latest Annex M.1 document. I have not been able to
locate. 


- Thanks
  Bharat

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


From daemon@optimus.ietf.org  Tue Apr  2 14:30: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 OAA29152
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 14:30:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA07738
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 14:30: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 OAA06365;
	Tue, 2 Apr 2002 14:04: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 OAA06334
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 14:04:16 -0500 (EST)
Received: from caduceus.fm.intel.com ([192.55.52.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28242
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:04:14 -0500 (EST)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39])
	by caduceus.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.37 2002/04/01 17:50:55 root Exp $) with ESMTP id g32J35L20904
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:03:05 GMT
Received: from fmsmsxvs043.fm.intel.com (fmsmsxv043-1.fm.intel.com [132.233.48.128])
	by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.15 2002/04/01 17:51:48 root Exp $) with SMTP id g32J4dL25343
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:04:39 GMT
Received: from fmsmsx28.fm.intel.com ([132.233.42.28])
 by fmsmsxvs043.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002040211023127106
 for <megaco@ietf.org>; Tue, 02 Apr 2002 11:02:31 -0800
Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <HKXH3WA7>; Tue, 2 Apr 2002 11:03:26 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D5018748111@FMSMSX37>
From: "Kaul, Bharat" <bharat@trillium.com>
To: Megaco <megaco@ietf.org>
Date: Tue, 2 Apr 2002 11:03:22 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Megaco] Annex M.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

Please point me to the latest Annex M.1 document. I have not been able to
locate. 


- Thanks
  Bharat

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



From megaco-admin@ietf.org  Tue Apr  2 14: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 OAA29853
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 14:47: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 OAA07513;
	Tue, 2 Apr 2002 14:29: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 OAA07482
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 14:29:43 -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 OAA29069
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:29:41 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AHF55640;
	Tue, 2 Apr 2002 14:28:37 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Rajesh N'" <nrajesh@netlab.hcltech.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 14:23:50 -0500
Message-ID: <005b01c1da7b$ebfe51f0$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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <4.3.2.7.1.20020402215335.00cba7f0@192.168.201.1>
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 Rajesh/All,
Not all parameters might be useful for the MG/MGC in case of physical
terminations. The SDP parameters are of no significance in case of physical
terminations (in normal scenario). Hence the mode was set to "sendrecv"
without specifying the local/remote descriptor information.
Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Rajesh N
Sent: Tuesday, April 02, 2002 11:32 AM
To: megaco@ietf.org
Subject: [Megaco] Local/Remote descriptors and Permanent terminations


Hi,

Sometime back there was a thread regarding usage of SendRecv mode for an
ephemeral termination, when Remote Descriptor values are yet to be defined.
And one of the choices for the MG in such a situation is to reply back with
error 411, "missing remote or local descriptor".

I would like to know, what is the significance of this problem w.r.to
permanent terminations. The example call flow in the draft shows a Modify
request for a permanent termination, from MGC to MG1, in which mode is set
as SendRecv and  the Local descriptor values alone are being provided.

Are local and remote descriptors relevant for physical terminations? If
yes, where should I get the values from?

Thanks
Regards,
Rajesh N


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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


From daemon@ns.ietf.org  Tue Apr  2 14:48: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 OAA29862
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 14:48:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA08618
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 14:48: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 OAA07513;
	Tue, 2 Apr 2002 14:29: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 OAA07482
	for <megaco@optimus.ietf.org>; Tue, 2 Apr 2002 14:29:43 -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 OAA29069
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:29:41 -0500 (EST)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AHF55640;
	Tue, 2 Apr 2002 14:28:37 -0500 (EST)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Rajesh N'" <nrajesh@netlab.hcltech.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 14:23:50 -0500
Message-ID: <005b01c1da7b$ebfe51f0$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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <4.3.2.7.1.20020402215335.00cba7f0@192.168.201.1>
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 Rajesh/All,
Not all parameters might be useful for the MG/MGC in case of physical
terminations. The SDP parameters are of no significance in case of physical
terminations (in normal scenario). Hence the mode was set to "sendrecv"
without specifying the local/remote descriptor information.
Regards
Madhubabu

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Rajesh N
Sent: Tuesday, April 02, 2002 11:32 AM
To: megaco@ietf.org
Subject: [Megaco] Local/Remote descriptors and Permanent terminations


Hi,

Sometime back there was a thread regarding usage of SendRecv mode for an
ephemeral termination, when Remote Descriptor values are yet to be defined.
And one of the choices for the MG in such a situation is to reply back with
error 411, "missing remote or local descriptor".

I would like to know, what is the significance of this problem w.r.to
permanent terminations. The example call flow in the draft shows a Modify
request for a permanent termination, from MGC to MG1, in which mode is set
as SendRecv and  the Local descriptor values alone are being provided.

Are local and remote descriptors relevant for physical terminations? If
yes, where should I get the values from?

Thanks
Regards,
Rajesh N


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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



From megaco-admin@ietf.org  Tue Apr  2 15:08: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 PAA00738
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 15:08: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 OAA08894;
	Tue, 2 Apr 2002 14:51: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 OAA08865
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 14:51:27 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29968
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:51: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 g32JosZ11138
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:50:54 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0N41>; Tue, 2 Apr 2002 14:50:55 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A234@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Kaul, Bharat'" <bharat@trillium.com>, Megaco <megaco@ietf.org>
Subject: RE: [Megaco] Annex M.1
Date: Tue, 2 Apr 2002 14:50: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

You can find it at
ftp://standards.nortelnetworks.com/megaco/docs/Current/ITU-SG16/ITU%20Last%2
0Call/

-----Original Message-----
From: Kaul, Bharat [mailto:bharat@trillium.com]
Sent: Tuesday, April 02, 2002 2:03 PM
To: Megaco
Subject: [Megaco] Annex M.1


Please point me to the latest Annex M.1 document. I have not been able to
locate. 


- Thanks
  Bharat

_______________________________________________
Megaco mailing list
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 Apr  2 15:08: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 PAA00754
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 15:08:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA10252
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 15:08: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 OAA08894;
	Tue, 2 Apr 2002 14:51: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 OAA08865
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 14:51:27 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29968
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:51: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 g32JosZ11138
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:50:54 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0N41>; Tue, 2 Apr 2002 14:50:55 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A234@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Kaul, Bharat'" <bharat@trillium.com>, Megaco <megaco@ietf.org>
Subject: RE: [Megaco] Annex M.1
Date: Tue, 2 Apr 2002 14:50: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

You can find it at
ftp://standards.nortelnetworks.com/megaco/docs/Current/ITU-SG16/ITU%20Last%2
0Call/

-----Original Message-----
From: Kaul, Bharat [mailto:bharat@trillium.com]
Sent: Tuesday, April 02, 2002 2:03 PM
To: Megaco
Subject: [Megaco] Annex M.1


Please point me to the latest Annex M.1 document. I have not been able to
locate. 


- Thanks
  Bharat

_______________________________________________
Megaco mailing list
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 Apr  2 15:10: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 PAA00869
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 15:10: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 OAA08714;
	Tue, 2 Apr 2002 14:49: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 OAA08683
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 14:48:58 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29891
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:48:56 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g32JmRV03107
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:48:27 -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 g32JlkO06229
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:47:46 -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 g32Jlk723499
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:47:46 -0600 (CST)
Message-ID: <3CAA0AE1.4E39A5C6@alcatel.com>
Date: Tue, 02 Apr 2002 13:47:46 -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] Local/Remote descriptors and Permanent terminations
References: <005b01c1da7b$ebfe51f0$c500a8c0@MBRAHMANAPALLY>
Content-Type: multipart/alternative;
 boundary="------------68CB2546A15F5A51AEB40A89"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


I don't know about the sendrecv issue here.

I don't know what you mean by SDP parameters are of no significance in case of
phy. term.

Tom wrote the SDP TDM draft which I wonder what is the status of this draft.
But I can't remember now whether it was intended to be used in local or
localControl Descriptor.



Madhu Babu Brahmanapally wrote:

> HI Rajesh/All,
> Not all parameters might be useful for the MG/MGC in case of physical
> terminations. The SDP parameters are of no significance in case of physical
> terminations (in normal scenario). Hence the mode was set to "sendrecv"
> without specifying the local/remote descriptor information.
> Regards
> Madhubabu
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Rajesh N
> Sent: Tuesday, April 02, 2002 11:32 AM
> To: megaco@ietf.org
> Subject: [Megaco] Local/Remote descriptors and Permanent terminations
>
> Hi,
>
> Sometime back there was a thread regarding usage of SendRecv mode for an
> ephemeral termination, when Remote Descriptor values are yet to be defined.
> And one of the choices for the MG in such a situation is to reply back with
> error 411, "missing remote or local descriptor".
>
> I would like to know, what is the significance of this problem w.r.to
> permanent terminations. The example call flow in the draft shows a Modify
> request for a permanent termination, from MGC to MG1, in which mode is set
> as SendRecv and  the Local descriptor values alone are being provided.
>
> Are local and remote descriptors relevant for physical terminations? If
> yes, where should I get the values from?
>
> Thanks
> Regards,
> Rajesh N
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> ---
> [This E-mail was scanned for viruses and is clean.]
>
> _______________________________________________
> 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 ****



--------------68CB2546A15F5A51AEB40A89
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;don't know about the sendrecv issue here.
<p>I&nbsp;don't know what you mean by SDP parameters are of no significance
in case of phy. term.
<p>Tom wrote the SDP TDM draft which I&nbsp;wonder what is the status of
this draft.
<br>But I&nbsp;can't remember now whether it was intended to be used in
local or localControl Descriptor.
<br>&nbsp;
<br>&nbsp;
<p>Madhu Babu Brahmanapally wrote:
<blockquote TYPE=CITE>HI Rajesh/All,
<br>Not all parameters might be useful for the MG/MGC in case of physical
<br>terminations. The SDP parameters are of no significance in case of
physical
<br>terminations (in normal scenario). Hence the mode was set to "sendrecv"
<br>without specifying the local/remote descriptor information.
<br>Regards
<br>Madhubabu
<p>-----Original Message-----
<br>From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]On
Behalf Of
<br>Rajesh N
<br>Sent: Tuesday, April 02, 2002 11:32 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Local/Remote descriptors and Permanent terminations
<p>Hi,
<p>Sometime back there was a thread regarding usage of SendRecv mode for
an
<br>ephemeral termination, when Remote Descriptor values are yet to be
defined.
<br>And one of the choices for the MG in such a situation is to reply back
with
<br>error 411, "missing remote or local descriptor".
<p>I would like to know, what is the significance of this problem w.r.to
<br>permanent terminations. The example call flow in the draft shows a
Modify
<br>request for a permanent termination, from MGC to MG1, in which mode
is set
<br>as SendRecv and&nbsp; the Local descriptor values alone are being provided.
<p>Are local and remote descriptors relevant for physical terminations?
If
<br>yes, where should I get the values from?
<p>Thanks
<br>Regards,
<br>Rajesh N
<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>
<br>---
<br>[This E-mail was scanned for viruses and is clean.]
<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>

--------------68CB2546A15F5A51AEB40A89--


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


From daemon@ns.ietf.org  Tue Apr  2 15:10: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 PAA00880
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 15:10:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA10428
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 15:10: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 OAA08714;
	Tue, 2 Apr 2002 14:49: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 OAA08683
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 14:48:58 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29891
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:48:56 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g32JmRV03107
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:48:27 -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 g32JlkO06229
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:47:46 -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 g32Jlk723499
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:47:46 -0600 (CST)
Message-ID: <3CAA0AE1.4E39A5C6@alcatel.com>
Date: Tue, 02 Apr 2002 13:47:46 -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] Local/Remote descriptors and Permanent terminations
References: <005b01c1da7b$ebfe51f0$c500a8c0@MBRAHMANAPALLY>
Content-Type: multipart/alternative;
 boundary="------------68CB2546A15F5A51AEB40A89"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


I don't know about the sendrecv issue here.

I don't know what you mean by SDP parameters are of no significance in case of
phy. term.

Tom wrote the SDP TDM draft which I wonder what is the status of this draft.
But I can't remember now whether it was intended to be used in local or
localControl Descriptor.



Madhu Babu Brahmanapally wrote:

> HI Rajesh/All,
> Not all parameters might be useful for the MG/MGC in case of physical
> terminations. The SDP parameters are of no significance in case of physical
> terminations (in normal scenario). Hence the mode was set to "sendrecv"
> without specifying the local/remote descriptor information.
> Regards
> Madhubabu
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Rajesh N
> Sent: Tuesday, April 02, 2002 11:32 AM
> To: megaco@ietf.org
> Subject: [Megaco] Local/Remote descriptors and Permanent terminations
>
> Hi,
>
> Sometime back there was a thread regarding usage of SendRecv mode for an
> ephemeral termination, when Remote Descriptor values are yet to be defined.
> And one of the choices for the MG in such a situation is to reply back with
> error 411, "missing remote or local descriptor".
>
> I would like to know, what is the significance of this problem w.r.to
> permanent terminations. The example call flow in the draft shows a Modify
> request for a permanent termination, from MGC to MG1, in which mode is set
> as SendRecv and  the Local descriptor values alone are being provided.
>
> Are local and remote descriptors relevant for physical terminations? If
> yes, where should I get the values from?
>
> Thanks
> Regards,
> Rajesh N
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> ---
> [This E-mail was scanned for viruses and is clean.]
>
> _______________________________________________
> 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 ****



--------------68CB2546A15F5A51AEB40A89
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;don't know about the sendrecv issue here.
<p>I&nbsp;don't know what you mean by SDP parameters are of no significance
in case of phy. term.
<p>Tom wrote the SDP TDM draft which I&nbsp;wonder what is the status of
this draft.
<br>But I&nbsp;can't remember now whether it was intended to be used in
local or localControl Descriptor.
<br>&nbsp;
<br>&nbsp;
<p>Madhu Babu Brahmanapally wrote:
<blockquote TYPE=CITE>HI Rajesh/All,
<br>Not all parameters might be useful for the MG/MGC in case of physical
<br>terminations. The SDP parameters are of no significance in case of
physical
<br>terminations (in normal scenario). Hence the mode was set to "sendrecv"
<br>without specifying the local/remote descriptor information.
<br>Regards
<br>Madhubabu
<p>-----Original Message-----
<br>From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]On
Behalf Of
<br>Rajesh N
<br>Sent: Tuesday, April 02, 2002 11:32 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Local/Remote descriptors and Permanent terminations
<p>Hi,
<p>Sometime back there was a thread regarding usage of SendRecv mode for
an
<br>ephemeral termination, when Remote Descriptor values are yet to be
defined.
<br>And one of the choices for the MG in such a situation is to reply back
with
<br>error 411, "missing remote or local descriptor".
<p>I would like to know, what is the significance of this problem w.r.to
<br>permanent terminations. The example call flow in the draft shows a
Modify
<br>request for a permanent termination, from MGC to MG1, in which mode
is set
<br>as SendRecv and&nbsp; the Local descriptor values alone are being provided.
<p>Are local and remote descriptors relevant for physical terminations?
If
<br>yes, where should I get the values from?
<p>Thanks
<br>Regards,
<br>Rajesh N
<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>
<br>---
<br>[This E-mail was scanned for viruses and is clean.]
<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>

--------------68CB2546A15F5A51AEB40A89--


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



From megaco-admin@ietf.org  Tue Apr  2 15:13: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 PAA01071
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 15:13: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 OAA09011;
	Tue, 2 Apr 2002 14:53: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 OAA08982
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 14:53:46 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00047
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:53:44 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g32JrAZ11469
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:53:10 -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 g32JrAh23956
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:53:10 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0NWD>; Tue, 2 Apr 2002 14:53:10 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A235@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] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 14:53:10 -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 noted earlier, you do need to specify the properties in the NAS case.
The SDP TDM draft has certainly had time to ripen, and I will reissue it and
the NAS packages within the next week.

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 2:48 PM
To: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.

But I can't remember now whether it was intended to be used in local or
localControl Descriptor. 
  
  
Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco 
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
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@ns.ietf.org  Tue Apr  2 15:13: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 PAA01083
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 15:13:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA10569
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 15:13: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 OAA09011;
	Tue, 2 Apr 2002 14:53: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 OAA08982
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 14:53:46 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00047
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:53:44 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g32JrAZ11469
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:53:10 -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 g32JrAh23956
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:53:10 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0NWD>; Tue, 2 Apr 2002 14:53:10 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A235@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] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 14:53:10 -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 noted earlier, you do need to specify the properties in the NAS case.
The SDP TDM draft has certainly had time to ripen, and I will reissue it and
the NAS packages within the next week.

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 2:48 PM
To: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.

But I can't remember now whether it was intended to be used in local or
localControl Descriptor. 
  
  
Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco 
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
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 Apr  2 15:18: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 PAA01185
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 15: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 PAA09892;
	Tue, 2 Apr 2002 15:02: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 PAA09852
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 15:02:07 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00387
	for <megaco@ietf.org>; Tue, 2 Apr 2002 15:02:05 -0500 (EST)
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 g32JxQx18365
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:59:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g32JwqO16768
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:58:52 -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 g32Jwp723506
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:58:51 -0600 (CST)
Message-ID: <3CAA0D7B.2794DA35@alcatel.com>
Date: Tue, 02 Apr 2002 13:58:51 -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
CC: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <4D79C746863DD51197690002A52CDA0001E8A235@zcard0kc.ca.nortel.com>
Content-Type: multipart/alternative;
 boundary="------------8CDCAD60EBE4D156AD0DA46D"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


So what was that discussion about adding silence suppression to TDM package?

Do we use SDP TDM or TDM package or both?
Or even worse combination of both within 1 command w/some parameters defined by
TDM package and
some parameters defined by SDP TDM.



Tom-PT Taylor wrote:

> As I noted earlier, you do need to specify the properties in the NAS case.
> The SDP TDM draft has certainly had time to ripen, and I will reissue it and
> the NAS packages within the next week.
>
> -----Original Message-----
> From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
> Sent: Tuesday, April 02, 2002 2:48 PM
> To: megaco@ietf.org
> Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
>
>
> I don't know about the sendrecv issue here.
> I don't know what you mean by SDP parameters are of no significance in case
> of phy. term.
> Tom wrote the SDP TDM draft which I wonder what is the status of this draft.
>
> But I can't remember now whether it was intended to be used in local or
> localControl Descriptor.
>
>
> Madhu Babu Brahmanapally wrote:
> HI Rajesh/All,
> Not all parameters might be useful for the MG/MGC in case of physical
> terminations. The SDP parameters are of no significance in case of physical
> terminations (in normal scenario). Hence the mode was set to "sendrecv"
> without specifying the local/remote descriptor information.
> Regards
> Madhubabu
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Rajesh N
> Sent: Tuesday, April 02, 2002 11:32 AM
> To: megaco@ietf.org
> Subject: [Megaco] Local/Remote descriptors and Permanent terminations
> Hi,
> Sometime back there was a thread regarding usage of SendRecv mode for an
> ephemeral termination, when Remote Descriptor values are yet to be defined.
> And one of the choices for the MG in such a situation is to reply back with
> error 411, "missing remote or local descriptor".
> I would like to know, what is the significance of this problem w.r.to
> permanent terminations. The example call flow in the draft shows a Modify
> request for a permanent termination, from MGC to MG1, in which mode is set
> as SendRecv and  the Local descriptor values alone are being provided.
> Are local and remote descriptors relevant for physical terminations? If
> yes, where should I get the values from?
> Thanks
> Regards,
> Rajesh N
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> ---
> [This E-mail was scanned for viruses and is clean.]
> _______________________________________________
> 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 ****
>

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



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>So what was that discussion about adding silence suppression to TDM&nbsp;package?
<p>Do we use SDP&nbsp;TDM&nbsp;or TDM&nbsp;package or both?
<br>Or even worse combination of both within 1 command w/some parameters
defined by TDM&nbsp;package and
<br>some parameters defined by SDP TDM.
<br>&nbsp;
<br>&nbsp;
<p>Tom-PT Taylor wrote:
<blockquote TYPE=CITE>As I noted earlier, you do need to specify the properties
in the NAS case.
<br>The SDP TDM draft has certainly had time to ripen, and I will reissue
it and
<br>the NAS packages within the next week.
<p>-----Original Message-----
<br>From: Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]
<br>Sent: Tuesday, April 02, 2002 2:48 PM
<br>To: megaco@ietf.org
<br>Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
<br>&nbsp;
<p>I don't know about the sendrecv issue here.
<br>I don't know what you mean by SDP parameters are of no significance
in case
<br>of phy. term.
<br>Tom wrote the SDP TDM draft which I wonder what is the status of this
draft.
<p>But I can't remember now whether it was intended to be used in local
or
<br>localControl Descriptor.
<br>&nbsp;
<p>Madhu Babu Brahmanapally wrote:
<br>HI Rajesh/All,
<br>Not all parameters might be useful for the MG/MGC in case of physical
<br>terminations. The SDP parameters are of no significance in case of
physical
<br>terminations (in normal scenario). Hence the mode was set to "sendrecv"
<br>without specifying the local/remote descriptor information.
<br>Regards
<br>Madhubabu
<br>-----Original Message-----
<br>From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]On
Behalf Of
<br>Rajesh N
<br>Sent: Tuesday, April 02, 2002 11:32 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Local/Remote descriptors and Permanent terminations
<br>Hi,
<br>Sometime back there was a thread regarding usage of SendRecv mode for
an
<br>ephemeral termination, when Remote Descriptor values are yet to be
defined.
<br>And one of the choices for the MG in such a situation is to reply back
with
<br>error 411, "missing remote or local descriptor".
<br>I would like to know, what is the significance of this problem w.r.to
<br>permanent terminations. The example call flow in the draft shows a
Modify
<br>request for a permanent termination, from MGC to MG1, in which mode
is set
<br>as SendRecv and&nbsp; the Local descriptor values alone are being provided.
<br>Are local and remote descriptors relevant for physical terminations?
If
<br>yes, where should I get the values from?
<br>Thanks
<br>Regards,
<br>Rajesh N
<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>[This E-mail was scanned for viruses and is clean.]
<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; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>&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; **** The opinions expressed are not those of Alcatel USA, Inc
****
<br>&nbsp;</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>

--------------8CDCAD60EBE4D156AD0DA46D--


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


From daemon@ns.ietf.org  Tue Apr  2 15:18: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 PAA01195
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 15:18:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA10706
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 15:18: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 PAA09892;
	Tue, 2 Apr 2002 15:02: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 PAA09852
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 15:02:07 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00387
	for <megaco@ietf.org>; Tue, 2 Apr 2002 15:02:05 -0500 (EST)
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 g32JxQx18365
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:59:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g32JwqO16768
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:58:52 -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 g32Jwp723506
	for <megaco@ietf.org>; Tue, 2 Apr 2002 13:58:51 -0600 (CST)
Message-ID: <3CAA0D7B.2794DA35@alcatel.com>
Date: Tue, 02 Apr 2002 13:58:51 -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
CC: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <4D79C746863DD51197690002A52CDA0001E8A235@zcard0kc.ca.nortel.com>
Content-Type: multipart/alternative;
 boundary="------------8CDCAD60EBE4D156AD0DA46D"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


So what was that discussion about adding silence suppression to TDM package?

Do we use SDP TDM or TDM package or both?
Or even worse combination of both within 1 command w/some parameters defined by
TDM package and
some parameters defined by SDP TDM.



Tom-PT Taylor wrote:

> As I noted earlier, you do need to specify the properties in the NAS case.
> The SDP TDM draft has certainly had time to ripen, and I will reissue it and
> the NAS packages within the next week.
>
> -----Original Message-----
> From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
> Sent: Tuesday, April 02, 2002 2:48 PM
> To: megaco@ietf.org
> Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
>
>
> I don't know about the sendrecv issue here.
> I don't know what you mean by SDP parameters are of no significance in case
> of phy. term.
> Tom wrote the SDP TDM draft which I wonder what is the status of this draft.
>
> But I can't remember now whether it was intended to be used in local or
> localControl Descriptor.
>
>
> Madhu Babu Brahmanapally wrote:
> HI Rajesh/All,
> Not all parameters might be useful for the MG/MGC in case of physical
> terminations. The SDP parameters are of no significance in case of physical
> terminations (in normal scenario). Hence the mode was set to "sendrecv"
> without specifying the local/remote descriptor information.
> Regards
> Madhubabu
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Rajesh N
> Sent: Tuesday, April 02, 2002 11:32 AM
> To: megaco@ietf.org
> Subject: [Megaco] Local/Remote descriptors and Permanent terminations
> Hi,
> Sometime back there was a thread regarding usage of SendRecv mode for an
> ephemeral termination, when Remote Descriptor values are yet to be defined.
> And one of the choices for the MG in such a situation is to reply back with
> error 411, "missing remote or local descriptor".
> I would like to know, what is the significance of this problem w.r.to
> permanent terminations. The example call flow in the draft shows a Modify
> request for a permanent termination, from MGC to MG1, in which mode is set
> as SendRecv and  the Local descriptor values alone are being provided.
> Are local and remote descriptors relevant for physical terminations? If
> yes, where should I get the values from?
> Thanks
> Regards,
> Rajesh N
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> ---
> [This E-mail was scanned for viruses and is clean.]
> _______________________________________________
> 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 ****
>

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



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>So what was that discussion about adding silence suppression to TDM&nbsp;package?
<p>Do we use SDP&nbsp;TDM&nbsp;or TDM&nbsp;package or both?
<br>Or even worse combination of both within 1 command w/some parameters
defined by TDM&nbsp;package and
<br>some parameters defined by SDP TDM.
<br>&nbsp;
<br>&nbsp;
<p>Tom-PT Taylor wrote:
<blockquote TYPE=CITE>As I noted earlier, you do need to specify the properties
in the NAS case.
<br>The SDP TDM draft has certainly had time to ripen, and I will reissue
it and
<br>the NAS packages within the next week.
<p>-----Original Message-----
<br>From: Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]
<br>Sent: Tuesday, April 02, 2002 2:48 PM
<br>To: megaco@ietf.org
<br>Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
<br>&nbsp;
<p>I don't know about the sendrecv issue here.
<br>I don't know what you mean by SDP parameters are of no significance
in case
<br>of phy. term.
<br>Tom wrote the SDP TDM draft which I wonder what is the status of this
draft.
<p>But I can't remember now whether it was intended to be used in local
or
<br>localControl Descriptor.
<br>&nbsp;
<p>Madhu Babu Brahmanapally wrote:
<br>HI Rajesh/All,
<br>Not all parameters might be useful for the MG/MGC in case of physical
<br>terminations. The SDP parameters are of no significance in case of
physical
<br>terminations (in normal scenario). Hence the mode was set to "sendrecv"
<br>without specifying the local/remote descriptor information.
<br>Regards
<br>Madhubabu
<br>-----Original Message-----
<br>From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]On
Behalf Of
<br>Rajesh N
<br>Sent: Tuesday, April 02, 2002 11:32 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Local/Remote descriptors and Permanent terminations
<br>Hi,
<br>Sometime back there was a thread regarding usage of SendRecv mode for
an
<br>ephemeral termination, when Remote Descriptor values are yet to be
defined.
<br>And one of the choices for the MG in such a situation is to reply back
with
<br>error 411, "missing remote or local descriptor".
<br>I would like to know, what is the significance of this problem w.r.to
<br>permanent terminations. The example call flow in the draft shows a
Modify
<br>request for a permanent termination, from MGC to MG1, in which mode
is set
<br>as SendRecv and&nbsp; the Local descriptor values alone are being provided.
<br>Are local and remote descriptors relevant for physical terminations?
If
<br>yes, where should I get the values from?
<br>Thanks
<br>Regards,
<br>Rajesh N
<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>[This E-mail was scanned for viruses and is clean.]
<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; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>&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; **** The opinions expressed are not those of Alcatel USA, Inc
****
<br>&nbsp;</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>

--------------8CDCAD60EBE4D156AD0DA46D--


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



From megaco-admin@ietf.org  Tue Apr  2 15:41: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 PAA02383
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 15:41: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 PAA10874;
	Tue, 2 Apr 2002 15:20: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 PAA10773
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 15:20:03 -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 PAA01259
	for <megaco@ietf.org>; Tue, 2 Apr 2002 15:19:54 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0M8D>; Tue, 2 Apr 2002 15:18:50 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C44@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 15:18:46 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DA83.97D871C0"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1DA83.97D871C0
Content-Type: text/plain;
	charset="iso-8859-1"

Chuong,
 
There was several ideas bouncing around but I don't believe
there was any closure.  There is a hole for G711 since we can't use 
annexa or annexb.
Lifting the support in RFC 3108, section 5.6.3.2 and putting it into
the TDM Circuit Package would give us a lot of flexibility.
 
Here are the ideas I know of:
1)
Another option is to extend the TDM Circuit Package (which has been

previously discussed on the list). The TDM Cicruit Package

currently has Gain and Echo Control as its properties. So, it's logical

(IMO) for Silence Suppression to be part of the package as

well. In fact, it looks like an oversight that it was missed off in the

first place.

Regards,

Wayne Cutler

2)

Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.  E.g.: 

Media={Stream=1{ Local { 
v=0 
c=IN IP4 $ 
m=audio $ RTP/AVP 0 13 
}}}

David Barr 

3)

I'm starting to think that the answer may be to use the a=silenceSupp 
attribute defined in RFC 3108, section 5.6.3.2. 

Tom Taylor

 

Carl

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 2:59 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
So what was that discussion about adding silence suppression to TDM package?


Do we use SDP TDM or TDM package or both? 
Or even worse combination of both within 1 command w/some parameters defined
by TDM package and 
some parameters defined by SDP TDM. 
  
  


Tom-PT Taylor wrote: 


As I noted earlier, you do need to specify the properties in the NAS case. 
The SDP TDM draft has certainly had time to ripen, and I will reissue it and

the NAS packages within the next week. 

-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 2:48 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations 
  


I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case 
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.



But I can't remember now whether it was intended to be used in local or 
localControl Descriptor. 
  


Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [ mailto:megaco-admin@ietf.org
<mailto:megaco-admin@ietf.org> ]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<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 **** 
 

-- 

  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_01C1DA83.97D871C0
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">


<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2>Chuong,</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff size=2>There 
was several ideas bouncing around but I don't believe</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff size=2>there 
was any closure.&nbsp; There is a hole for G711 since we can't use 
</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff size=2>annexa 
or annexb.</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2>Lifting the support in <FONT face="Times New Roman" color=#000000>RFC 
3108, section 5.6.3.2 and putting it into</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT size=2>the TDM Circuit Package would 
give us a lot of flexibility.</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff size=2>Here 
are the ideas I know of:</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2>1)</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002>
<P><FONT face=Arial color=#0000ff size=2>Another option is to extend the TDM 
Circuit Package (which has been</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>previously discussed on the list). The 
TDM Cicruit Package</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>currently has Gain and Echo Control as 
its properties. So, it's logical</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>(IMO) for Silence Suppression to be 
part of the package as</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>well. In fact, it looks like an 
oversight that it was missed off in the</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>first place.</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>Regards,</FONT></P>
<P><FONT face=Arial><FONT color=#0000ff><FONT size=2>Wayne<SPAN 
class=491101120-02042002> Cutler</SPAN></FONT></FONT></FONT></P>
<P><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2>2)</FONT></SPAN></P><SPAN class=491101120-02042002>
<P><FONT size=2>Another possibility is to use payload 13 as defined in 
draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</FONT> </P>
<P><FONT size=2>Media={Stream=1{ Local {</FONT> <BR><FONT size=2>v=0</FONT> 
<BR><FONT size=2>c=IN IP4 $</FONT> <BR><FONT size=2>m=audio $ RTP/AVP 0 
13</FONT> <BR><FONT size=2>}}}</FONT></P>
<P><SPAN class=491101120-02042002><FONT size=2>David 
Barr</FONT></SPAN>&nbsp;</P>
<P><SPAN class=491101120-02042002><FONT size=2>3)</FONT></SPAN></P>
<P><SPAN class=491101120-02042002></SPAN><SPAN class=491101120-02042002><FONT 
size=2>I'm starting to think that the answer may be to use the a=silenceSupp 
<BR>attribute defined in RFC 3108, section 5.6.3.2. </FONT></P>
<P><SPAN class=491101120-02042002><FONT size=2>Tom Taylor</FONT></SPAN></P>
<P><FONT size=2></FONT>&nbsp;</P>
<P><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2>Carl</FONT></SPAN></P></SPAN></SPAN></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Chuong N. Nguyen 
  [mailto:Chuong.Nguyen@alcatel.com]<BR><B>Sent:</B> Tuesday, April 02, 2002 
  2:59 PM<BR><B>Cc:</B> megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] 
  Local/Remote descriptors and Permanent terminations<BR><BR></FONT></DIV>&nbsp; 
  <BR>So what was that discussion about adding silence suppression to 
  TDM&nbsp;package? 
  <P>Do we use SDP&nbsp;TDM&nbsp;or TDM&nbsp;package or both? <BR>Or even worse 
  combination of both within 1 command w/some parameters defined by 
  TDM&nbsp;package and <BR>some parameters defined by SDP TDM. <BR>&nbsp; 
  <BR>&nbsp; 
  <P>Tom-PT Taylor wrote: 
  <BLOCKQUOTE TYPE="CITE">As I noted earlier, you do need to specify the 
    properties in the NAS case. <BR>The SDP TDM draft has certainly had time to 
    ripen, and I will reissue it and <BR>the NAS packages within the next week. 
    <P>-----Original Message----- <BR>From: Chuong N. Nguyen [<A 
    href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>] 
    <BR>Sent: Tuesday, April 02, 2002 2:48 PM <BR>To: megaco@ietf.org 
    <BR>Subject: Re: [Megaco] Local/Remote descriptors and Permanent 
    terminations <BR>&nbsp; 
    <P>I don't know about the sendrecv issue here. <BR>I don't know what you 
    mean by SDP parameters are of no significance in case <BR>of phy. term. 
    <BR>Tom wrote the SDP TDM draft which I wonder what is the status of this 
    draft. 
    <P>But I can't remember now whether it was intended to be used in local or 
    <BR>localControl Descriptor. <BR>&nbsp; 
    <P>Madhu Babu Brahmanapally wrote: <BR>HI Rajesh/All, <BR>Not all parameters 
    might be useful for the MG/MGC in case of physical <BR>terminations. The SDP 
    parameters are of no significance in case of physical <BR>terminations (in 
    normal scenario). Hence the mode was set to "sendrecv" <BR>without 
    specifying the local/remote descriptor information. <BR>Regards 
    <BR>Madhubabu <BR>-----Original Message----- <BR>From: megaco-admin@ietf.org 
    [<A href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]On 
    Behalf Of <BR>Rajesh N <BR>Sent: Tuesday, April 02, 2002 11:32 AM <BR>To: 
    megaco@ietf.org <BR>Subject: [Megaco] Local/Remote descriptors and Permanent 
    terminations <BR>Hi, <BR>Sometime back there was a thread regarding usage of 
    SendRecv mode for an <BR>ephemeral termination, when Remote Descriptor 
    values are yet to be defined. <BR>And one of the choices for the MG in such 
    a situation is to reply back with <BR>error 411, "missing remote or local 
    descriptor". <BR>I would like to know, what is the significance of this 
    problem w.r.to <BR>permanent terminations. The example call flow in the 
    draft shows a Modify <BR>request for a permanent termination, from MGC to 
    MG1, in which mode is set <BR>as SendRecv and&nbsp; the Local descriptor 
    values alone are being provided. <BR>Are local and remote descriptors 
    relevant for physical terminations? If <BR>yes, where should I get the 
    values from? <BR>Thanks <BR>Regards, <BR>Rajesh N 
    <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>[This E-mail was scanned for viruses and is clean.] 
    <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; Alcatel USA, 
    Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Internet: Chuong.Nguyen@usa.alcatel.com <BR>&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; **** The opinions 
    expressed are not those of Alcatel USA, Inc **** <BR>&nbsp;</P></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; 
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1DA83.97D871C0--

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


From daemon@ns.ietf.org  Tue Apr  2 15:41: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 PAA02394
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 15:41:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA12214
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 15:41: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 PAA10874;
	Tue, 2 Apr 2002 15:20: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 PAA10773
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 15:20:03 -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 PAA01259
	for <megaco@ietf.org>; Tue, 2 Apr 2002 15:19:54 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0M8D>; Tue, 2 Apr 2002 15:18:50 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C44@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 15:18:46 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DA83.97D871C0"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1DA83.97D871C0
Content-Type: text/plain;
	charset="iso-8859-1"

Chuong,
 
There was several ideas bouncing around but I don't believe
there was any closure.  There is a hole for G711 since we can't use 
annexa or annexb.
Lifting the support in RFC 3108, section 5.6.3.2 and putting it into
the TDM Circuit Package would give us a lot of flexibility.
 
Here are the ideas I know of:
1)
Another option is to extend the TDM Circuit Package (which has been

previously discussed on the list). The TDM Cicruit Package

currently has Gain and Echo Control as its properties. So, it's logical

(IMO) for Silence Suppression to be part of the package as

well. In fact, it looks like an oversight that it was missed off in the

first place.

Regards,

Wayne Cutler

2)

Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.  E.g.: 

Media={Stream=1{ Local { 
v=0 
c=IN IP4 $ 
m=audio $ RTP/AVP 0 13 
}}}

David Barr 

3)

I'm starting to think that the answer may be to use the a=silenceSupp 
attribute defined in RFC 3108, section 5.6.3.2. 

Tom Taylor

 

Carl

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 2:59 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
So what was that discussion about adding silence suppression to TDM package?


Do we use SDP TDM or TDM package or both? 
Or even worse combination of both within 1 command w/some parameters defined
by TDM package and 
some parameters defined by SDP TDM. 
  
  


Tom-PT Taylor wrote: 


As I noted earlier, you do need to specify the properties in the NAS case. 
The SDP TDM draft has certainly had time to ripen, and I will reissue it and

the NAS packages within the next week. 

-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 2:48 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations 
  


I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case 
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.



But I can't remember now whether it was intended to be used in local or 
localControl Descriptor. 
  


Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [ mailto:megaco-admin@ietf.org
<mailto:megaco-admin@ietf.org> ]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<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 **** 
 

-- 

  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_01C1DA83.97D871C0
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">


<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2>Chuong,</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff size=2>There 
was several ideas bouncing around but I don't believe</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff size=2>there 
was any closure.&nbsp; There is a hole for G711 since we can't use 
</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff size=2>annexa 
or annexb.</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2>Lifting the support in <FONT face="Times New Roman" color=#000000>RFC 
3108, section 5.6.3.2 and putting it into</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT size=2>the TDM Circuit Package would 
give us a lot of flexibility.</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff size=2>Here 
are the ideas I know of:</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2>1)</FONT></SPAN></DIV>
<DIV><SPAN class=491101120-02042002>
<P><FONT face=Arial color=#0000ff size=2>Another option is to extend the TDM 
Circuit Package (which has been</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>previously discussed on the list). The 
TDM Cicruit Package</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>currently has Gain and Echo Control as 
its properties. So, it's logical</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>(IMO) for Silence Suppression to be 
part of the package as</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>well. In fact, it looks like an 
oversight that it was missed off in the</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>first place.</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>Regards,</FONT></P>
<P><FONT face=Arial><FONT color=#0000ff><FONT size=2>Wayne<SPAN 
class=491101120-02042002> Cutler</SPAN></FONT></FONT></FONT></P>
<P><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2>2)</FONT></SPAN></P><SPAN class=491101120-02042002>
<P><FONT size=2>Another possibility is to use payload 13 as defined in 
draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</FONT> </P>
<P><FONT size=2>Media={Stream=1{ Local {</FONT> <BR><FONT size=2>v=0</FONT> 
<BR><FONT size=2>c=IN IP4 $</FONT> <BR><FONT size=2>m=audio $ RTP/AVP 0 
13</FONT> <BR><FONT size=2>}}}</FONT></P>
<P><SPAN class=491101120-02042002><FONT size=2>David 
Barr</FONT></SPAN>&nbsp;</P>
<P><SPAN class=491101120-02042002><FONT size=2>3)</FONT></SPAN></P>
<P><SPAN class=491101120-02042002></SPAN><SPAN class=491101120-02042002><FONT 
size=2>I'm starting to think that the answer may be to use the a=silenceSupp 
<BR>attribute defined in RFC 3108, section 5.6.3.2. </FONT></P>
<P><SPAN class=491101120-02042002><FONT size=2>Tom Taylor</FONT></SPAN></P>
<P><FONT size=2></FONT>&nbsp;</P>
<P><SPAN class=491101120-02042002><FONT face=Arial color=#0000ff 
size=2>Carl</FONT></SPAN></P></SPAN></SPAN></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Chuong N. Nguyen 
  [mailto:Chuong.Nguyen@alcatel.com]<BR><B>Sent:</B> Tuesday, April 02, 2002 
  2:59 PM<BR><B>Cc:</B> megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] 
  Local/Remote descriptors and Permanent terminations<BR><BR></FONT></DIV>&nbsp; 
  <BR>So what was that discussion about adding silence suppression to 
  TDM&nbsp;package? 
  <P>Do we use SDP&nbsp;TDM&nbsp;or TDM&nbsp;package or both? <BR>Or even worse 
  combination of both within 1 command w/some parameters defined by 
  TDM&nbsp;package and <BR>some parameters defined by SDP TDM. <BR>&nbsp; 
  <BR>&nbsp; 
  <P>Tom-PT Taylor wrote: 
  <BLOCKQUOTE TYPE="CITE">As I noted earlier, you do need to specify the 
    properties in the NAS case. <BR>The SDP TDM draft has certainly had time to 
    ripen, and I will reissue it and <BR>the NAS packages within the next week. 
    <P>-----Original Message----- <BR>From: Chuong N. Nguyen [<A 
    href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>] 
    <BR>Sent: Tuesday, April 02, 2002 2:48 PM <BR>To: megaco@ietf.org 
    <BR>Subject: Re: [Megaco] Local/Remote descriptors and Permanent 
    terminations <BR>&nbsp; 
    <P>I don't know about the sendrecv issue here. <BR>I don't know what you 
    mean by SDP parameters are of no significance in case <BR>of phy. term. 
    <BR>Tom wrote the SDP TDM draft which I wonder what is the status of this 
    draft. 
    <P>But I can't remember now whether it was intended to be used in local or 
    <BR>localControl Descriptor. <BR>&nbsp; 
    <P>Madhu Babu Brahmanapally wrote: <BR>HI Rajesh/All, <BR>Not all parameters 
    might be useful for the MG/MGC in case of physical <BR>terminations. The SDP 
    parameters are of no significance in case of physical <BR>terminations (in 
    normal scenario). Hence the mode was set to "sendrecv" <BR>without 
    specifying the local/remote descriptor information. <BR>Regards 
    <BR>Madhubabu <BR>-----Original Message----- <BR>From: megaco-admin@ietf.org 
    [<A href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]On 
    Behalf Of <BR>Rajesh N <BR>Sent: Tuesday, April 02, 2002 11:32 AM <BR>To: 
    megaco@ietf.org <BR>Subject: [Megaco] Local/Remote descriptors and Permanent 
    terminations <BR>Hi, <BR>Sometime back there was a thread regarding usage of 
    SendRecv mode for an <BR>ephemeral termination, when Remote Descriptor 
    values are yet to be defined. <BR>And one of the choices for the MG in such 
    a situation is to reply back with <BR>error 411, "missing remote or local 
    descriptor". <BR>I would like to know, what is the significance of this 
    problem w.r.to <BR>permanent terminations. The example call flow in the 
    draft shows a Modify <BR>request for a permanent termination, from MGC to 
    MG1, in which mode is set <BR>as SendRecv and&nbsp; the Local descriptor 
    values alone are being provided. <BR>Are local and remote descriptors 
    relevant for physical terminations? If <BR>yes, where should I get the 
    values from? <BR>Thanks <BR>Regards, <BR>Rajesh N 
    <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>[This E-mail was scanned for viruses and is clean.] 
    <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; Alcatel USA, 
    Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Internet: Chuong.Nguyen@usa.alcatel.com <BR>&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; **** The opinions 
    expressed are not those of Alcatel USA, Inc **** <BR>&nbsp;</P></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; 
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1DA83.97D871C0--

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



From megaco-admin@ietf.org  Tue Apr  2 16:03: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 QAA03363
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 16: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 PAA12317;
	Tue, 2 Apr 2002 15:42: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 PAA12281
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 15:41:57 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02569
	for <megaco@ietf.org>; Tue, 2 Apr 2002 15:41:55 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g32KfQV17233
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:41:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g32KedO26513
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:40:40 -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 g32Ked726293
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:40:39 -0600 (CST)
Message-ID: <3CAA1746.297E27B@alcatel.com>
Date: Tue, 02 Apr 2002 14:40:39 -0600
From: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <2415C206C515244DBFB12EC0C064A448404C44@wench>
Content-Type: multipart/alternative;
 boundary="------------DE067D1398926FF28E6A8260"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


I thought the reason that we decided to have SDP TDM is to get away from
TDM package
to be more inline w/how we specify RTP termination characteristics.
Also to reuse the good stuffs from RTP/ATM SDP.

I guess we can start by asking the questions

1) Can we live w/o the TDM package?
2) Can we just use SDP for TDM going forward?
3) For backward compatibility, just leave TDM package as is and don't
extend it anymore.

For the TDM package, echo control is understood but the Gain control is
not quite right.
I have discussed the Gain control before and gotten nowhere.

Gain control is also defined in the SDP for ATM which seems more
correct.



Carl Rutter wrote:

> Chuong,There was several ideas bouncing around but I don't
> believethere was any closure.  There is a hole for G711 since we can't
> use annexa or annexb.Lifting the support in RFC 3108, section 5.6.3.2
> and putting it intothe TDM Circuit Package would give us a lot of
> flexibility.Here are the ideas I know of:1)
>
> Another option is to extend the TDM Circuit Package (which has been
>
> previously discussed on the list). The TDM Cicruit Package
>
> currently has Gain and Echo Control as its properties. So, it's
> logical
>
> (IMO) for Silence Suppression to be part of the package as
>
> well. In fact, it looks like an oversight that it was missed off in
> the
>
> first place.
>
> Regards,
>
> Wayne Cutler
>
> 2)
>
> Another possibility is to use payload 13 as defined in
> draft-ietf-avt-rtp-cn-05.  E.g.:
>
> Media={Stream=1{ Local {
> v=0
> c=IN IP4 $
> m=audio $ RTP/AVP 0 13
> }}}
>
> David Barr
>
> 3)
>
> I'm starting to think that the answer may be to use the a=silenceSupp
> attribute defined in RFC 3108, section 5.6.3.2.
>
> Tom Taylor
>
>
>
> Carl
>
>      -----Original Message-----
>      From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
>      Sent: Tuesday, April 02, 2002 2:59 PM
>      Cc: megaco@ietf.org
>      Subject: Re: [Megaco] Local/Remote descriptors and Permanent
>      terminations
>
>
>      So what was that discussion about adding silence suppression
>      to TDM package?
>
>      Do we use SDP TDM or TDM package or both?
>      Or even worse combination of both within 1 command w/some
>      parameters defined by TDM package and
>      some parameters defined by SDP TDM.
>
>
>
>      Tom-PT Taylor wrote:
>
>     > As I noted earlier, you do need to specify the properties
>     > in the NAS case.
>     > The SDP TDM draft has certainly had time to ripen, and I
>     > will reissue it and
>     > the NAS packages within the next week.
>     >
>     > -----Original Message-----
>     > From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
>     > Sent: Tuesday, April 02, 2002 2:48 PM
>     > To: megaco@ietf.org
>     > Subject: Re: [Megaco] Local/Remote descriptors and
>     > Permanent terminations
>     >
>     >
>     > I don't know about the sendrecv issue here.
>     > I don't know what you mean by SDP parameters are of no
>     > significance in case
>     > of phy. term.
>     > Tom wrote the SDP TDM draft which I wonder what is the
>     > status of this draft.
>     >
>     > But I can't remember now whether it was intended to be
>     > used in local or
>     > localControl Descriptor.
>     >
>     >
>     > Madhu Babu Brahmanapally wrote:
>     > HI Rajesh/All,
>     > Not all parameters might be useful for the MG/MGC in case
>     > of physical
>     > terminations. The SDP parameters are of no significance in
>     > case of physical
>     > terminations (in normal scenario). Hence the mode was set
>     > to "sendrecv"
>     > without specifying the local/remote descriptor
>     > information.
>     > Regards
>     > Madhubabu
>     > -----Original Message-----
>     > From: megaco-admin@ietf.org
>     > [mailto:megaco-admin@ietf.org]On Behalf Of
>     > Rajesh N
>     > Sent: Tuesday, April 02, 2002 11:32 AM
>     > To: megaco@ietf.org
>     > Subject: [Megaco] Local/Remote descriptors and Permanent
>     > terminations
>     > Hi,
>     > Sometime back there was a thread regarding usage of
>     > SendRecv mode for an
>     > ephemeral termination, when Remote Descriptor values are
>     > yet to be defined.
>     > And one of the choices for the MG in such a situation is
>     > to reply back with
>     > error 411, "missing remote or local descriptor".
>     > I would like to know, what is the significance of this
>     > problem w.r.to
>     > permanent terminations. The example call flow in the draft
>     > shows a Modify
>     > request for a permanent termination, from MGC to MG1, in
>     > which mode is set
>     > as SendRecv and  the Local descriptor values alone are
>     > being provided.
>     > Are local and remote descriptors relevant for physical
>     > terminations? If
>     > yes, where should I get the values from?
>     > Thanks
>     > Regards,
>     > Rajesh N
>     > _______________________________________________
>     > Megaco mailing list
>     > Megaco@ietf.org
>     > https://www1.ietf.org/mailman/listinfo/megaco
>     > ---
>     > [This E-mail was scanned for viruses and is clean.]
>     > _______________________________________________
>     > 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 ****
>     >
>
>      --
>        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 ****



--------------DE067D1398926FF28E6A8260
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;thought the reason that we decided to have SDP TDM is to get
away from TDM&nbsp;package
<br>to be more inline w/how we specify RTP&nbsp;termination characteristics.
<br>Also to reuse the good stuffs from RTP/ATM SDP.
<p>I guess we can start by asking the questions
<p>1) Can we live w/o the TDM package?
<br>2) Can we just use SDP for TDM going forward?
<br>3) For backward compatibility, just leave TDM&nbsp;package as is and
don't extend it anymore.
<p>For the TDM package, echo control is understood but the Gain control
is not quite right.
<br>I&nbsp;have discussed the Gain control before and gotten nowhere.
<p>Gain control is also defined in the SDP&nbsp;for ATM which seems more
correct.
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE=CITE><span class=491101120-02042002><font size=-1><font face="Arial"><font color="#0000FF">Chuong,</span><span class=491101120-02042002></span><span class=491101120-02042002>There
was several ideas bouncing around but I don't believe</span><span class=491101120-02042002>there
was any closure.&nbsp; There is a hole for G711 since we can't use&nbsp;</span><span class=491101120-02042002>annexa
or annexb.</span><span class=491101120-02042002>Lifting the support in
</font></font><font face="Times New Roman"><font color="#000000">RFC 3108,
section 5.6.3.2 and putting it into</span><span class=491101120-02042002></font></font>the
TDM Circuit Package would give us a lot of flexibility.</span><span class=491101120-02042002></span><span class=491101120-02042002><font face="Arial"><font color="#0000FF">Here
are the ideas I know of:</span><span class=491101120-02042002>1)</font></font></font></span><span class=491101120-02042002>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Another option
is to extend the TDM Circuit Package (which has been</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>previously discussed
on the list). The TDM Cicruit Package</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>currently has
Gain and Echo Control as its properties. So, it's logical</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>(IMO) for Silence
Suppression to be part of the package as</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>well. In fact,
it looks like an oversight that it was missed off in the</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>first place.</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Regards,</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Wayne<span 
class=491101120-02042002>
Cutler</font></font></font></span>
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>2)</font></font></font></span>
<br><span class=491101120-02042002>
<p><font size=-1>Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</font>
<p><font size=-1>Media={Stream=1{ Local {</font>
<br><font size=-1>v=0</font>
<br><font size=-1>c=IN IP4 $</font>
<br><font size=-1>m=audio $ RTP/AVP 0 13</font>
<br><font size=-1>}}}</font>
<p><span class=491101120-02042002><font size=-1>David Barr</font></span>
<p><span class=491101120-02042002><font size=-1>3)</font></span>
<p><span class=491101120-02042002></span><span class=491101120-02042002><font size=-1>I'm
starting to think that the answer may be to use the a=silenceSupp</font>
<br><font size=-1>attribute defined in RFC 3108, section 5.6.3.2.</font>
<p><span class=491101120-02042002><font size=-1>Tom Taylor</font></span>
<br>&nbsp;
<br>&nbsp;
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>Carl</font></font></font></span>
<br></span></span></span>
<blockquote>
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<A HREF="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
2:59 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>Cc:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>

<p><br>So what was that discussion about adding silence suppression to
TDM package?
<p>Do we use SDP TDM or TDM package or both?
<br>Or even worse combination of both within 1 command w/some parameters
defined by TDM package and
<br>some parameters defined by SDP TDM.
<br>&nbsp;
<br>&nbsp;
<p>Tom-PT Taylor wrote:
<blockquote TYPE="CITE">As I noted earlier, you do need to specify the
properties in the NAS case.
<br>The SDP TDM draft has certainly had time to ripen, and I will reissue
it and
<br>the NAS packages within the next week.
<p>-----Original Message-----
<br>From: Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]
<br>Sent: Tuesday, April 02, 2002 2:48 PM
<br>To: megaco@ietf.org
<br>Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
<br>&nbsp;
<p>I don't know about the sendrecv issue here.
<br>I don't know what you mean by SDP parameters are of no significance
in case
<br>of phy. term.
<br>Tom wrote the SDP TDM draft which I wonder what is the status of this
draft.
<p>But I can't remember now whether it was intended to be used in local
or
<br>localControl Descriptor.
<br>&nbsp;
<p>Madhu Babu Brahmanapally wrote:
<br>HI Rajesh/All,
<br>Not all parameters might be useful for the MG/MGC in case of physical
<br>terminations. The SDP parameters are of no significance in case of
physical
<br>terminations (in normal scenario). Hence the mode was set to "sendrecv"
<br>without specifying the local/remote descriptor information.
<br>Regards
<br>Madhubabu
<br>-----Original Message-----
<br>From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]On
Behalf Of
<br>Rajesh N
<br>Sent: Tuesday, April 02, 2002 11:32 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Local/Remote descriptors and Permanent terminations
<br>Hi,
<br>Sometime back there was a thread regarding usage of SendRecv mode for
an
<br>ephemeral termination, when Remote Descriptor values are yet to be
defined.
<br>And one of the choices for the MG in such a situation is to reply back
with
<br>error 411, "missing remote or local descriptor".
<br>I would like to know, what is the significance of this problem w.r.to
<br>permanent terminations. The example call flow in the draft shows a
Modify
<br>request for a permanent termination, from MGC to MG1, in which mode
is set
<br>as SendRecv and&nbsp; the Local descriptor values alone are being provided.
<br>Are local and remote descriptors relevant for physical terminations?
If
<br>yes, where should I get the values from?
<br>Thanks
<br>Regards,
<br>Rajesh N
<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>[This E-mail was scanned for viruses and is clean.]
<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; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>&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; **** The opinions expressed are not those of Alcatel USA, Inc
****
<br>&nbsp;</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;</blockquote>
</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>

--------------DE067D1398926FF28E6A8260--


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


From daemon@ns.ietf.org  Tue Apr  2 16:03: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 QAA03372
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 16:03:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA13665
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 16:03: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 PAA12317;
	Tue, 2 Apr 2002 15:42: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 PAA12281
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 15:41:57 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02569
	for <megaco@ietf.org>; Tue, 2 Apr 2002 15:41:55 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g32KfQV17233
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:41:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g32KedO26513
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:40:40 -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 g32Ked726293
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:40:39 -0600 (CST)
Message-ID: <3CAA1746.297E27B@alcatel.com>
Date: Tue, 02 Apr 2002 14:40:39 -0600
From: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <2415C206C515244DBFB12EC0C064A448404C44@wench>
Content-Type: multipart/alternative;
 boundary="------------DE067D1398926FF28E6A8260"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


I thought the reason that we decided to have SDP TDM is to get away from
TDM package
to be more inline w/how we specify RTP termination characteristics.
Also to reuse the good stuffs from RTP/ATM SDP.

I guess we can start by asking the questions

1) Can we live w/o the TDM package?
2) Can we just use SDP for TDM going forward?
3) For backward compatibility, just leave TDM package as is and don't
extend it anymore.

For the TDM package, echo control is understood but the Gain control is
not quite right.
I have discussed the Gain control before and gotten nowhere.

Gain control is also defined in the SDP for ATM which seems more
correct.



Carl Rutter wrote:

> Chuong,There was several ideas bouncing around but I don't
> believethere was any closure.  There is a hole for G711 since we can't
> use annexa or annexb.Lifting the support in RFC 3108, section 5.6.3.2
> and putting it intothe TDM Circuit Package would give us a lot of
> flexibility.Here are the ideas I know of:1)
>
> Another option is to extend the TDM Circuit Package (which has been
>
> previously discussed on the list). The TDM Cicruit Package
>
> currently has Gain and Echo Control as its properties. So, it's
> logical
>
> (IMO) for Silence Suppression to be part of the package as
>
> well. In fact, it looks like an oversight that it was missed off in
> the
>
> first place.
>
> Regards,
>
> Wayne Cutler
>
> 2)
>
> Another possibility is to use payload 13 as defined in
> draft-ietf-avt-rtp-cn-05.  E.g.:
>
> Media={Stream=1{ Local {
> v=0
> c=IN IP4 $
> m=audio $ RTP/AVP 0 13
> }}}
>
> David Barr
>
> 3)
>
> I'm starting to think that the answer may be to use the a=silenceSupp
> attribute defined in RFC 3108, section 5.6.3.2.
>
> Tom Taylor
>
>
>
> Carl
>
>      -----Original Message-----
>      From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
>      Sent: Tuesday, April 02, 2002 2:59 PM
>      Cc: megaco@ietf.org
>      Subject: Re: [Megaco] Local/Remote descriptors and Permanent
>      terminations
>
>
>      So what was that discussion about adding silence suppression
>      to TDM package?
>
>      Do we use SDP TDM or TDM package or both?
>      Or even worse combination of both within 1 command w/some
>      parameters defined by TDM package and
>      some parameters defined by SDP TDM.
>
>
>
>      Tom-PT Taylor wrote:
>
>     > As I noted earlier, you do need to specify the properties
>     > in the NAS case.
>     > The SDP TDM draft has certainly had time to ripen, and I
>     > will reissue it and
>     > the NAS packages within the next week.
>     >
>     > -----Original Message-----
>     > From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
>     > Sent: Tuesday, April 02, 2002 2:48 PM
>     > To: megaco@ietf.org
>     > Subject: Re: [Megaco] Local/Remote descriptors and
>     > Permanent terminations
>     >
>     >
>     > I don't know about the sendrecv issue here.
>     > I don't know what you mean by SDP parameters are of no
>     > significance in case
>     > of phy. term.
>     > Tom wrote the SDP TDM draft which I wonder what is the
>     > status of this draft.
>     >
>     > But I can't remember now whether it was intended to be
>     > used in local or
>     > localControl Descriptor.
>     >
>     >
>     > Madhu Babu Brahmanapally wrote:
>     > HI Rajesh/All,
>     > Not all parameters might be useful for the MG/MGC in case
>     > of physical
>     > terminations. The SDP parameters are of no significance in
>     > case of physical
>     > terminations (in normal scenario). Hence the mode was set
>     > to "sendrecv"
>     > without specifying the local/remote descriptor
>     > information.
>     > Regards
>     > Madhubabu
>     > -----Original Message-----
>     > From: megaco-admin@ietf.org
>     > [mailto:megaco-admin@ietf.org]On Behalf Of
>     > Rajesh N
>     > Sent: Tuesday, April 02, 2002 11:32 AM
>     > To: megaco@ietf.org
>     > Subject: [Megaco] Local/Remote descriptors and Permanent
>     > terminations
>     > Hi,
>     > Sometime back there was a thread regarding usage of
>     > SendRecv mode for an
>     > ephemeral termination, when Remote Descriptor values are
>     > yet to be defined.
>     > And one of the choices for the MG in such a situation is
>     > to reply back with
>     > error 411, "missing remote or local descriptor".
>     > I would like to know, what is the significance of this
>     > problem w.r.to
>     > permanent terminations. The example call flow in the draft
>     > shows a Modify
>     > request for a permanent termination, from MGC to MG1, in
>     > which mode is set
>     > as SendRecv and  the Local descriptor values alone are
>     > being provided.
>     > Are local and remote descriptors relevant for physical
>     > terminations? If
>     > yes, where should I get the values from?
>     > Thanks
>     > Regards,
>     > Rajesh N
>     > _______________________________________________
>     > Megaco mailing list
>     > Megaco@ietf.org
>     > https://www1.ietf.org/mailman/listinfo/megaco
>     > ---
>     > [This E-mail was scanned for viruses and is clean.]
>     > _______________________________________________
>     > 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 ****
>     >
>
>      --
>        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 ****



--------------DE067D1398926FF28E6A8260
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;thought the reason that we decided to have SDP TDM is to get
away from TDM&nbsp;package
<br>to be more inline w/how we specify RTP&nbsp;termination characteristics.
<br>Also to reuse the good stuffs from RTP/ATM SDP.
<p>I guess we can start by asking the questions
<p>1) Can we live w/o the TDM package?
<br>2) Can we just use SDP for TDM going forward?
<br>3) For backward compatibility, just leave TDM&nbsp;package as is and
don't extend it anymore.
<p>For the TDM package, echo control is understood but the Gain control
is not quite right.
<br>I&nbsp;have discussed the Gain control before and gotten nowhere.
<p>Gain control is also defined in the SDP&nbsp;for ATM which seems more
correct.
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE=CITE><span class=491101120-02042002><font size=-1><font face="Arial"><font color="#0000FF">Chuong,</span><span class=491101120-02042002></span><span class=491101120-02042002>There
was several ideas bouncing around but I don't believe</span><span class=491101120-02042002>there
was any closure.&nbsp; There is a hole for G711 since we can't use&nbsp;</span><span class=491101120-02042002>annexa
or annexb.</span><span class=491101120-02042002>Lifting the support in
</font></font><font face="Times New Roman"><font color="#000000">RFC 3108,
section 5.6.3.2 and putting it into</span><span class=491101120-02042002></font></font>the
TDM Circuit Package would give us a lot of flexibility.</span><span class=491101120-02042002></span><span class=491101120-02042002><font face="Arial"><font color="#0000FF">Here
are the ideas I know of:</span><span class=491101120-02042002>1)</font></font></font></span><span class=491101120-02042002>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Another option
is to extend the TDM Circuit Package (which has been</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>previously discussed
on the list). The TDM Cicruit Package</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>currently has
Gain and Echo Control as its properties. So, it's logical</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>(IMO) for Silence
Suppression to be part of the package as</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>well. In fact,
it looks like an oversight that it was missed off in the</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>first place.</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Regards,</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Wayne<span 
class=491101120-02042002>
Cutler</font></font></font></span>
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>2)</font></font></font></span>
<br><span class=491101120-02042002>
<p><font size=-1>Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</font>
<p><font size=-1>Media={Stream=1{ Local {</font>
<br><font size=-1>v=0</font>
<br><font size=-1>c=IN IP4 $</font>
<br><font size=-1>m=audio $ RTP/AVP 0 13</font>
<br><font size=-1>}}}</font>
<p><span class=491101120-02042002><font size=-1>David Barr</font></span>
<p><span class=491101120-02042002><font size=-1>3)</font></span>
<p><span class=491101120-02042002></span><span class=491101120-02042002><font size=-1>I'm
starting to think that the answer may be to use the a=silenceSupp</font>
<br><font size=-1>attribute defined in RFC 3108, section 5.6.3.2.</font>
<p><span class=491101120-02042002><font size=-1>Tom Taylor</font></span>
<br>&nbsp;
<br>&nbsp;
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>Carl</font></font></font></span>
<br></span></span></span>
<blockquote>
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<A HREF="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
2:59 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>Cc:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>

<p><br>So what was that discussion about adding silence suppression to
TDM package?
<p>Do we use SDP TDM or TDM package or both?
<br>Or even worse combination of both within 1 command w/some parameters
defined by TDM package and
<br>some parameters defined by SDP TDM.
<br>&nbsp;
<br>&nbsp;
<p>Tom-PT Taylor wrote:
<blockquote TYPE="CITE">As I noted earlier, you do need to specify the
properties in the NAS case.
<br>The SDP TDM draft has certainly had time to ripen, and I will reissue
it and
<br>the NAS packages within the next week.
<p>-----Original Message-----
<br>From: Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]
<br>Sent: Tuesday, April 02, 2002 2:48 PM
<br>To: megaco@ietf.org
<br>Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
<br>&nbsp;
<p>I don't know about the sendrecv issue here.
<br>I don't know what you mean by SDP parameters are of no significance
in case
<br>of phy. term.
<br>Tom wrote the SDP TDM draft which I wonder what is the status of this
draft.
<p>But I can't remember now whether it was intended to be used in local
or
<br>localControl Descriptor.
<br>&nbsp;
<p>Madhu Babu Brahmanapally wrote:
<br>HI Rajesh/All,
<br>Not all parameters might be useful for the MG/MGC in case of physical
<br>terminations. The SDP parameters are of no significance in case of
physical
<br>terminations (in normal scenario). Hence the mode was set to "sendrecv"
<br>without specifying the local/remote descriptor information.
<br>Regards
<br>Madhubabu
<br>-----Original Message-----
<br>From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]On
Behalf Of
<br>Rajesh N
<br>Sent: Tuesday, April 02, 2002 11:32 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Local/Remote descriptors and Permanent terminations
<br>Hi,
<br>Sometime back there was a thread regarding usage of SendRecv mode for
an
<br>ephemeral termination, when Remote Descriptor values are yet to be
defined.
<br>And one of the choices for the MG in such a situation is to reply back
with
<br>error 411, "missing remote or local descriptor".
<br>I would like to know, what is the significance of this problem w.r.to
<br>permanent terminations. The example call flow in the draft shows a
Modify
<br>request for a permanent termination, from MGC to MG1, in which mode
is set
<br>as SendRecv and&nbsp; the Local descriptor values alone are being provided.
<br>Are local and remote descriptors relevant for physical terminations?
If
<br>yes, where should I get the values from?
<br>Thanks
<br>Regards,
<br>Rajesh N
<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>[This E-mail was scanned for viruses and is clean.]
<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; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>&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; **** The opinions expressed are not those of Alcatel USA, Inc
****
<br>&nbsp;</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;</blockquote>
</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>

--------------DE067D1398926FF28E6A8260--


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



From megaco-admin@ietf.org  Tue Apr  2 16:18: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 QAA03879
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 16:18: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 PAA12841;
	Tue, 2 Apr 2002 15:51: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 PAA12736
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 15:51:34 -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 PAA02959
	for <megaco@ietf.org>; Tue, 2 Apr 2002 15:51:32 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0NCJ>; Tue, 2 Apr 2002 15:51:03 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C46@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 15:51:02 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DA88.197FAE10"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1DA88.197FAE10
Content-Type: text/plain;
	charset="iso-8859-1"

All good questions another I would add is:
If we use SDP for TDM going forward 
how is silence suppression implemented?
 

Carl 

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 3:41 PM
To: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
I thought the reason that we decided to have SDP TDM is to get away from TDM
package 
to be more inline w/how we specify RTP termination characteristics. 
Also to reuse the good stuffs from RTP/ATM SDP. 

I guess we can start by asking the questions 


1) Can we live w/o the TDM package? 
2) Can we just use SDP for TDM going forward? 
3) For backward compatibility, just leave TDM package as is and don't extend
it anymore. 


For the TDM package, echo control is understood but the Gain control is not
quite right. 
I have discussed the Gain control before and gotten nowhere. 


Gain control is also defined in the SDP for ATM which seems more correct. 
  
  


Carl Rutter wrote: 


Chuong,There was several ideas bouncing around but I don't believethere was
any closure.  There is a hole for G711 since we can't use annexa or
annexb.Lifting the support in RFC 3108, section 5.6.3.2 and putting it
intothe TDM Circuit Package would give us a lot of flexibility.Here are the
ideas I know of:1) 

Another option is to extend the TDM Circuit Package (which has been 


previously discussed on the list). The TDM Cicruit Package 


currently has Gain and Echo Control as its properties. So, it's logical 


(IMO) for Silence Suppression to be part of the package as 


well. In fact, it looks like an oversight that it was missed off in the 


first place. 


Regards, 


Wayne Cutler 


2) 



Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.  E.g.: 


Media={Stream=1{ Local { 
v=0 
c=IN IP4 $ 
m=audio $ RTP/AVP 0 13 
}}} 


David Barr 


3) 


I'm starting to think that the answer may be to use the a=silenceSupp 
attribute defined in RFC 3108, section 5.6.3.2. 


Tom Taylor 
  
  


Carl 



-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 2:59 PM 
Cc: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


So what was that discussion about adding silence suppression to TDM package?



Do we use SDP TDM or TDM package or both? 
Or even worse combination of both within 1 command w/some parameters defined
by TDM package and 
some parameters defined by SDP TDM. 
  
  


Tom-PT Taylor wrote: 


As I noted earlier, you do need to specify the properties in the NAS case. 
The SDP TDM draft has certainly had time to ripen, and I will reissue it and

the NAS packages within the next week. 

-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 2:48 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations 
  


I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case 
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.



But I can't remember now whether it was intended to be used in local or 
localControl Descriptor. 
  


Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [ mailto:megaco-admin@ietf.org
<mailto:megaco-admin@ietf.org> ]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<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 **** 
 

-- 

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


------_=_NextPart_001_01C1DA88.197FAE10
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">


<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=967084920-02042002>All 
good questions another I would add is:</SPAN></FONT></DIV>
<DIV><SPAN class=967084920-02042002>If we use SDP for TDM going forward 
</SPAN></DIV>
<DIV><SPAN class=967084920-02042002>how is silence suppression 
implemented?</SPAN></DIV>
<DIV><SPAN class=967084920-02042002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=967084920-02042002><BR>Carl&nbsp;</SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Chuong N. Nguyen 
  [mailto:Chuong.Nguyen@alcatel.com]<BR><B>Sent:</B> Tuesday, April 02, 2002 
  3:41 PM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] 
  Local/Remote descriptors and Permanent terminations<BR><BR></FONT></DIV>&nbsp; 
  <BR>I&nbsp;thought the reason that we decided to have SDP TDM is to get away 
  from TDM&nbsp;package <BR>to be more inline w/how we specify 
  RTP&nbsp;termination characteristics. <BR>Also to reuse the good stuffs from 
  RTP/ATM SDP. 
  <P>I guess we can start by asking the questions 
  <P>1) Can we live w/o the TDM package? <BR>2) Can we just use SDP for TDM 
  going forward? <BR>3) For backward compatibility, just leave TDM&nbsp;package 
  as is and don't extend it anymore. 
  <P>For the TDM package, echo control is understood but the Gain control is not 
  quite right. <BR>I&nbsp;have discussed the Gain control before and gotten 
  nowhere. 
  <P>Gain control is also defined in the SDP&nbsp;for ATM which seems more 
  correct. <BR>&nbsp; <BR>&nbsp; 
  <P>Carl Rutter wrote: 
  <BLOCKQUOTE TYPE="CITE"><SPAN class=491101120-02042002><FONT size=-1><FONT 
    face=Arial><FONT color=#0000ff>Chuong,</SPAN><SPAN 
    class=491101120-02042002></SPAN><SPAN class=491101120-02042002>There was 
    several ideas bouncing around but I don't believe</SPAN><SPAN 
    class=491101120-02042002>there was any closure.&nbsp; There is a hole for 
    G711 since we can't use&nbsp;</SPAN><SPAN class=491101120-02042002>annexa or 
    annexb.</SPAN><SPAN class=491101120-02042002>Lifting the support in 
    </FONT></FONT><FONT face="Times New Roman"><FONT color=#000000>RFC 3108, 
    section 5.6.3.2 and putting it into</SPAN><SPAN 
    class=491101120-02042002></FONT></FONT>the TDM Circuit Package would give us 
    a lot of flexibility.</SPAN><SPAN class=491101120-02042002></SPAN><SPAN 
    class=491101120-02042002><FONT face=Arial><FONT color=#0000ff>Here are the 
    ideas I know of:</SPAN><SPAN 
    class=491101120-02042002>1)</FONT></FONT></FONT></SPAN><SPAN 
    class=491101120-02042002> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>Another option is to 
    extend the TDM Circuit Package (which has been</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>previously discussed 
    on the list). The TDM Cicruit Package</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>currently has Gain and 
    Echo Control as its properties. So, it's logical</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>(IMO) for Silence 
    Suppression to be part of the package as</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>well. In fact, it 
    looks like an oversight that it was missed off in the</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>first 
    place.</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT 
    size=-1>Regards,</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>Wayne<SPAN 
    class=491101120-02042002> Cutler</FONT></FONT></FONT></SPAN> 
    <P><SPAN class=491101120-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
    size=-1>2)</FONT></FONT></FONT></SPAN> <BR><SPAN class=491101120-02042002>
    <P><FONT size=-1>Another possibility is to use payload 13 as defined in 
    draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</FONT> 
    <P><FONT size=-1>Media={Stream=1{ Local {</FONT> <BR><FONT 
    size=-1>v=0</FONT> <BR><FONT size=-1>c=IN IP4 $</FONT> <BR><FONT 
    size=-1>m=audio $ RTP/AVP 0 13</FONT> <BR><FONT size=-1>}}}</FONT> 
    <P><SPAN class=491101120-02042002><FONT size=-1>David Barr</FONT></SPAN> 
    <P><SPAN class=491101120-02042002><FONT size=-1>3)</FONT></SPAN> 
    <P><SPAN class=491101120-02042002></SPAN><SPAN 
    class=491101120-02042002><FONT size=-1>I'm starting to think that the answer 
    may be to use the a=silenceSupp</FONT> <BR><FONT size=-1>attribute defined 
    in RFC 3108, section 5.6.3.2.</FONT> 
    <P><SPAN class=491101120-02042002><FONT size=-1>Tom Taylor</FONT></SPAN> 
    <BR>&nbsp; <BR>&nbsp; 
    <P><SPAN class=491101120-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
    size=-1>Carl</FONT></FONT></FONT></SPAN> <BR></SPAN></SPAN></SPAN>
    <BLOCKQUOTE>
      <DIV class=OutlookMessageHeader dir=ltr><FONT face=Tahoma><FONT 
      size=-1>-----Original Message-----</FONT></FONT> <BR><FONT 
      face=Tahoma><FONT size=-1><B>From:</B> Chuong N. Nguyen [<A 
      href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</FONT></FONT> 
      <BR><FONT face=Tahoma><FONT size=-1><B>Sent:</B> Tuesday, April 02, 2002 
      2:59 PM</FONT></FONT> <BR><FONT face=Tahoma><FONT size=-1><B>Cc:</B> 
      megaco@ietf.org</FONT></FONT> <BR><FONT face=Tahoma><FONT 
      size=-1><B>Subject:</B> Re: [Megaco] Local/Remote descriptors and 
      Permanent terminations</FONT></FONT></DIV>
      <P><BR>So what was that discussion about adding silence suppression to TDM 
      package? 
      <P>Do we use SDP TDM or TDM package or both? <BR>Or even worse combination 
      of both within 1 command w/some parameters defined by TDM package and 
      <BR>some parameters defined by SDP TDM. <BR>&nbsp; <BR>&nbsp; 
      <P>Tom-PT Taylor wrote: 
      <BLOCKQUOTE TYPE="CITE">As I noted earlier, you do need to specify the 
        properties in the NAS case. <BR>The SDP TDM draft has certainly had time 
        to ripen, and I will reissue it and <BR>the NAS packages within the next 
        week. 
        <P>-----Original Message----- <BR>From: Chuong N. Nguyen [<A 
        href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>] 
        <BR>Sent: Tuesday, April 02, 2002 2:48 PM <BR>To: megaco@ietf.org 
        <BR>Subject: Re: [Megaco] Local/Remote descriptors and Permanent 
        terminations <BR>&nbsp; 
        <P>I don't know about the sendrecv issue here. <BR>I don't know what you 
        mean by SDP parameters are of no significance in case <BR>of phy. term. 
        <BR>Tom wrote the SDP TDM draft which I wonder what is the status of 
        this draft. 
        <P>But I can't remember now whether it was intended to be used in local 
        or <BR>localControl Descriptor. <BR>&nbsp; 
        <P>Madhu Babu Brahmanapally wrote: <BR>HI Rajesh/All, <BR>Not all 
        parameters might be useful for the MG/MGC in case of physical 
        <BR>terminations. The SDP parameters are of no significance in case of 
        physical <BR>terminations (in normal scenario). Hence the mode was set 
        to "sendrecv" <BR>without specifying the local/remote descriptor 
        information. <BR>Regards <BR>Madhubabu <BR>-----Original Message----- 
        <BR>From: megaco-admin@ietf.org [<A 
        href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]On 
        Behalf Of <BR>Rajesh N <BR>Sent: Tuesday, April 02, 2002 11:32 AM 
        <BR>To: megaco@ietf.org <BR>Subject: [Megaco] Local/Remote descriptors 
        and Permanent terminations <BR>Hi, <BR>Sometime back there was a thread 
        regarding usage of SendRecv mode for an <BR>ephemeral termination, when 
        Remote Descriptor values are yet to be defined. <BR>And one of the 
        choices for the MG in such a situation is to reply back with <BR>error 
        411, "missing remote or local descriptor". <BR>I would like to know, 
        what is the significance of this problem w.r.to <BR>permanent 
        terminations. The example call flow in the draft shows a Modify 
        <BR>request for a permanent termination, from MGC to MG1, in which mode 
        is set <BR>as SendRecv and&nbsp; the Local descriptor values alone are 
        being provided. <BR>Are local and remote descriptors relevant for 
        physical terminations? If <BR>yes, where should I get the values from? 
        <BR>Thanks <BR>Regards, <BR>Rajesh N 
        <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>[This E-mail was scanned for viruses and is clean.] 
        <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; Alcatel USA, 
        Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
        Internet: Chuong.Nguyen@usa.alcatel.com <BR>&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; **** The opinions 
        expressed are not those of Alcatel USA, Inc **** 
      <BR>&nbsp;</P></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;</BLOCKQUOTE></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; 
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1DA88.197FAE10--

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


From daemon@ns.ietf.org  Tue Apr  2 16:18: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 QAA03893
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 16:18:15 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA14349
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 16: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 PAA12841;
	Tue, 2 Apr 2002 15:51: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 PAA12736
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 15:51:34 -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 PAA02959
	for <megaco@ietf.org>; Tue, 2 Apr 2002 15:51:32 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0NCJ>; Tue, 2 Apr 2002 15:51:03 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C46@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 15:51:02 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DA88.197FAE10"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1DA88.197FAE10
Content-Type: text/plain;
	charset="iso-8859-1"

All good questions another I would add is:
If we use SDP for TDM going forward 
how is silence suppression implemented?
 

Carl 

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 3:41 PM
To: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
I thought the reason that we decided to have SDP TDM is to get away from TDM
package 
to be more inline w/how we specify RTP termination characteristics. 
Also to reuse the good stuffs from RTP/ATM SDP. 

I guess we can start by asking the questions 


1) Can we live w/o the TDM package? 
2) Can we just use SDP for TDM going forward? 
3) For backward compatibility, just leave TDM package as is and don't extend
it anymore. 


For the TDM package, echo control is understood but the Gain control is not
quite right. 
I have discussed the Gain control before and gotten nowhere. 


Gain control is also defined in the SDP for ATM which seems more correct. 
  
  


Carl Rutter wrote: 


Chuong,There was several ideas bouncing around but I don't believethere was
any closure.  There is a hole for G711 since we can't use annexa or
annexb.Lifting the support in RFC 3108, section 5.6.3.2 and putting it
intothe TDM Circuit Package would give us a lot of flexibility.Here are the
ideas I know of:1) 

Another option is to extend the TDM Circuit Package (which has been 


previously discussed on the list). The TDM Cicruit Package 


currently has Gain and Echo Control as its properties. So, it's logical 


(IMO) for Silence Suppression to be part of the package as 


well. In fact, it looks like an oversight that it was missed off in the 


first place. 


Regards, 


Wayne Cutler 


2) 



Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.  E.g.: 


Media={Stream=1{ Local { 
v=0 
c=IN IP4 $ 
m=audio $ RTP/AVP 0 13 
}}} 


David Barr 


3) 


I'm starting to think that the answer may be to use the a=silenceSupp 
attribute defined in RFC 3108, section 5.6.3.2. 


Tom Taylor 
  
  


Carl 



-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 2:59 PM 
Cc: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


So what was that discussion about adding silence suppression to TDM package?



Do we use SDP TDM or TDM package or both? 
Or even worse combination of both within 1 command w/some parameters defined
by TDM package and 
some parameters defined by SDP TDM. 
  
  


Tom-PT Taylor wrote: 


As I noted earlier, you do need to specify the properties in the NAS case. 
The SDP TDM draft has certainly had time to ripen, and I will reissue it and

the NAS packages within the next week. 

-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 2:48 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations 
  


I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case 
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.



But I can't remember now whether it was intended to be used in local or 
localControl Descriptor. 
  


Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [ mailto:megaco-admin@ietf.org
<mailto:megaco-admin@ietf.org> ]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<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 **** 
 

-- 

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


------_=_NextPart_001_01C1DA88.197FAE10
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">


<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=967084920-02042002>All 
good questions another I would add is:</SPAN></FONT></DIV>
<DIV><SPAN class=967084920-02042002>If we use SDP for TDM going forward 
</SPAN></DIV>
<DIV><SPAN class=967084920-02042002>how is silence suppression 
implemented?</SPAN></DIV>
<DIV><SPAN class=967084920-02042002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=967084920-02042002><BR>Carl&nbsp;</SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Chuong N. Nguyen 
  [mailto:Chuong.Nguyen@alcatel.com]<BR><B>Sent:</B> Tuesday, April 02, 2002 
  3:41 PM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] 
  Local/Remote descriptors and Permanent terminations<BR><BR></FONT></DIV>&nbsp; 
  <BR>I&nbsp;thought the reason that we decided to have SDP TDM is to get away 
  from TDM&nbsp;package <BR>to be more inline w/how we specify 
  RTP&nbsp;termination characteristics. <BR>Also to reuse the good stuffs from 
  RTP/ATM SDP. 
  <P>I guess we can start by asking the questions 
  <P>1) Can we live w/o the TDM package? <BR>2) Can we just use SDP for TDM 
  going forward? <BR>3) For backward compatibility, just leave TDM&nbsp;package 
  as is and don't extend it anymore. 
  <P>For the TDM package, echo control is understood but the Gain control is not 
  quite right. <BR>I&nbsp;have discussed the Gain control before and gotten 
  nowhere. 
  <P>Gain control is also defined in the SDP&nbsp;for ATM which seems more 
  correct. <BR>&nbsp; <BR>&nbsp; 
  <P>Carl Rutter wrote: 
  <BLOCKQUOTE TYPE="CITE"><SPAN class=491101120-02042002><FONT size=-1><FONT 
    face=Arial><FONT color=#0000ff>Chuong,</SPAN><SPAN 
    class=491101120-02042002></SPAN><SPAN class=491101120-02042002>There was 
    several ideas bouncing around but I don't believe</SPAN><SPAN 
    class=491101120-02042002>there was any closure.&nbsp; There is a hole for 
    G711 since we can't use&nbsp;</SPAN><SPAN class=491101120-02042002>annexa or 
    annexb.</SPAN><SPAN class=491101120-02042002>Lifting the support in 
    </FONT></FONT><FONT face="Times New Roman"><FONT color=#000000>RFC 3108, 
    section 5.6.3.2 and putting it into</SPAN><SPAN 
    class=491101120-02042002></FONT></FONT>the TDM Circuit Package would give us 
    a lot of flexibility.</SPAN><SPAN class=491101120-02042002></SPAN><SPAN 
    class=491101120-02042002><FONT face=Arial><FONT color=#0000ff>Here are the 
    ideas I know of:</SPAN><SPAN 
    class=491101120-02042002>1)</FONT></FONT></FONT></SPAN><SPAN 
    class=491101120-02042002> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>Another option is to 
    extend the TDM Circuit Package (which has been</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>previously discussed 
    on the list). The TDM Cicruit Package</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>currently has Gain and 
    Echo Control as its properties. So, it's logical</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>(IMO) for Silence 
    Suppression to be part of the package as</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>well. In fact, it 
    looks like an oversight that it was missed off in the</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>first 
    place.</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT 
    size=-1>Regards,</FONT></FONT></FONT> 
    <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>Wayne<SPAN 
    class=491101120-02042002> Cutler</FONT></FONT></FONT></SPAN> 
    <P><SPAN class=491101120-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
    size=-1>2)</FONT></FONT></FONT></SPAN> <BR><SPAN class=491101120-02042002>
    <P><FONT size=-1>Another possibility is to use payload 13 as defined in 
    draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</FONT> 
    <P><FONT size=-1>Media={Stream=1{ Local {</FONT> <BR><FONT 
    size=-1>v=0</FONT> <BR><FONT size=-1>c=IN IP4 $</FONT> <BR><FONT 
    size=-1>m=audio $ RTP/AVP 0 13</FONT> <BR><FONT size=-1>}}}</FONT> 
    <P><SPAN class=491101120-02042002><FONT size=-1>David Barr</FONT></SPAN> 
    <P><SPAN class=491101120-02042002><FONT size=-1>3)</FONT></SPAN> 
    <P><SPAN class=491101120-02042002></SPAN><SPAN 
    class=491101120-02042002><FONT size=-1>I'm starting to think that the answer 
    may be to use the a=silenceSupp</FONT> <BR><FONT size=-1>attribute defined 
    in RFC 3108, section 5.6.3.2.</FONT> 
    <P><SPAN class=491101120-02042002><FONT size=-1>Tom Taylor</FONT></SPAN> 
    <BR>&nbsp; <BR>&nbsp; 
    <P><SPAN class=491101120-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
    size=-1>Carl</FONT></FONT></FONT></SPAN> <BR></SPAN></SPAN></SPAN>
    <BLOCKQUOTE>
      <DIV class=OutlookMessageHeader dir=ltr><FONT face=Tahoma><FONT 
      size=-1>-----Original Message-----</FONT></FONT> <BR><FONT 
      face=Tahoma><FONT size=-1><B>From:</B> Chuong N. Nguyen [<A 
      href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</FONT></FONT> 
      <BR><FONT face=Tahoma><FONT size=-1><B>Sent:</B> Tuesday, April 02, 2002 
      2:59 PM</FONT></FONT> <BR><FONT face=Tahoma><FONT size=-1><B>Cc:</B> 
      megaco@ietf.org</FONT></FONT> <BR><FONT face=Tahoma><FONT 
      size=-1><B>Subject:</B> Re: [Megaco] Local/Remote descriptors and 
      Permanent terminations</FONT></FONT></DIV>
      <P><BR>So what was that discussion about adding silence suppression to TDM 
      package? 
      <P>Do we use SDP TDM or TDM package or both? <BR>Or even worse combination 
      of both within 1 command w/some parameters defined by TDM package and 
      <BR>some parameters defined by SDP TDM. <BR>&nbsp; <BR>&nbsp; 
      <P>Tom-PT Taylor wrote: 
      <BLOCKQUOTE TYPE="CITE">As I noted earlier, you do need to specify the 
        properties in the NAS case. <BR>The SDP TDM draft has certainly had time 
        to ripen, and I will reissue it and <BR>the NAS packages within the next 
        week. 
        <P>-----Original Message----- <BR>From: Chuong N. Nguyen [<A 
        href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>] 
        <BR>Sent: Tuesday, April 02, 2002 2:48 PM <BR>To: megaco@ietf.org 
        <BR>Subject: Re: [Megaco] Local/Remote descriptors and Permanent 
        terminations <BR>&nbsp; 
        <P>I don't know about the sendrecv issue here. <BR>I don't know what you 
        mean by SDP parameters are of no significance in case <BR>of phy. term. 
        <BR>Tom wrote the SDP TDM draft which I wonder what is the status of 
        this draft. 
        <P>But I can't remember now whether it was intended to be used in local 
        or <BR>localControl Descriptor. <BR>&nbsp; 
        <P>Madhu Babu Brahmanapally wrote: <BR>HI Rajesh/All, <BR>Not all 
        parameters might be useful for the MG/MGC in case of physical 
        <BR>terminations. The SDP parameters are of no significance in case of 
        physical <BR>terminations (in normal scenario). Hence the mode was set 
        to "sendrecv" <BR>without specifying the local/remote descriptor 
        information. <BR>Regards <BR>Madhubabu <BR>-----Original Message----- 
        <BR>From: megaco-admin@ietf.org [<A 
        href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]On 
        Behalf Of <BR>Rajesh N <BR>Sent: Tuesday, April 02, 2002 11:32 AM 
        <BR>To: megaco@ietf.org <BR>Subject: [Megaco] Local/Remote descriptors 
        and Permanent terminations <BR>Hi, <BR>Sometime back there was a thread 
        regarding usage of SendRecv mode for an <BR>ephemeral termination, when 
        Remote Descriptor values are yet to be defined. <BR>And one of the 
        choices for the MG in such a situation is to reply back with <BR>error 
        411, "missing remote or local descriptor". <BR>I would like to know, 
        what is the significance of this problem w.r.to <BR>permanent 
        terminations. The example call flow in the draft shows a Modify 
        <BR>request for a permanent termination, from MGC to MG1, in which mode 
        is set <BR>as SendRecv and&nbsp; the Local descriptor values alone are 
        being provided. <BR>Are local and remote descriptors relevant for 
        physical terminations? If <BR>yes, where should I get the values from? 
        <BR>Thanks <BR>Regards, <BR>Rajesh N 
        <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>[This E-mail was scanned for viruses and is clean.] 
        <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; Alcatel USA, 
        Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
        Internet: Chuong.Nguyen@usa.alcatel.com <BR>&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; **** The opinions 
        expressed are not those of Alcatel USA, Inc **** 
      <BR>&nbsp;</P></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;</BLOCKQUOTE></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; 
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1DA88.197FAE10--

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



From megaco-admin@ietf.org  Tue Apr  2 16: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 QAA03961
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 16:20: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 PAA13107;
	Tue, 2 Apr 2002 15:59: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 PAA13077
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 15:59:22 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03224
	for <megaco@ietf.org>; Tue, 2 Apr 2002 15:59:19 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g32KwQV21744
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:58:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g32KvlO12937
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:57:47 -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 g32Kvl726989
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:57:47 -0600 (CST)
Message-ID: <3CAA1B4B.1036E354@alcatel.com>
Date: Tue, 02 Apr 2002 14:57: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] Local/Remote descriptors and Permanent terminations
References: <2415C206C515244DBFB12EC0C064A448404C46@wench>
Content-Type: multipart/alternative;
 boundary="------------7AC61FFE2A16F760A84DBB49"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

Doesn't the following cover this already?

5.6.3.2 The 'silenceSupp' attribute

   When present, the 'silenceSupp' attribute is used to indicate the use

   or non-use of silence suppression.  The format of the 'silenceSupp'
   media attribute line is as follows:

   a=silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse>

                   <fxnslevel>





Carl Rutter wrote:

> All good questions another I would add is:If we use SDP for TDM going
> forward how is silence suppression implemented?
> Carl
>
>      -----Original Message-----
>      From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
>      Sent: Tuesday, April 02, 2002 3:41 PM
>      To: megaco@ietf.org
>      Subject: Re: [Megaco] Local/Remote descriptors and Permanent
>      terminations
>
>
>      I thought the reason that we decided to have SDP TDM is to
>      get away from TDM package
>      to be more inline w/how we specify RTP termination
>      characteristics.
>      Also to reuse the good stuffs from RTP/ATM SDP.
>
>      I guess we can start by asking the questions
>
>      1) Can we live w/o the TDM package?
>      2) Can we just use SDP for TDM going forward?
>      3) For backward compatibility, just leave TDM package as is
>      and don't extend it anymore.
>
>      For the TDM package, echo control is understood but the Gain
>      control is not quite right.
>      I have discussed the Gain control before and gotten nowhere.
>
>      Gain control is also defined in the SDP for ATM which seems
>      more correct.
>
>
>
>      Carl Rutter wrote:
>
>     > Chuong,There was several ideas bouncing around but I don't
>     > believethere was any closure.  There is a hole for G711
>     > since we can't use annexa or annexb.Lifting the support in
>     > RFC 3108, section 5.6.3.2 and putting it intothe TDM
>     > Circuit Package would give us a lot of flexibility.Here
>     > are the ideas I know of:1)
>     >
>     > Another option is to extend the TDM Circuit Package (which
>     > has been
>     >
>     > previously discussed on the list). The TDM Cicruit Package
>     >
>     > currently has Gain and Echo Control as its properties. So,
>     > it's logical
>     >
>     > (IMO) for Silence Suppression to be part of the package as
>     >
>     > well. In fact, it looks like an oversight that it was
>     > missed off in the
>     >
>     > first place.
>     >
>     > Regards,
>     >
>     > Wayne Cutler
>     >
>     > 2)
>     >
>     > Another possibility is to use payload 13 as defined in
>     > draft-ietf-avt-rtp-cn-05.  E.g.:
>     >
>     > Media={Stream=1{ Local {
>     > v=0
>     > c=IN IP4 $
>     > m=audio $ RTP/AVP 0 13
>     > }}}
>     >
>     > David Barr
>     >
>     > 3)
>     >
>     > I'm starting to think that the answer may be to use the
>     > a=silenceSupp
>     > attribute defined in RFC 3108, section 5.6.3.2.
>     >
>     > Tom Taylor
>     >
>     >
>     >
>     > Carl
>     >
>     >      -----Original Message-----
>     >      From: Chuong N. Nguyen
>     >      [mailto:Chuong.Nguyen@alcatel.com]
>     >      Sent: Tuesday, April 02, 2002 2:59 PM
>     >      Cc: megaco@ietf.org
>     >      Subject: Re: [Megaco] Local/Remote descriptors
>     >      and Permanent terminations
>     >
>     >
>     >      So what was that discussion about adding silence
>     >      suppression to TDM package?
>     >
>     >      Do we use SDP TDM or TDM package or both?
>     >      Or even worse combination of both within 1
>     >      command w/some parameters defined by TDM package
>     >      and
>     >      some parameters defined by SDP TDM.
>     >
>     >
>     >
>     >      Tom-PT Taylor wrote:
>     >
>     >      > As I noted earlier, you do need to specify the
>     >      > properties in the NAS case.
>     >      > The SDP TDM draft has certainly had time to
>     >      > ripen, and I will reissue it and
>     >      > the NAS packages within the next week.
>     >      >
>     >      > -----Original Message-----
>     >      > From: Chuong N. Nguyen
>     >      > [mailto:Chuong.Nguyen@alcatel.com]
>     >      > Sent: Tuesday, April 02, 2002 2:48 PM
>     >      > To: megaco@ietf.org
>     >      > Subject: Re: [Megaco] Local/Remote descriptors
>     >      > and Permanent terminations
>     >      >
>     >      >
>     >      > I don't know about the sendrecv issue here.
>     >      > I don't know what you mean by SDP parameters
>     >      > are of no significance in case
>     >      > of phy. term.
>     >      > Tom wrote the SDP TDM draft which I wonder what
>     >      > is the status of this draft.
>     >      >
>     >      > But I can't remember now whether it was
>     >      > intended to be used in local or
>     >      > localControl Descriptor.
>     >      >
>     >      >
>     >      > Madhu Babu Brahmanapally wrote:
>     >      > HI Rajesh/All,
>     >      > Not all parameters might be useful for the
>     >      > MG/MGC in case of physical
>     >      > terminations. The SDP parameters are of no
>     >      > significance in case of physical
>     >      > terminations (in normal scenario). Hence the
>     >      > mode was set to "sendrecv"
>     >      > without specifying the local/remote descriptor
>     >      > information.
>     >      > Regards
>     >      > Madhubabu
>     >      > -----Original Message-----
>     >      > From: megaco-admin@ietf.org
>     >      > [mailto:megaco-admin@ietf.org]On Behalf Of
>     >      > Rajesh N
>     >      > Sent: Tuesday, April 02, 2002 11:32 AM
>     >      > To: megaco@ietf.org
>     >      > Subject: [Megaco] Local/Remote descriptors and
>     >      > Permanent terminations
>     >      > Hi,
>     >      > Sometime back there was a thread regarding
>     >      > usage of SendRecv mode for an
>     >      > ephemeral termination, when Remote Descriptor
>     >      > values are yet to be defined.
>     >      > And one of the choices for the MG in such a
>     >      > situation is to reply back with
>     >      > error 411, "missing remote or local
>     >      > descriptor".
>     >      > I would like to know, what is the significance
>     >      > of this problem w.r.to
>     >      > permanent terminations. The example call flow
>     >      > in the draft shows a Modify
>     >      > request for a permanent termination, from MGC
>     >      > to MG1, in which mode is set
>     >      > as SendRecv and  the Local descriptor values
>     >      > alone are being provided.
>     >      > Are local and remote descriptors relevant for
>     >      > physical terminations? If
>     >      > yes, where should I get the values from?
>     >      > Thanks
>     >      > Regards,
>     >      > Rajesh N
>     >      > _______________________________________________
>     >      >
>     >      > Megaco mailing list
>     >      > Megaco@ietf.org
>     >      > https://www1.ietf.org/mailman/listinfo/megaco
>     >      > ---
>     >      > [This E-mail was scanned for viruses and is
>     >      > clean.]
>     >      > _______________________________________________
>     >      >
>     >      > 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 ****
>     >      >
>     >
>     >      --
>     >        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 ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Doesn't the following cover this already?
<p>5.6.3.2 The 'silenceSupp' attribute
<p>&nbsp;&nbsp; When present, the 'silenceSupp' attribute is used to indicate
the use
<br>&nbsp;&nbsp; or non-use of silence suppression.&nbsp; The format of
the 'silenceSupp'
<br>&nbsp;&nbsp; media attribute line is as follows:
<p>&nbsp;&nbsp; a=silenceSupp: &lt;silenceSuppEnable> &lt;silenceTimer>
&lt;suppPref> &lt;sidUse>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;fxnslevel>
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE=CITE><span class=967084920-02042002><font face="Arial"><font color="#0000FF"><font size=-1>All
good questions another I would add is:</span><span class=967084920-02042002></font></font></font>If
we use SDP for TDM going forward&nbsp;</span><span class=967084920-02042002>how
is silence suppression implemented?</span><span class=967084920-02042002></span><span class=967084920-02042002>
<br>Carl&nbsp;</span>
<blockquote>
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<A HREF="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
3:41 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>

<p><br>I thought the reason that we decided to have SDP TDM is to get away
from TDM package
<br>to be more inline w/how we specify RTP termination characteristics.
<br>Also to reuse the good stuffs from RTP/ATM SDP.
<p>I guess we can start by asking the questions
<p>1) Can we live w/o the TDM package?
<br>2) Can we just use SDP for TDM going forward?
<br>3) For backward compatibility, just leave TDM package as is and don't
extend it anymore.
<p>For the TDM package, echo control is understood but the Gain control
is not quite right.
<br>I have discussed the Gain control before and gotten nowhere.
<p>Gain control is also defined in the SDP for ATM which seems more correct.
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE="CITE"><span class=491101120-02042002><font size=-1><font face="Arial"><font color="#0000FF">Chuong,</span><span 
    class=491101120-02042002></span><span class=491101120-02042002>There
was several ideas bouncing around but I don't believe</span><span 
    class=491101120-02042002>there
was any closure.&nbsp; There is a hole for G711 since we can't use&nbsp;</span><span class=491101120-02042002>annexa
or annexb.</span><span class=491101120-02042002>Lifting the support in
</font></font><font face="Times New Roman"><font color="#000000">RFC
3108, section 5.6.3.2 and putting it into</span><span 
    class=491101120-02042002></font></font>the
TDM Circuit Package would give us a lot of flexibility.</span><span class=491101120-02042002></span><span 
    class=491101120-02042002><font face="Arial"><font color="#0000FF">Here
are the ideas I know of:</span><span 
    class=491101120-02042002>1)</font></font></font></span><span 
    class=491101120-02042002>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Another option
is to extend the TDM Circuit Package (which has been</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>previously discussed
on the list). The TDM Cicruit Package</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>currently has
Gain and Echo Control as its properties. So, it's logical</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>(IMO) for Silence
Suppression to be part of the package as</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>well. In fact,
it looks like an oversight that it was missed off in the</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>first place.</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Regards,</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Wayne<span 
    class=491101120-02042002>
Cutler</font></font></font></span>
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>2)</font></font></font></span>
<br><span class=491101120-02042002>
<p><font size=-1>Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</font>
<p><font size=-1>Media={Stream=1{ Local {</font>
<br><font size=-1>v=0</font>
<br><font size=-1>c=IN IP4 $</font>
<br><font size=-1>m=audio $ RTP/AVP 0 13</font>
<br><font size=-1>}}}</font>
<p><span class=491101120-02042002><font size=-1>David Barr</font></span>
<p><span class=491101120-02042002><font size=-1>3)</font></span>
<p><span class=491101120-02042002></span><span 
    class=491101120-02042002><font size=-1>I'm
starting to think that the answer may be to use the a=silenceSupp</font>
<br><font size=-1>attribute defined in RFC 3108, section 5.6.3.2.</font>
<p><span class=491101120-02042002><font size=-1>Tom Taylor</font></span>
<br>&nbsp;
<br>&nbsp;
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>Carl</font></font></font></span>
<br></span></span></span>
<blockquote>
<div class=OutlookMessageHeader dir=ltr><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
2:59 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>Cc:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>

<p><br>So what was that discussion about adding silence suppression to
TDM package?
<p>Do we use SDP TDM or TDM package or both?
<br>Or even worse combination of both within 1 command w/some parameters
defined by TDM package and
<br>some parameters defined by SDP TDM.
<br>&nbsp;
<br>&nbsp;
<p>Tom-PT Taylor wrote:
<blockquote TYPE="CITE">As I noted earlier, you do need to specify the
properties in the NAS case.
<br>The SDP TDM draft has certainly had time to ripen, and I will reissue
it and
<br>the NAS packages within the next week.
<p>-----Original Message-----
<br>From: Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]
<br>Sent: Tuesday, April 02, 2002 2:48 PM
<br>To: megaco@ietf.org
<br>Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
<br>&nbsp;
<p>I don't know about the sendrecv issue here.
<br>I don't know what you mean by SDP parameters are of no significance
in case
<br>of phy. term.
<br>Tom wrote the SDP TDM draft which I wonder what is the status of this
draft.
<p>But I can't remember now whether it was intended to be used in local
or
<br>localControl Descriptor.
<br>&nbsp;
<p>Madhu Babu Brahmanapally wrote:
<br>HI Rajesh/All,
<br>Not all parameters might be useful for the MG/MGC in case of physical
<br>terminations. The SDP parameters are of no significance in case of
physical
<br>terminations (in normal scenario). Hence the mode was set to "sendrecv"
<br>without specifying the local/remote descriptor information.
<br>Regards
<br>Madhubabu
<br>-----Original Message-----
<br>From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]On
Behalf Of
<br>Rajesh N
<br>Sent: Tuesday, April 02, 2002 11:32 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Local/Remote descriptors and Permanent terminations
<br>Hi,
<br>Sometime back there was a thread regarding usage of SendRecv mode for
an
<br>ephemeral termination, when Remote Descriptor values are yet to be
defined.
<br>And one of the choices for the MG in such a situation is to reply back
with
<br>error 411, "missing remote or local descriptor".
<br>I would like to know, what is the significance of this problem w.r.to
<br>permanent terminations. The example call flow in the draft shows a
Modify
<br>request for a permanent termination, from MGC to MG1, in which mode
is set
<br>as SendRecv and&nbsp; the Local descriptor values alone are being provided.
<br>Are local and remote descriptors relevant for physical terminations?
If
<br>yes, where should I get the values from?
<br>Thanks
<br>Regards,
<br>Rajesh N
<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>[This E-mail was scanned for viruses and is clean.]
<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; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>&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; **** The opinions expressed are not those of Alcatel USA, Inc
****
<br>&nbsp;</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;</blockquote>
</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;</blockquote>
</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>

--------------7AC61FFE2A16F760A84DBB49--


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


From daemon@ns.ietf.org  Tue Apr  2 16: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 QAA03976
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 16:20:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA14431
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 16: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 PAA13107;
	Tue, 2 Apr 2002 15:59: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 PAA13077
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 15:59:22 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03224
	for <megaco@ietf.org>; Tue, 2 Apr 2002 15:59:19 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g32KwQV21744
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:58:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g32KvlO12937
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:57:47 -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 g32Kvl726989
	for <megaco@ietf.org>; Tue, 2 Apr 2002 14:57:47 -0600 (CST)
Message-ID: <3CAA1B4B.1036E354@alcatel.com>
Date: Tue, 02 Apr 2002 14:57: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] Local/Remote descriptors and Permanent terminations
References: <2415C206C515244DBFB12EC0C064A448404C46@wench>
Content-Type: multipart/alternative;
 boundary="------------7AC61FFE2A16F760A84DBB49"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

Doesn't the following cover this already?

5.6.3.2 The 'silenceSupp' attribute

   When present, the 'silenceSupp' attribute is used to indicate the use

   or non-use of silence suppression.  The format of the 'silenceSupp'
   media attribute line is as follows:

   a=silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse>

                   <fxnslevel>





Carl Rutter wrote:

> All good questions another I would add is:If we use SDP for TDM going
> forward how is silence suppression implemented?
> Carl
>
>      -----Original Message-----
>      From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
>      Sent: Tuesday, April 02, 2002 3:41 PM
>      To: megaco@ietf.org
>      Subject: Re: [Megaco] Local/Remote descriptors and Permanent
>      terminations
>
>
>      I thought the reason that we decided to have SDP TDM is to
>      get away from TDM package
>      to be more inline w/how we specify RTP termination
>      characteristics.
>      Also to reuse the good stuffs from RTP/ATM SDP.
>
>      I guess we can start by asking the questions
>
>      1) Can we live w/o the TDM package?
>      2) Can we just use SDP for TDM going forward?
>      3) For backward compatibility, just leave TDM package as is
>      and don't extend it anymore.
>
>      For the TDM package, echo control is understood but the Gain
>      control is not quite right.
>      I have discussed the Gain control before and gotten nowhere.
>
>      Gain control is also defined in the SDP for ATM which seems
>      more correct.
>
>
>
>      Carl Rutter wrote:
>
>     > Chuong,There was several ideas bouncing around but I don't
>     > believethere was any closure.  There is a hole for G711
>     > since we can't use annexa or annexb.Lifting the support in
>     > RFC 3108, section 5.6.3.2 and putting it intothe TDM
>     > Circuit Package would give us a lot of flexibility.Here
>     > are the ideas I know of:1)
>     >
>     > Another option is to extend the TDM Circuit Package (which
>     > has been
>     >
>     > previously discussed on the list). The TDM Cicruit Package
>     >
>     > currently has Gain and Echo Control as its properties. So,
>     > it's logical
>     >
>     > (IMO) for Silence Suppression to be part of the package as
>     >
>     > well. In fact, it looks like an oversight that it was
>     > missed off in the
>     >
>     > first place.
>     >
>     > Regards,
>     >
>     > Wayne Cutler
>     >
>     > 2)
>     >
>     > Another possibility is to use payload 13 as defined in
>     > draft-ietf-avt-rtp-cn-05.  E.g.:
>     >
>     > Media={Stream=1{ Local {
>     > v=0
>     > c=IN IP4 $
>     > m=audio $ RTP/AVP 0 13
>     > }}}
>     >
>     > David Barr
>     >
>     > 3)
>     >
>     > I'm starting to think that the answer may be to use the
>     > a=silenceSupp
>     > attribute defined in RFC 3108, section 5.6.3.2.
>     >
>     > Tom Taylor
>     >
>     >
>     >
>     > Carl
>     >
>     >      -----Original Message-----
>     >      From: Chuong N. Nguyen
>     >      [mailto:Chuong.Nguyen@alcatel.com]
>     >      Sent: Tuesday, April 02, 2002 2:59 PM
>     >      Cc: megaco@ietf.org
>     >      Subject: Re: [Megaco] Local/Remote descriptors
>     >      and Permanent terminations
>     >
>     >
>     >      So what was that discussion about adding silence
>     >      suppression to TDM package?
>     >
>     >      Do we use SDP TDM or TDM package or both?
>     >      Or even worse combination of both within 1
>     >      command w/some parameters defined by TDM package
>     >      and
>     >      some parameters defined by SDP TDM.
>     >
>     >
>     >
>     >      Tom-PT Taylor wrote:
>     >
>     >      > As I noted earlier, you do need to specify the
>     >      > properties in the NAS case.
>     >      > The SDP TDM draft has certainly had time to
>     >      > ripen, and I will reissue it and
>     >      > the NAS packages within the next week.
>     >      >
>     >      > -----Original Message-----
>     >      > From: Chuong N. Nguyen
>     >      > [mailto:Chuong.Nguyen@alcatel.com]
>     >      > Sent: Tuesday, April 02, 2002 2:48 PM
>     >      > To: megaco@ietf.org
>     >      > Subject: Re: [Megaco] Local/Remote descriptors
>     >      > and Permanent terminations
>     >      >
>     >      >
>     >      > I don't know about the sendrecv issue here.
>     >      > I don't know what you mean by SDP parameters
>     >      > are of no significance in case
>     >      > of phy. term.
>     >      > Tom wrote the SDP TDM draft which I wonder what
>     >      > is the status of this draft.
>     >      >
>     >      > But I can't remember now whether it was
>     >      > intended to be used in local or
>     >      > localControl Descriptor.
>     >      >
>     >      >
>     >      > Madhu Babu Brahmanapally wrote:
>     >      > HI Rajesh/All,
>     >      > Not all parameters might be useful for the
>     >      > MG/MGC in case of physical
>     >      > terminations. The SDP parameters are of no
>     >      > significance in case of physical
>     >      > terminations (in normal scenario). Hence the
>     >      > mode was set to "sendrecv"
>     >      > without specifying the local/remote descriptor
>     >      > information.
>     >      > Regards
>     >      > Madhubabu
>     >      > -----Original Message-----
>     >      > From: megaco-admin@ietf.org
>     >      > [mailto:megaco-admin@ietf.org]On Behalf Of
>     >      > Rajesh N
>     >      > Sent: Tuesday, April 02, 2002 11:32 AM
>     >      > To: megaco@ietf.org
>     >      > Subject: [Megaco] Local/Remote descriptors and
>     >      > Permanent terminations
>     >      > Hi,
>     >      > Sometime back there was a thread regarding
>     >      > usage of SendRecv mode for an
>     >      > ephemeral termination, when Remote Descriptor
>     >      > values are yet to be defined.
>     >      > And one of the choices for the MG in such a
>     >      > situation is to reply back with
>     >      > error 411, "missing remote or local
>     >      > descriptor".
>     >      > I would like to know, what is the significance
>     >      > of this problem w.r.to
>     >      > permanent terminations. The example call flow
>     >      > in the draft shows a Modify
>     >      > request for a permanent termination, from MGC
>     >      > to MG1, in which mode is set
>     >      > as SendRecv and  the Local descriptor values
>     >      > alone are being provided.
>     >      > Are local and remote descriptors relevant for
>     >      > physical terminations? If
>     >      > yes, where should I get the values from?
>     >      > Thanks
>     >      > Regards,
>     >      > Rajesh N
>     >      > _______________________________________________
>     >      >
>     >      > Megaco mailing list
>     >      > Megaco@ietf.org
>     >      > https://www1.ietf.org/mailman/listinfo/megaco
>     >      > ---
>     >      > [This E-mail was scanned for viruses and is
>     >      > clean.]
>     >      > _______________________________________________
>     >      >
>     >      > 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 ****
>     >      >
>     >
>     >      --
>     >        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 ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Doesn't the following cover this already?
<p>5.6.3.2 The 'silenceSupp' attribute
<p>&nbsp;&nbsp; When present, the 'silenceSupp' attribute is used to indicate
the use
<br>&nbsp;&nbsp; or non-use of silence suppression.&nbsp; The format of
the 'silenceSupp'
<br>&nbsp;&nbsp; media attribute line is as follows:
<p>&nbsp;&nbsp; a=silenceSupp: &lt;silenceSuppEnable> &lt;silenceTimer>
&lt;suppPref> &lt;sidUse>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;fxnslevel>
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE=CITE><span class=967084920-02042002><font face="Arial"><font color="#0000FF"><font size=-1>All
good questions another I would add is:</span><span class=967084920-02042002></font></font></font>If
we use SDP for TDM going forward&nbsp;</span><span class=967084920-02042002>how
is silence suppression implemented?</span><span class=967084920-02042002></span><span class=967084920-02042002>
<br>Carl&nbsp;</span>
<blockquote>
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<A HREF="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
3:41 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>

<p><br>I thought the reason that we decided to have SDP TDM is to get away
from TDM package
<br>to be more inline w/how we specify RTP termination characteristics.
<br>Also to reuse the good stuffs from RTP/ATM SDP.
<p>I guess we can start by asking the questions
<p>1) Can we live w/o the TDM package?
<br>2) Can we just use SDP for TDM going forward?
<br>3) For backward compatibility, just leave TDM package as is and don't
extend it anymore.
<p>For the TDM package, echo control is understood but the Gain control
is not quite right.
<br>I have discussed the Gain control before and gotten nowhere.
<p>Gain control is also defined in the SDP for ATM which seems more correct.
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE="CITE"><span class=491101120-02042002><font size=-1><font face="Arial"><font color="#0000FF">Chuong,</span><span 
    class=491101120-02042002></span><span class=491101120-02042002>There
was several ideas bouncing around but I don't believe</span><span 
    class=491101120-02042002>there
was any closure.&nbsp; There is a hole for G711 since we can't use&nbsp;</span><span class=491101120-02042002>annexa
or annexb.</span><span class=491101120-02042002>Lifting the support in
</font></font><font face="Times New Roman"><font color="#000000">RFC
3108, section 5.6.3.2 and putting it into</span><span 
    class=491101120-02042002></font></font>the
TDM Circuit Package would give us a lot of flexibility.</span><span class=491101120-02042002></span><span 
    class=491101120-02042002><font face="Arial"><font color="#0000FF">Here
are the ideas I know of:</span><span 
    class=491101120-02042002>1)</font></font></font></span><span 
    class=491101120-02042002>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Another option
is to extend the TDM Circuit Package (which has been</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>previously discussed
on the list). The TDM Cicruit Package</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>currently has
Gain and Echo Control as its properties. So, it's logical</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>(IMO) for Silence
Suppression to be part of the package as</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>well. In fact,
it looks like an oversight that it was missed off in the</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>first place.</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Regards,</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Wayne<span 
    class=491101120-02042002>
Cutler</font></font></font></span>
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>2)</font></font></font></span>
<br><span class=491101120-02042002>
<p><font size=-1>Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</font>
<p><font size=-1>Media={Stream=1{ Local {</font>
<br><font size=-1>v=0</font>
<br><font size=-1>c=IN IP4 $</font>
<br><font size=-1>m=audio $ RTP/AVP 0 13</font>
<br><font size=-1>}}}</font>
<p><span class=491101120-02042002><font size=-1>David Barr</font></span>
<p><span class=491101120-02042002><font size=-1>3)</font></span>
<p><span class=491101120-02042002></span><span 
    class=491101120-02042002><font size=-1>I'm
starting to think that the answer may be to use the a=silenceSupp</font>
<br><font size=-1>attribute defined in RFC 3108, section 5.6.3.2.</font>
<p><span class=491101120-02042002><font size=-1>Tom Taylor</font></span>
<br>&nbsp;
<br>&nbsp;
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>Carl</font></font></font></span>
<br></span></span></span>
<blockquote>
<div class=OutlookMessageHeader dir=ltr><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
2:59 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>Cc:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>

<p><br>So what was that discussion about adding silence suppression to
TDM package?
<p>Do we use SDP TDM or TDM package or both?
<br>Or even worse combination of both within 1 command w/some parameters
defined by TDM package and
<br>some parameters defined by SDP TDM.
<br>&nbsp;
<br>&nbsp;
<p>Tom-PT Taylor wrote:
<blockquote TYPE="CITE">As I noted earlier, you do need to specify the
properties in the NAS case.
<br>The SDP TDM draft has certainly had time to ripen, and I will reissue
it and
<br>the NAS packages within the next week.
<p>-----Original Message-----
<br>From: Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]
<br>Sent: Tuesday, April 02, 2002 2:48 PM
<br>To: megaco@ietf.org
<br>Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
<br>&nbsp;
<p>I don't know about the sendrecv issue here.
<br>I don't know what you mean by SDP parameters are of no significance
in case
<br>of phy. term.
<br>Tom wrote the SDP TDM draft which I wonder what is the status of this
draft.
<p>But I can't remember now whether it was intended to be used in local
or
<br>localControl Descriptor.
<br>&nbsp;
<p>Madhu Babu Brahmanapally wrote:
<br>HI Rajesh/All,
<br>Not all parameters might be useful for the MG/MGC in case of physical
<br>terminations. The SDP parameters are of no significance in case of
physical
<br>terminations (in normal scenario). Hence the mode was set to "sendrecv"
<br>without specifying the local/remote descriptor information.
<br>Regards
<br>Madhubabu
<br>-----Original Message-----
<br>From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]On
Behalf Of
<br>Rajesh N
<br>Sent: Tuesday, April 02, 2002 11:32 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Local/Remote descriptors and Permanent terminations
<br>Hi,
<br>Sometime back there was a thread regarding usage of SendRecv mode for
an
<br>ephemeral termination, when Remote Descriptor values are yet to be
defined.
<br>And one of the choices for the MG in such a situation is to reply back
with
<br>error 411, "missing remote or local descriptor".
<br>I would like to know, what is the significance of this problem w.r.to
<br>permanent terminations. The example call flow in the draft shows a
Modify
<br>request for a permanent termination, from MGC to MG1, in which mode
is set
<br>as SendRecv and&nbsp; the Local descriptor values alone are being provided.
<br>Are local and remote descriptors relevant for physical terminations?
If
<br>yes, where should I get the values from?
<br>Thanks
<br>Regards,
<br>Rajesh N
<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>[This E-mail was scanned for viruses and is clean.]
<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; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>&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; **** The opinions expressed are not those of Alcatel USA, Inc
****
<br>&nbsp;</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;</blockquote>
</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;</blockquote>
</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>

--------------7AC61FFE2A16F760A84DBB49--


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



From megaco-admin@ietf.org  Tue Apr  2 16:38: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 QAA04522
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 16:38: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 QAA14050;
	Tue, 2 Apr 2002 16:11: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 QAA13987
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:11:24 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03691;
	Tue, 2 Apr 2002 16:11:16 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g32LAeZ05340;
	Tue, 2 Apr 2002 16:10: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 g32LAeh29370;
	Tue, 2 Apr 2002 16:10:40 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0P94>; Tue, 2 Apr 2002 16:10:40 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A237@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: mmusic@ietf.org, "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 2 Apr 2002 16:10:41 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Silence Suppression 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

The issue of how to signal silence suppression capability keeps coming up on
the Megaco list.  The situation is fairly complicated:
 - some codecs come with a pre-defined capability for silence suppression.
This capability can be invoked by the appropriate MIME type parameter as
defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to RTP
transport, arguably over UDP only.
 - other codecs like G.711 have no such parameter, yet silence suppression
is possible
 - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
transport only.

How would people feel about allowing the a=silenceSupp parameter to be used
independently of the transport type?

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  Tue Apr  2 16:38: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 QAA04532
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 16:38:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA15471
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 16:38: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 QAA14050;
	Tue, 2 Apr 2002 16:11: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 QAA13987
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:11:24 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03691;
	Tue, 2 Apr 2002 16:11:16 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g32LAeZ05340;
	Tue, 2 Apr 2002 16:10: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 g32LAeh29370;
	Tue, 2 Apr 2002 16:10:40 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0P94>; Tue, 2 Apr 2002 16:10:40 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A237@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: mmusic@ietf.org, "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 2 Apr 2002 16:10:41 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Silence Suppression 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

The issue of how to signal silence suppression capability keeps coming up on
the Megaco list.  The situation is fairly complicated:
 - some codecs come with a pre-defined capability for silence suppression.
This capability can be invoked by the appropriate MIME type parameter as
defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to RTP
transport, arguably over UDP only.
 - other codecs like G.711 have no such parameter, yet silence suppression
is possible
 - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
transport only.

How would people feel about allowing the a=silenceSupp parameter to be used
independently of the transport type?

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 Apr  2 16: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 QAA04795
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 16: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 QAA14570;
	Tue, 2 Apr 2002 16:25: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 QAA14543
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:25:24 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04092
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:25: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 g32LOpA07074
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:24:52 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0QLC>; Tue, 2 Apr 2002 16:24:53 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A23A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Carl Rutter'" <crutter@telica.com>,
        "'Chuong N. Nguyen'"
	 <Chuong.Nguyen@alcatel.com>
Cc: megaco@ietf.org, "Peter Barany"<pbarany@nortelnetworks.com>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 16:24:56 -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 had a message pointing out the existence of
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711
would indicate the use of silence suppression implicitly.  That covers RTP
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.
Do we need anything for TDM?

-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Tuesday, April 02, 2002 3:19 PM
To: 'Chuong N. Nguyen'
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


Chuong,
 
There was several ideas bouncing around but I don't believe
there was any closure.  There is a hole for G711 since we can't use 
annexa or annexb.
Lifting the support in RFC 3108, section 5.6.3.2 and putting it into
the TDM Circuit Package would give us a lot of flexibility.
 
Here are the ideas I know of:
1)
Another option is to extend the TDM Circuit Package (which has been
previously discussed on the list). The TDM Cicruit Package
currently has Gain and Echo Control as its properties. So, it's logical
(IMO) for Silence Suppression to be part of the package as
well. In fact, it looks like an oversight that it was missed off in the
first place.
Regards,
Wayne Cutler
2)
Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.  E.g.: 
Media={Stream=1{ Local { 
v=0 
c=IN IP4 $ 
m=audio $ RTP/AVP 0 13 
}}}
David Barr 
3)
I'm starting to think that the answer may be to use the a=silenceSupp 
attribute defined in RFC 3108, section 5.6.3.2. 
Tom Taylor
 
Carl
-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 2:59 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
So what was that discussion about adding silence suppression to TDM package?

Do we use SDP TDM or TDM package or both? 
Or even worse combination of both within 1 command w/some parameters defined
by TDM package and 
some parameters defined by SDP TDM. 
  
  
Tom-PT Taylor wrote: 
As I noted earlier, you do need to specify the properties in the NAS case. 
The SDP TDM draft has certainly had time to ripen, and I will reissue it and

the NAS packages within the next week. 
-----Original Message----- 
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com] 
Sent: Tuesday, April 02, 2002 2:48 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations 
  
I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case 
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.

But I can't remember now whether it was intended to be used in local or 
localControl Descriptor. 
  
Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco 
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
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 **** 
 
-- 
  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 Apr  2 16:47: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 QAA04806
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 16:47:17 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA15882
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 16: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 QAA14570;
	Tue, 2 Apr 2002 16:25: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 QAA14543
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:25:24 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04092
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:25: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 g32LOpA07074
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:24:52 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0QLC>; Tue, 2 Apr 2002 16:24:53 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A23A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Carl Rutter'" <crutter@telica.com>,
        "'Chuong N. Nguyen'"
	 <Chuong.Nguyen@alcatel.com>
Cc: megaco@ietf.org, "Peter Barany"<pbarany@nortelnetworks.com>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 16:24:56 -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 had a message pointing out the existence of
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711
would indicate the use of silence suppression implicitly.  That covers RTP
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.
Do we need anything for TDM?

-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Tuesday, April 02, 2002 3:19 PM
To: 'Chuong N. Nguyen'
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


Chuong,
 
There was several ideas bouncing around but I don't believe
there was any closure.  There is a hole for G711 since we can't use 
annexa or annexb.
Lifting the support in RFC 3108, section 5.6.3.2 and putting it into
the TDM Circuit Package would give us a lot of flexibility.
 
Here are the ideas I know of:
1)
Another option is to extend the TDM Circuit Package (which has been
previously discussed on the list). The TDM Cicruit Package
currently has Gain and Echo Control as its properties. So, it's logical
(IMO) for Silence Suppression to be part of the package as
well. In fact, it looks like an oversight that it was missed off in the
first place.
Regards,
Wayne Cutler
2)
Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.  E.g.: 
Media={Stream=1{ Local { 
v=0 
c=IN IP4 $ 
m=audio $ RTP/AVP 0 13 
}}}
David Barr 
3)
I'm starting to think that the answer may be to use the a=silenceSupp 
attribute defined in RFC 3108, section 5.6.3.2. 
Tom Taylor
 
Carl
-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 2:59 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
So what was that discussion about adding silence suppression to TDM package?

Do we use SDP TDM or TDM package or both? 
Or even worse combination of both within 1 command w/some parameters defined
by TDM package and 
some parameters defined by SDP TDM. 
  
  
Tom-PT Taylor wrote: 
As I noted earlier, you do need to specify the properties in the NAS case. 
The SDP TDM draft has certainly had time to ripen, and I will reissue it and

the NAS packages within the next week. 
-----Original Message----- 
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com] 
Sent: Tuesday, April 02, 2002 2:48 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations 
  
I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case 
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.

But I can't remember now whether it was intended to be used in local or 
localControl Descriptor. 
  
Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco 
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
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 **** 
 
-- 
  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 Apr  2 17:04: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 RAA05312
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:04: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 QAA14948;
	Tue, 2 Apr 2002 16:30: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 QAA14843
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:30:28 -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 QAA04172
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:30:18 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0NG8>; Tue, 2 Apr 2002 16:27:57 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C47@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 16:27:49 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DA8D.3D524410"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1DA8D.3D524410
Content-Type: text/plain;
	charset="iso-8859-1"

I'm confused, are you talking about section 5.6.3.2 of  RFC 3108?
I know there was discussion about snagging this but that is for ATM
right now.
 
 
Carl
  

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 3:58 PM
To: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


Doesn't the following cover this already? 

5.6.3.2 The 'silenceSupp' attribute 


   When present, the 'silenceSupp' attribute is used to indicate the use 
   or non-use of silence suppression.  The format of the 'silenceSupp' 
   media attribute line is as follows: 


   a=silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse> 
                   <fxnslevel> 
  
  
  
  


Carl Rutter wrote: 


All good questions another I would add is:If we use SDP for TDM going
forward how is silence suppression implemented? 
Carl  

-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 3:41 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


I thought the reason that we decided to have SDP TDM is to get away from TDM
package 
to be more inline w/how we specify RTP termination characteristics. 
Also to reuse the good stuffs from RTP/ATM SDP. 


I guess we can start by asking the questions 


1) Can we live w/o the TDM package? 
2) Can we just use SDP for TDM going forward? 
3) For backward compatibility, just leave TDM package as is and don't extend
it anymore. 


For the TDM package, echo control is understood but the Gain control is not
quite right. 
I have discussed the Gain control before and gotten nowhere. 


Gain control is also defined in the SDP for ATM which seems more correct. 
  
  


Carl Rutter wrote: 


Chuong,There was several ideas bouncing around but I don't believethere was
any closure.  There is a hole for G711 since we can't use annexa or
annexb.Lifting the support in RFC 3108, section 5.6.3.2 and putting it
intothe TDM Circuit Package would give us a lot of flexibility.Here are the
ideas I know of:1) 

Another option is to extend the TDM Circuit Package (which has been 


previously discussed on the list). The TDM Cicruit Package 


currently has Gain and Echo Control as its properties. So, it's logical 


(IMO) for Silence Suppression to be part of the package as 


well. In fact, it looks like an oversight that it was missed off in the 


first place. 


Regards, 


Wayne Cutler 


2) 



Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.  E.g.: 


Media={Stream=1{ Local { 
v=0 
c=IN IP4 $ 
m=audio $ RTP/AVP 0 13 
}}} 


David Barr 


3) 


I'm starting to think that the answer may be to use the a=silenceSupp 
attribute defined in RFC 3108, section 5.6.3.2. 


Tom Taylor 
  
  


Carl 



-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 2:59 PM 
Cc: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


So what was that discussion about adding silence suppression to TDM package?



Do we use SDP TDM or TDM package or both? 
Or even worse combination of both within 1 command w/some parameters defined
by TDM package and 
some parameters defined by SDP TDM. 
  
  


Tom-PT Taylor wrote: 


As I noted earlier, you do need to specify the properties in the NAS case. 
The SDP TDM draft has certainly had time to ripen, and I will reissue it and

the NAS packages within the next week. 

-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 2:48 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations 
  


I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case 
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.



But I can't remember now whether it was intended to be used in local or 
localControl Descriptor. 
  


Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [ mailto:megaco-admin@ietf.org
<mailto:megaco-admin@ietf.org> ]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<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 **** 
 

-- 

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


------_=_NextPart_001_01C1DA8D.3D524410
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">


<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2>I'm confused, are you talking about section 5.6.3.2 of&nbsp;&nbsp;<SPAN 
class=109342521-02042002>RFC 3108?</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN class=109342521-02042002>I know there was discussion about snagging 
this but that is for ATM</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN class=109342521-02042002>right 
now.</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN 
class=109342521-02042002></SPAN></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN 
class=109342521-02042002></SPAN></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN 
class=109342521-02042002>Carl</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN class=109342521-02042002>&nbsp;</SPAN><SPAN 
class=109342521-02042002>&nbsp;</SPAN></FONT></FONT></FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Chuong N. Nguyen 
  [mailto:Chuong.Nguyen@alcatel.com]<BR><B>Sent:</B> Tuesday, April 02, 2002 
  3:58 PM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] 
  Local/Remote descriptors and Permanent 
  terminations<BR><BR></FONT></DIV>Doesn't the following cover this already? 
  <P>5.6.3.2 The 'silenceSupp' attribute 
  <P>&nbsp;&nbsp; When present, the 'silenceSupp' attribute is used to indicate 
  the use <BR>&nbsp;&nbsp; or non-use of silence suppression.&nbsp; The format 
  of the 'silenceSupp' <BR>&nbsp;&nbsp; media attribute line is as follows: 
  <P>&nbsp;&nbsp; a=silenceSupp: &lt;silenceSuppEnable&gt; &lt;silenceTimer&gt; 
  &lt;suppPref&gt; &lt;sidUse&gt; 
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &lt;fxnslevel&gt; <BR>&nbsp; <BR>&nbsp; <BR>&nbsp; <BR>&nbsp; 
  <P>Carl Rutter wrote: 
  <BLOCKQUOTE TYPE="CITE"><SPAN class=967084920-02042002><FONT 
    face=Arial><FONT color=#0000ff><FONT size=-1>All good questions another I 
    would add is:</SPAN><SPAN class=967084920-02042002></FONT></FONT></FONT>If 
    we use SDP for TDM going forward&nbsp;</SPAN><SPAN 
    class=967084920-02042002>how is silence suppression implemented?</SPAN><SPAN 
    class=967084920-02042002></SPAN><SPAN class=967084920-02042002> 
    <BR>Carl&nbsp;</SPAN> 
    <BLOCKQUOTE>
      <DIV class=OutlookMessageHeader dir=ltr><FONT face=Tahoma><FONT 
      size=-1>-----Original Message-----</FONT></FONT> <BR><FONT 
      face=Tahoma><FONT size=-1><B>From:</B> Chuong N. Nguyen [<A 
      href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</FONT></FONT> 
      <BR><FONT face=Tahoma><FONT size=-1><B>Sent:</B> Tuesday, April 02, 2002 
      3:41 PM</FONT></FONT> <BR><FONT face=Tahoma><FONT size=-1><B>To:</B> 
      megaco@ietf.org</FONT></FONT> <BR><FONT face=Tahoma><FONT 
      size=-1><B>Subject:</B> Re: [Megaco] Local/Remote descriptors and 
      Permanent terminations</FONT></FONT></DIV>
      <P><BR>I thought the reason that we decided to have SDP TDM is to get away 
      from TDM package <BR>to be more inline w/how we specify RTP termination 
      characteristics. <BR>Also to reuse the good stuffs from RTP/ATM SDP. 
      <P>I guess we can start by asking the questions 
      <P>1) Can we live w/o the TDM package? <BR>2) Can we just use SDP for TDM 
      going forward? <BR>3) For backward compatibility, just leave TDM package 
      as is and don't extend it anymore. 
      <P>For the TDM package, echo control is understood but the Gain control is 
      not quite right. <BR>I have discussed the Gain control before and gotten 
      nowhere. 
      <P>Gain control is also defined in the SDP for ATM which seems more 
      correct. <BR>&nbsp; <BR>&nbsp; 
      <P>Carl Rutter wrote: 
      <BLOCKQUOTE TYPE="CITE"><SPAN class=491101120-02042002><FONT 
        size=-1><FONT face=Arial><FONT color=#0000ff>Chuong,</SPAN><SPAN 
        class=491101120-02042002></SPAN><SPAN class=491101120-02042002>There was 
        several ideas bouncing around but I don't believe</SPAN><SPAN 
        class=491101120-02042002>there was any closure.&nbsp; There is a hole 
        for G711 since we can't use&nbsp;</SPAN><SPAN 
        class=491101120-02042002>annexa or annexb.</SPAN><SPAN 
        class=491101120-02042002>Lifting the support in </FONT></FONT><FONT 
        face="Times New Roman"><FONT color=#000000>RFC 3108, section 5.6.3.2 and 
        putting it into</SPAN><SPAN class=491101120-02042002></FONT></FONT>the 
        TDM Circuit Package would give us a lot of flexibility.</SPAN><SPAN 
        class=491101120-02042002></SPAN><SPAN class=491101120-02042002><FONT 
        face=Arial><FONT color=#0000ff>Here are the ideas I know of:</SPAN><SPAN 
        class=491101120-02042002>1)</FONT></FONT></FONT></SPAN><SPAN 
        class=491101120-02042002> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>Another option is 
        to extend the TDM Circuit Package (which has been</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>previously 
        discussed on the list). The TDM Cicruit Package</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>currently has Gain 
        and Echo Control as its properties. So, it's 
        logical</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>(IMO) for Silence 
        Suppression to be part of the package as</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>well. In fact, it 
        looks like an oversight that it was missed off in 
        the</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>first 
        place.</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT 
        size=-1>Regards,</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>Wayne<SPAN 
        class=491101120-02042002> Cutler</FONT></FONT></FONT></SPAN> 
        <P><SPAN class=491101120-02042002><FONT face=Arial><FONT 
        color=#0000ff><FONT size=-1>2)</FONT></FONT></FONT></SPAN> <BR><SPAN 
        class=491101120-02042002>
        <P><FONT size=-1>Another possibility is to use payload 13 as defined in 
        draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</FONT> 
        <P><FONT size=-1>Media={Stream=1{ Local {</FONT> <BR><FONT 
        size=-1>v=0</FONT> <BR><FONT size=-1>c=IN IP4 $</FONT> <BR><FONT 
        size=-1>m=audio $ RTP/AVP 0 13</FONT> <BR><FONT size=-1>}}}</FONT> 
        <P><SPAN class=491101120-02042002><FONT size=-1>David Barr</FONT></SPAN> 

        <P><SPAN class=491101120-02042002><FONT size=-1>3)</FONT></SPAN> 
        <P><SPAN class=491101120-02042002></SPAN><SPAN 
        class=491101120-02042002><FONT size=-1>I'm starting to think that the 
        answer may be to use the a=silenceSupp</FONT> <BR><FONT 
        size=-1>attribute defined in RFC 3108, section 5.6.3.2.</FONT> 
        <P><SPAN class=491101120-02042002><FONT size=-1>Tom Taylor</FONT></SPAN> 
        <BR>&nbsp; <BR>&nbsp; 
        <P><SPAN class=491101120-02042002><FONT face=Arial><FONT 
        color=#0000ff><FONT size=-1>Carl</FONT></FONT></FONT></SPAN> 
        <BR></SPAN></SPAN></SPAN>
        <BLOCKQUOTE>
          <DIV class=OutlookMessageHeader dir=ltr><FONT face=Tahoma><FONT 
          size=-1>-----Original Message-----</FONT></FONT> <BR><FONT 
          face=Tahoma><FONT size=-1><B>From:</B> Chuong N. Nguyen [<A 
          href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</FONT></FONT> 
          <BR><FONT face=Tahoma><FONT size=-1><B>Sent:</B> Tuesday, April 02, 
          2002 2:59 PM</FONT></FONT> <BR><FONT face=Tahoma><FONT 
          size=-1><B>Cc:</B> megaco@ietf.org</FONT></FONT> <BR><FONT 
          face=Tahoma><FONT size=-1><B>Subject:</B> Re: [Megaco] Local/Remote 
          descriptors and Permanent terminations</FONT></FONT></DIV>
          <P><BR>So what was that discussion about adding silence suppression to 
          TDM package? 
          <P>Do we use SDP TDM or TDM package or both? <BR>Or even worse 
          combination of both within 1 command w/some parameters defined by TDM 
          package and <BR>some parameters defined by SDP TDM. <BR>&nbsp; 
          <BR>&nbsp; 
          <P>Tom-PT Taylor wrote: 
          <BLOCKQUOTE TYPE="CITE">As I noted earlier, you do need to specify 
            the properties in the NAS case. <BR>The SDP TDM draft has certainly 
            had time to ripen, and I will reissue it and <BR>the NAS packages 
            within the next week. 
            <P>-----Original Message----- <BR>From: Chuong N. Nguyen [<A 
            href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>] 
            <BR>Sent: Tuesday, April 02, 2002 2:48 PM <BR>To: megaco@ietf.org 
            <BR>Subject: Re: [Megaco] Local/Remote descriptors and Permanent 
            terminations <BR>&nbsp; 
            <P>I don't know about the sendrecv issue here. <BR>I don't know what 
            you mean by SDP parameters are of no significance in case <BR>of 
            phy. term. <BR>Tom wrote the SDP TDM draft which I wonder what is 
            the status of this draft. 
            <P>But I can't remember now whether it was intended to be used in 
            local or <BR>localControl Descriptor. <BR>&nbsp; 
            <P>Madhu Babu Brahmanapally wrote: <BR>HI Rajesh/All, <BR>Not all 
            parameters might be useful for the MG/MGC in case of physical 
            <BR>terminations. The SDP parameters are of no significance in case 
            of physical <BR>terminations (in normal scenario). Hence the mode 
            was set to "sendrecv" <BR>without specifying the local/remote 
            descriptor information. <BR>Regards <BR>Madhubabu <BR>-----Original 
            Message----- <BR>From: megaco-admin@ietf.org [<A 
            href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]On 
            Behalf Of <BR>Rajesh N <BR>Sent: Tuesday, April 02, 2002 11:32 AM 
            <BR>To: megaco@ietf.org <BR>Subject: [Megaco] Local/Remote 
            descriptors and Permanent terminations <BR>Hi, <BR>Sometime back 
            there was a thread regarding usage of SendRecv mode for an 
            <BR>ephemeral termination, when Remote Descriptor values are yet to 
            be defined. <BR>And one of the choices for the MG in such a 
            situation is to reply back with <BR>error 411, "missing remote or 
            local descriptor". <BR>I would like to know, what is the 
            significance of this problem w.r.to <BR>permanent terminations. The 
            example call flow in the draft shows a Modify <BR>request for a 
            permanent termination, from MGC to MG1, in which mode is set <BR>as 
            SendRecv and&nbsp; the Local descriptor values alone are being 
            provided. <BR>Are local and remote descriptors relevant for physical 
            terminations? If <BR>yes, where should I get the values from? 
            <BR>Thanks <BR>Regards, <BR>Rajesh N 
            <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>[This E-mail was scanned for viruses and is clean.] 
            <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; Alcatel USA, 
            Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            Internet: Chuong.Nguyen@usa.alcatel.com <BR>&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; **** The opinions 
            expressed are not those of Alcatel USA, Inc **** 
          <BR>&nbsp;</P></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;</BLOCKQUOTE></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;</BLOCKQUOTE></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; 
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1DA8D.3D524410--

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


From daemon@ns.ietf.org  Tue Apr  2 17:04: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 RAA05323
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:04:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA17244
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 17:04: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 QAA14948;
	Tue, 2 Apr 2002 16:30: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 QAA14843
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:30:28 -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 QAA04172
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:30:18 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0NG8>; Tue, 2 Apr 2002 16:27:57 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C47@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 16:27:49 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DA8D.3D524410"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1DA8D.3D524410
Content-Type: text/plain;
	charset="iso-8859-1"

I'm confused, are you talking about section 5.6.3.2 of  RFC 3108?
I know there was discussion about snagging this but that is for ATM
right now.
 
 
Carl
  

-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 3:58 PM
To: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


Doesn't the following cover this already? 

5.6.3.2 The 'silenceSupp' attribute 


   When present, the 'silenceSupp' attribute is used to indicate the use 
   or non-use of silence suppression.  The format of the 'silenceSupp' 
   media attribute line is as follows: 


   a=silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse> 
                   <fxnslevel> 
  
  
  
  


Carl Rutter wrote: 


All good questions another I would add is:If we use SDP for TDM going
forward how is silence suppression implemented? 
Carl  

-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 3:41 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


I thought the reason that we decided to have SDP TDM is to get away from TDM
package 
to be more inline w/how we specify RTP termination characteristics. 
Also to reuse the good stuffs from RTP/ATM SDP. 


I guess we can start by asking the questions 


1) Can we live w/o the TDM package? 
2) Can we just use SDP for TDM going forward? 
3) For backward compatibility, just leave TDM package as is and don't extend
it anymore. 


For the TDM package, echo control is understood but the Gain control is not
quite right. 
I have discussed the Gain control before and gotten nowhere. 


Gain control is also defined in the SDP for ATM which seems more correct. 
  
  


Carl Rutter wrote: 


Chuong,There was several ideas bouncing around but I don't believethere was
any closure.  There is a hole for G711 since we can't use annexa or
annexb.Lifting the support in RFC 3108, section 5.6.3.2 and putting it
intothe TDM Circuit Package would give us a lot of flexibility.Here are the
ideas I know of:1) 

Another option is to extend the TDM Circuit Package (which has been 


previously discussed on the list). The TDM Cicruit Package 


currently has Gain and Echo Control as its properties. So, it's logical 


(IMO) for Silence Suppression to be part of the package as 


well. In fact, it looks like an oversight that it was missed off in the 


first place. 


Regards, 


Wayne Cutler 


2) 



Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.  E.g.: 


Media={Stream=1{ Local { 
v=0 
c=IN IP4 $ 
m=audio $ RTP/AVP 0 13 
}}} 


David Barr 


3) 


I'm starting to think that the answer may be to use the a=silenceSupp 
attribute defined in RFC 3108, section 5.6.3.2. 


Tom Taylor 
  
  


Carl 



-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 2:59 PM 
Cc: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


So what was that discussion about adding silence suppression to TDM package?



Do we use SDP TDM or TDM package or both? 
Or even worse combination of both within 1 command w/some parameters defined
by TDM package and 
some parameters defined by SDP TDM. 
  
  


Tom-PT Taylor wrote: 


As I noted earlier, you do need to specify the properties in the NAS case. 
The SDP TDM draft has certainly had time to ripen, and I will reissue it and

the NAS packages within the next week. 

-----Original Message----- 
From: Chuong N. Nguyen [ mailto:Chuong.Nguyen@alcatel.com
<mailto:Chuong.Nguyen@alcatel.com> ] 
Sent: Tuesday, April 02, 2002 2:48 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations 
  


I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case 
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.



But I can't remember now whether it was intended to be used in local or 
localControl Descriptor. 
  


Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [ mailto:megaco-admin@ietf.org
<mailto:megaco-admin@ietf.org> ]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<https://www1.ietf.org/mailman/listinfo/megaco>  
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco
<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 **** 
 

-- 

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


------_=_NextPart_001_01C1DA8D.3D524410
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">


<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2>I'm confused, are you talking about section 5.6.3.2 of&nbsp;&nbsp;<SPAN 
class=109342521-02042002>RFC 3108?</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN class=109342521-02042002>I know there was discussion about snagging 
this but that is for ATM</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN class=109342521-02042002>right 
now.</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN 
class=109342521-02042002></SPAN></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN 
class=109342521-02042002></SPAN></FONT></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN 
class=109342521-02042002>Carl</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=448232421-02042002><FONT face=Arial><FONT color=#0000ff><FONT 
size=2><SPAN class=109342521-02042002>&nbsp;</SPAN><SPAN 
class=109342521-02042002>&nbsp;</SPAN></FONT></FONT></FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Chuong N. Nguyen 
  [mailto:Chuong.Nguyen@alcatel.com]<BR><B>Sent:</B> Tuesday, April 02, 2002 
  3:58 PM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] 
  Local/Remote descriptors and Permanent 
  terminations<BR><BR></FONT></DIV>Doesn't the following cover this already? 
  <P>5.6.3.2 The 'silenceSupp' attribute 
  <P>&nbsp;&nbsp; When present, the 'silenceSupp' attribute is used to indicate 
  the use <BR>&nbsp;&nbsp; or non-use of silence suppression.&nbsp; The format 
  of the 'silenceSupp' <BR>&nbsp;&nbsp; media attribute line is as follows: 
  <P>&nbsp;&nbsp; a=silenceSupp: &lt;silenceSuppEnable&gt; &lt;silenceTimer&gt; 
  &lt;suppPref&gt; &lt;sidUse&gt; 
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &lt;fxnslevel&gt; <BR>&nbsp; <BR>&nbsp; <BR>&nbsp; <BR>&nbsp; 
  <P>Carl Rutter wrote: 
  <BLOCKQUOTE TYPE="CITE"><SPAN class=967084920-02042002><FONT 
    face=Arial><FONT color=#0000ff><FONT size=-1>All good questions another I 
    would add is:</SPAN><SPAN class=967084920-02042002></FONT></FONT></FONT>If 
    we use SDP for TDM going forward&nbsp;</SPAN><SPAN 
    class=967084920-02042002>how is silence suppression implemented?</SPAN><SPAN 
    class=967084920-02042002></SPAN><SPAN class=967084920-02042002> 
    <BR>Carl&nbsp;</SPAN> 
    <BLOCKQUOTE>
      <DIV class=OutlookMessageHeader dir=ltr><FONT face=Tahoma><FONT 
      size=-1>-----Original Message-----</FONT></FONT> <BR><FONT 
      face=Tahoma><FONT size=-1><B>From:</B> Chuong N. Nguyen [<A 
      href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</FONT></FONT> 
      <BR><FONT face=Tahoma><FONT size=-1><B>Sent:</B> Tuesday, April 02, 2002 
      3:41 PM</FONT></FONT> <BR><FONT face=Tahoma><FONT size=-1><B>To:</B> 
      megaco@ietf.org</FONT></FONT> <BR><FONT face=Tahoma><FONT 
      size=-1><B>Subject:</B> Re: [Megaco] Local/Remote descriptors and 
      Permanent terminations</FONT></FONT></DIV>
      <P><BR>I thought the reason that we decided to have SDP TDM is to get away 
      from TDM package <BR>to be more inline w/how we specify RTP termination 
      characteristics. <BR>Also to reuse the good stuffs from RTP/ATM SDP. 
      <P>I guess we can start by asking the questions 
      <P>1) Can we live w/o the TDM package? <BR>2) Can we just use SDP for TDM 
      going forward? <BR>3) For backward compatibility, just leave TDM package 
      as is and don't extend it anymore. 
      <P>For the TDM package, echo control is understood but the Gain control is 
      not quite right. <BR>I have discussed the Gain control before and gotten 
      nowhere. 
      <P>Gain control is also defined in the SDP for ATM which seems more 
      correct. <BR>&nbsp; <BR>&nbsp; 
      <P>Carl Rutter wrote: 
      <BLOCKQUOTE TYPE="CITE"><SPAN class=491101120-02042002><FONT 
        size=-1><FONT face=Arial><FONT color=#0000ff>Chuong,</SPAN><SPAN 
        class=491101120-02042002></SPAN><SPAN class=491101120-02042002>There was 
        several ideas bouncing around but I don't believe</SPAN><SPAN 
        class=491101120-02042002>there was any closure.&nbsp; There is a hole 
        for G711 since we can't use&nbsp;</SPAN><SPAN 
        class=491101120-02042002>annexa or annexb.</SPAN><SPAN 
        class=491101120-02042002>Lifting the support in </FONT></FONT><FONT 
        face="Times New Roman"><FONT color=#000000>RFC 3108, section 5.6.3.2 and 
        putting it into</SPAN><SPAN class=491101120-02042002></FONT></FONT>the 
        TDM Circuit Package would give us a lot of flexibility.</SPAN><SPAN 
        class=491101120-02042002></SPAN><SPAN class=491101120-02042002><FONT 
        face=Arial><FONT color=#0000ff>Here are the ideas I know of:</SPAN><SPAN 
        class=491101120-02042002>1)</FONT></FONT></FONT></SPAN><SPAN 
        class=491101120-02042002> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>Another option is 
        to extend the TDM Circuit Package (which has been</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>previously 
        discussed on the list). The TDM Cicruit Package</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>currently has Gain 
        and Echo Control as its properties. So, it's 
        logical</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>(IMO) for Silence 
        Suppression to be part of the package as</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>well. In fact, it 
        looks like an oversight that it was missed off in 
        the</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>first 
        place.</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT 
        size=-1>Regards,</FONT></FONT></FONT> 
        <P><FONT face=Arial><FONT color=#0000ff><FONT size=-1>Wayne<SPAN 
        class=491101120-02042002> Cutler</FONT></FONT></FONT></SPAN> 
        <P><SPAN class=491101120-02042002><FONT face=Arial><FONT 
        color=#0000ff><FONT size=-1>2)</FONT></FONT></FONT></SPAN> <BR><SPAN 
        class=491101120-02042002>
        <P><FONT size=-1>Another possibility is to use payload 13 as defined in 
        draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</FONT> 
        <P><FONT size=-1>Media={Stream=1{ Local {</FONT> <BR><FONT 
        size=-1>v=0</FONT> <BR><FONT size=-1>c=IN IP4 $</FONT> <BR><FONT 
        size=-1>m=audio $ RTP/AVP 0 13</FONT> <BR><FONT size=-1>}}}</FONT> 
        <P><SPAN class=491101120-02042002><FONT size=-1>David Barr</FONT></SPAN> 

        <P><SPAN class=491101120-02042002><FONT size=-1>3)</FONT></SPAN> 
        <P><SPAN class=491101120-02042002></SPAN><SPAN 
        class=491101120-02042002><FONT size=-1>I'm starting to think that the 
        answer may be to use the a=silenceSupp</FONT> <BR><FONT 
        size=-1>attribute defined in RFC 3108, section 5.6.3.2.</FONT> 
        <P><SPAN class=491101120-02042002><FONT size=-1>Tom Taylor</FONT></SPAN> 
        <BR>&nbsp; <BR>&nbsp; 
        <P><SPAN class=491101120-02042002><FONT face=Arial><FONT 
        color=#0000ff><FONT size=-1>Carl</FONT></FONT></FONT></SPAN> 
        <BR></SPAN></SPAN></SPAN>
        <BLOCKQUOTE>
          <DIV class=OutlookMessageHeader dir=ltr><FONT face=Tahoma><FONT 
          size=-1>-----Original Message-----</FONT></FONT> <BR><FONT 
          face=Tahoma><FONT size=-1><B>From:</B> Chuong N. Nguyen [<A 
          href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</FONT></FONT> 
          <BR><FONT face=Tahoma><FONT size=-1><B>Sent:</B> Tuesday, April 02, 
          2002 2:59 PM</FONT></FONT> <BR><FONT face=Tahoma><FONT 
          size=-1><B>Cc:</B> megaco@ietf.org</FONT></FONT> <BR><FONT 
          face=Tahoma><FONT size=-1><B>Subject:</B> Re: [Megaco] Local/Remote 
          descriptors and Permanent terminations</FONT></FONT></DIV>
          <P><BR>So what was that discussion about adding silence suppression to 
          TDM package? 
          <P>Do we use SDP TDM or TDM package or both? <BR>Or even worse 
          combination of both within 1 command w/some parameters defined by TDM 
          package and <BR>some parameters defined by SDP TDM. <BR>&nbsp; 
          <BR>&nbsp; 
          <P>Tom-PT Taylor wrote: 
          <BLOCKQUOTE TYPE="CITE">As I noted earlier, you do need to specify 
            the properties in the NAS case. <BR>The SDP TDM draft has certainly 
            had time to ripen, and I will reissue it and <BR>the NAS packages 
            within the next week. 
            <P>-----Original Message----- <BR>From: Chuong N. Nguyen [<A 
            href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>] 
            <BR>Sent: Tuesday, April 02, 2002 2:48 PM <BR>To: megaco@ietf.org 
            <BR>Subject: Re: [Megaco] Local/Remote descriptors and Permanent 
            terminations <BR>&nbsp; 
            <P>I don't know about the sendrecv issue here. <BR>I don't know what 
            you mean by SDP parameters are of no significance in case <BR>of 
            phy. term. <BR>Tom wrote the SDP TDM draft which I wonder what is 
            the status of this draft. 
            <P>But I can't remember now whether it was intended to be used in 
            local or <BR>localControl Descriptor. <BR>&nbsp; 
            <P>Madhu Babu Brahmanapally wrote: <BR>HI Rajesh/All, <BR>Not all 
            parameters might be useful for the MG/MGC in case of physical 
            <BR>terminations. The SDP parameters are of no significance in case 
            of physical <BR>terminations (in normal scenario). Hence the mode 
            was set to "sendrecv" <BR>without specifying the local/remote 
            descriptor information. <BR>Regards <BR>Madhubabu <BR>-----Original 
            Message----- <BR>From: megaco-admin@ietf.org [<A 
            href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]On 
            Behalf Of <BR>Rajesh N <BR>Sent: Tuesday, April 02, 2002 11:32 AM 
            <BR>To: megaco@ietf.org <BR>Subject: [Megaco] Local/Remote 
            descriptors and Permanent terminations <BR>Hi, <BR>Sometime back 
            there was a thread regarding usage of SendRecv mode for an 
            <BR>ephemeral termination, when Remote Descriptor values are yet to 
            be defined. <BR>And one of the choices for the MG in such a 
            situation is to reply back with <BR>error 411, "missing remote or 
            local descriptor". <BR>I would like to know, what is the 
            significance of this problem w.r.to <BR>permanent terminations. The 
            example call flow in the draft shows a Modify <BR>request for a 
            permanent termination, from MGC to MG1, in which mode is set <BR>as 
            SendRecv and&nbsp; the Local descriptor values alone are being 
            provided. <BR>Are local and remote descriptors relevant for physical 
            terminations? If <BR>yes, where should I get the values from? 
            <BR>Thanks <BR>Regards, <BR>Rajesh N 
            <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>[This E-mail was scanned for viruses and is clean.] 
            <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; Alcatel USA, 
            Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
            Internet: Chuong.Nguyen@usa.alcatel.com <BR>&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; **** The opinions 
            expressed are not those of Alcatel USA, Inc **** 
          <BR>&nbsp;</P></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;</BLOCKQUOTE></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;</BLOCKQUOTE></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; 
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1DA8D.3D524410--

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



From megaco-admin@ietf.org  Tue Apr  2 17:07: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 RAA05385
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:07: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 QAA15402;
	Tue, 2 Apr 2002 16:37: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 QAA15375
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:37:00 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04470
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:36:57 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g32LaSV01603;
	Tue, 2 Apr 2002 15:36:28 -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 g32LZUO18971;
	Tue, 2 Apr 2002 15:35: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 g32LZU727442;
	Tue, 2 Apr 2002 15:35:30 -0600 (CST)
Message-ID: <3CAA2422.839D82C4@alcatel.com>
Date: Tue, 02 Apr 2002 15:35:30 -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: Carl Rutter <crutter@telica.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <2415C206C515244DBFB12EC0C064A448404C47@wench>
Content-Type: multipart/alternative;
 boundary="------------649848D302D678D5E3BF55E7"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


Yes, just like you suggested it before instead of snagging it for
TDM package.
Snagg it for the SDP for TDM draft.


Carl Rutter wrote:

> I'm confused, are you talking about section 5.6.3.2 of RFC 3108?I know
> there was discussion about snagging this but that is for ATMright
> now.Carl
>
>      -----Original Message-----
>      From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
>      Sent: Tuesday, April 02, 2002 3:58 PM
>      To: megaco@ietf.org
>      Subject: Re: [Megaco] Local/Remote descriptors and Permanent
>      terminations
>      Doesn't the following cover this already?
>
>      5.6.3.2 The 'silenceSupp' attribute
>
>         When present, the 'silenceSupp' attribute is used to
>      indicate the use
>         or non-use of silence suppression.  The format of the
>      'silenceSupp'
>         media attribute line is as follows:
>
>         a=silenceSupp: <silenceSuppEnable> <silenceTimer>
>      <suppPref> <sidUse>
>                         <fxnslevel>
>
>
>
>
>
>      Carl Rutter wrote:
>
>     > All good questions another I would add is:If we use SDP
>     > for TDM going forward how is silence suppression
>     > implemented?
>     > Carl
>     >
>     >      -----Original Message-----
>     >      From: Chuong N. Nguyen
>     >      [mailto:Chuong.Nguyen@alcatel.com]
>     >      Sent: Tuesday, April 02, 2002 3:41 PM
>     >      To: megaco@ietf.org
>     >      Subject: Re: [Megaco] Local/Remote descriptors
>     >      and Permanent terminations
>     >
>     >
>     >      I thought the reason that we decided to have SDP
>     >      TDM is to get away from TDM package
>     >      to be more inline w/how we specify RTP
>     >      termination characteristics.
>     >      Also to reuse the good stuffs from RTP/ATM SDP.
>     >
>     >      I guess we can start by asking the questions
>     >
>     >      1) Can we live w/o the TDM package?
>     >      2) Can we just use SDP for TDM going forward?
>     >      3) For backward compatibility, just leave TDM
>     >      package as is and don't extend it anymore.
>     >
>     >      For the TDM package, echo control is understood
>     >      but the Gain control is not quite right.
>     >      I have discussed the Gain control before and
>     >      gotten nowhere.
>     >
>     >      Gain control is also defined in the SDP for ATM
>     >      which seems more correct.
>     >
>     >
>     >
>     >      Carl Rutter wrote:
>     >
>     >      > Chuong,There was several ideas bouncing around
>     >      > but I don't believethere was any closure.
>     >      > There is a hole for G711 since we can't
>     >      > use annexa or annexb.Lifting the support in RFC
>     >      > 3108, section 5.6.3.2 and putting it intothe
>     >      > TDM Circuit Package would give us a lot of
>     >      > flexibility.Here are the ideas I know of:1)
>     >      >
>     >      > Another option is to extend the TDM Circuit
>     >      > Package (which has been
>     >      >
>     >      > previously discussed on the list). The TDM
>     >      > Cicruit Package
>     >      >
>     >      > currently has Gain and Echo Control as its
>     >      > properties. So, it's logical
>     >      >
>     >      > (IMO) for Silence Suppression to be part of the
>     >      > package as
>     >      >
>     >      > well. In fact, it looks like an oversight that
>     >      > it was missed off in the
>     >      >
>     >      > first place.
>     >      >
>     >      > Regards,
>     >      >
>     >      > Wayne Cutler
>     >      >
>     >      > 2)
>     >      >
>     >      > Another possibility is to use payload 13 as
>     >      > defined in draft-ietf-avt-rtp-cn-05.  E.g.:
>     >      >
>     >      > Media={Stream=1{ Local {
>     >      > v=0
>     >      > c=IN IP4 $
>     >      > m=audio $ RTP/AVP 0 13
>     >      > }}}
>     >      >
>     >      > David Barr
>     >      >
>     >      > 3)
>     >      >
>     >      > I'm starting to think that the answer may be to
>     >      > use the a=silenceSupp
>     >      > attribute defined in RFC 3108, section 5.6.3.2.
>     >      >
>     >      > Tom Taylor
>     >      >
>     >      >
>     >      >
>     >      > Carl
>     >      >
>     >      >      -----Original Message-----
>     >      >      From: Chuong N. Nguyen
>     >      >      [mailto:Chuong.Nguyen@alcatel.com]
>     >      >      Sent: Tuesday, April 02, 2002 2:59 PM
>     >      >
>     >      >      Cc: megaco@ietf.org
>     >      >      Subject: Re: [Megaco] Local/Remote
>     >      >      descriptors and Permanent
>     >      >      terminations
>     >      >
>     >      >
>     >      >      So what was that discussion about
>     >      >      adding silence suppression to TDM
>     >      >      package?
>     >      >
>     >      >      Do we use SDP TDM or TDM package or
>     >      >      both?
>     >      >      Or even worse combination of both
>     >      >      within 1 command w/some parameters
>     >      >      defined by TDM package and
>     >      >      some parameters defined by SDP TDM.
>     >      >
>     >      >
>     >      >
>     >      >      Tom-PT Taylor wrote:
>     >      >
>     >      >     >  As I noted earlier, you do need to
>     >      >     >  specify the properties in the NAS
>     >      >     >  case.
>     >      >     >  The SDP TDM draft has certainly had
>     >      >     >  time to ripen, and I will reissue
>     >      >     >  it and
>     >      >     >  the NAS packages within the next
>     >      >     >  week.
>     >      >     >
>     >      >     >  -----Original Message-----
>     >      >     >  From: Chuong N. Nguyen
>     >      >     >  [mailto:Chuong.Nguyen@alcatel.com]
>     >      >     >  Sent: Tuesday, April 02, 2002 2:48
>     >      >     >  PM
>     >      >     >  To: megaco@ietf.org
>     >      >     >  Subject: Re: [Megaco] Local/Remote
>     >      >     >  descriptors and Permanent
>     >      >     >  terminations
>     >      >     >
>     >      >     >
>     >      >     >  I don't know about the sendrecv
>     >      >     >  issue here.
>     >      >     >  I don't know what you mean by SDP
>     >      >     >  parameters are of no significance
>     >      >     >  in case
>     >      >     >  of phy. term.
>     >      >     >  Tom wrote the SDP TDM draft which I
>     >      >     >  wonder what is the status of this
>     >      >     >  draft.
>     >      >     >
>     >      >     >  But I can't remember now whether it
>     >      >     >  was intended to be used in local or
>     >      >     >
>     >      >     >  localControl Descriptor.
>     >      >     >
>     >      >     >
>     >      >     >  Madhu Babu Brahmanapally wrote:
>     >      >     >  HI Rajesh/All,
>     >      >     >  Not all parameters might be useful
>     >      >     >  for the MG/MGC in case of physical
>     >      >     >  terminations. The SDP parameters
>     >      >     >  are of no significance in case of
>     >      >     >  physical
>     >      >     >  terminations (in normal scenario).
>     >      >     >  Hence the mode was set to
>     >      >     >  "sendrecv"
>     >      >     >  without specifying the local/remote
>     >      >     >  descriptor information.
>     >      >     >  Regards
>     >      >     >  Madhubabu
>     >      >     >  -----Original Message-----
>     >      >     >  From: megaco-admin@ietf.org
>     >      >     >  [mailto:megaco-admin@ietf.org]On
>     >      >     >  Behalf Of
>     >      >     >  Rajesh N
>     >      >     >  Sent: Tuesday, April 02, 2002 11:32
>     >      >     >  AM
>     >      >     >  To: megaco@ietf.org
>     >      >     >  Subject: [Megaco] Local/Remote
>     >      >     >  descriptors and Permanent
>     >      >     >  terminations
>     >      >     >  Hi,
>     >      >     >  Sometime back there was a thread
>     >      >     >  regarding usage of SendRecv mode
>     >      >     >  for an
>     >      >     >  ephemeral termination, when Remote
>     >      >     >  Descriptor values are yet to be
>     >      >     >  defined.
>     >      >     >  And one of the choices for the MG
>     >      >     >  in such a situation is to reply
>     >      >     >  back with
>     >      >     >  error 411, "missing remote or local
>     >      >     >  descriptor".
>     >      >     >  I would like to know, what is the
>     >      >     >  significance of this problem w.r.to
>     >      >     >
>     >      >     >  permanent terminations. The example
>     >      >     >  call flow in the draft shows a
>     >      >     >  Modify
>     >      >     >  request for a permanent
>     >      >     >  termination, from MGC to MG1, in
>     >      >     >  which mode is set
>     >      >     >  as SendRecv and  the Local
>     >      >     >  descriptor values alone are being
>     >      >     >  provided.
>     >      >     >  Are local and remote descriptors
>     >      >     >  relevant for physical terminations?
>     >      >     >  If
>     >      >     >  yes, where should I get the values
>     >      >     >  from?
>     >      >     >  Thanks
>     >      >     >  Regards,
>     >      >     >  Rajesh N
>     >      >     >  ________
>     >      >     >  ______________________________________
>     >      >     >
>     >      >     >  Megaco mailing list
>     >      >     >  Megaco@ietf.org
>     >      >     >  https://www1.ie
>     >      >     >  f.org/mailman/listinfo/megaco
>     >      >     >  ---
>     >      >     >  [This E-mail was scanned for
>     >      >     >  viruses and is clean.]
>     >      >     >  ______________________
>     >      >     >  ________________________
>     >      >     >  Megaco mailing list
>     >      >     >  Megaco@ietf.org
>     >      >     >  https://www1.ie
>     >      >     >  f.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 ****
>     >      >     >
>     >      >
>     >      >      --
>     >      >        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 ****
>
>
>
--
  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 ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Yes, just like you suggested it before instead of snagging it for TDM&nbsp;package.
<br>Snagg it for the SDP for TDM draft.
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE=CITE><span class=448232421-02042002><font face="Arial"><font color="#0000FF"><font size=-1>I'm
confused, are you talking about section 5.6.3.2 of&nbsp;<span 
class=109342521-02042002>RFC
3108?</span></span><span class=448232421-02042002><span class=109342521-02042002>I
know there was discussion about snagging this but that is for ATM</span></span><span class=448232421-02042002><span class=109342521-02042002>right
now.</span></span><span class=448232421-02042002><span 
class=109342521-02042002></span></span><span class=448232421-02042002><span 
class=109342521-02042002></span></span><span class=448232421-02042002><span 
class=109342521-02042002>Carl</font></font></font></span></span><span class=448232421-02042002><span class=109342521-02042002></span><span 
class=109342521-02042002></span></span>
<blockquote>
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<A HREF="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
3:58 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>
Doesn't the following cover this already?
<p>5.6.3.2 The 'silenceSupp' attribute
<p>&nbsp;&nbsp; When present, the 'silenceSupp' attribute is used to indicate
the use
<br>&nbsp;&nbsp; or non-use of silence suppression.&nbsp; The format of
the 'silenceSupp'
<br>&nbsp;&nbsp; media attribute line is as follows:
<p>&nbsp;&nbsp; a=silenceSupp: &lt;silenceSuppEnable> &lt;silenceTimer>
&lt;suppPref> &lt;sidUse>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;fxnslevel>
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE="CITE"><span class=967084920-02042002><font face="Arial"><font color="#0000FF"><font size=-1>All
good questions another I would add is:</span><span class=967084920-02042002></font></font></font>If
we use SDP for TDM going forward&nbsp;</span><span 
    class=967084920-02042002>how
is silence suppression implemented?</span><span 
    class=967084920-02042002></span><span class=967084920-02042002>
<br>Carl&nbsp;</span>
<blockquote>
<div class=OutlookMessageHeader dir=ltr><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
3:41 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>

<p><br>I thought the reason that we decided to have SDP TDM is to get away
from TDM package
<br>to be more inline w/how we specify RTP termination characteristics.
<br>Also to reuse the good stuffs from RTP/ATM SDP.
<p>I guess we can start by asking the questions
<p>1) Can we live w/o the TDM package?
<br>2) Can we just use SDP for TDM going forward?
<br>3) For backward compatibility, just leave TDM package as is and don't
extend it anymore.
<p>For the TDM package, echo control is understood but the Gain control
is not quite right.
<br>I have discussed the Gain control before and gotten nowhere.
<p>Gain control is also defined in the SDP for ATM which seems more correct.
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE="CITE"><span class=491101120-02042002><font size=-1><font face="Arial"><font color="#0000FF">Chuong,</span><span 
        class=491101120-02042002></span><span class=491101120-02042002>There
was several ideas bouncing around but I don't believe</span><span 
        class=491101120-02042002>there
was any closure.&nbsp; There is a hole for G711 since we can't use&nbsp;</span><span 
        class=491101120-02042002>annexa
or annexb.</span><span 
        class=491101120-02042002>Lifting the support
in </font></font><font face="Times New Roman"><font color="#000000">RFC
3108, section 5.6.3.2 and putting it into</span><span class=491101120-02042002></font></font>the
TDM Circuit Package would give us a lot of flexibility.</span><span 
        class=491101120-02042002></span><span class=491101120-02042002><font face="Arial"><font color="#0000FF">Here
are the ideas I know of:</span><span 
        class=491101120-02042002>1)</font></font></font></span><span 
        class=491101120-02042002>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Another option
is to extend the TDM Circuit Package (which has been</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>previously discussed
on the list). The TDM Cicruit Package</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>currently has
Gain and Echo Control as its properties. So, it's logical</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>(IMO) for Silence
Suppression to be part of the package as</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>well. In fact,
it looks like an oversight that it was missed off in the</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>first place.</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Regards,</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Wayne<span 
        class=491101120-02042002>
Cutler</font></font></font></span>
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>2)</font></font></font></span>
<br><span 
        class=491101120-02042002>
<p><font size=-1>Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</font>
<p><font size=-1>Media={Stream=1{ Local {</font>
<br><font size=-1>v=0</font>
<br><font size=-1>c=IN IP4 $</font>
<br><font size=-1>m=audio $ RTP/AVP 0 13</font>
<br><font size=-1>}}}</font>
<p><span class=491101120-02042002><font size=-1>David Barr</font></span>
<p><span class=491101120-02042002><font size=-1>3)</font></span>
<p><span class=491101120-02042002></span><span 
        class=491101120-02042002><font size=-1>I'm
starting to think that the answer may be to use the a=silenceSupp</font>
<br><font size=-1>attribute defined in RFC 3108, section 5.6.3.2.</font>
<p><span class=491101120-02042002><font size=-1>Tom Taylor</font></span>
<br>&nbsp;
<br>&nbsp;
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>Carl</font></font></font></span>
<br></span></span></span>
<blockquote>
<div class=OutlookMessageHeader dir=ltr><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
2:59 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>Cc:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>

<p><br>So what was that discussion about adding silence suppression to
TDM package?
<p>Do we use SDP TDM or TDM package or both?
<br>Or even worse combination of both within 1 command w/some parameters
defined by TDM package and
<br>some parameters defined by SDP TDM.
<br>&nbsp;
<br>&nbsp;
<p>Tom-PT Taylor wrote:
<blockquote TYPE="CITE">As I noted earlier, you do need to specify the
properties in the NAS case.
<br>The SDP TDM draft has certainly had time to ripen, and I will reissue
it and
<br>the NAS packages within the next week.
<p>-----Original Message-----
<br>From: Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]
<br>Sent: Tuesday, April 02, 2002 2:48 PM
<br>To: megaco@ietf.org
<br>Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
<br>&nbsp;
<p>I don't know about the sendrecv issue here.
<br>I don't know what you mean by SDP parameters are of no significance
in case
<br>of phy. term.
<br>Tom wrote the SDP TDM draft which I wonder what is the status of this
draft.
<p>But I can't remember now whether it was intended to be used in local
or
<br>localControl Descriptor.
<br>&nbsp;
<p>Madhu Babu Brahmanapally wrote:
<br>HI Rajesh/All,
<br>Not all parameters might be useful for the MG/MGC in case of physical
<br>terminations. The SDP parameters are of no significance in case of
physical
<br>terminations (in normal scenario). Hence the mode was set to "sendrecv"
<br>without specifying the local/remote descriptor information.
<br>Regards
<br>Madhubabu
<br>-----Original Message-----
<br>From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]On
Behalf Of
<br>Rajesh N
<br>Sent: Tuesday, April 02, 2002 11:32 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Local/Remote descriptors and Permanent terminations
<br>Hi,
<br>Sometime back there was a thread regarding usage of SendRecv mode for
an
<br>ephemeral termination, when Remote Descriptor values are yet to be
defined.
<br>And one of the choices for the MG in such a situation is to reply back
with
<br>error 411, "missing remote or local descriptor".
<br>I would like to know, what is the significance of this problem w.r.to
<br>permanent terminations. The example call flow in the draft shows a
Modify
<br>request for a permanent termination, from MGC to MG1, in which mode
is set
<br>as SendRecv and&nbsp; the Local descriptor values alone are being provided.
<br>Are local and remote descriptors relevant for physical terminations?
If
<br>yes, where should I get the values from?
<br>Thanks
<br>Regards,
<br>Rajesh N
<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>[This E-mail was scanned for viruses and is clean.]
<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; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>&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; **** The opinions expressed are not those of Alcatel USA, Inc
****
<br>&nbsp;</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;</blockquote>
</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;</blockquote>
</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;</blockquote>
</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>

--------------649848D302D678D5E3BF55E7--


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


From daemon@ns.ietf.org  Tue Apr  2 17:07: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 RAA05393
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:07:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA17432
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 17:07: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 QAA15402;
	Tue, 2 Apr 2002 16:37: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 QAA15375
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:37:00 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04470
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:36:57 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g32LaSV01603;
	Tue, 2 Apr 2002 15:36:28 -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 g32LZUO18971;
	Tue, 2 Apr 2002 15:35: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 g32LZU727442;
	Tue, 2 Apr 2002 15:35:30 -0600 (CST)
Message-ID: <3CAA2422.839D82C4@alcatel.com>
Date: Tue, 02 Apr 2002 15:35:30 -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: Carl Rutter <crutter@telica.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <2415C206C515244DBFB12EC0C064A448404C47@wench>
Content-Type: multipart/alternative;
 boundary="------------649848D302D678D5E3BF55E7"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


Yes, just like you suggested it before instead of snagging it for
TDM package.
Snagg it for the SDP for TDM draft.


Carl Rutter wrote:

> I'm confused, are you talking about section 5.6.3.2 of RFC 3108?I know
> there was discussion about snagging this but that is for ATMright
> now.Carl
>
>      -----Original Message-----
>      From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
>      Sent: Tuesday, April 02, 2002 3:58 PM
>      To: megaco@ietf.org
>      Subject: Re: [Megaco] Local/Remote descriptors and Permanent
>      terminations
>      Doesn't the following cover this already?
>
>      5.6.3.2 The 'silenceSupp' attribute
>
>         When present, the 'silenceSupp' attribute is used to
>      indicate the use
>         or non-use of silence suppression.  The format of the
>      'silenceSupp'
>         media attribute line is as follows:
>
>         a=silenceSupp: <silenceSuppEnable> <silenceTimer>
>      <suppPref> <sidUse>
>                         <fxnslevel>
>
>
>
>
>
>      Carl Rutter wrote:
>
>     > All good questions another I would add is:If we use SDP
>     > for TDM going forward how is silence suppression
>     > implemented?
>     > Carl
>     >
>     >      -----Original Message-----
>     >      From: Chuong N. Nguyen
>     >      [mailto:Chuong.Nguyen@alcatel.com]
>     >      Sent: Tuesday, April 02, 2002 3:41 PM
>     >      To: megaco@ietf.org
>     >      Subject: Re: [Megaco] Local/Remote descriptors
>     >      and Permanent terminations
>     >
>     >
>     >      I thought the reason that we decided to have SDP
>     >      TDM is to get away from TDM package
>     >      to be more inline w/how we specify RTP
>     >      termination characteristics.
>     >      Also to reuse the good stuffs from RTP/ATM SDP.
>     >
>     >      I guess we can start by asking the questions
>     >
>     >      1) Can we live w/o the TDM package?
>     >      2) Can we just use SDP for TDM going forward?
>     >      3) For backward compatibility, just leave TDM
>     >      package as is and don't extend it anymore.
>     >
>     >      For the TDM package, echo control is understood
>     >      but the Gain control is not quite right.
>     >      I have discussed the Gain control before and
>     >      gotten nowhere.
>     >
>     >      Gain control is also defined in the SDP for ATM
>     >      which seems more correct.
>     >
>     >
>     >
>     >      Carl Rutter wrote:
>     >
>     >      > Chuong,There was several ideas bouncing around
>     >      > but I don't believethere was any closure.
>     >      > There is a hole for G711 since we can't
>     >      > use annexa or annexb.Lifting the support in RFC
>     >      > 3108, section 5.6.3.2 and putting it intothe
>     >      > TDM Circuit Package would give us a lot of
>     >      > flexibility.Here are the ideas I know of:1)
>     >      >
>     >      > Another option is to extend the TDM Circuit
>     >      > Package (which has been
>     >      >
>     >      > previously discussed on the list). The TDM
>     >      > Cicruit Package
>     >      >
>     >      > currently has Gain and Echo Control as its
>     >      > properties. So, it's logical
>     >      >
>     >      > (IMO) for Silence Suppression to be part of the
>     >      > package as
>     >      >
>     >      > well. In fact, it looks like an oversight that
>     >      > it was missed off in the
>     >      >
>     >      > first place.
>     >      >
>     >      > Regards,
>     >      >
>     >      > Wayne Cutler
>     >      >
>     >      > 2)
>     >      >
>     >      > Another possibility is to use payload 13 as
>     >      > defined in draft-ietf-avt-rtp-cn-05.  E.g.:
>     >      >
>     >      > Media={Stream=1{ Local {
>     >      > v=0
>     >      > c=IN IP4 $
>     >      > m=audio $ RTP/AVP 0 13
>     >      > }}}
>     >      >
>     >      > David Barr
>     >      >
>     >      > 3)
>     >      >
>     >      > I'm starting to think that the answer may be to
>     >      > use the a=silenceSupp
>     >      > attribute defined in RFC 3108, section 5.6.3.2.
>     >      >
>     >      > Tom Taylor
>     >      >
>     >      >
>     >      >
>     >      > Carl
>     >      >
>     >      >      -----Original Message-----
>     >      >      From: Chuong N. Nguyen
>     >      >      [mailto:Chuong.Nguyen@alcatel.com]
>     >      >      Sent: Tuesday, April 02, 2002 2:59 PM
>     >      >
>     >      >      Cc: megaco@ietf.org
>     >      >      Subject: Re: [Megaco] Local/Remote
>     >      >      descriptors and Permanent
>     >      >      terminations
>     >      >
>     >      >
>     >      >      So what was that discussion about
>     >      >      adding silence suppression to TDM
>     >      >      package?
>     >      >
>     >      >      Do we use SDP TDM or TDM package or
>     >      >      both?
>     >      >      Or even worse combination of both
>     >      >      within 1 command w/some parameters
>     >      >      defined by TDM package and
>     >      >      some parameters defined by SDP TDM.
>     >      >
>     >      >
>     >      >
>     >      >      Tom-PT Taylor wrote:
>     >      >
>     >      >     >  As I noted earlier, you do need to
>     >      >     >  specify the properties in the NAS
>     >      >     >  case.
>     >      >     >  The SDP TDM draft has certainly had
>     >      >     >  time to ripen, and I will reissue
>     >      >     >  it and
>     >      >     >  the NAS packages within the next
>     >      >     >  week.
>     >      >     >
>     >      >     >  -----Original Message-----
>     >      >     >  From: Chuong N. Nguyen
>     >      >     >  [mailto:Chuong.Nguyen@alcatel.com]
>     >      >     >  Sent: Tuesday, April 02, 2002 2:48
>     >      >     >  PM
>     >      >     >  To: megaco@ietf.org
>     >      >     >  Subject: Re: [Megaco] Local/Remote
>     >      >     >  descriptors and Permanent
>     >      >     >  terminations
>     >      >     >
>     >      >     >
>     >      >     >  I don't know about the sendrecv
>     >      >     >  issue here.
>     >      >     >  I don't know what you mean by SDP
>     >      >     >  parameters are of no significance
>     >      >     >  in case
>     >      >     >  of phy. term.
>     >      >     >  Tom wrote the SDP TDM draft which I
>     >      >     >  wonder what is the status of this
>     >      >     >  draft.
>     >      >     >
>     >      >     >  But I can't remember now whether it
>     >      >     >  was intended to be used in local or
>     >      >     >
>     >      >     >  localControl Descriptor.
>     >      >     >
>     >      >     >
>     >      >     >  Madhu Babu Brahmanapally wrote:
>     >      >     >  HI Rajesh/All,
>     >      >     >  Not all parameters might be useful
>     >      >     >  for the MG/MGC in case of physical
>     >      >     >  terminations. The SDP parameters
>     >      >     >  are of no significance in case of
>     >      >     >  physical
>     >      >     >  terminations (in normal scenario).
>     >      >     >  Hence the mode was set to
>     >      >     >  "sendrecv"
>     >      >     >  without specifying the local/remote
>     >      >     >  descriptor information.
>     >      >     >  Regards
>     >      >     >  Madhubabu
>     >      >     >  -----Original Message-----
>     >      >     >  From: megaco-admin@ietf.org
>     >      >     >  [mailto:megaco-admin@ietf.org]On
>     >      >     >  Behalf Of
>     >      >     >  Rajesh N
>     >      >     >  Sent: Tuesday, April 02, 2002 11:32
>     >      >     >  AM
>     >      >     >  To: megaco@ietf.org
>     >      >     >  Subject: [Megaco] Local/Remote
>     >      >     >  descriptors and Permanent
>     >      >     >  terminations
>     >      >     >  Hi,
>     >      >     >  Sometime back there was a thread
>     >      >     >  regarding usage of SendRecv mode
>     >      >     >  for an
>     >      >     >  ephemeral termination, when Remote
>     >      >     >  Descriptor values are yet to be
>     >      >     >  defined.
>     >      >     >  And one of the choices for the MG
>     >      >     >  in such a situation is to reply
>     >      >     >  back with
>     >      >     >  error 411, "missing remote or local
>     >      >     >  descriptor".
>     >      >     >  I would like to know, what is the
>     >      >     >  significance of this problem w.r.to
>     >      >     >
>     >      >     >  permanent terminations. The example
>     >      >     >  call flow in the draft shows a
>     >      >     >  Modify
>     >      >     >  request for a permanent
>     >      >     >  termination, from MGC to MG1, in
>     >      >     >  which mode is set
>     >      >     >  as SendRecv and  the Local
>     >      >     >  descriptor values alone are being
>     >      >     >  provided.
>     >      >     >  Are local and remote descriptors
>     >      >     >  relevant for physical terminations?
>     >      >     >  If
>     >      >     >  yes, where should I get the values
>     >      >     >  from?
>     >      >     >  Thanks
>     >      >     >  Regards,
>     >      >     >  Rajesh N
>     >      >     >  ________
>     >      >     >  ______________________________________
>     >      >     >
>     >      >     >  Megaco mailing list
>     >      >     >  Megaco@ietf.org
>     >      >     >  https://www1.ie
>     >      >     >  f.org/mailman/listinfo/megaco
>     >      >     >  ---
>     >      >     >  [This E-mail was scanned for
>     >      >     >  viruses and is clean.]
>     >      >     >  ______________________
>     >      >     >  ________________________
>     >      >     >  Megaco mailing list
>     >      >     >  Megaco@ietf.org
>     >      >     >  https://www1.ie
>     >      >     >  f.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 ****
>     >      >     >
>     >      >
>     >      >      --
>     >      >        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 ****
>
>
>
--
  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 ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Yes, just like you suggested it before instead of snagging it for TDM&nbsp;package.
<br>Snagg it for the SDP for TDM draft.
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE=CITE><span class=448232421-02042002><font face="Arial"><font color="#0000FF"><font size=-1>I'm
confused, are you talking about section 5.6.3.2 of&nbsp;<span 
class=109342521-02042002>RFC
3108?</span></span><span class=448232421-02042002><span class=109342521-02042002>I
know there was discussion about snagging this but that is for ATM</span></span><span class=448232421-02042002><span class=109342521-02042002>right
now.</span></span><span class=448232421-02042002><span 
class=109342521-02042002></span></span><span class=448232421-02042002><span 
class=109342521-02042002></span></span><span class=448232421-02042002><span 
class=109342521-02042002>Carl</font></font></font></span></span><span class=448232421-02042002><span class=109342521-02042002></span><span 
class=109342521-02042002></span></span>
<blockquote>
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<A HREF="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</A>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
3:58 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>
Doesn't the following cover this already?
<p>5.6.3.2 The 'silenceSupp' attribute
<p>&nbsp;&nbsp; When present, the 'silenceSupp' attribute is used to indicate
the use
<br>&nbsp;&nbsp; or non-use of silence suppression.&nbsp; The format of
the 'silenceSupp'
<br>&nbsp;&nbsp; media attribute line is as follows:
<p>&nbsp;&nbsp; a=silenceSupp: &lt;silenceSuppEnable> &lt;silenceTimer>
&lt;suppPref> &lt;sidUse>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;fxnslevel>
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE="CITE"><span class=967084920-02042002><font face="Arial"><font color="#0000FF"><font size=-1>All
good questions another I would add is:</span><span class=967084920-02042002></font></font></font>If
we use SDP for TDM going forward&nbsp;</span><span 
    class=967084920-02042002>how
is silence suppression implemented?</span><span 
    class=967084920-02042002></span><span class=967084920-02042002>
<br>Carl&nbsp;</span>
<blockquote>
<div class=OutlookMessageHeader dir=ltr><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
3:41 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>

<p><br>I thought the reason that we decided to have SDP TDM is to get away
from TDM package
<br>to be more inline w/how we specify RTP termination characteristics.
<br>Also to reuse the good stuffs from RTP/ATM SDP.
<p>I guess we can start by asking the questions
<p>1) Can we live w/o the TDM package?
<br>2) Can we just use SDP for TDM going forward?
<br>3) For backward compatibility, just leave TDM package as is and don't
extend it anymore.
<p>For the TDM package, echo control is understood but the Gain control
is not quite right.
<br>I have discussed the Gain control before and gotten nowhere.
<p>Gain control is also defined in the SDP for ATM which seems more correct.
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE="CITE"><span class=491101120-02042002><font size=-1><font face="Arial"><font color="#0000FF">Chuong,</span><span 
        class=491101120-02042002></span><span class=491101120-02042002>There
was several ideas bouncing around but I don't believe</span><span 
        class=491101120-02042002>there
was any closure.&nbsp; There is a hole for G711 since we can't use&nbsp;</span><span 
        class=491101120-02042002>annexa
or annexb.</span><span 
        class=491101120-02042002>Lifting the support
in </font></font><font face="Times New Roman"><font color="#000000">RFC
3108, section 5.6.3.2 and putting it into</span><span class=491101120-02042002></font></font>the
TDM Circuit Package would give us a lot of flexibility.</span><span 
        class=491101120-02042002></span><span class=491101120-02042002><font face="Arial"><font color="#0000FF">Here
are the ideas I know of:</span><span 
        class=491101120-02042002>1)</font></font></font></span><span 
        class=491101120-02042002>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Another option
is to extend the TDM Circuit Package (which has been</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>previously discussed
on the list). The TDM Cicruit Package</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>currently has
Gain and Echo Control as its properties. So, it's logical</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>(IMO) for Silence
Suppression to be part of the package as</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>well. In fact,
it looks like an oversight that it was missed off in the</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>first place.</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Regards,</font></font></font>
<p><font face="Arial"><font color="#0000FF"><font size=-1>Wayne<span 
        class=491101120-02042002>
Cutler</font></font></font></span>
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>2)</font></font></font></span>
<br><span 
        class=491101120-02042002>
<p><font size=-1>Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.&nbsp; E.g.:</font>
<p><font size=-1>Media={Stream=1{ Local {</font>
<br><font size=-1>v=0</font>
<br><font size=-1>c=IN IP4 $</font>
<br><font size=-1>m=audio $ RTP/AVP 0 13</font>
<br><font size=-1>}}}</font>
<p><span class=491101120-02042002><font size=-1>David Barr</font></span>
<p><span class=491101120-02042002><font size=-1>3)</font></span>
<p><span class=491101120-02042002></span><span 
        class=491101120-02042002><font size=-1>I'm
starting to think that the answer may be to use the a=silenceSupp</font>
<br><font size=-1>attribute defined in RFC 3108, section 5.6.3.2.</font>
<p><span class=491101120-02042002><font size=-1>Tom Taylor</font></span>
<br>&nbsp;
<br>&nbsp;
<p><span class=491101120-02042002><font face="Arial"><font color="#0000FF"><font size=-1>Carl</font></font></font></span>
<br></span></span></span>
<blockquote>
<div class=OutlookMessageHeader dir=ltr><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
2:59 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>Cc:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>

<p><br>So what was that discussion about adding silence suppression to
TDM package?
<p>Do we use SDP TDM or TDM package or both?
<br>Or even worse combination of both within 1 command w/some parameters
defined by TDM package and
<br>some parameters defined by SDP TDM.
<br>&nbsp;
<br>&nbsp;
<p>Tom-PT Taylor wrote:
<blockquote TYPE="CITE">As I noted earlier, you do need to specify the
properties in the NAS case.
<br>The SDP TDM draft has certainly had time to ripen, and I will reissue
it and
<br>the NAS packages within the next week.
<p>-----Original Message-----
<br>From: Chuong N. Nguyen [<a href="mailto:Chuong.Nguyen@alcatel.com">mailto:Chuong.Nguyen@alcatel.com</a>]
<br>Sent: Tuesday, April 02, 2002 2:48 PM
<br>To: megaco@ietf.org
<br>Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
<br>&nbsp;
<p>I don't know about the sendrecv issue here.
<br>I don't know what you mean by SDP parameters are of no significance
in case
<br>of phy. term.
<br>Tom wrote the SDP TDM draft which I wonder what is the status of this
draft.
<p>But I can't remember now whether it was intended to be used in local
or
<br>localControl Descriptor.
<br>&nbsp;
<p>Madhu Babu Brahmanapally wrote:
<br>HI Rajesh/All,
<br>Not all parameters might be useful for the MG/MGC in case of physical
<br>terminations. The SDP parameters are of no significance in case of
physical
<br>terminations (in normal scenario). Hence the mode was set to "sendrecv"
<br>without specifying the local/remote descriptor information.
<br>Regards
<br>Madhubabu
<br>-----Original Message-----
<br>From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]On
Behalf Of
<br>Rajesh N
<br>Sent: Tuesday, April 02, 2002 11:32 AM
<br>To: megaco@ietf.org
<br>Subject: [Megaco] Local/Remote descriptors and Permanent terminations
<br>Hi,
<br>Sometime back there was a thread regarding usage of SendRecv mode for
an
<br>ephemeral termination, when Remote Descriptor values are yet to be
defined.
<br>And one of the choices for the MG in such a situation is to reply back
with
<br>error 411, "missing remote or local descriptor".
<br>I would like to know, what is the significance of this problem w.r.to
<br>permanent terminations. The example call flow in the draft shows a
Modify
<br>request for a permanent termination, from MGC to MG1, in which mode
is set
<br>as SendRecv and&nbsp; the Local descriptor values alone are being provided.
<br>Are local and remote descriptors relevant for physical terminations?
If
<br>yes, where should I get the values from?
<br>Thanks
<br>Regards,
<br>Rajesh N
<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>[This E-mail was scanned for viruses and is clean.]
<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; Alcatel USA, Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Internet: Chuong.Nguyen@usa.alcatel.com
<br>&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; **** The opinions expressed are not those of Alcatel USA, Inc
****
<br>&nbsp;</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;</blockquote>
</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;</blockquote>
</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;</blockquote>
</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>

--------------649848D302D678D5E3BF55E7--


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



From megaco-admin@ietf.org  Tue Apr  2 17:15: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 RAA05595
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:15: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 QAA16065;
	Tue, 2 Apr 2002 16:50: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 QAA16034
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:50:40 -0500 (EST)
Received: from gateus.nmss.com (gateus.nmss.com [208.236.204.65])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA04957
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:50:34 -0500 (EST)
From: David_Franklin@nmss.com
Received: from NAMASMTP01 by gateus.nmss.com
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 2 Apr 2002 16:46:42 UT
To: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF18ED72BF.AC7C9902-ON85256B8F.0076C6B9@nmss.com>
Date: Tue, 2 Apr 2002 16:51:52 -0500
X-MIMETrack: Serialize by Router on NAMASMTP01/Natural MicroSystems/US(Release 5.0.9a |January
 7, 2002) at 04/02/2002 04:50:47 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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

Hi folks,

Would anyone be able to tell me what is the current status regarding the
packages defined in Q.1950 Annex A ? I seem to recall that Annexes A.8
through A.10 are to be removed from the published version of Q.1950 and
will instead reference something that is being produced by the IETF.

Many thanks,
Dave

David Franklin
Principal Software Engineer
NMS Communications
david_franklin@nmss.com
tel. +1.508.271.1038




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


From megaco-admin@ietf.org  Tue Apr  2 17:24: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 RAA05855
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:24: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 RAA17384;
	Tue, 2 Apr 2002 17:06: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 RAA17277
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 17:06:02 -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 RAA05350
	for <megaco@ietf.org>; Tue, 2 Apr 2002 17:05:58 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0NMQ>; Tue, 2 Apr 2002 17:05:30 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C48@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        Carl Rutter
	 <crutter@telica.com>,
        "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>
Cc: megaco@ietf.org, Peter Barany <pbarany@nortelnetworks.com>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 17:05:28 -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

OK,
m=audio $ RTP/AVP 0 13 
To enable G711 Silent Suppresion.
I think this works, and we can use this for now
however 

a=silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse>
                   <fxnslevel>

I think is clearer and cleaner and
would allow greater flexibility in the future.

My two Cents,
Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Tuesday, April 02, 2002 4:25 PM
To: 'Carl Rutter'; 'Chuong N. Nguyen'
Cc: megaco@ietf.org; Peter Barany
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations



I've had a message pointing out the existence of
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711
would indicate the use of silence suppression implicitly.  That covers RTP
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.
Do we need anything for TDM?

-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Tuesday, April 02, 2002 3:19 PM
To: 'Chuong N. Nguyen'
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


Chuong,
 
There was several ideas bouncing around but I don't believe
there was any closure.  There is a hole for G711 since we can't use 
annexa or annexb.
Lifting the support in RFC 3108, section 5.6.3.2 and putting it into
the TDM Circuit Package would give us a lot of flexibility.
 
Here are the ideas I know of:
1)
Another option is to extend the TDM Circuit Package (which has been
previously discussed on the list). The TDM Cicruit Package
currently has Gain and Echo Control as its properties. So, it's logical
(IMO) for Silence Suppression to be part of the package as
well. In fact, it looks like an oversight that it was missed off in the
first place.
Regards,
Wayne Cutler
2)
Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.  E.g.: 
Media={Stream=1{ Local { 
v=0 
c=IN IP4 $ 
m=audio $ RTP/AVP 0 13 
}}}
David Barr 
3)
I'm starting to think that the answer may be to use the a=silenceSupp 
attribute defined in RFC 3108, section 5.6.3.2. 
Tom Taylor
 
Carl
-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 2:59 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
So what was that discussion about adding silence suppression to TDM package?

Do we use SDP TDM or TDM package or both? 
Or even worse combination of both within 1 command w/some parameters defined
by TDM package and 
some parameters defined by SDP TDM. 
  
  
Tom-PT Taylor wrote: 
As I noted earlier, you do need to specify the properties in the NAS case. 
The SDP TDM draft has certainly had time to ripen, and I will reissue it and

the NAS packages within the next week. 
-----Original Message----- 
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com] 
Sent: Tuesday, April 02, 2002 2:48 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations 
  
I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case 
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.

But I can't remember now whether it was intended to be used in local or 
localControl Descriptor. 
  
Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco 
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
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 **** 
 
-- 
  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 Apr  2 17: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 RAA05866
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:24:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA18156
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 17:24: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 RAA17384;
	Tue, 2 Apr 2002 17:06: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 RAA17277
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 17:06:02 -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 RAA05350
	for <megaco@ietf.org>; Tue, 2 Apr 2002 17:05:58 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0NMQ>; Tue, 2 Apr 2002 17:05:30 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C48@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        Carl Rutter
	 <crutter@telica.com>,
        "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>
Cc: megaco@ietf.org, Peter Barany <pbarany@nortelnetworks.com>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 17:05:28 -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

OK,
m=audio $ RTP/AVP 0 13 
To enable G711 Silent Suppresion.
I think this works, and we can use this for now
however 

a=silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse>
                   <fxnslevel>

I think is clearer and cleaner and
would allow greater flexibility in the future.

My two Cents,
Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Tuesday, April 02, 2002 4:25 PM
To: 'Carl Rutter'; 'Chuong N. Nguyen'
Cc: megaco@ietf.org; Peter Barany
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations



I've had a message pointing out the existence of
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711
would indicate the use of silence suppression implicitly.  That covers RTP
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.
Do we need anything for TDM?

-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Tuesday, April 02, 2002 3:19 PM
To: 'Chuong N. Nguyen'
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


Chuong,
 
There was several ideas bouncing around but I don't believe
there was any closure.  There is a hole for G711 since we can't use 
annexa or annexb.
Lifting the support in RFC 3108, section 5.6.3.2 and putting it into
the TDM Circuit Package would give us a lot of flexibility.
 
Here are the ideas I know of:
1)
Another option is to extend the TDM Circuit Package (which has been
previously discussed on the list). The TDM Cicruit Package
currently has Gain and Echo Control as its properties. So, it's logical
(IMO) for Silence Suppression to be part of the package as
well. In fact, it looks like an oversight that it was missed off in the
first place.
Regards,
Wayne Cutler
2)
Another possibility is to use payload 13 as defined in
draft-ietf-avt-rtp-cn-05.  E.g.: 
Media={Stream=1{ Local { 
v=0 
c=IN IP4 $ 
m=audio $ RTP/AVP 0 13 
}}}
David Barr 
3)
I'm starting to think that the answer may be to use the a=silenceSupp 
attribute defined in RFC 3108, section 5.6.3.2. 
Tom Taylor
 
Carl
-----Original Message-----
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com]
Sent: Tuesday, April 02, 2002 2:59 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
So what was that discussion about adding silence suppression to TDM package?

Do we use SDP TDM or TDM package or both? 
Or even worse combination of both within 1 command w/some parameters defined
by TDM package and 
some parameters defined by SDP TDM. 
  
  
Tom-PT Taylor wrote: 
As I noted earlier, you do need to specify the properties in the NAS case. 
The SDP TDM draft has certainly had time to ripen, and I will reissue it and

the NAS packages within the next week. 
-----Original Message----- 
From: Chuong N. Nguyen [mailto:Chuong.Nguyen@alcatel.com] 
Sent: Tuesday, April 02, 2002 2:48 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations 
  
I don't know about the sendrecv issue here. 
I don't know what you mean by SDP parameters are of no significance in case 
of phy. term. 
Tom wrote the SDP TDM draft which I wonder what is the status of this draft.

But I can't remember now whether it was intended to be used in local or 
localControl Descriptor. 
  
Madhu Babu Brahmanapally wrote: 
HI Rajesh/All, 
Not all parameters might be useful for the MG/MGC in case of physical 
terminations. The SDP parameters are of no significance in case of physical 
terminations (in normal scenario). Hence the mode was set to "sendrecv" 
without specifying the local/remote descriptor information. 
Regards 
Madhubabu 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of 
Rajesh N 
Sent: Tuesday, April 02, 2002 11:32 AM 
To: megaco@ietf.org 
Subject: [Megaco] Local/Remote descriptors and Permanent terminations 
Hi, 
Sometime back there was a thread regarding usage of SendRecv mode for an 
ephemeral termination, when Remote Descriptor values are yet to be defined. 
And one of the choices for the MG in such a situation is to reply back with 
error 411, "missing remote or local descriptor". 
I would like to know, what is the significance of this problem w.r.to 
permanent terminations. The example call flow in the draft shows a Modify 
request for a permanent termination, from MGC to MG1, in which mode is set 
as SendRecv and  the Local descriptor values alone are being provided. 
Are local and remote descriptors relevant for physical terminations? If 
yes, where should I get the values from? 
Thanks 
Regards, 
Rajesh N 
_______________________________________________ 
Megaco mailing list 
Megaco@ietf.org 
https://www1.ietf.org/mailman/listinfo/megaco 
--- 
[This E-mail was scanned for viruses and is clean.] 
_______________________________________________ 
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 **** 
 
-- 
  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 Apr  2 17:24: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 RAA05884
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:24: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 QAA16311;
	Tue, 2 Apr 2002 16:59: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 QAA16269
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:59:47 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05184
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:59: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 g32LxDA11575
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:59:14 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0RC6>; Tue, 2 Apr 2002 16:59:15 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A23B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'David_Franklin@nmss.com'" <David_Franklin@nmss.com>, megaco@ietf.org
Subject: RE: [Megaco] (no subject)
Date: Tue, 2 Apr 2002 16:59: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 whole thing has ended up in a ball of confusion.  When
draft-boyle-megaco-tonepkgs-xx.txt was first passed to the IESG it contained
these packages.  However, I may have misunderstood SG 11's intentions if
they really do mean to remove the packages from Q.1950.  The IESG did not
care for the overlap between Q.1950 and the draft and I was unable to defend
it.  As a result, succeeding versions of the draft have only the additional
packages defined by Kevin Boyle et al.

-----Original Message-----
From: David_Franklin@nmss.com [mailto:David_Franklin@nmss.com]
Sent: Tuesday, April 02, 2002 4:52 PM
To: megaco@ietf.org
Subject: [Megaco] (no subject)


Hi folks,

Would anyone be able to tell me what is the current status regarding the
packages defined in Q.1950 Annex A ? I seem to recall that Annexes A.8
through A.10 are to be removed from the published version of Q.1950 and
will instead reference something that is being produced by the IETF.

Many thanks,
Dave

David Franklin
Principal Software Engineer
NMS Communications
david_franklin@nmss.com
tel. +1.508.271.1038




_______________________________________________
Megaco mailing list
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 Apr  2 17:24: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 RAA05904
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:24:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA18170
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 17:24: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 QAA16311;
	Tue, 2 Apr 2002 16:59: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 QAA16269
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:59:47 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05184
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:59: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 g32LxDA11575
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:59:14 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0RC6>; Tue, 2 Apr 2002 16:59:15 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A23B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'David_Franklin@nmss.com'" <David_Franklin@nmss.com>, megaco@ietf.org
Subject: RE: [Megaco] (no subject)
Date: Tue, 2 Apr 2002 16:59: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 whole thing has ended up in a ball of confusion.  When
draft-boyle-megaco-tonepkgs-xx.txt was first passed to the IESG it contained
these packages.  However, I may have misunderstood SG 11's intentions if
they really do mean to remove the packages from Q.1950.  The IESG did not
care for the overlap between Q.1950 and the draft and I was unable to defend
it.  As a result, succeeding versions of the draft have only the additional
packages defined by Kevin Boyle et al.

-----Original Message-----
From: David_Franklin@nmss.com [mailto:David_Franklin@nmss.com]
Sent: Tuesday, April 02, 2002 4:52 PM
To: megaco@ietf.org
Subject: [Megaco] (no subject)


Hi folks,

Would anyone be able to tell me what is the current status regarding the
packages defined in Q.1950 Annex A ? I seem to recall that Annexes A.8
through A.10 are to be removed from the published version of Q.1950 and
will instead reference something that is being produced by the IETF.

Many thanks,
Dave

David Franklin
Principal Software Engineer
NMS Communications
david_franklin@nmss.com
tel. +1.508.271.1038




_______________________________________________
Megaco mailing list
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 Apr  2 18: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 RAA05606
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:15:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA17733
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 17:15: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 QAA16065;
	Tue, 2 Apr 2002 16:50: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 QAA16034
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 16:50:40 -0500 (EST)
Received: from gateus.nmss.com (gateus.nmss.com [208.236.204.65])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA04957
	for <megaco@ietf.org>; Tue, 2 Apr 2002 16:50:34 -0500 (EST)
From: David_Franklin@nmss.com
Received: from NAMASMTP01 by gateus.nmss.com
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 2 Apr 2002 16:46:42 UT
To: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF18ED72BF.AC7C9902-ON85256B8F.0076C6B9@nmss.com>
Date: Tue, 2 Apr 2002 16:51:52 -0500
X-MIMETrack: Serialize by Router on NAMASMTP01/Natural MicroSystems/US(Release 5.0.9a |January
 7, 2002) at 04/02/2002 04:50:47 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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

Hi folks,

Would anyone be able to tell me what is the current status regarding the
packages defined in Q.1950 Annex A ? I seem to recall that Annexes A.8
through A.10 are to be removed from the published version of Q.1950 and
will instead reference something that is being produced by the IETF.

Many thanks,
Dave

David Franklin
Principal Software Engineer
NMS Communications
david_franklin@nmss.com
tel. +1.508.271.1038




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



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


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

Tom-PT Taylor wrote:

> I've had a message pointing out the existence of
> draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711
> would indicate the use of silence suppression implicitly.  That covers RTP
> transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.
> Do we need anything for TDM?
>

What if someone wanted to make a TDM-TDM, hairpin call?
Would silenceSupp be used for such a call?
If yes, then what?



--
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Tom-PT Taylor wrote:
<blockquote TYPE=CITE>I've had a message pointing out the existence of
<br>draft-ietf-avt-rtp-cn-05.txt.&nbsp; Specifying this payload type as
well as G.711
<br>would indicate the use of silence suppression implicitly.&nbsp; That
covers RTP
<br>transport.&nbsp; For ATM we have the a=silenceSupp attribute defined
in RFC 3108.
<br>Do we need anything for TDM?
<br>&nbsp;</blockquote>

<p><br>What if someone wanted to make a TDM-TDM, hairpin call?
<br>Would silenceSupp be used for such a call?
<br>If yes, then what?
<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>

--------------5968615F4FC9ABE4064587AD--


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


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


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

Tom-PT Taylor wrote:

> I've had a message pointing out the existence of
> draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711
> would indicate the use of silence suppression implicitly.  That covers RTP
> transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.
> Do we need anything for TDM?
>

What if someone wanted to make a TDM-TDM, hairpin call?
Would silenceSupp be used for such a call?
If yes, then what?



--
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Tom-PT Taylor wrote:
<blockquote TYPE=CITE>I've had a message pointing out the existence of
<br>draft-ietf-avt-rtp-cn-05.txt.&nbsp; Specifying this payload type as
well as G.711
<br>would indicate the use of silence suppression implicitly.&nbsp; That
covers RTP
<br>transport.&nbsp; For ATM we have the a=silenceSupp attribute defined
in RFC 3108.
<br>Do we need anything for TDM?
<br>&nbsp;</blockquote>

<p><br>What if someone wanted to make a TDM-TDM, hairpin call?
<br>Would silenceSupp be used for such a call?
<br>If yes, then what?
<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>

--------------5968615F4FC9ABE4064587AD--


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



From megaco-admin@ietf.org  Tue Apr  2 20: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 UAA10731
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 20: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 TAA29960;
	Tue, 2 Apr 2002 19:54: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 TAA29930
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 19:54:32 -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 TAA10107
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:54:31 -0500 (EST)
Received: from CRHOMEPC ([10.0.104.27]) by wench.telica.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GQDA0N74; Tue, 2 Apr 2002 19:54:02 -0500
From: "Carl Rutter" <crutter@telica.com>
To: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 19:51:08 -0500
Message-ID: <001901c1daa9$a4aeeca0$0300a8c0@telica.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001A_01C1DA7F.BBD8E4A0"
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
In-Reply-To: <3CAA49A5.ABEBF2C1@alcatel.com>
Sender: megaco-admin@ietf.org
Errors-To: 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_001A_01C1DA7F.BBD8E4A0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

I can't think of an application where you'd want to do that.
Silence suppression really wouldn't make sense for a TDM-TDM
which is hairpined at the CO.  The DS0 is dedicated.
The advantage of Silent suppression it to limit the RTP traffic on the
IP side, which you wouldn't have in that case.

Maybe if you wanted to inject Comfort Noise instead of background
noice in the TDM-TDM call??

Carl
  -----Original Message-----
  From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
  Sent: Tuesday, April 02, 2002 7:16 PM
  To: megaco@ietf.org
  Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  Tom-PT Taylor wrote:
    I've had a message pointing out the existence of
    draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as
G.711
    would indicate the use of silence suppression implicitly.  That covers
RTP
    transport.  For ATM we have the a=silenceSupp attribute defined in RFC
3108.
    Do we need anything for TDM?


  What if someone wanted to make a TDM-TDM, hairpin call?
  Would silenceSupp be used for such a call?
  If yes, then what?



--
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****


------=_NextPart_000_001A_01C1DA7F.BBD8E4A0
Content-Type: text/html;
	charset="Windows-1252"
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=3Dus-ascii">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
can't think of an application where you'd want to do that. =
</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Silence suppression really wouldn't make sense for a=20
TDM-TDM</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>which=20
is hairpined at the CO.&nbsp; </FONT></SPAN><SPAN =
class=3D204534100-03042002><FONT=20
face=3DArial color=3D#0000ff size=3D2>The DS0 is dedicated.&nbsp; =
</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>The=20
advantage of Silent suppression&nbsp;</FONT></SPAN><SPAN=20
class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>it to limit the=20
RTP traffic on the </FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>IP=20
side, which you wouldn't have in that case.</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>Maybe=20
if you wanted to inject Comfort Noise instead of =
background</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>noice=20
in the TDM-TDM call??</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Carl</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
megaco-admin@ietf.org=20
  [mailto:megaco-admin@ietf.org]<B>On Behalf Of </B>Chuong N.=20
  Nguyen<BR><B>Sent:</B> Tuesday, April 02, 2002 7:16 PM<BR><B>To:</B>=20
  megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] Local/Remote =
descriptors and=20
  Permanent terminations<BR><BR></FONT></DIV>Tom-PT Taylor wrote:=20
  <BLOCKQUOTE TYPE=3D"CITE">I've had a message pointing out the =
existence of=20
    <BR>draft-ietf-avt-rtp-cn-05.txt.&nbsp; Specifying this payload type =
as well=20
    as G.711 <BR>would indicate the use of silence suppression =
implicitly.&nbsp;=20
    That covers RTP <BR>transport.&nbsp; For ATM we have the =
a=3DsilenceSupp=20
    attribute defined in RFC 3108. <BR>Do we need anything for TDM?=20
  <BR>&nbsp;</BLOCKQUOTE>
  <P><BR>What if someone wanted to make a TDM-TDM, hairpin call? =
<BR>Would=20
  silenceSupp be used for such a call? <BR>If yes, then what? <BR>&nbsp; =

  <BR>&nbsp; <PRE>--&nbsp;
&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; 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_000_001A_01C1DA7F.BBD8E4A0--


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


From daemon@ns.ietf.org  Tue Apr  2 20:20: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 UAA10741
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 20:20:22 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA01633
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 20: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 TAA29960;
	Tue, 2 Apr 2002 19:54: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 TAA29930
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 19:54:32 -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 TAA10107
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:54:31 -0500 (EST)
Received: from CRHOMEPC ([10.0.104.27]) by wench.telica.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GQDA0N74; Tue, 2 Apr 2002 19:54:02 -0500
From: "Carl Rutter" <crutter@telica.com>
To: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 19:51:08 -0500
Message-ID: <001901c1daa9$a4aeeca0$0300a8c0@telica.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001A_01C1DA7F.BBD8E4A0"
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
In-Reply-To: <3CAA49A5.ABEBF2C1@alcatel.com>
Sender: megaco-admin@ietf.org
Errors-To: 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_001A_01C1DA7F.BBD8E4A0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

I can't think of an application where you'd want to do that.
Silence suppression really wouldn't make sense for a TDM-TDM
which is hairpined at the CO.  The DS0 is dedicated.
The advantage of Silent suppression it to limit the RTP traffic on the
IP side, which you wouldn't have in that case.

Maybe if you wanted to inject Comfort Noise instead of background
noice in the TDM-TDM call??

Carl
  -----Original Message-----
  From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
  Sent: Tuesday, April 02, 2002 7:16 PM
  To: megaco@ietf.org
  Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  Tom-PT Taylor wrote:
    I've had a message pointing out the existence of
    draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as
G.711
    would indicate the use of silence suppression implicitly.  That covers
RTP
    transport.  For ATM we have the a=silenceSupp attribute defined in RFC
3108.
    Do we need anything for TDM?


  What if someone wanted to make a TDM-TDM, hairpin call?
  Would silenceSupp be used for such a call?
  If yes, then what?



--
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****


------=_NextPart_000_001A_01C1DA7F.BBD8E4A0
Content-Type: text/html;
	charset="Windows-1252"
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=3Dus-ascii">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
can't think of an application where you'd want to do that. =
</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Silence suppression really wouldn't make sense for a=20
TDM-TDM</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>which=20
is hairpined at the CO.&nbsp; </FONT></SPAN><SPAN =
class=3D204534100-03042002><FONT=20
face=3DArial color=3D#0000ff size=3D2>The DS0 is dedicated.&nbsp; =
</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>The=20
advantage of Silent suppression&nbsp;</FONT></SPAN><SPAN=20
class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>it to limit the=20
RTP traffic on the </FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>IP=20
side, which you wouldn't have in that case.</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>Maybe=20
if you wanted to inject Comfort Noise instead of =
background</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>noice=20
in the TDM-TDM call??</FONT></SPAN></DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D204534100-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Carl</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
megaco-admin@ietf.org=20
  [mailto:megaco-admin@ietf.org]<B>On Behalf Of </B>Chuong N.=20
  Nguyen<BR><B>Sent:</B> Tuesday, April 02, 2002 7:16 PM<BR><B>To:</B>=20
  megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] Local/Remote =
descriptors and=20
  Permanent terminations<BR><BR></FONT></DIV>Tom-PT Taylor wrote:=20
  <BLOCKQUOTE TYPE=3D"CITE">I've had a message pointing out the =
existence of=20
    <BR>draft-ietf-avt-rtp-cn-05.txt.&nbsp; Specifying this payload type =
as well=20
    as G.711 <BR>would indicate the use of silence suppression =
implicitly.&nbsp;=20
    That covers RTP <BR>transport.&nbsp; For ATM we have the =
a=3DsilenceSupp=20
    attribute defined in RFC 3108. <BR>Do we need anything for TDM?=20
  <BR>&nbsp;</BLOCKQUOTE>
  <P><BR>What if someone wanted to make a TDM-TDM, hairpin call? =
<BR>Would=20
  silenceSupp be used for such a call? <BR>If yes, then what? <BR>&nbsp; =

  <BR>&nbsp; <PRE>--&nbsp;
&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; 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_000_001A_01C1DA7F.BBD8E4A0--


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



From megaco-admin@ietf.org  Tue Apr  2 21: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 VAA11994
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 21:37: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 UAA02883;
	Tue, 2 Apr 2002 20:39: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 UAA02852
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 20:39:18 -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 UAA11100
	for <megaco@ietf.org>; Tue, 2 Apr 2002 20:39:16 -0500 (EST)
Received: from CRHOMEPC ([10.0.104.27]) by wench.telica.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GQDA0N04; Tue, 2 Apr 2002 20:38:48 -0500
From: "Carl Rutter" <crutter@telica.com>
To: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
Cc: <megaco@ietf.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 20:35:54 -0500
Message-ID: <000401c1daaf$e537b5d0$0300a8c0@telica.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01C1DA85.FC633470"
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
In-Reply-To: <3CAA553D.193B1C29@alcatel.com>
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1DA85.FC633470
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

You bring up a good point,
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more sense to
be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach for
SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
  -----Original Message-----
  From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
  Sent: Tuesday, April 02, 2002 8:05 PM
  Cc: megaco@ietf.org
  Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations



  That is what  I initially thought silence suppression was about.
  But then I was told differently.
  It could be applied to TDM.
  If not, then why are we discussing adding silence suppresion to the TDM
package?


  By the way,  I thought TDM-TDM calls are being made at the Gwy too.
  Aren't you guys doing that now?



  Carl Rutter wrote:

    I can't think of an application where you'd want to do that. Silence
suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at
the CO. The DS0 is dedicated. The advantage of Silent suppression it to
limit the RTP traffic on the IP side, which you wouldn't have in that
case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice
in the TDM-TDM call??Carl
      -----Original Message-----
      From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
      Sent: Tuesday, April 02, 2002 7:16 PM
      To: megaco@ietf.org
      Subject: Re: [Megaco] Local/Remote descriptors and Permanent
terminations
      Tom-PT Taylor wrote:
        I've had a message pointing out the existence of
        draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well
as G.711
        would indicate the use of silence suppression implicitly.  That
covers RTP
        transport.  For ATM we have the a=silenceSupp attribute defined in
RFC 3108.
        Do we need anything for TDM?

      What if someone wanted to make a TDM-TDM, hairpin call?
      Would silenceSupp be used for such a call?
      If yes, then what?



--
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****

--
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****


------=_NextPart_000_0005_01C1DA85.FC633470
Content-Type: text/html;
	charset="Windows-1252"
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=3Dus-ascii">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>You=20
bring up a good point, </FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Is/Should Silient Suppression be tied to the TDM package=20
or</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>SDP=20
TDM, if in fact its really more applicable to the Ephemral=20
side.</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>If no=20
can think of a good reason then your right it would make more sense to =
be in the=20
SDP.</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>For=20
now we could use 0 13 for G711 and long-term </FONT></SPAN><SPAN=20
class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>use the ATM=20
approach for SDP.</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>Trying=20
to drive towards closure as we have a need to implement=20
this.</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>Yea,=20
the hairpinning would be in the MG Switch.</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Comments?</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Carl</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
megaco-admin@ietf.org=20
  [mailto:megaco-admin@ietf.org]<B>On Behalf Of </B>Chuong N.=20
  Nguyen<BR><B>Sent:</B> Tuesday, April 02, 2002 8:05 PM<BR><B>Cc:</B>=20
  megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] Local/Remote =
descriptors and=20
  Permanent terminations<BR><BR></FONT></DIV>&nbsp; <BR>That is what =
&nbsp;I=20
  initially thought silence suppression was about. <BR>But then =
I&nbsp;was told=20
  differently. <BR>It could be applied to TDM.=20
  <P>If not, then why are we discussing adding silence suppresion to the =

  TDM&nbsp;package? <BR>&nbsp;=20
  <P>By the way,&nbsp; I&nbsp;thought TDM-TDM calls are being made at =
the Gwy=20
  too. <BR>Aren't you guys doing that now? <BR>&nbsp; <BR>&nbsp;=20
  <P>Carl Rutter wrote:=20
  <BLOCKQUOTE TYPE=3D"CITE"><SPAN class=3D204534100-03042002><FONT=20
    face=3DArial><FONT color=3D#0000ff><FONT size=3D-1>I can't think of =
an application=20
    where you'd want to do that.&nbsp;</SPAN><SPAN=20
    class=3D204534100-03042002>Silence suppression really wouldn't make =
sense for=20
    a TDM-TDM</SPAN><SPAN class=3D204534100-03042002>which is hairpined =
at the=20
    CO.&nbsp;</SPAN><SPAN class=3D204534100-03042002>The DS0 is=20
    dedicated.&nbsp;</SPAN><SPAN class=3D204534100-03042002>The =
advantage of=20
    Silent suppression&nbsp;</SPAN><SPAN class=3D204534100-03042002>it =
to limit=20
    the RTP traffic on the&nbsp;</SPAN><SPAN =
class=3D204534100-03042002>IP side,=20
    which you wouldn't have in that case.</SPAN><SPAN=20
    class=3D204534100-03042002></SPAN><SPAN =
class=3D204534100-03042002>Maybe if you=20
    wanted to inject Comfort Noise instead of background</SPAN><SPAN=20
    class=3D204534100-03042002>noice in the TDM-TDM call??</SPAN><SPAN=20
    class=3D204534100-03042002></SPAN><SPAN=20
    class=3D204534100-03042002>Carl</FONT></FONT></FONT></SPAN>=20
    <BLOCKQUOTE>
      <DIV class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma><FONT=20
      size=3D-1>-----Original Message-----</FONT></FONT> <BR><FONT=20
      face=3DTahoma><FONT size=3D-1><B>From:</B> megaco-admin@ietf.org =
[<A=20
      =
href=3D"mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]<B=
>On=20
      Behalf Of </B>Chuong N. Nguyen</FONT></FONT> <BR><FONT =
face=3DTahoma><FONT=20
      size=3D-1><B>Sent:</B> Tuesday, April 02, 2002 7:16 =
PM</FONT></FONT>=20
      <BR><FONT face=3DTahoma><FONT size=3D-1><B>To:</B>=20
      megaco@ietf.org</FONT></FONT> <BR><FONT face=3DTahoma><FONT=20
      size=3D-1><B>Subject:</B> Re: [Megaco] Local/Remote descriptors =
and=20
      Permanent terminations</FONT></FONT></DIV>Tom-PT Taylor wrote:=20
      <BLOCKQUOTE TYPE=3D"CITE">I've had a message pointing out the =
existence of=20
        <BR>draft-ietf-avt-rtp-cn-05.txt.&nbsp; Specifying this payload =
type as=20
        well as G.711 <BR>would indicate the use of silence suppression=20
        implicitly.&nbsp; That covers RTP <BR>transport.&nbsp; For ATM =
we have=20
        the a=3DsilenceSupp attribute defined in RFC 3108. <BR>Do we =
need anything=20
        for TDM?</BLOCKQUOTE>
      <P><BR>What if someone wanted to make a TDM-TDM, hairpin call? =
<BR>Would=20
      silenceSupp be used for such a call? <BR>If yes, then what? =
<BR>&nbsp;=20
      <BR>&nbsp; <PRE>--&nbsp;
&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; 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;</BLOCKQUOTE></BLOCKQUOTE><PRE>--&nbsp;
&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; 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_000_0005_01C1DA85.FC633470--


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


From megaco-admin@ietf.org  Tue Apr  2 21: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 VAA12056
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 21:37: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 UAA00948;
	Tue, 2 Apr 2002 20:05: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 UAA00920
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 20:05:56 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10338
	for <megaco@ietf.org>; Tue, 2 Apr 2002 20:05:55 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g3315QV12528
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:05:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g33151O07785
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:05:01 -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 g33151727528
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:05:01 -0600 (CST)
Message-ID: <3CAA553D.193B1C29@alcatel.com>
Date: Tue, 02 Apr 2002 19:05:01 -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
CC: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <001901c1daa9$a4aeeca0$0300a8c0@telica.com>
Content-Type: multipart/alternative;
 boundary="------------D6A0A43CD85EF028A0C445B1"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


That is what  I initially thought silence suppression was about.
But then I was told differently.
It could be applied to TDM.

If not, then why are we discussing adding silence suppresion to the
TDM package?


By the way,  I thought TDM-TDM calls are being made at the Gwy too.
Aren't you guys doing that now?



Carl Rutter wrote:

> I can't think of an application where you'd want to do that. Silence
> suppression really wouldn't make sense for a TDM-TDMwhich is hairpined
> at the CO. The DS0 is dedicated. The advantage of Silent
> suppression it to limit the RTP traffic on the IP side, which you
> wouldn't have in that case.Maybe if you wanted to inject Comfort Noise
> instead of backgroundnoice in the TDM-TDM call??Carl
>
>      -----Original Message-----
>      From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On
>      Behalf Of Chuong N. Nguyen
>      Sent: Tuesday, April 02, 2002 7:16 PM
>      To: megaco@ietf.org
>      Subject: Re: [Megaco] Local/Remote descriptors and Permanent
>      terminations
>      Tom-PT Taylor wrote:
>
>     > I've had a message pointing out the existence of
>     > draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload
>     > type as well as G.711
>     > would indicate the use of silence suppression implicitly.
>     > That covers RTP
>     > transport.  For ATM we have the a=silenceSupp attribute
>     > defined in RFC 3108.
>     > Do we need anything for TDM?
>
>
>      What if someone wanted to make a TDM-TDM, hairpin call?
>      Would silenceSupp be used for such a call?
>      If yes, then what?
>
>
>
>      --
>        Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
>        1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
>        **** The opinions expressed are not those of Alcatel USA, Inc ****
>
>
>
--
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>That is what &nbsp;I initially thought silence suppression was about.
<br>But then I&nbsp;was told differently.
<br>It could be applied to TDM.
<p>If not, then why are we discussing adding silence suppresion to the
TDM&nbsp;package?
<br>&nbsp;
<p>By the way,&nbsp; I&nbsp;thought TDM-TDM calls are being made at the
Gwy too.
<br>Aren't you guys doing that now?
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE=CITE><span class=204534100-03042002><font face="Arial"><font color="#0000FF"><font size=-1>I
can't think of an application where you'd want to do that.&nbsp;</span><span class=204534100-03042002>Silence
suppression really wouldn't make sense for a TDM-TDM</span><span class=204534100-03042002>which
is hairpined at the CO.&nbsp;</span><span class=204534100-03042002>The
DS0 is dedicated.&nbsp;</span><span class=204534100-03042002>The advantage
of Silent suppression&nbsp;</span><span 
class=204534100-03042002>it to
limit the RTP traffic on the&nbsp;</span><span class=204534100-03042002>IP
side, which you wouldn't have in that case.</span><span class=204534100-03042002></span><span class=204534100-03042002>Maybe
if you wanted to inject Comfort Noise instead of background</span><span class=204534100-03042002>noice
in the TDM-TDM call??</span><span class=204534100-03042002></span><span class=204534100-03042002>Carl</font></font></font></span>
<blockquote>
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> megaco-admin@ietf.org
[<A HREF="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]<b>On Behalf Of </b>Chuong N. Nguyen</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
7:16 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>
Tom-PT Taylor wrote:
<blockquote TYPE="CITE">I've had a message pointing out the existence of
<br>draft-ietf-avt-rtp-cn-05.txt.&nbsp; Specifying this payload type as
well as G.711
<br>would indicate the use of silence suppression implicitly.&nbsp; That
covers RTP
<br>transport.&nbsp; For ATM we have the a=silenceSupp attribute defined
in RFC 3108.
<br>Do we need anything for TDM?</blockquote>

<p><br>What if someone wanted to make a TDM-TDM, hairpin call?
<br>Would silenceSupp be used for such a call?
<br>If yes, then what?
<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;</blockquote>
</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>

--------------D6A0A43CD85EF028A0C445B1--


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


From daemon@ns.ietf.org  Tue Apr  2 21:37: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 VAA12080
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 21:37:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA05609
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 21:37: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 UAA00948;
	Tue, 2 Apr 2002 20:05: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 UAA00920
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 20:05:56 -0500 (EST)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10338
	for <megaco@ietf.org>; Tue, 2 Apr 2002 20:05:55 -0500 (EST)
Received: from ssd.usa.alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id g3315QV12528
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:05:26 -0600 (CST)
Received: from sun3144.ssd.usa.alcatel.com (sun3144.ssd.usa.alcatel.com [143.209.151.53])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g33151O07785
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:05:01 -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 g33151727528
	for <megaco@ietf.org>; Tue, 2 Apr 2002 19:05:01 -0600 (CST)
Message-ID: <3CAA553D.193B1C29@alcatel.com>
Date: Tue, 02 Apr 2002 19:05:01 -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
CC: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <001901c1daa9$a4aeeca0$0300a8c0@telica.com>
Content-Type: multipart/alternative;
 boundary="------------D6A0A43CD85EF028A0C445B1"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


That is what  I initially thought silence suppression was about.
But then I was told differently.
It could be applied to TDM.

If not, then why are we discussing adding silence suppresion to the
TDM package?


By the way,  I thought TDM-TDM calls are being made at the Gwy too.
Aren't you guys doing that now?



Carl Rutter wrote:

> I can't think of an application where you'd want to do that. Silence
> suppression really wouldn't make sense for a TDM-TDMwhich is hairpined
> at the CO. The DS0 is dedicated. The advantage of Silent
> suppression it to limit the RTP traffic on the IP side, which you
> wouldn't have in that case.Maybe if you wanted to inject Comfort Noise
> instead of backgroundnoice in the TDM-TDM call??Carl
>
>      -----Original Message-----
>      From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On
>      Behalf Of Chuong N. Nguyen
>      Sent: Tuesday, April 02, 2002 7:16 PM
>      To: megaco@ietf.org
>      Subject: Re: [Megaco] Local/Remote descriptors and Permanent
>      terminations
>      Tom-PT Taylor wrote:
>
>     > I've had a message pointing out the existence of
>     > draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload
>     > type as well as G.711
>     > would indicate the use of silence suppression implicitly.
>     > That covers RTP
>     > transport.  For ATM we have the a=silenceSupp attribute
>     > defined in RFC 3108.
>     > Do we need anything for TDM?
>
>
>      What if someone wanted to make a TDM-TDM, hairpin call?
>      Would silenceSupp be used for such a call?
>      If yes, then what?
>
>
>
>      --
>        Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
>        1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
>        **** The opinions expressed are not those of Alcatel USA, Inc ****
>
>
>
--
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>That is what &nbsp;I initially thought silence suppression was about.
<br>But then I&nbsp;was told differently.
<br>It could be applied to TDM.
<p>If not, then why are we discussing adding silence suppresion to the
TDM&nbsp;package?
<br>&nbsp;
<p>By the way,&nbsp; I&nbsp;thought TDM-TDM calls are being made at the
Gwy too.
<br>Aren't you guys doing that now?
<br>&nbsp;
<br>&nbsp;
<p>Carl Rutter wrote:
<blockquote TYPE=CITE><span class=204534100-03042002><font face="Arial"><font color="#0000FF"><font size=-1>I
can't think of an application where you'd want to do that.&nbsp;</span><span class=204534100-03042002>Silence
suppression really wouldn't make sense for a TDM-TDM</span><span class=204534100-03042002>which
is hairpined at the CO.&nbsp;</span><span class=204534100-03042002>The
DS0 is dedicated.&nbsp;</span><span class=204534100-03042002>The advantage
of Silent suppression&nbsp;</span><span 
class=204534100-03042002>it to
limit the RTP traffic on the&nbsp;</span><span class=204534100-03042002>IP
side, which you wouldn't have in that case.</span><span class=204534100-03042002></span><span class=204534100-03042002>Maybe
if you wanted to inject Comfort Noise instead of background</span><span class=204534100-03042002>noice
in the TDM-TDM call??</span><span class=204534100-03042002></span><span class=204534100-03042002>Carl</font></font></font></span>
<blockquote>
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> megaco-admin@ietf.org
[<A HREF="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]<b>On Behalf Of </b>Chuong N. Nguyen</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Tuesday, April 02, 2002
7:16 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> megaco@ietf.org</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: [Megaco] Local/Remote
descriptors and Permanent terminations</font></font></div>
Tom-PT Taylor wrote:
<blockquote TYPE="CITE">I've had a message pointing out the existence of
<br>draft-ietf-avt-rtp-cn-05.txt.&nbsp; Specifying this payload type as
well as G.711
<br>would indicate the use of silence suppression implicitly.&nbsp; That
covers RTP
<br>transport.&nbsp; For ATM we have the a=silenceSupp attribute defined
in RFC 3108.
<br>Do we need anything for TDM?</blockquote>

<p><br>What if someone wanted to make a TDM-TDM, hairpin call?
<br>Would silenceSupp be used for such a call?
<br>If yes, then what?
<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;</blockquote>
</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>

--------------D6A0A43CD85EF028A0C445B1--


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



From daemon@ns.ietf.org  Tue Apr  2 22:24: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 VAA12003
	for <megaco-archive@odin.ietf.org>; Tue, 2 Apr 2002 21:37:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA05569
	for megaco-archive@odin.ietf.org; Tue, 2 Apr 2002 21:37: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 UAA02883;
	Tue, 2 Apr 2002 20:39: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 UAA02852
	for <megaco@ns.ietf.org>; Tue, 2 Apr 2002 20:39:18 -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 UAA11100
	for <megaco@ietf.org>; Tue, 2 Apr 2002 20:39:16 -0500 (EST)
Received: from CRHOMEPC ([10.0.104.27]) by wench.telica.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id GQDA0N04; Tue, 2 Apr 2002 20:38:48 -0500
From: "Carl Rutter" <crutter@telica.com>
To: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
Cc: <megaco@ietf.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Tue, 2 Apr 2002 20:35:54 -0500
Message-ID: <000401c1daaf$e537b5d0$0300a8c0@telica.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01C1DA85.FC633470"
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
In-Reply-To: <3CAA553D.193B1C29@alcatel.com>
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1DA85.FC633470
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

You bring up a good point,
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more sense to
be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach for
SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
  -----Original Message-----
  From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
  Sent: Tuesday, April 02, 2002 8:05 PM
  Cc: megaco@ietf.org
  Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations



  That is what  I initially thought silence suppression was about.
  But then I was told differently.
  It could be applied to TDM.
  If not, then why are we discussing adding silence suppresion to the TDM
package?


  By the way,  I thought TDM-TDM calls are being made at the Gwy too.
  Aren't you guys doing that now?



  Carl Rutter wrote:

    I can't think of an application where you'd want to do that. Silence
suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at
the CO. The DS0 is dedicated. The advantage of Silent suppression it to
limit the RTP traffic on the IP side, which you wouldn't have in that
case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice
in the TDM-TDM call??Carl
      -----Original Message-----
      From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
      Sent: Tuesday, April 02, 2002 7:16 PM
      To: megaco@ietf.org
      Subject: Re: [Megaco] Local/Remote descriptors and Permanent
terminations
      Tom-PT Taylor wrote:
        I've had a message pointing out the existence of
        draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well
as G.711
        would indicate the use of silence suppression implicitly.  That
covers RTP
        transport.  For ATM we have the a=silenceSupp attribute defined in
RFC 3108.
        Do we need anything for TDM?

      What if someone wanted to make a TDM-TDM, hairpin call?
      Would silenceSupp be used for such a call?
      If yes, then what?



--
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****

--
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****


------=_NextPart_000_0005_01C1DA85.FC633470
Content-Type: text/html;
	charset="Windows-1252"
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=3Dus-ascii">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>You=20
bring up a good point, </FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Is/Should Silient Suppression be tied to the TDM package=20
or</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>SDP=20
TDM, if in fact its really more applicable to the Ephemral=20
side.</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>If no=20
can think of a good reason then your right it would make more sense to =
be in the=20
SDP.</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>For=20
now we could use 0 13 for G711 and long-term </FONT></SPAN><SPAN=20
class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>use the ATM=20
approach for SDP.</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>Trying=20
to drive towards closure as we have a need to implement=20
this.</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =
size=3D2>Yea,=20
the hairpinning would be in the MG Switch.</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Comments?</FONT></SPAN></DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D697531801-03042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Carl</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
megaco-admin@ietf.org=20
  [mailto:megaco-admin@ietf.org]<B>On Behalf Of </B>Chuong N.=20
  Nguyen<BR><B>Sent:</B> Tuesday, April 02, 2002 8:05 PM<BR><B>Cc:</B>=20
  megaco@ietf.org<BR><B>Subject:</B> Re: [Megaco] Local/Remote =
descriptors and=20
  Permanent terminations<BR><BR></FONT></DIV>&nbsp; <BR>That is what =
&nbsp;I=20
  initially thought silence suppression was about. <BR>But then =
I&nbsp;was told=20
  differently. <BR>It could be applied to TDM.=20
  <P>If not, then why are we discussing adding silence suppresion to the =

  TDM&nbsp;package? <BR>&nbsp;=20
  <P>By the way,&nbsp; I&nbsp;thought TDM-TDM calls are being made at =
the Gwy=20
  too. <BR>Aren't you guys doing that now? <BR>&nbsp; <BR>&nbsp;=20
  <P>Carl Rutter wrote:=20
  <BLOCKQUOTE TYPE=3D"CITE"><SPAN class=3D204534100-03042002><FONT=20
    face=3DArial><FONT color=3D#0000ff><FONT size=3D-1>I can't think of =
an application=20
    where you'd want to do that.&nbsp;</SPAN><SPAN=20
    class=3D204534100-03042002>Silence suppression really wouldn't make =
sense for=20
    a TDM-TDM</SPAN><SPAN class=3D204534100-03042002>which is hairpined =
at the=20
    CO.&nbsp;</SPAN><SPAN class=3D204534100-03042002>The DS0 is=20
    dedicated.&nbsp;</SPAN><SPAN class=3D204534100-03042002>The =
advantage of=20
    Silent suppression&nbsp;</SPAN><SPAN class=3D204534100-03042002>it =
to limit=20
    the RTP traffic on the&nbsp;</SPAN><SPAN =
class=3D204534100-03042002>IP side,=20
    which you wouldn't have in that case.</SPAN><SPAN=20
    class=3D204534100-03042002></SPAN><SPAN =
class=3D204534100-03042002>Maybe if you=20
    wanted to inject Comfort Noise instead of background</SPAN><SPAN=20
    class=3D204534100-03042002>noice in the TDM-TDM call??</SPAN><SPAN=20
    class=3D204534100-03042002></SPAN><SPAN=20
    class=3D204534100-03042002>Carl</FONT></FONT></FONT></SPAN>=20
    <BLOCKQUOTE>
      <DIV class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma><FONT=20
      size=3D-1>-----Original Message-----</FONT></FONT> <BR><FONT=20
      face=3DTahoma><FONT size=3D-1><B>From:</B> megaco-admin@ietf.org =
[<A=20
      =
href=3D"mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]<B=
>On=20
      Behalf Of </B>Chuong N. Nguyen</FONT></FONT> <BR><FONT =
face=3DTahoma><FONT=20
      size=3D-1><B>Sent:</B> Tuesday, April 02, 2002 7:16 =
PM</FONT></FONT>=20
      <BR><FONT face=3DTahoma><FONT size=3D-1><B>To:</B>=20
      megaco@ietf.org</FONT></FONT> <BR><FONT face=3DTahoma><FONT=20
      size=3D-1><B>Subject:</B> Re: [Megaco] Local/Remote descriptors =
and=20
      Permanent terminations</FONT></FONT></DIV>Tom-PT Taylor wrote:=20
      <BLOCKQUOTE TYPE=3D"CITE">I've had a message pointing out the =
existence of=20
        <BR>draft-ietf-avt-rtp-cn-05.txt.&nbsp; Specifying this payload =
type as=20
        well as G.711 <BR>would indicate the use of silence suppression=20
        implicitly.&nbsp; That covers RTP <BR>transport.&nbsp; For ATM =
we have=20
        the a=3DsilenceSupp attribute defined in RFC 3108. <BR>Do we =
need anything=20
        for TDM?</BLOCKQUOTE>
      <P><BR>What if someone wanted to make a TDM-TDM, hairpin call? =
<BR>Would=20
      silenceSupp be used for such a call? <BR>If yes, then what? =
<BR>&nbsp;=20
      <BR>&nbsp; <PRE>--&nbsp;
&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; 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;</BLOCKQUOTE></BLOCKQUOTE><PRE>--&nbsp;
&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; 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_000_0005_01C1DA85.FC633470--


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



From megaco-admin@ietf.org  Wed Apr  3 02:16: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 CAA26326
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 02:16: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 BAA27834;
	Wed, 3 Apr 2002 01:46: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 BAA27804
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 01:45:58 -0500 (EST)
Received: from postman ([217.31.228.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17665
	for <megaco@ietf.org>; Wed, 3 Apr 2002 01:45:54 -0500 (EST)
To: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.4  June 8, 2000
Message-ID: <OFB627BCCB.875F704D-ONC2256B90.002A2F55@LocalDomain>
From: "SERDAR CABUK" <serdar.cabuk@o2.com.tr>
Date: Wed, 3 Apr 2002 09:43:35 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 04/03/2002
 09:44:10 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Megaco] JAIN 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


Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



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


From daemon@ns.ietf.org  Wed Apr  3 02:16: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 CAA26336
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 02:16:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA29478
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 02:16: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 BAA27834;
	Wed, 3 Apr 2002 01:46: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 BAA27804
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 01:45:58 -0500 (EST)
Received: from postman ([217.31.228.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17665
	for <megaco@ietf.org>; Wed, 3 Apr 2002 01:45:54 -0500 (EST)
To: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.4  June 8, 2000
Message-ID: <OFB627BCCB.875F704D-ONC2256B90.002A2F55@LocalDomain>
From: "SERDAR CABUK" <serdar.cabuk@o2.com.tr>
Date: Wed, 3 Apr 2002 09:43:35 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 04/03/2002
 09:44:10 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Megaco] JAIN 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


Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



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



From megaco-admin@ietf.org  Wed Apr  3 07:38: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 HAA00974
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 07:38:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17887;
	Wed, 3 Apr 2002 07:22:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA01304
	for <megaco@optimus.ietf.org>; Wed, 3 Apr 2002 02:50:32 -0500 (EST)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26661
	for <megaco@ietf.org>; Wed, 3 Apr 2002 02:49:08 -0500 (EST)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id JAA01570;
	Wed, 3 Apr 2002 09:49:03 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id JAA01070;
	Wed, 3 Apr 2002 09:48:45 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2653.19)
	id <H22NL17P>; Wed, 3 Apr 2002 09:49:04 +0200
Message-ID: <E01FD2A7A400D511A97C0008C791E2DF5FCBF0@MCHH262E>
From: Pauls Markus <Markus.Pauls@icn.siemens.de>
To: megaco@ietf.org
Cc: "'Carl Rutter'" <crutter@telica.com>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 3 Apr 2002 09:48:51 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id CAA01305
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org
Content-Transfer-Encoding: 8bit

Suppose you have the following SDP:

m=audio 4444 RTP/AVP 0 18
a=fmtp:18 annexb=no         // G.729, Silence Suppression off (see draft-ietf-avt-rtp-mime-05)
a=silenceSupp: on - - - -

(that means the GW may either use G.711 µ-law or G.729)

The silenceSupp attribute is not specific for a payload type, the fmtp attribute is. So which one has precedence in this case?

In my opinion you should have the ability to switch on silence suppression depending on the payload type. If you want to use it with G.711, it does not mean that you want it with G.729.

Beyond that I believe generally it is more suited to an ephemeral termination. Therefore it should be expressed by means of SDP.

However, if you want to transport the comfort noise payload (according to draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP media line as well (IMO).

From my point of view the SDP should therefore look something like this:

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes

where this PCMU specific parameter silSup must still be defined (for PCMA as well).

Any comment is appreciated.


	Kind regards

		Markus Pauls


________________________________________________________
Markus Pauls

SIEMENS
Information and Communication Networks

ICN WN CC NA B13   	Tel.:  	+49 89 722 62937
Hofmannstr. 51     	Fax:   	+49 89 722 44176
81359 Munich        	Email: 	markus.pauls@icn.siemens.de
Germany




-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 3:36 AM
To: Chuong N. Nguyen
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


You bring up a good point, 
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more sense to be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach for SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of Chuong N. Nguyen
Sent: Tuesday, April 02, 2002 8:05 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
That is what  I initially thought silence suppression was about. 
But then I was told differently. 
It could be applied to TDM. 
If not, then why are we discussing adding silence suppresion to the TDM package? 
  
By the way,  I thought TDM-TDM calls are being made at the Gwy too. 
Aren't you guys doing that now? 
  
  
Carl Rutter wrote: 
I can't think of an application where you'd want to do that. Silence suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at the CO. The DS0 is dedicated. The advantage of Silent suppression it to limit the RTP traffic on the IP side, which you wouldn't have in that case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice in the TDM-TDM call??Carl 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of Chuong N. Nguyen 
Sent: Tuesday, April 02, 2002 7:16 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
Tom-PT Taylor wrote: 
I've had a message pointing out the existence of 
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711 
would indicate the use of silence suppression implicitly.  That covers RTP 
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108. 
Do we need anything for TDM?

What if someone wanted to make a TDM-TDM, hairpin call? 
Would silenceSupp be used for such a call? 
If yes, then what? 
  
  
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc **** 
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****  


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


From daemon@ns.ietf.org  Wed Apr  3 07:39: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 HAA00991
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 07:39:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA19914
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 07: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 HAA17887;
	Wed, 3 Apr 2002 07:22:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA01304
	for <megaco@optimus.ietf.org>; Wed, 3 Apr 2002 02:50:32 -0500 (EST)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26661
	for <megaco@ietf.org>; Wed, 3 Apr 2002 02:49:08 -0500 (EST)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id JAA01570;
	Wed, 3 Apr 2002 09:49:03 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id JAA01070;
	Wed, 3 Apr 2002 09:48:45 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2653.19)
	id <H22NL17P>; Wed, 3 Apr 2002 09:49:04 +0200
Message-ID: <E01FD2A7A400D511A97C0008C791E2DF5FCBF0@MCHH262E>
From: Pauls Markus <Markus.Pauls@icn.siemens.de>
To: megaco@ietf.org
Cc: "'Carl Rutter'" <crutter@telica.com>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 3 Apr 2002 09:48:51 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id CAA01305
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org
Content-Transfer-Encoding: 8bit

Suppose you have the following SDP:

m=audio 4444 RTP/AVP 0 18
a=fmtp:18 annexb=no         // G.729, Silence Suppression off (see draft-ietf-avt-rtp-mime-05)
a=silenceSupp: on - - - -

(that means the GW may either use G.711 µ-law or G.729)

The silenceSupp attribute is not specific for a payload type, the fmtp attribute is. So which one has precedence in this case?

In my opinion you should have the ability to switch on silence suppression depending on the payload type. If you want to use it with G.711, it does not mean that you want it with G.729.

Beyond that I believe generally it is more suited to an ephemeral termination. Therefore it should be expressed by means of SDP.

However, if you want to transport the comfort noise payload (according to draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP media line as well (IMO).

From my point of view the SDP should therefore look something like this:

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes

where this PCMU specific parameter silSup must still be defined (for PCMA as well).

Any comment is appreciated.


	Kind regards

		Markus Pauls


________________________________________________________
Markus Pauls

SIEMENS
Information and Communication Networks

ICN WN CC NA B13   	Tel.:  	+49 89 722 62937
Hofmannstr. 51     	Fax:   	+49 89 722 44176
81359 Munich        	Email: 	markus.pauls@icn.siemens.de
Germany




-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 3:36 AM
To: Chuong N. Nguyen
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


You bring up a good point, 
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more sense to be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach for SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of Chuong N. Nguyen
Sent: Tuesday, April 02, 2002 8:05 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
That is what  I initially thought silence suppression was about. 
But then I was told differently. 
It could be applied to TDM. 
If not, then why are we discussing adding silence suppresion to the TDM package? 
  
By the way,  I thought TDM-TDM calls are being made at the Gwy too. 
Aren't you guys doing that now? 
  
  
Carl Rutter wrote: 
I can't think of an application where you'd want to do that. Silence suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at the CO. The DS0 is dedicated. The advantage of Silent suppression it to limit the RTP traffic on the IP side, which you wouldn't have in that case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice in the TDM-TDM call??Carl 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of Chuong N. Nguyen 
Sent: Tuesday, April 02, 2002 7:16 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
Tom-PT Taylor wrote: 
I've had a message pointing out the existence of 
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711 
would indicate the use of silence suppression implicitly.  That covers RTP 
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108. 
Do we need anything for TDM?

What if someone wanted to make a TDM-TDM, hairpin call? 
Would silenceSupp be used for such a call? 
If yes, then what? 
  
  
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc **** 
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****  


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



From megaco-admin@ietf.org  Wed Apr  3 08:10: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 IAA02061
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 08:10: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 HAA21089;
	Wed, 3 Apr 2002 07:52: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 HAA20982
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 07:52:23 -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 HAA01369
	for <megaco@ietf.org>; Wed, 3 Apr 2002 07:52:19 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA03TK>; Wed, 3 Apr 2002 07:51:52 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C4E@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Pauls Markus'" <Markus.Pauls@icn.siemens.de>, megaco@ietf.org
Cc: Carl Rutter <crutter@telica.com>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 3 Apr 2002 07:51:43 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA20983
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

Yea, for overspecification I see your point.

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes
makes sense, 
but still seems kind of awkward in that
we have different ways of implementing Silent Suppression
based on the payload.

It would be nice to have a common parameter among the payloads
that had more than just an ON/OFF option to provide future flexibility
like they thought of in RFC3018:
silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse> 
                   <fxnslevel> 
So from the discussions I've read, Silent Suppression should:
1) Be implemented in SDP 
2) Enabled/Disabled on a per payload type
3) Should have more than just and On/Off option
4) Be backward compatable to allow support for the Annex option 
   with the compressed vocoders
5) Be consistant among Payload types

I guess if we gave up on #3 and #5 we could implement Pauls suggestion.
Not sure the logistics of how thats done??

Are we getting close?

Carl


-----Original Message-----
From: Pauls Markus [mailto:Markus.Pauls@icn.siemens.de]
Sent: Wednesday, April 03, 2002 2:49 AM
To: megaco@ietf.org
Cc: 'Carl Rutter'
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Suppose you have the following SDP:

m=audio 4444 RTP/AVP 0 18
a=fmtp:18 annexb=no         // G.729, Silence Suppression off (see
draft-ietf-avt-rtp-mime-05)
a=silenceSupp: on - - - -

(that means the GW may either use G.711 µ-law or G.729)

The silenceSupp attribute is not specific for a payload type, the fmtp
attribute is. So which one has precedence in this case?

In my opinion you should have the ability to switch on silence suppression
depending on the payload type. If you want to use it with G.711, it does not
mean that you want it with G.729.

Beyond that I believe generally it is more suited to an ephemeral
termination. Therefore it should be expressed by means of SDP.

However, if you want to transport the comfort noise payload (according to
draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP
media line as well (IMO).

From my point of view the SDP should therefore look something like this:

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes

where this PCMU specific parameter silSup must still be defined (for PCMA as
well).

Any comment is appreciated.


	Kind regards

		Markus Pauls


________________________________________________________
Markus Pauls

SIEMENS
Information and Communication Networks

ICN WN CC NA B13   	Tel.:  	+49 89 722 62937
Hofmannstr. 51     	Fax:   	+49 89 722 44176
81359 Munich        	Email: 	markus.pauls@icn.siemens.de
Germany




-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 3:36 AM
To: Chuong N. Nguyen
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


You bring up a good point, 
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more sense to
be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach for
SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
Sent: Tuesday, April 02, 2002 8:05 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
That is what  I initially thought silence suppression was about. 
But then I was told differently. 
It could be applied to TDM. 
If not, then why are we discussing adding silence suppresion to the TDM
package? 
  
By the way,  I thought TDM-TDM calls are being made at the Gwy too. 
Aren't you guys doing that now? 
  
  
Carl Rutter wrote: 
I can't think of an application where you'd want to do that. Silence
suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at
the CO. The DS0 is dedicated. The advantage of Silent suppression it to
limit the RTP traffic on the IP side, which you wouldn't have in that
case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice
in the TDM-TDM call??Carl 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen 
Sent: Tuesday, April 02, 2002 7:16 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
Tom-PT Taylor wrote: 
I've had a message pointing out the existence of 
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711

would indicate the use of silence suppression implicitly.  That covers RTP 
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.

Do we need anything for TDM?

What if someone wanted to make a TDM-TDM, hairpin call? 
Would silenceSupp be used for such a call? 
If yes, then what? 
  
  
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc **** 
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****  

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


From daemon@ns.ietf.org  Wed Apr  3 08:10: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 IAA02074
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 08:10:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA22286
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 08:10: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 HAA21089;
	Wed, 3 Apr 2002 07:52: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 HAA20982
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 07:52:23 -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 HAA01369
	for <megaco@ietf.org>; Wed, 3 Apr 2002 07:52:19 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA03TK>; Wed, 3 Apr 2002 07:51:52 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C4E@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Pauls Markus'" <Markus.Pauls@icn.siemens.de>, megaco@ietf.org
Cc: Carl Rutter <crutter@telica.com>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 3 Apr 2002 07:51:43 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA20983
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

Yea, for overspecification I see your point.

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes
makes sense, 
but still seems kind of awkward in that
we have different ways of implementing Silent Suppression
based on the payload.

It would be nice to have a common parameter among the payloads
that had more than just an ON/OFF option to provide future flexibility
like they thought of in RFC3018:
silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse> 
                   <fxnslevel> 
So from the discussions I've read, Silent Suppression should:
1) Be implemented in SDP 
2) Enabled/Disabled on a per payload type
3) Should have more than just and On/Off option
4) Be backward compatable to allow support for the Annex option 
   with the compressed vocoders
5) Be consistant among Payload types

I guess if we gave up on #3 and #5 we could implement Pauls suggestion.
Not sure the logistics of how thats done??

Are we getting close?

Carl


-----Original Message-----
From: Pauls Markus [mailto:Markus.Pauls@icn.siemens.de]
Sent: Wednesday, April 03, 2002 2:49 AM
To: megaco@ietf.org
Cc: 'Carl Rutter'
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Suppose you have the following SDP:

m=audio 4444 RTP/AVP 0 18
a=fmtp:18 annexb=no         // G.729, Silence Suppression off (see
draft-ietf-avt-rtp-mime-05)
a=silenceSupp: on - - - -

(that means the GW may either use G.711 µ-law or G.729)

The silenceSupp attribute is not specific for a payload type, the fmtp
attribute is. So which one has precedence in this case?

In my opinion you should have the ability to switch on silence suppression
depending on the payload type. If you want to use it with G.711, it does not
mean that you want it with G.729.

Beyond that I believe generally it is more suited to an ephemeral
termination. Therefore it should be expressed by means of SDP.

However, if you want to transport the comfort noise payload (according to
draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP
media line as well (IMO).

From my point of view the SDP should therefore look something like this:

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes

where this PCMU specific parameter silSup must still be defined (for PCMA as
well).

Any comment is appreciated.


	Kind regards

		Markus Pauls


________________________________________________________
Markus Pauls

SIEMENS
Information and Communication Networks

ICN WN CC NA B13   	Tel.:  	+49 89 722 62937
Hofmannstr. 51     	Fax:   	+49 89 722 44176
81359 Munich        	Email: 	markus.pauls@icn.siemens.de
Germany




-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 3:36 AM
To: Chuong N. Nguyen
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


You bring up a good point, 
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more sense to
be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach for
SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
Sent: Tuesday, April 02, 2002 8:05 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
That is what  I initially thought silence suppression was about. 
But then I was told differently. 
It could be applied to TDM. 
If not, then why are we discussing adding silence suppresion to the TDM
package? 
  
By the way,  I thought TDM-TDM calls are being made at the Gwy too. 
Aren't you guys doing that now? 
  
  
Carl Rutter wrote: 
I can't think of an application where you'd want to do that. Silence
suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at
the CO. The DS0 is dedicated. The advantage of Silent suppression it to
limit the RTP traffic on the IP side, which you wouldn't have in that
case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice
in the TDM-TDM call??Carl 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen 
Sent: Tuesday, April 02, 2002 7:16 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
Tom-PT Taylor wrote: 
I've had a message pointing out the existence of 
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711

would indicate the use of silence suppression implicitly.  That covers RTP 
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.

Do we need anything for TDM?

What if someone wanted to make a TDM-TDM, hairpin call? 
Would silenceSupp be used for such a call? 
If yes, then what? 
  
  
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc **** 
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****  

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



From megaco-admin@ietf.org  Wed Apr  3 08:10: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 IAA02086
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 08:10: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 HAA21241;
	Wed, 3 Apr 2002 07:53: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 HAA21214
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 07:53: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 HAA01412
	for <megaco@ietf.org>; Wed, 3 Apr 2002 07:53:49 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA03TL>; Wed, 3 Apr 2002 07:53:22 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C4F@wench>
From: Carl Rutter <crutter@telica.com>
To: Carl Rutter <crutter@telica.com>,
        "'Pauls Markus'"
	 <Markus.Pauls@icn.siemens.de>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 3 Apr 2002 07:53:17 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA21215
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

One more comment, 
sorry for so many.
Would be really need to specify the 13
if we had the SilSup parameter?

Carl
-----Original Message-----
From: Carl Rutter 
Sent: Wednesday, April 03, 2002 7:52 AM
To: 'Pauls Markus'; megaco@ietf.org
Cc: Carl Rutter
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Yea, for overspecification I see your point.

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes
makes sense, 
but still seems kind of awkward in that
we have different ways of implementing Silent Suppression
based on the payload.

It would be nice to have a common parameter among the payloads
that had more than just an ON/OFF option to provide future flexibility
like they thought of in RFC3018:
silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse> 
                   <fxnslevel> 
So from the discussions I've read, Silent Suppression should:
1) Be implemented in SDP 
2) Enabled/Disabled on a per payload type
3) Should have more than just and On/Off option
4) Be backward compatable to allow support for the Annex option 
   with the compressed vocoders
5) Be consistant among Payload types

I guess if we gave up on #3 and #5 we could implement Pauls suggestion.
Not sure the logistics of how thats done??

Are we getting close?

Carl


-----Original Message-----
From: Pauls Markus [mailto:Markus.Pauls@icn.siemens.de]
Sent: Wednesday, April 03, 2002 2:49 AM
To: megaco@ietf.org
Cc: 'Carl Rutter'
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Suppose you have the following SDP:

m=audio 4444 RTP/AVP 0 18
a=fmtp:18 annexb=no         // G.729, Silence Suppression off (see
draft-ietf-avt-rtp-mime-05)
a=silenceSupp: on - - - -

(that means the GW may either use G.711 µ-law or G.729)

The silenceSupp attribute is not specific for a payload type, the fmtp
attribute is. So which one has precedence in this case?

In my opinion you should have the ability to switch on silence suppression
depending on the payload type. If you want to use it with G.711, it does not
mean that you want it with G.729.

Beyond that I believe generally it is more suited to an ephemeral
termination. Therefore it should be expressed by means of SDP.

However, if you want to transport the comfort noise payload (according to
draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP
media line as well (IMO).

From my point of view the SDP should therefore look something like this:

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes

where this PCMU specific parameter silSup must still be defined (for PCMA as
well).

Any comment is appreciated.


	Kind regards

		Markus Pauls


________________________________________________________
Markus Pauls

SIEMENS
Information and Communication Networks

ICN WN CC NA B13   	Tel.:  	+49 89 722 62937
Hofmannstr. 51     	Fax:   	+49 89 722 44176
81359 Munich        	Email: 	markus.pauls@icn.siemens.de
Germany




-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 3:36 AM
To: Chuong N. Nguyen
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


You bring up a good point, 
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more sense to
be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach for
SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
Sent: Tuesday, April 02, 2002 8:05 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
That is what  I initially thought silence suppression was about. 
But then I was told differently. 
It could be applied to TDM. 
If not, then why are we discussing adding silence suppresion to the TDM
package? 
  
By the way,  I thought TDM-TDM calls are being made at the Gwy too. 
Aren't you guys doing that now? 
  
  
Carl Rutter wrote: 
I can't think of an application where you'd want to do that. Silence
suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at
the CO. The DS0 is dedicated. The advantage of Silent suppression it to
limit the RTP traffic on the IP side, which you wouldn't have in that
case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice
in the TDM-TDM call??Carl 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen 
Sent: Tuesday, April 02, 2002 7:16 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
Tom-PT Taylor wrote: 
I've had a message pointing out the existence of 
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711

would indicate the use of silence suppression implicitly.  That covers RTP 
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.

Do we need anything for TDM?

What if someone wanted to make a TDM-TDM, hairpin call? 
Would silenceSupp be used for such a call? 
If yes, then what? 
  
  
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc **** 
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****  

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


From daemon@ns.ietf.org  Wed Apr  3 08:10: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 IAA02100
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 08:10:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA22300
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 08:10: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 HAA21241;
	Wed, 3 Apr 2002 07:53: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 HAA21214
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 07:53: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 HAA01412
	for <megaco@ietf.org>; Wed, 3 Apr 2002 07:53:49 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA03TL>; Wed, 3 Apr 2002 07:53:22 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C4F@wench>
From: Carl Rutter <crutter@telica.com>
To: Carl Rutter <crutter@telica.com>,
        "'Pauls Markus'"
	 <Markus.Pauls@icn.siemens.de>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 3 Apr 2002 07:53:17 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id HAA21215
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

One more comment, 
sorry for so many.
Would be really need to specify the 13
if we had the SilSup parameter?

Carl
-----Original Message-----
From: Carl Rutter 
Sent: Wednesday, April 03, 2002 7:52 AM
To: 'Pauls Markus'; megaco@ietf.org
Cc: Carl Rutter
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Yea, for overspecification I see your point.

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes
makes sense, 
but still seems kind of awkward in that
we have different ways of implementing Silent Suppression
based on the payload.

It would be nice to have a common parameter among the payloads
that had more than just an ON/OFF option to provide future flexibility
like they thought of in RFC3018:
silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse> 
                   <fxnslevel> 
So from the discussions I've read, Silent Suppression should:
1) Be implemented in SDP 
2) Enabled/Disabled on a per payload type
3) Should have more than just and On/Off option
4) Be backward compatable to allow support for the Annex option 
   with the compressed vocoders
5) Be consistant among Payload types

I guess if we gave up on #3 and #5 we could implement Pauls suggestion.
Not sure the logistics of how thats done??

Are we getting close?

Carl


-----Original Message-----
From: Pauls Markus [mailto:Markus.Pauls@icn.siemens.de]
Sent: Wednesday, April 03, 2002 2:49 AM
To: megaco@ietf.org
Cc: 'Carl Rutter'
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Suppose you have the following SDP:

m=audio 4444 RTP/AVP 0 18
a=fmtp:18 annexb=no         // G.729, Silence Suppression off (see
draft-ietf-avt-rtp-mime-05)
a=silenceSupp: on - - - -

(that means the GW may either use G.711 µ-law or G.729)

The silenceSupp attribute is not specific for a payload type, the fmtp
attribute is. So which one has precedence in this case?

In my opinion you should have the ability to switch on silence suppression
depending on the payload type. If you want to use it with G.711, it does not
mean that you want it with G.729.

Beyond that I believe generally it is more suited to an ephemeral
termination. Therefore it should be expressed by means of SDP.

However, if you want to transport the comfort noise payload (according to
draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP
media line as well (IMO).

From my point of view the SDP should therefore look something like this:

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes

where this PCMU specific parameter silSup must still be defined (for PCMA as
well).

Any comment is appreciated.


	Kind regards

		Markus Pauls


________________________________________________________
Markus Pauls

SIEMENS
Information and Communication Networks

ICN WN CC NA B13   	Tel.:  	+49 89 722 62937
Hofmannstr. 51     	Fax:   	+49 89 722 44176
81359 Munich        	Email: 	markus.pauls@icn.siemens.de
Germany




-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 3:36 AM
To: Chuong N. Nguyen
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


You bring up a good point, 
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more sense to
be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach for
SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
Sent: Tuesday, April 02, 2002 8:05 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
That is what  I initially thought silence suppression was about. 
But then I was told differently. 
It could be applied to TDM. 
If not, then why are we discussing adding silence suppresion to the TDM
package? 
  
By the way,  I thought TDM-TDM calls are being made at the Gwy too. 
Aren't you guys doing that now? 
  
  
Carl Rutter wrote: 
I can't think of an application where you'd want to do that. Silence
suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at
the CO. The DS0 is dedicated. The advantage of Silent suppression it to
limit the RTP traffic on the IP side, which you wouldn't have in that
case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice
in the TDM-TDM call??Carl 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen 
Sent: Tuesday, April 02, 2002 7:16 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
Tom-PT Taylor wrote: 
I've had a message pointing out the existence of 
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711

would indicate the use of silence suppression implicitly.  That covers RTP 
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.

Do we need anything for TDM?

What if someone wanted to make a TDM-TDM, hairpin call? 
Would silenceSupp be used for such a call? 
If yes, then what? 
  
  
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc **** 
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****  

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



From megaco-admin@ietf.org  Wed Apr  3 08:32: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 IAA02679
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 08:32: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 IAA22228;
	Wed, 3 Apr 2002 08:08: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 IAA22200
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 08:08:49 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01998
	for <megaco@ietf.org>; Wed, 3 Apr 2002 08:08:46 -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 g33D8Gi04023
	for <megaco@ietf.org>; Wed, 3 Apr 2002 08:08:16 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0WCQ>; Wed, 3 Apr 2002 08:08:18 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A23F@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Pauls Markus'" <Markus.Pauls@icn.siemens.de>, megaco@ietf.org
Cc: "'Carl Rutter'" <crutter@telica.com>,
        "'Chuong N. Nguyen'"
	 <Chuong.Nguyen@alcatel.com>,
        "'Stephen Casner'" <casner@acm.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 3 Apr 2002 08:08: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

[Stephen Casner copied because this potentially affects AVT WG work in
progress.]

To summarize: we are trying to define how to indicate that silence
suppression is desired for a given audio flow.  We could do it through an
a=silenceSupp attribute, through codec-specific a=fmtp: parameters, or
implicitly by specifying the Comfort Noise codec as an alternative.  Markus
shows the sort of contradictions we could arrive at if we are not careful.

I think it's quite clear that we do NOT want to tie silence suppression to
the TDM package.  

The cleanest way would be to ensure that every codec where silence
suppression might apply has a silence suppression parameter.  For RTP, this
requires revisiting draft-ietf-avt-rtp-mime-06.txt, which is currently in
IETF Last Call.  Not sure what we do about ATM: RFC 3108 defines a profile
that just picks up the RTP mappings, so maybe it would also pick up the
parameters defined in the MIME type registrations and payload format
descriptions.  I find this whole area murky because theoretically there
should be new MIME type registrations for each transport in order to reuse
the profiles in SDP.

A second possibility is to define the a=silenceSupp attribute for all
transports, but specify that it takes second priority to a=fmtp parameters
where these are defined.  This is probably the most practical route.

Stephen, any comments?

-----Original Message-----
From: Pauls Markus [mailto:Markus.Pauls@icn.siemens.de]
Sent: Wednesday, April 03, 2002 2:49 AM
To: megaco@ietf.org
Cc: 'Carl Rutter'
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Suppose you have the following SDP:

m=audio 4444 RTP/AVP 0 18
a=fmtp:18 annexb=no         // G.729, Silence Suppression off (see
draft-ietf-avt-rtp-mime-05)
a=silenceSupp: on - - - -

(that means the GW may either use G.711 µ-law or G.729)

The silenceSupp attribute is not specific for a payload type, the fmtp
attribute is. So which one has precedence in this case?

In my opinion you should have the ability to switch on silence suppression
depending on the payload type. If you want to use it with G.711, it does not
mean that you want it with G.729.

Beyond that I believe generally it is more suited to an ephemeral
termination. Therefore it should be expressed by means of SDP.

However, if you want to transport the comfort noise payload (according to
draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP
media line as well (IMO).

From my point of view the SDP should therefore look something like this:

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes

where this PCMU specific parameter silSup must still be defined (for PCMA as
well).

Any comment is appreciated.


	Kind regards

		Markus Pauls


________________________________________________________
Markus Pauls

SIEMENS
Information and Communication Networks

ICN WN CC NA B13   	Tel.:  	+49 89 722 62937
Hofmannstr. 51     	Fax:   	+49 89 722 44176
81359 Munich        	Email: 	markus.pauls@icn.siemens.de
Germany




-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 3:36 AM
To: Chuong N. Nguyen
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


You bring up a good point, 
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more sense to
be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach for
SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
Sent: Tuesday, April 02, 2002 8:05 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
That is what  I initially thought silence suppression was about. 
But then I was told differently. 
It could be applied to TDM. 
If not, then why are we discussing adding silence suppresion to the TDM
package? 
  
By the way,  I thought TDM-TDM calls are being made at the Gwy too. 
Aren't you guys doing that now? 
  
  
Carl Rutter wrote: 
I can't think of an application where you'd want to do that. Silence
suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at
the CO. The DS0 is dedicated. The advantage of Silent suppression it to
limit the RTP traffic on the IP side, which you wouldn't have in that
case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice
in the TDM-TDM call??Carl 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen 
Sent: Tuesday, April 02, 2002 7:16 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
Tom-PT Taylor wrote: 
I've had a message pointing out the existence of 
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711

would indicate the use of silence suppression implicitly.  That covers RTP 
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.

Do we need anything for TDM?

What if someone wanted to make a TDM-TDM, hairpin call? 
Would silenceSupp be used for such a call? 
If yes, then what? 
  
  
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc **** 
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****  


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

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


From daemon@ns.ietf.org  Wed Apr  3 08:32: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 IAA02691
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 08:32:24 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA23966
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 08:32: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 IAA22228;
	Wed, 3 Apr 2002 08:08: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 IAA22200
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 08:08:49 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01998
	for <megaco@ietf.org>; Wed, 3 Apr 2002 08:08:46 -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 g33D8Gi04023
	for <megaco@ietf.org>; Wed, 3 Apr 2002 08:08:16 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63K0WCQ>; Wed, 3 Apr 2002 08:08:18 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A23F@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Pauls Markus'" <Markus.Pauls@icn.siemens.de>, megaco@ietf.org
Cc: "'Carl Rutter'" <crutter@telica.com>,
        "'Chuong N. Nguyen'"
	 <Chuong.Nguyen@alcatel.com>,
        "'Stephen Casner'" <casner@acm.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 3 Apr 2002 08:08: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

[Stephen Casner copied because this potentially affects AVT WG work in
progress.]

To summarize: we are trying to define how to indicate that silence
suppression is desired for a given audio flow.  We could do it through an
a=silenceSupp attribute, through codec-specific a=fmtp: parameters, or
implicitly by specifying the Comfort Noise codec as an alternative.  Markus
shows the sort of contradictions we could arrive at if we are not careful.

I think it's quite clear that we do NOT want to tie silence suppression to
the TDM package.  

The cleanest way would be to ensure that every codec where silence
suppression might apply has a silence suppression parameter.  For RTP, this
requires revisiting draft-ietf-avt-rtp-mime-06.txt, which is currently in
IETF Last Call.  Not sure what we do about ATM: RFC 3108 defines a profile
that just picks up the RTP mappings, so maybe it would also pick up the
parameters defined in the MIME type registrations and payload format
descriptions.  I find this whole area murky because theoretically there
should be new MIME type registrations for each transport in order to reuse
the profiles in SDP.

A second possibility is to define the a=silenceSupp attribute for all
transports, but specify that it takes second priority to a=fmtp parameters
where these are defined.  This is probably the most practical route.

Stephen, any comments?

-----Original Message-----
From: Pauls Markus [mailto:Markus.Pauls@icn.siemens.de]
Sent: Wednesday, April 03, 2002 2:49 AM
To: megaco@ietf.org
Cc: 'Carl Rutter'
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Suppose you have the following SDP:

m=audio 4444 RTP/AVP 0 18
a=fmtp:18 annexb=no         // G.729, Silence Suppression off (see
draft-ietf-avt-rtp-mime-05)
a=silenceSupp: on - - - -

(that means the GW may either use G.711 µ-law or G.729)

The silenceSupp attribute is not specific for a payload type, the fmtp
attribute is. So which one has precedence in this case?

In my opinion you should have the ability to switch on silence suppression
depending on the payload type. If you want to use it with G.711, it does not
mean that you want it with G.729.

Beyond that I believe generally it is more suited to an ephemeral
termination. Therefore it should be expressed by means of SDP.

However, if you want to transport the comfort noise payload (according to
draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP
media line as well (IMO).

From my point of view the SDP should therefore look something like this:

m=audio 4444 RTP/AVP 0 18 13
a=fmtp:18 annexb=no
a=fmtp:0 silSup=yes

where this PCMU specific parameter silSup must still be defined (for PCMA as
well).

Any comment is appreciated.


	Kind regards

		Markus Pauls


________________________________________________________
Markus Pauls

SIEMENS
Information and Communication Networks

ICN WN CC NA B13   	Tel.:  	+49 89 722 62937
Hofmannstr. 51     	Fax:   	+49 89 722 44176
81359 Munich        	Email: 	markus.pauls@icn.siemens.de
Germany




-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 3:36 AM
To: Chuong N. Nguyen
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations


You bring up a good point, 
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more sense to
be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach for
SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
Sent: Tuesday, April 02, 2002 8:05 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations


  
That is what  I initially thought silence suppression was about. 
But then I was told differently. 
It could be applied to TDM. 
If not, then why are we discussing adding silence suppresion to the TDM
package? 
  
By the way,  I thought TDM-TDM calls are being made at the Gwy too. 
Aren't you guys doing that now? 
  
  
Carl Rutter wrote: 
I can't think of an application where you'd want to do that. Silence
suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at
the CO. The DS0 is dedicated. The advantage of Silent suppression it to
limit the RTP traffic on the IP side, which you wouldn't have in that
case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice
in the TDM-TDM call??Carl 
-----Original Message----- 
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen 
Sent: Tuesday, April 02, 2002 7:16 PM 
To: megaco@ietf.org 
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
Tom-PT Taylor wrote: 
I've had a message pointing out the existence of 
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711

would indicate the use of silence suppression implicitly.  That covers RTP 
transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.

Do we need anything for TDM?

What if someone wanted to make a TDM-TDM, hairpin call? 
Would silenceSupp be used for such a call? 
If yes, then what? 
  
  
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc **** 
-- 
  Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
  1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
  **** The opinions expressed are not those of Alcatel USA, Inc ****  


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

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



From megaco-admin@ietf.org  Wed Apr  3 09:19: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 JAA03901
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 09:19: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 IAA24905;
	Wed, 3 Apr 2002 08:53: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 IAA24789
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 08:52:58 -0500 (EST)
Received: from zctfs063.nortelnetworks.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03209
	for <megaco@ietf.org>; Wed, 3 Apr 2002 08:52:49 -0500 (EST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g33DqKv16702;
	Wed, 3 Apr 2002 15:52:20 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g33DpjJ07274;
	Wed, 3 Apr 2002 14:51:45 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <HLDBCBZD>; Wed, 3 Apr 2002 14:52:26 +0100
Message-ID: <4103264BC8D3D51180B7002048400C4502F281@zhard0jd.europe.nortel.com>
From: "David Barr"<david.barr@nortelnetworks.com>
To: "'Carl Rutter'" <crutter@telica.com>,
        "'Pauls Markus'"
	 <Markus.Pauls@icn.siemens.de>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 3 Apr 2002 14:52:25 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DB16.C91F491E"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1DB16.C91F491E
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: quoted-printable

In making a decision please consider the following:

With silence suppression, there are actually 2 separate things we need =
to
achieve:

(A) To have a way for the MGC to "hint" to the MG that it wants silence
suppression to be used or not.

(B) To have a way for the two MGs to negotiate whether silence =
suppression
should be used or not.  If one of the MGs cannot support silence
suppression, then the peer-MG must not send silence-packets, regardless =
of
what the "hint" from the MGC was.

For (B), the SDP exchange between MGs is used to negotiate silence
suppression capability.  For G.711, payload-type 13 on the media line =
of the
returned Local descriptor is typically used to indicate a MG's ability =
to do
silence suppression.

Now, whatever method is chosen for (A) should not conflict with what is
currently done for (B), especially if the underspecified Local =
descriptor
from MGC to MG is used to convey the "hint" from the MGC.

Dave.

-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 1:53 PM
To: Carl Rutter; 'Pauls Markus'; 'megaco@ietf.org'
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


One more comment,=20
sorry for so many.
Would be really need to specify the 13
if we had the SilSup parameter?

Carl
-----Original Message-----
From: Carl Rutter=20
Sent: Wednesday, April 03, 2002 7:52 AM
To: 'Pauls Markus'; megaco@ietf.org
Cc: Carl Rutter
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Yea, for overspecification I see your point.

m=3Daudio 4444 RTP/AVP 0 18 13
a=3Dfmtp:18 annexb=3Dno
a=3Dfmtp:0 silSup=3Dyes
makes sense,=20
but still seems kind of awkward in that
we have different ways of implementing Silent Suppression
based on the payload.

It would be nice to have a common parameter among the payloads
that had more than just an ON/OFF option to provide future flexibility
like they thought of in RFC3018:
silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse>=20
                   <fxnslevel>=20
So from the discussions I've read, Silent Suppression should:
1) Be implemented in SDP=20
2) Enabled/Disabled on a per payload type
3) Should have more than just and On/Off option
4) Be backward compatable to allow support for the Annex option=20
   with the compressed vocoders
5) Be consistant among Payload types

I guess if we gave up on #3 and #5 we could implement Pauls suggestion.
Not sure the logistics of how thats done??

Are we getting close?

Carl


-----Original Message-----
From: Pauls Markus [mailto:Markus.Pauls@icn.siemens.de]
Sent: Wednesday, April 03, 2002 2:49 AM
To: megaco@ietf.org
Cc: 'Carl Rutter'
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Suppose you have the following SDP:

m=3Daudio 4444 RTP/AVP 0 18
a=3Dfmtp:18 annexb=3Dno         // G.729, Silence Suppression off (see
draft-ietf-avt-rtp-mime-05)
a=3DsilenceSupp: on - - - -

(that means the GW may either use G.711 =B5-law or G.729)

The silenceSupp attribute is not specific for a payload type, the fmtp
attribute is. So which one has precedence in this case?

In my opinion you should have the ability to switch on silence =
suppression
depending on the payload type. If you want to use it with G.711, it =
does not
mean that you want it with G.729.

Beyond that I believe generally it is more suited to an ephemeral
termination. Therefore it should be expressed by means of SDP.

However, if you want to transport the comfort noise payload (according =
to
draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the =
SDP
media line as well (IMO).

From my point of view the SDP should therefore look something like =
this:

m=3Daudio 4444 RTP/AVP 0 18 13
a=3Dfmtp:18 annexb=3Dno
a=3Dfmtp:0 silSup=3Dyes

where this PCMU specific parameter silSup must still be defined (for =
PCMA as
well).

Any comment is appreciated.


	Kind regards

		Markus Pauls


________________________________________________________
Markus Pauls

SIEMENS
Information and Communication Networks

ICN WN CC NA B13   	Tel.:  	+49 89 722 62937
Hofmannstr. 51     	Fax:   	+49 89 722 44176
81359 Munich        	Email: 	markus.pauls@icn.siemens.de
Germany




-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 3:36 AM
To: Chuong N. Nguyen
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent =
terminations


You bring up a good point,=20
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more =
sense to
be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach =
for
SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
Sent: Tuesday, April 02, 2002 8:05 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent =
terminations


 =20
That is what  I initially thought silence suppression was about.=20
But then I was told differently.=20
It could be applied to TDM.=20
If not, then why are we discussing adding silence suppresion to the TDM
package?=20
 =20
By the way,  I thought TDM-TDM calls are being made at the Gwy too.=20
Aren't you guys doing that now?=20
 =20
 =20
Carl Rutter wrote:=20
I can't think of an application where you'd want to do that. Silence
suppression really wouldn't make sense for a TDM-TDMwhich is hairpined =
at
the CO. The DS0 is dedicated. The advantage of Silent suppression it to
limit the RTP traffic on the IP side, which you wouldn't have in that
case.Maybe if you wanted to inject Comfort Noise instead of =
backgroundnoice
in the TDM-TDM call??Carl=20
-----Original Message-----=20
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen=20
Sent: Tuesday, April 02, 2002 7:16 PM=20
To: megaco@ietf.org=20
Subject: Re: [Megaco] Local/Remote descriptors and Permanent =
terminations
Tom-PT Taylor wrote:=20
I've had a message pointing out the existence of=20
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as =
G.711

would indicate the use of silence suppression implicitly.  That covers =
RTP=20
transport.  For ATM we have the a=3DsilenceSupp attribute defined in =
RFC 3108.

Do we need anything for TDM?

What if someone wanted to make a TDM-TDM, hairpin call?=20
Would silenceSupp be used for such a call?=20
If yes, then what?=20
 =20
 =20
--=20
  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 ****=20
--=20
  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 **** =20

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

------_=_NextPart_001_01C1DB16.C91F491E
Content-Type: text/html;
	charset="windows-1252"
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-1252">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Megaco] Local/Remote descriptors and Permanent =
terminations</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>In making a decision please consider the =
following:</FONT>
</P>

<P><FONT SIZE=3D2>With silence suppression, there are actually 2 =
separate things we need to achieve:</FONT>
</P>

<P><FONT SIZE=3D2>(A) To have a way for the MGC to &quot;hint&quot; to =
the MG that it wants silence suppression to be used or not.</FONT>
</P>

<P><FONT SIZE=3D2>(B) To have a way for the two MGs to negotiate =
whether silence suppression should be used or not.&nbsp; If one of the =
MGs cannot support silence suppression, then the peer-MG must not send =
silence-packets, regardless of what the &quot;hint&quot; from the MGC =
was.</FONT></P>

<P><FONT SIZE=3D2>For (B), the SDP exchange between MGs is used to =
negotiate silence suppression capability.&nbsp; For G.711, payload-type =
13 on the media line of the returned Local descriptor is typically used =
to indicate a MG's ability to do silence suppression.</FONT></P>

<P><FONT SIZE=3D2>Now, whatever method is chosen for (A) should not =
conflict with what is currently done for (B), especially if the =
underspecified Local descriptor from MGC to MG is used to convey the =
&quot;hint&quot; from the MGC.</FONT></P>

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Carl Rutter [<A =
HREF=3D"mailto:crutter@telica.com">mailto:crutter@telica.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Wednesday, April 03, 2002 1:53 PM</FONT>
<BR><FONT SIZE=3D2>To: Carl Rutter; 'Pauls Markus'; =
'megaco@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Local/Remote descriptors and =
Permanent</FONT>
<BR><FONT SIZE=3D2>terminations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>One more comment, </FONT>
<BR><FONT SIZE=3D2>sorry for so many.</FONT>
<BR><FONT SIZE=3D2>Would be really need to specify the 13</FONT>
<BR><FONT SIZE=3D2>if we had the SilSup parameter?</FONT>
</P>

<P><FONT SIZE=3D2>Carl</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Carl Rutter </FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, April 03, 2002 7:52 AM</FONT>
<BR><FONT SIZE=3D2>To: 'Pauls Markus'; megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Cc: Carl Rutter</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Local/Remote descriptors and =
Permanent</FONT>
<BR><FONT SIZE=3D2>terminations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Yea, for overspecification I see your point.</FONT>
</P>

<P><FONT SIZE=3D2>m=3Daudio 4444 RTP/AVP 0 18 13</FONT>
<BR><FONT SIZE=3D2>a=3Dfmtp:18 annexb=3Dno</FONT>
<BR><FONT SIZE=3D2>a=3Dfmtp:0 silSup=3Dyes</FONT>
<BR><FONT SIZE=3D2>makes sense, </FONT>
<BR><FONT SIZE=3D2>but still seems kind of awkward in that</FONT>
<BR><FONT SIZE=3D2>we have different ways of implementing Silent =
Suppression</FONT>
<BR><FONT SIZE=3D2>based on the payload.</FONT>
</P>

<P><FONT SIZE=3D2>It would be nice to have a common parameter among the =
payloads</FONT>
<BR><FONT SIZE=3D2>that had more than just an ON/OFF option to provide =
future flexibility</FONT>
<BR><FONT SIZE=3D2>like they thought of in RFC3018:</FONT>
<BR><FONT SIZE=3D2>silenceSupp: &lt;silenceSuppEnable&gt; =
&lt;silenceTimer&gt; &lt;suppPref&gt; &lt;sidUse&gt; </FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;fxnslevel&gt; </FONT>
<BR><FONT SIZE=3D2>So from the discussions I've read, Silent =
Suppression should:</FONT>
<BR><FONT SIZE=3D2>1) Be implemented in SDP </FONT>
<BR><FONT SIZE=3D2>2) Enabled/Disabled on a per payload type</FONT>
<BR><FONT SIZE=3D2>3) Should have more than just and On/Off option</FONT=
>
<BR><FONT SIZE=3D2>4) Be backward compatable to allow support for the =
Annex option </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; with the compressed vocoders</FONT>
<BR><FONT SIZE=3D2>5) Be consistant among Payload types</FONT>
</P>

<P><FONT SIZE=3D2>I guess if we gave up on #3 and #5 we could implement =
Pauls suggestion.</FONT>
<BR><FONT SIZE=3D2>Not sure the logistics of how thats done??</FONT>
</P>

<P><FONT SIZE=3D2>Are we getting close?</FONT>
</P>

<P><FONT SIZE=3D2>Carl</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Pauls Markus [<A =
HREF=3D"mailto:Markus.Pauls@icn.siemens.de">mailto:Markus.Pauls@icn.siem=
ens.de</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, April 03, 2002 2:49 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Cc: 'Carl Rutter'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Local/Remote descriptors and =
Permanent</FONT>
<BR><FONT SIZE=3D2>terminations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Suppose you have the following SDP:</FONT>
</P>

<P><FONT SIZE=3D2>m=3Daudio 4444 RTP/AVP 0 18</FONT>
<BR><FONT SIZE=3D2>a=3Dfmtp:18 =
annexb=3Dno&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // G.729, =
Silence Suppression off (see</FONT>
<BR><FONT SIZE=3D2>draft-ietf-avt-rtp-mime-05)</FONT>
<BR><FONT SIZE=3D2>a=3DsilenceSupp: on - - - -</FONT>
</P>

<P><FONT SIZE=3D2>(that means the GW may either use G.711 =B5-law or =
G.729)</FONT>
</P>

<P><FONT SIZE=3D2>The silenceSupp attribute is not specific for a =
payload type, the fmtp</FONT>
<BR><FONT SIZE=3D2>attribute is. So which one has precedence in this =
case?</FONT>
</P>

<P><FONT SIZE=3D2>In my opinion you should have the ability to switch =
on silence suppression</FONT>
<BR><FONT SIZE=3D2>depending on the payload type. If you want to use it =
with G.711, it does not</FONT>
<BR><FONT SIZE=3D2>mean that you want it with G.729.</FONT>
</P>

<P><FONT SIZE=3D2>Beyond that I believe generally it is more suited to =
an ephemeral</FONT>
<BR><FONT SIZE=3D2>termination. Therefore it should be expressed by =
means of SDP.</FONT>
</P>

<P><FONT SIZE=3D2>However, if you want to transport the comfort noise =
payload (according to</FONT>
<BR><FONT SIZE=3D2>draft-ietf-avt-rtp-cn-05), you should add the =
payload type 13 to the SDP</FONT>
<BR><FONT SIZE=3D2>media line as well (IMO).</FONT>
</P>

<P><FONT SIZE=3D2>From my point of view the SDP should therefore look =
something like this:</FONT>
</P>

<P><FONT SIZE=3D2>m=3Daudio 4444 RTP/AVP 0 18 13</FONT>
<BR><FONT SIZE=3D2>a=3Dfmtp:18 annexb=3Dno</FONT>
<BR><FONT SIZE=3D2>a=3Dfmtp:0 silSup=3Dyes</FONT>
</P>

<P><FONT SIZE=3D2>where this PCMU specific parameter silSup must still =
be defined (for PCMA as</FONT>
<BR><FONT SIZE=3D2>well).</FONT>
</P>

<P><FONT SIZE=3D2>Any comment is appreciated.</FONT>
</P>
<BR>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Kind =
regards</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Markus =
Pauls</FONT>
</P>
<BR>

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

<BR><FONT SIZE=3D2>Markus Pauls</FONT>
</P>

<P><FONT SIZE=3D2>SIEMENS</FONT>
<BR><FONT SIZE=3D2>Information and Communication Networks</FONT>
</P>

<P><FONT SIZE=3D2>ICN WN CC NA B13&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; =
Tel.:&nbsp;&nbsp; +49 89 722 62937</FONT>
<BR><FONT SIZE=3D2>Hofmannstr. 51&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp; Fax:&nbsp;&nbsp;&nbsp; +49 89 722 44176</FONT>
<BR><FONT SIZE=3D2>81359 =
Munich&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
Email:&nbsp; markus.pauls@icn.siemens.de</FONT>
<BR><FONT SIZE=3D2>Germany</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Carl Rutter [<A =
HREF=3D"mailto:crutter@telica.com">mailto:crutter@telica.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Wednesday, April 03, 2002 3:36 AM</FONT>
<BR><FONT SIZE=3D2>To: Chuong N. Nguyen</FONT>
<BR><FONT SIZE=3D2>Cc: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Local/Remote descriptors and =
Permanent terminations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>You bring up a good point, </FONT>
<BR><FONT SIZE=3D2>Is/Should Silient Suppression be tied to the TDM =
package or</FONT>
<BR><FONT SIZE=3D2>SDP TDM, if in fact its really more applicable to =
the Ephemral side.</FONT>
<BR><FONT SIZE=3D2>If no can think of a good reason then your right it =
would make more sense to</FONT>
<BR><FONT SIZE=3D2>be in the SDP.</FONT>
<BR><FONT SIZE=3D2>For now we could use 0 13 for G711 and long-term use =
the ATM approach for</FONT>
<BR><FONT SIZE=3D2>SDP.</FONT>
<BR><FONT SIZE=3D2>Trying to drive towards closure as we have a need to =
implement this.</FONT>
<BR><FONT SIZE=3D2>Yea, the hairpinning would be in the MG =
Switch.</FONT>
<BR><FONT SIZE=3D2>Comments?</FONT>
</P>

<P><FONT SIZE=3D2>Carl</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: megaco-admin@ietf.org [<A =
HREF=3D"mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]O=
n Behalf Of</FONT>
<BR><FONT SIZE=3D2>Chuong N. Nguyen</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, April 02, 2002 8:05 PM</FONT>
<BR><FONT SIZE=3D2>Cc: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] Local/Remote descriptors and =
Permanent terminations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>That is what&nbsp; I initially thought silence =
suppression was about. </FONT>
<BR><FONT SIZE=3D2>But then I was told differently. </FONT>
<BR><FONT SIZE=3D2>It could be applied to TDM. </FONT>
<BR><FONT SIZE=3D2>If not, then why are we discussing adding silence =
suppresion to the TDM</FONT>
<BR><FONT SIZE=3D2>package? </FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>By the way,&nbsp; I thought TDM-TDM calls are being =
made at the Gwy too. </FONT>
<BR><FONT SIZE=3D2>Aren't you guys doing that now? </FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>Carl Rutter wrote: </FONT>
<BR><FONT SIZE=3D2>I can't think of an application where you'd want to =
do that. Silence</FONT>
<BR><FONT SIZE=3D2>suppression really wouldn't make sense for a =
TDM-TDMwhich is hairpined at</FONT>
<BR><FONT SIZE=3D2>the CO. The DS0 is dedicated. The advantage of =
Silent suppression it to</FONT>
<BR><FONT SIZE=3D2>limit the RTP traffic on the IP side, which you =
wouldn't have in that</FONT>
<BR><FONT SIZE=3D2>case.Maybe if you wanted to inject Comfort Noise =
instead of backgroundnoice</FONT>
<BR><FONT SIZE=3D2>in the TDM-TDM call??Carl </FONT>
<BR><FONT SIZE=3D2>-----Original Message----- </FONT>
<BR><FONT SIZE=3D2>From: megaco-admin@ietf.org [<A =
HREF=3D"mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]O=
n Behalf Of</FONT>
<BR><FONT SIZE=3D2>Chuong N. Nguyen </FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, April 02, 2002 7:16 PM </FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org </FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] Local/Remote descriptors and =
Permanent terminations</FONT>
<BR><FONT SIZE=3D2>Tom-PT Taylor wrote: </FONT>
<BR><FONT SIZE=3D2>I've had a message pointing out the existence of =
</FONT>
<BR><FONT SIZE=3D2>draft-ietf-avt-rtp-cn-05.txt.&nbsp; Specifying this =
payload type as well as G.711</FONT>
</P>

<P><FONT SIZE=3D2>would indicate the use of silence suppression =
implicitly.&nbsp; That covers RTP </FONT>
<BR><FONT SIZE=3D2>transport.&nbsp; For ATM we have the a=3DsilenceSupp =
attribute defined in RFC 3108.</FONT>
</P>

<P><FONT SIZE=3D2>Do we need anything for TDM?</FONT>
</P>

<P><FONT SIZE=3D2>What if someone wanted to make a TDM-TDM, hairpin =
call? </FONT>
<BR><FONT SIZE=3D2>Would silenceSupp be used for such a call? </FONT>
<BR><FONT SIZE=3D2>If yes, then what? </FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Internet: Chuong.Nguyen@usa.alcatel.com</FONT>
<BR><FONT SIZE=3D2>&nbsp; 1000 Coit Road Plano, Texas =
75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613</FONT>
<BR><FONT SIZE=3D2>&nbsp; **** The opinions expressed are not those of =
Alcatel USA, Inc **** </FONT>
<BR><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Internet: Chuong.Nguyen@usa.alcatel.com</FONT>
<BR><FONT SIZE=3D2>&nbsp; 1000 Coit Road Plano, Texas =
75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613</FONT>
<BR><FONT SIZE=3D2>&nbsp; **** The opinions expressed are not those of =
Alcatel USA, Inc ****&nbsp; </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_01C1DB16.C91F491E--

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


From daemon@ns.ietf.org  Wed Apr  3 09:19: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 JAA03912
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 09:19:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA26586
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 09:19: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 IAA24905;
	Wed, 3 Apr 2002 08:53: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 IAA24789
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 08:52:58 -0500 (EST)
Received: from zctfs063.nortelnetworks.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03209
	for <megaco@ietf.org>; Wed, 3 Apr 2002 08:52:49 -0500 (EST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g33DqKv16702;
	Wed, 3 Apr 2002 15:52:20 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g33DpjJ07274;
	Wed, 3 Apr 2002 14:51:45 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <HLDBCBZD>; Wed, 3 Apr 2002 14:52:26 +0100
Message-ID: <4103264BC8D3D51180B7002048400C4502F281@zhard0jd.europe.nortel.com>
From: "David Barr"<david.barr@nortelnetworks.com>
To: "'Carl Rutter'" <crutter@telica.com>,
        "'Pauls Markus'"
	 <Markus.Pauls@icn.siemens.de>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
Date: Wed, 3 Apr 2002 14:52:25 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DB16.C91F491E"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1DB16.C91F491E
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: quoted-printable

In making a decision please consider the following:

With silence suppression, there are actually 2 separate things we need =
to
achieve:

(A) To have a way for the MGC to "hint" to the MG that it wants silence
suppression to be used or not.

(B) To have a way for the two MGs to negotiate whether silence =
suppression
should be used or not.  If one of the MGs cannot support silence
suppression, then the peer-MG must not send silence-packets, regardless =
of
what the "hint" from the MGC was.

For (B), the SDP exchange between MGs is used to negotiate silence
suppression capability.  For G.711, payload-type 13 on the media line =
of the
returned Local descriptor is typically used to indicate a MG's ability =
to do
silence suppression.

Now, whatever method is chosen for (A) should not conflict with what is
currently done for (B), especially if the underspecified Local =
descriptor
from MGC to MG is used to convey the "hint" from the MGC.

Dave.

-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 1:53 PM
To: Carl Rutter; 'Pauls Markus'; 'megaco@ietf.org'
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


One more comment,=20
sorry for so many.
Would be really need to specify the 13
if we had the SilSup parameter?

Carl
-----Original Message-----
From: Carl Rutter=20
Sent: Wednesday, April 03, 2002 7:52 AM
To: 'Pauls Markus'; megaco@ietf.org
Cc: Carl Rutter
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Yea, for overspecification I see your point.

m=3Daudio 4444 RTP/AVP 0 18 13
a=3Dfmtp:18 annexb=3Dno
a=3Dfmtp:0 silSup=3Dyes
makes sense,=20
but still seems kind of awkward in that
we have different ways of implementing Silent Suppression
based on the payload.

It would be nice to have a common parameter among the payloads
that had more than just an ON/OFF option to provide future flexibility
like they thought of in RFC3018:
silenceSupp: <silenceSuppEnable> <silenceTimer> <suppPref> <sidUse>=20
                   <fxnslevel>=20
So from the discussions I've read, Silent Suppression should:
1) Be implemented in SDP=20
2) Enabled/Disabled on a per payload type
3) Should have more than just and On/Off option
4) Be backward compatable to allow support for the Annex option=20
   with the compressed vocoders
5) Be consistant among Payload types

I guess if we gave up on #3 and #5 we could implement Pauls suggestion.
Not sure the logistics of how thats done??

Are we getting close?

Carl


-----Original Message-----
From: Pauls Markus [mailto:Markus.Pauls@icn.siemens.de]
Sent: Wednesday, April 03, 2002 2:49 AM
To: megaco@ietf.org
Cc: 'Carl Rutter'
Subject: RE: [Megaco] Local/Remote descriptors and Permanent
terminations


Suppose you have the following SDP:

m=3Daudio 4444 RTP/AVP 0 18
a=3Dfmtp:18 annexb=3Dno         // G.729, Silence Suppression off (see
draft-ietf-avt-rtp-mime-05)
a=3DsilenceSupp: on - - - -

(that means the GW may either use G.711 =B5-law or G.729)

The silenceSupp attribute is not specific for a payload type, the fmtp
attribute is. So which one has precedence in this case?

In my opinion you should have the ability to switch on silence =
suppression
depending on the payload type. If you want to use it with G.711, it =
does not
mean that you want it with G.729.

Beyond that I believe generally it is more suited to an ephemeral
termination. Therefore it should be expressed by means of SDP.

However, if you want to transport the comfort noise payload (according =
to
draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the =
SDP
media line as well (IMO).

From my point of view the SDP should therefore look something like =
this:

m=3Daudio 4444 RTP/AVP 0 18 13
a=3Dfmtp:18 annexb=3Dno
a=3Dfmtp:0 silSup=3Dyes

where this PCMU specific parameter silSup must still be defined (for =
PCMA as
well).

Any comment is appreciated.


	Kind regards

		Markus Pauls


________________________________________________________
Markus Pauls

SIEMENS
Information and Communication Networks

ICN WN CC NA B13   	Tel.:  	+49 89 722 62937
Hofmannstr. 51     	Fax:   	+49 89 722 44176
81359 Munich        	Email: 	markus.pauls@icn.siemens.de
Germany




-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Wednesday, April 03, 2002 3:36 AM
To: Chuong N. Nguyen
Cc: megaco@ietf.org
Subject: RE: [Megaco] Local/Remote descriptors and Permanent =
terminations


You bring up a good point,=20
Is/Should Silient Suppression be tied to the TDM package or
SDP TDM, if in fact its really more applicable to the Ephemral side.
If no can think of a good reason then your right it would make more =
sense to
be in the SDP.
For now we could use 0 13 for G711 and long-term use the ATM approach =
for
SDP.
Trying to drive towards closure as we have a need to implement this.
Yea, the hairpinning would be in the MG Switch.
Comments?

Carl
-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen
Sent: Tuesday, April 02, 2002 8:05 PM
Cc: megaco@ietf.org
Subject: Re: [Megaco] Local/Remote descriptors and Permanent =
terminations


 =20
That is what  I initially thought silence suppression was about.=20
But then I was told differently.=20
It could be applied to TDM.=20
If not, then why are we discussing adding silence suppresion to the TDM
package?=20
 =20
By the way,  I thought TDM-TDM calls are being made at the Gwy too.=20
Aren't you guys doing that now?=20
 =20
 =20
Carl Rutter wrote:=20
I can't think of an application where you'd want to do that. Silence
suppression really wouldn't make sense for a TDM-TDMwhich is hairpined =
at
the CO. The DS0 is dedicated. The advantage of Silent suppression it to
limit the RTP traffic on the IP side, which you wouldn't have in that
case.Maybe if you wanted to inject Comfort Noise instead of =
backgroundnoice
in the TDM-TDM call??Carl=20
-----Original Message-----=20
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Chuong N. Nguyen=20
Sent: Tuesday, April 02, 2002 7:16 PM=20
To: megaco@ietf.org=20
Subject: Re: [Megaco] Local/Remote descriptors and Permanent =
terminations
Tom-PT Taylor wrote:=20
I've had a message pointing out the existence of=20
draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as =
G.711

would indicate the use of silence suppression implicitly.  That covers =
RTP=20
transport.  For ATM we have the a=3DsilenceSupp attribute defined in =
RFC 3108.

Do we need anything for TDM?

What if someone wanted to make a TDM-TDM, hairpin call?=20
Would silenceSupp be used for such a call?=20
If yes, then what?=20
 =20
 =20
--=20
  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 ****=20
--=20
  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 **** =20

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

------_=_NextPart_001_01C1DB16.C91F491E
Content-Type: text/html;
	charset="windows-1252"
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-1252">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Megaco] Local/Remote descriptors and Permanent =
terminations</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>In making a decision please consider the =
following:</FONT>
</P>

<P><FONT SIZE=3D2>With silence suppression, there are actually 2 =
separate things we need to achieve:</FONT>
</P>

<P><FONT SIZE=3D2>(A) To have a way for the MGC to &quot;hint&quot; to =
the MG that it wants silence suppression to be used or not.</FONT>
</P>

<P><FONT SIZE=3D2>(B) To have a way for the two MGs to negotiate =
whether silence suppression should be used or not.&nbsp; If one of the =
MGs cannot support silence suppression, then the peer-MG must not send =
silence-packets, regardless of what the &quot;hint&quot; from the MGC =
was.</FONT></P>

<P><FONT SIZE=3D2>For (B), the SDP exchange between MGs is used to =
negotiate silence suppression capability.&nbsp; For G.711, payload-type =
13 on the media line of the returned Local descriptor is typically used =
to indicate a MG's ability to do silence suppression.</FONT></P>

<P><FONT SIZE=3D2>Now, whatever method is chosen for (A) should not =
conflict with what is currently done for (B), especially if the =
underspecified Local descriptor from MGC to MG is used to convey the =
&quot;hint&quot; from the MGC.</FONT></P>

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Carl Rutter [<A =
HREF=3D"mailto:crutter@telica.com">mailto:crutter@telica.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Wednesday, April 03, 2002 1:53 PM</FONT>
<BR><FONT SIZE=3D2>To: Carl Rutter; 'Pauls Markus'; =
'megaco@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Local/Remote descriptors and =
Permanent</FONT>
<BR><FONT SIZE=3D2>terminations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>One more comment, </FONT>
<BR><FONT SIZE=3D2>sorry for so many.</FONT>
<BR><FONT SIZE=3D2>Would be really need to specify the 13</FONT>
<BR><FONT SIZE=3D2>if we had the SilSup parameter?</FONT>
</P>

<P><FONT SIZE=3D2>Carl</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Carl Rutter </FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, April 03, 2002 7:52 AM</FONT>
<BR><FONT SIZE=3D2>To: 'Pauls Markus'; megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Cc: Carl Rutter</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Local/Remote descriptors and =
Permanent</FONT>
<BR><FONT SIZE=3D2>terminations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Yea, for overspecification I see your point.</FONT>
</P>

<P><FONT SIZE=3D2>m=3Daudio 4444 RTP/AVP 0 18 13</FONT>
<BR><FONT SIZE=3D2>a=3Dfmtp:18 annexb=3Dno</FONT>
<BR><FONT SIZE=3D2>a=3Dfmtp:0 silSup=3Dyes</FONT>
<BR><FONT SIZE=3D2>makes sense, </FONT>
<BR><FONT SIZE=3D2>but still seems kind of awkward in that</FONT>
<BR><FONT SIZE=3D2>we have different ways of implementing Silent =
Suppression</FONT>
<BR><FONT SIZE=3D2>based on the payload.</FONT>
</P>

<P><FONT SIZE=3D2>It would be nice to have a common parameter among the =
payloads</FONT>
<BR><FONT SIZE=3D2>that had more than just an ON/OFF option to provide =
future flexibility</FONT>
<BR><FONT SIZE=3D2>like they thought of in RFC3018:</FONT>
<BR><FONT SIZE=3D2>silenceSupp: &lt;silenceSuppEnable&gt; =
&lt;silenceTimer&gt; &lt;suppPref&gt; &lt;sidUse&gt; </FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;fxnslevel&gt; </FONT>
<BR><FONT SIZE=3D2>So from the discussions I've read, Silent =
Suppression should:</FONT>
<BR><FONT SIZE=3D2>1) Be implemented in SDP </FONT>
<BR><FONT SIZE=3D2>2) Enabled/Disabled on a per payload type</FONT>
<BR><FONT SIZE=3D2>3) Should have more than just and On/Off option</FONT=
>
<BR><FONT SIZE=3D2>4) Be backward compatable to allow support for the =
Annex option </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; with the compressed vocoders</FONT>
<BR><FONT SIZE=3D2>5) Be consistant among Payload types</FONT>
</P>

<P><FONT SIZE=3D2>I guess if we gave up on #3 and #5 we could implement =
Pauls suggestion.</FONT>
<BR><FONT SIZE=3D2>Not sure the logistics of how thats done??</FONT>
</P>

<P><FONT SIZE=3D2>Are we getting close?</FONT>
</P>

<P><FONT SIZE=3D2>Carl</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Pauls Markus [<A =
HREF=3D"mailto:Markus.Pauls@icn.siemens.de">mailto:Markus.Pauls@icn.siem=
ens.de</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, April 03, 2002 2:49 AM</FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Cc: 'Carl Rutter'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Local/Remote descriptors and =
Permanent</FONT>
<BR><FONT SIZE=3D2>terminations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Suppose you have the following SDP:</FONT>
</P>

<P><FONT SIZE=3D2>m=3Daudio 4444 RTP/AVP 0 18</FONT>
<BR><FONT SIZE=3D2>a=3Dfmtp:18 =
annexb=3Dno&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // G.729, =
Silence Suppression off (see</FONT>
<BR><FONT SIZE=3D2>draft-ietf-avt-rtp-mime-05)</FONT>
<BR><FONT SIZE=3D2>a=3DsilenceSupp: on - - - -</FONT>
</P>

<P><FONT SIZE=3D2>(that means the GW may either use G.711 =B5-law or =
G.729)</FONT>
</P>

<P><FONT SIZE=3D2>The silenceSupp attribute is not specific for a =
payload type, the fmtp</FONT>
<BR><FONT SIZE=3D2>attribute is. So which one has precedence in this =
case?</FONT>
</P>

<P><FONT SIZE=3D2>In my opinion you should have the ability to switch =
on silence suppression</FONT>
<BR><FONT SIZE=3D2>depending on the payload type. If you want to use it =
with G.711, it does not</FONT>
<BR><FONT SIZE=3D2>mean that you want it with G.729.</FONT>
</P>

<P><FONT SIZE=3D2>Beyond that I believe generally it is more suited to =
an ephemeral</FONT>
<BR><FONT SIZE=3D2>termination. Therefore it should be expressed by =
means of SDP.</FONT>
</P>

<P><FONT SIZE=3D2>However, if you want to transport the comfort noise =
payload (according to</FONT>
<BR><FONT SIZE=3D2>draft-ietf-avt-rtp-cn-05), you should add the =
payload type 13 to the SDP</FONT>
<BR><FONT SIZE=3D2>media line as well (IMO).</FONT>
</P>

<P><FONT SIZE=3D2>From my point of view the SDP should therefore look =
something like this:</FONT>
</P>

<P><FONT SIZE=3D2>m=3Daudio 4444 RTP/AVP 0 18 13</FONT>
<BR><FONT SIZE=3D2>a=3Dfmtp:18 annexb=3Dno</FONT>
<BR><FONT SIZE=3D2>a=3Dfmtp:0 silSup=3Dyes</FONT>
</P>

<P><FONT SIZE=3D2>where this PCMU specific parameter silSup must still =
be defined (for PCMA as</FONT>
<BR><FONT SIZE=3D2>well).</FONT>
</P>

<P><FONT SIZE=3D2>Any comment is appreciated.</FONT>
</P>
<BR>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Kind =
regards</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Markus =
Pauls</FONT>
</P>
<BR>

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

<BR><FONT SIZE=3D2>Markus Pauls</FONT>
</P>

<P><FONT SIZE=3D2>SIEMENS</FONT>
<BR><FONT SIZE=3D2>Information and Communication Networks</FONT>
</P>

<P><FONT SIZE=3D2>ICN WN CC NA B13&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; =
Tel.:&nbsp;&nbsp; +49 89 722 62937</FONT>
<BR><FONT SIZE=3D2>Hofmannstr. 51&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp; Fax:&nbsp;&nbsp;&nbsp; +49 89 722 44176</FONT>
<BR><FONT SIZE=3D2>81359 =
Munich&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
Email:&nbsp; markus.pauls@icn.siemens.de</FONT>
<BR><FONT SIZE=3D2>Germany</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Carl Rutter [<A =
HREF=3D"mailto:crutter@telica.com">mailto:crutter@telica.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Wednesday, April 03, 2002 3:36 AM</FONT>
<BR><FONT SIZE=3D2>To: Chuong N. Nguyen</FONT>
<BR><FONT SIZE=3D2>Cc: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Megaco] Local/Remote descriptors and =
Permanent terminations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>You bring up a good point, </FONT>
<BR><FONT SIZE=3D2>Is/Should Silient Suppression be tied to the TDM =
package or</FONT>
<BR><FONT SIZE=3D2>SDP TDM, if in fact its really more applicable to =
the Ephemral side.</FONT>
<BR><FONT SIZE=3D2>If no can think of a good reason then your right it =
would make more sense to</FONT>
<BR><FONT SIZE=3D2>be in the SDP.</FONT>
<BR><FONT SIZE=3D2>For now we could use 0 13 for G711 and long-term use =
the ATM approach for</FONT>
<BR><FONT SIZE=3D2>SDP.</FONT>
<BR><FONT SIZE=3D2>Trying to drive towards closure as we have a need to =
implement this.</FONT>
<BR><FONT SIZE=3D2>Yea, the hairpinning would be in the MG =
Switch.</FONT>
<BR><FONT SIZE=3D2>Comments?</FONT>
</P>

<P><FONT SIZE=3D2>Carl</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: megaco-admin@ietf.org [<A =
HREF=3D"mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]O=
n Behalf Of</FONT>
<BR><FONT SIZE=3D2>Chuong N. Nguyen</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, April 02, 2002 8:05 PM</FONT>
<BR><FONT SIZE=3D2>Cc: megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] Local/Remote descriptors and =
Permanent terminations</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>That is what&nbsp; I initially thought silence =
suppression was about. </FONT>
<BR><FONT SIZE=3D2>But then I was told differently. </FONT>
<BR><FONT SIZE=3D2>It could be applied to TDM. </FONT>
<BR><FONT SIZE=3D2>If not, then why are we discussing adding silence =
suppresion to the TDM</FONT>
<BR><FONT SIZE=3D2>package? </FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>By the way,&nbsp; I thought TDM-TDM calls are being =
made at the Gwy too. </FONT>
<BR><FONT SIZE=3D2>Aren't you guys doing that now? </FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>Carl Rutter wrote: </FONT>
<BR><FONT SIZE=3D2>I can't think of an application where you'd want to =
do that. Silence</FONT>
<BR><FONT SIZE=3D2>suppression really wouldn't make sense for a =
TDM-TDMwhich is hairpined at</FONT>
<BR><FONT SIZE=3D2>the CO. The DS0 is dedicated. The advantage of =
Silent suppression it to</FONT>
<BR><FONT SIZE=3D2>limit the RTP traffic on the IP side, which you =
wouldn't have in that</FONT>
<BR><FONT SIZE=3D2>case.Maybe if you wanted to inject Comfort Noise =
instead of backgroundnoice</FONT>
<BR><FONT SIZE=3D2>in the TDM-TDM call??Carl </FONT>
<BR><FONT SIZE=3D2>-----Original Message----- </FONT>
<BR><FONT SIZE=3D2>From: megaco-admin@ietf.org [<A =
HREF=3D"mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</A>]O=
n Behalf Of</FONT>
<BR><FONT SIZE=3D2>Chuong N. Nguyen </FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, April 02, 2002 7:16 PM </FONT>
<BR><FONT SIZE=3D2>To: megaco@ietf.org </FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Megaco] Local/Remote descriptors and =
Permanent terminations</FONT>
<BR><FONT SIZE=3D2>Tom-PT Taylor wrote: </FONT>
<BR><FONT SIZE=3D2>I've had a message pointing out the existence of =
</FONT>
<BR><FONT SIZE=3D2>draft-ietf-avt-rtp-cn-05.txt.&nbsp; Specifying this =
payload type as well as G.711</FONT>
</P>

<P><FONT SIZE=3D2>would indicate the use of silence suppression =
implicitly.&nbsp; That covers RTP </FONT>
<BR><FONT SIZE=3D2>transport.&nbsp; For ATM we have the a=3DsilenceSupp =
attribute defined in RFC 3108.</FONT>
</P>

<P><FONT SIZE=3D2>Do we need anything for TDM?</FONT>
</P>

<P><FONT SIZE=3D2>What if someone wanted to make a TDM-TDM, hairpin =
call? </FONT>
<BR><FONT SIZE=3D2>Would silenceSupp be used for such a call? </FONT>
<BR><FONT SIZE=3D2>If yes, then what? </FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp; </FONT>
<BR><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Internet: Chuong.Nguyen@usa.alcatel.com</FONT>
<BR><FONT SIZE=3D2>&nbsp; 1000 Coit Road Plano, Texas =
75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613</FONT>
<BR><FONT SIZE=3D2>&nbsp; **** The opinions expressed are not those of =
Alcatel USA, Inc **** </FONT>
<BR><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>&nbsp; Alcatel USA, =
Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; Internet: Chuong.Nguyen@usa.alcatel.com</FONT>
<BR><FONT SIZE=3D2>&nbsp; 1000 Coit Road Plano, Texas =
75075&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Phone:&nbsp;&nbsp;&nbsp; (972) 519-4613</FONT>
<BR><FONT SIZE=3D2>&nbsp; **** The opinions expressed are not those of =
Alcatel USA, Inc ****&nbsp; </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_01C1DB16.C91F491E--

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



From megaco-admin@ietf.org  Wed Apr  3 10:05: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 KAA05167
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 10:05: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 JAA28064;
	Wed, 3 Apr 2002 09:39: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 JAA28035
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 09:39:04 -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 JAA04444
	for <megaco@ietf.org>; Wed, 3 Apr 2002 09:38:59 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g33EbvD13899;
	Wed, 3 Apr 2002 09:37:58 -0500 (EST)
Received: from lucent.com (tla.lra.lucent.com [192.11.62.65])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA21882;
	Wed, 3 Apr 2002 09:38:40 -0500 (EST)
Message-ID: <3CAB13B0.5B7B5284@lucent.com>
Date: Wed, 03 Apr 2002 09:37:36 -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: "'Pauls Markus'" <Markus.Pauls@icn.siemens.de>, megaco@ietf.org,
        "'Carl Rutter'" <crutter@telica.com>,
        "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        "'Stephen Casner'" <casner@acm.org>
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <4D79C746863DD51197690002A52CDA0001E8A23F@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------AE44D80F31F7B735404D2940"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------AE44D80F31F7B735404D2940
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

just to be clear about the options, I do not believe that the comfort noise
draft alone provides a solution.  The payload provides a way to specify the
nature of the comfort noise to be used when silence suppression is in use, but
its absence is not intended to imply that silence suppression should not occur
(just that no comfort noise is played).  We would still need one of the other
ways to indicate that silence suppression should be turned off.

Tom-PT Taylor wrote:

> [Stephen Casner copied because this potentially affects AVT WG work in
> progress.]
>
> To summarize: we are trying to define how to indicate that silence
> suppression is desired for a given audio flow.  We could do it through an
> a=silenceSupp attribute, through codec-specific a=fmtp: parameters, or
> implicitly by specifying the Comfort Noise codec as an alternative.  Markus
> shows the sort of contradictions we could arrive at if we are not careful.
>
> I think it's quite clear that we do NOT want to tie silence suppression to
> the TDM package.
>
> The cleanest way would be to ensure that every codec where silence
> suppression might apply has a silence suppression parameter.  For RTP, this
> requires revisiting draft-ietf-avt-rtp-mime-06.txt, which is currently in
> IETF Last Call.  Not sure what we do about ATM: RFC 3108 defines a profile
> that just picks up the RTP mappings, so maybe it would also pick up the
> parameters defined in the MIME type registrations and payload format
> descriptions.  I find this whole area murky because theoretically there
> should be new MIME type registrations for each transport in order to reuse
> the profiles in SDP.
>
> A second possibility is to define the a=silenceSupp attribute for all
> transports, but specify that it takes second priority to a=fmtp parameters
> where these are defined.  This is probably the most practical route.
>
> Stephen, any comments?
>
> -----Original Message-----
> From: Pauls Markus [mailto:Markus.Pauls@icn.siemens.de]
> Sent: Wednesday, April 03, 2002 2:49 AM
> To: megaco@ietf.org
> Cc: 'Carl Rutter'
> Subject: RE: [Megaco] Local/Remote descriptors and Permanent
> terminations
>
> Suppose you have the following SDP:
>
> m=audio 4444 RTP/AVP 0 18
> a=fmtp:18 annexb=no         // G.729, Silence Suppression off (see
> draft-ietf-avt-rtp-mime-05)
> a=silenceSupp: on - - - -
>
> (that means the GW may either use G.711 µ-law or G.729)
>
> The silenceSupp attribute is not specific for a payload type, the fmtp
> attribute is. So which one has precedence in this case?
>
> In my opinion you should have the ability to switch on silence suppression
> depending on the payload type. If you want to use it with G.711, it does not
> mean that you want it with G.729.
>
> Beyond that I believe generally it is more suited to an ephemeral
> termination. Therefore it should be expressed by means of SDP.
>
> However, if you want to transport the comfort noise payload (according to
> draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP
> media line as well (IMO).
>
> From my point of view the SDP should therefore look something like this:
>
> m=audio 4444 RTP/AVP 0 18 13
> a=fmtp:18 annexb=no
> a=fmtp:0 silSup=yes
>
> where this PCMU specific parameter silSup must still be defined (for PCMA as
> well).
>
> Any comment is appreciated.
>
>         Kind regards
>
>                 Markus Pauls
>
> ________________________________________________________
> Markus Pauls
>
> SIEMENS
> Information and Communication Networks
>
> ICN WN CC NA B13        Tel.:   +49 89 722 62937
> Hofmannstr. 51          Fax:    +49 89 722 44176
> 81359 Munich            Email:  markus.pauls@icn.siemens.de
> Germany
>
> -----Original Message-----
> From: Carl Rutter [mailto:crutter@telica.com]
> Sent: Wednesday, April 03, 2002 3:36 AM
> To: Chuong N. Nguyen
> Cc: megaco@ietf.org
> Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
>
> You bring up a good point,
> Is/Should Silient Suppression be tied to the TDM package or
> SDP TDM, if in fact its really more applicable to the Ephemral side.
> If no can think of a good reason then your right it would make more sense to
> be in the SDP.
> For now we could use 0 13 for G711 and long-term use the ATM approach for
> SDP.
> Trying to drive towards closure as we have a need to implement this.
> Yea, the hairpinning would be in the MG Switch.
> Comments?
>
> Carl
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Chuong N. Nguyen
> Sent: Tuesday, April 02, 2002 8:05 PM
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
>
>
> That is what  I initially thought silence suppression was about.
> But then I was told differently.
> It could be applied to TDM.
> If not, then why are we discussing adding silence suppresion to the TDM
> package?
>
> By the way,  I thought TDM-TDM calls are being made at the Gwy too.
> Aren't you guys doing that now?
>
>
> Carl Rutter wrote:
> I can't think of an application where you'd want to do that. Silence
> suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at
> the CO. The DS0 is dedicated. The advantage of Silent suppression it to
> limit the RTP traffic on the IP side, which you wouldn't have in that
> case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice
> in the TDM-TDM call??Carl
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Chuong N. Nguyen
> Sent: Tuesday, April 02, 2002 7:16 PM
> To: megaco@ietf.org
> Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
> Tom-PT Taylor wrote:
> I've had a message pointing out the existence of
> draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711
>
> would indicate the use of silence suppression implicitly.  That covers RTP
> transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.
>
> Do we need anything for TDM?
>
> What if someone wanted to make a TDM-TDM, hairpin call?
> Would silenceSupp be used for such a call?
> If yes, then what?
>
>
> --
>   Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
>   1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
>   **** The opinions expressed are not those of Alcatel USA, Inc ****
> --
>   Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
>   1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
>   **** The opinions expressed are not those of Alcatel USA, Inc ****
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------AE44D80F31F7B735404D2940
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------AE44D80F31F7B735404D2940--


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


From daemon@ns.ietf.org  Wed Apr  3 10:05: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 KAA05179
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 10:05:12 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA29915
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 10:05: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 JAA28064;
	Wed, 3 Apr 2002 09:39: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 JAA28035
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 09:39:04 -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 JAA04444
	for <megaco@ietf.org>; Wed, 3 Apr 2002 09:38:59 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g33EbvD13899;
	Wed, 3 Apr 2002 09:37:58 -0500 (EST)
Received: from lucent.com (tla.lra.lucent.com [192.11.62.65])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA21882;
	Wed, 3 Apr 2002 09:38:40 -0500 (EST)
Message-ID: <3CAB13B0.5B7B5284@lucent.com>
Date: Wed, 03 Apr 2002 09:37:36 -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: "'Pauls Markus'" <Markus.Pauls@icn.siemens.de>, megaco@ietf.org,
        "'Carl Rutter'" <crutter@telica.com>,
        "'Chuong N. Nguyen'" <Chuong.Nguyen@alcatel.com>,
        "'Stephen Casner'" <casner@acm.org>
Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
References: <4D79C746863DD51197690002A52CDA0001E8A23F@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------AE44D80F31F7B735404D2940"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------AE44D80F31F7B735404D2940
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

just to be clear about the options, I do not believe that the comfort noise
draft alone provides a solution.  The payload provides a way to specify the
nature of the comfort noise to be used when silence suppression is in use, but
its absence is not intended to imply that silence suppression should not occur
(just that no comfort noise is played).  We would still need one of the other
ways to indicate that silence suppression should be turned off.

Tom-PT Taylor wrote:

> [Stephen Casner copied because this potentially affects AVT WG work in
> progress.]
>
> To summarize: we are trying to define how to indicate that silence
> suppression is desired for a given audio flow.  We could do it through an
> a=silenceSupp attribute, through codec-specific a=fmtp: parameters, or
> implicitly by specifying the Comfort Noise codec as an alternative.  Markus
> shows the sort of contradictions we could arrive at if we are not careful.
>
> I think it's quite clear that we do NOT want to tie silence suppression to
> the TDM package.
>
> The cleanest way would be to ensure that every codec where silence
> suppression might apply has a silence suppression parameter.  For RTP, this
> requires revisiting draft-ietf-avt-rtp-mime-06.txt, which is currently in
> IETF Last Call.  Not sure what we do about ATM: RFC 3108 defines a profile
> that just picks up the RTP mappings, so maybe it would also pick up the
> parameters defined in the MIME type registrations and payload format
> descriptions.  I find this whole area murky because theoretically there
> should be new MIME type registrations for each transport in order to reuse
> the profiles in SDP.
>
> A second possibility is to define the a=silenceSupp attribute for all
> transports, but specify that it takes second priority to a=fmtp parameters
> where these are defined.  This is probably the most practical route.
>
> Stephen, any comments?
>
> -----Original Message-----
> From: Pauls Markus [mailto:Markus.Pauls@icn.siemens.de]
> Sent: Wednesday, April 03, 2002 2:49 AM
> To: megaco@ietf.org
> Cc: 'Carl Rutter'
> Subject: RE: [Megaco] Local/Remote descriptors and Permanent
> terminations
>
> Suppose you have the following SDP:
>
> m=audio 4444 RTP/AVP 0 18
> a=fmtp:18 annexb=no         // G.729, Silence Suppression off (see
> draft-ietf-avt-rtp-mime-05)
> a=silenceSupp: on - - - -
>
> (that means the GW may either use G.711 µ-law or G.729)
>
> The silenceSupp attribute is not specific for a payload type, the fmtp
> attribute is. So which one has precedence in this case?
>
> In my opinion you should have the ability to switch on silence suppression
> depending on the payload type. If you want to use it with G.711, it does not
> mean that you want it with G.729.
>
> Beyond that I believe generally it is more suited to an ephemeral
> termination. Therefore it should be expressed by means of SDP.
>
> However, if you want to transport the comfort noise payload (according to
> draft-ietf-avt-rtp-cn-05), you should add the payload type 13 to the SDP
> media line as well (IMO).
>
> From my point of view the SDP should therefore look something like this:
>
> m=audio 4444 RTP/AVP 0 18 13
> a=fmtp:18 annexb=no
> a=fmtp:0 silSup=yes
>
> where this PCMU specific parameter silSup must still be defined (for PCMA as
> well).
>
> Any comment is appreciated.
>
>         Kind regards
>
>                 Markus Pauls
>
> ________________________________________________________
> Markus Pauls
>
> SIEMENS
> Information and Communication Networks
>
> ICN WN CC NA B13        Tel.:   +49 89 722 62937
> Hofmannstr. 51          Fax:    +49 89 722 44176
> 81359 Munich            Email:  markus.pauls@icn.siemens.de
> Germany
>
> -----Original Message-----
> From: Carl Rutter [mailto:crutter@telica.com]
> Sent: Wednesday, April 03, 2002 3:36 AM
> To: Chuong N. Nguyen
> Cc: megaco@ietf.org
> Subject: RE: [Megaco] Local/Remote descriptors and Permanent terminations
>
> You bring up a good point,
> Is/Should Silient Suppression be tied to the TDM package or
> SDP TDM, if in fact its really more applicable to the Ephemral side.
> If no can think of a good reason then your right it would make more sense to
> be in the SDP.
> For now we could use 0 13 for G711 and long-term use the ATM approach for
> SDP.
> Trying to drive towards closure as we have a need to implement this.
> Yea, the hairpinning would be in the MG Switch.
> Comments?
>
> Carl
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Chuong N. Nguyen
> Sent: Tuesday, April 02, 2002 8:05 PM
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
>
>
> That is what  I initially thought silence suppression was about.
> But then I was told differently.
> It could be applied to TDM.
> If not, then why are we discussing adding silence suppresion to the TDM
> package?
>
> By the way,  I thought TDM-TDM calls are being made at the Gwy too.
> Aren't you guys doing that now?
>
>
> Carl Rutter wrote:
> I can't think of an application where you'd want to do that. Silence
> suppression really wouldn't make sense for a TDM-TDMwhich is hairpined at
> the CO. The DS0 is dedicated. The advantage of Silent suppression it to
> limit the RTP traffic on the IP side, which you wouldn't have in that
> case.Maybe if you wanted to inject Comfort Noise instead of backgroundnoice
> in the TDM-TDM call??Carl
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Chuong N. Nguyen
> Sent: Tuesday, April 02, 2002 7:16 PM
> To: megaco@ietf.org
> Subject: Re: [Megaco] Local/Remote descriptors and Permanent terminations
> Tom-PT Taylor wrote:
> I've had a message pointing out the existence of
> draft-ietf-avt-rtp-cn-05.txt.  Specifying this payload type as well as G.711
>
> would indicate the use of silence suppression implicitly.  That covers RTP
> transport.  For ATM we have the a=silenceSupp attribute defined in RFC 3108.
>
> Do we need anything for TDM?
>
> What if someone wanted to make a TDM-TDM, hairpin call?
> Would silenceSupp be used for such a call?
> If yes, then what?
>
>
> --
>   Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
>   1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
>   **** The opinions expressed are not those of Alcatel USA, Inc ****
> --
>   Alcatel USA, Inc             Internet: Chuong.Nguyen@usa.alcatel.com
>   1000 Coit Road Plano, Texas 75075           Phone:    (972) 519-4613
>   **** The opinions expressed are not those of Alcatel USA, Inc ****
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------AE44D80F31F7B735404D2940
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------AE44D80F31F7B735404D2940--


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



From megaco-admin@ietf.org  Wed Apr  3 10:38: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 KAA06607
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 10:38: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 KAA00492;
	Wed, 3 Apr 2002 10:12: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 KAA00460
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 10:12: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 KAA05496
	for <megaco@ietf.org>; Wed, 3 Apr 2002 10:12:40 -0500 (EST)
From: vbajaj@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 g33FDF325764;
	Wed, 3 Apr 2002 20:43:15 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B90.0053567D ; Wed, 3 Apr 2002 20:40:16 +0530
X-Lotus-FromDomain: HSS
To: "SERDAR CABUK" <serdar.cabuk@o2.com.tr>
cc: megaco@ietf.org
Message-ID: <65256B90.0053544E.00@sandesh.hss.hns.com>
Date: Wed, 3 Apr 2002 20:42:43 +0530
Subject: Re: [Megaco] JAIN Megaco
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



Serdar,
           The JAIN MEGACO API document is in the development stage. A majority
of the
  work has been completed. We expect it to go for JAIN community review very
soon.
 Subsequent to the community review, it shall be put for public review and
Reference
Implementation shall be developed in parallel.

Rgds,

Vikas Bajaj





"SERDAR CABUK" <serdar.cabuk@o2.com.tr> on 04/03/2002 01:13:35 PM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  [Megaco] JAIN Megaco





Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



_______________________________________________
Megaco mailing list
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 Apr  3 10:38: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 KAA06617
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 10:38:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA03385
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 10:38: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 KAA00492;
	Wed, 3 Apr 2002 10:12: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 KAA00460
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 10:12: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 KAA05496
	for <megaco@ietf.org>; Wed, 3 Apr 2002 10:12:40 -0500 (EST)
From: vbajaj@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 g33FDF325764;
	Wed, 3 Apr 2002 20:43:15 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B90.0053567D ; Wed, 3 Apr 2002 20:40:16 +0530
X-Lotus-FromDomain: HSS
To: "SERDAR CABUK" <serdar.cabuk@o2.com.tr>
cc: megaco@ietf.org
Message-ID: <65256B90.0053544E.00@sandesh.hss.hns.com>
Date: Wed, 3 Apr 2002 20:42:43 +0530
Subject: Re: [Megaco] JAIN Megaco
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



Serdar,
           The JAIN MEGACO API document is in the development stage. A majority
of the
  work has been completed. We expect it to go for JAIN community review very
soon.
 Subsequent to the community review, it shall be put for public review and
Reference
Implementation shall be developed in parallel.

Rgds,

Vikas Bajaj





"SERDAR CABUK" <serdar.cabuk@o2.com.tr> on 04/03/2002 01:13:35 PM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  [Megaco] JAIN Megaco





Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



_______________________________________________
Megaco mailing list
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 Apr  3 11: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 LAA07361
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 11:00: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 KAA01977;
	Wed, 3 Apr 2002 10:26: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 KAA01924
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 10:26:54 -0500 (EST)
Received: from postman ([217.31.228.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06010
	for <megaco@ietf.org>; Wed, 3 Apr 2002 10:26:51 -0500 (EST)
Subject: Re: [Megaco] JAIN Megaco
To: vbajaj@hss.hns.com
Cc: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.4  June 8, 2000
Message-ID: <OFAAEB0D68.FB80BBEA-ONC2256B90.005A049F@LocalDomain>
From: "SERDAR CABUK" <serdar.cabuk@o2.com.tr>
Date: Wed, 3 Apr 2002 18:24:33 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 04/03/2002
 06:25:08 PM
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


Thank you,

So what is the time frame of this process? Do you have any idea when the RI
will be opened for community review?

Regards,

Serdar Cabuk



                                                                                                                                 
                    vbajaj@hss.hns                                                                                               
                    .com                 To:     "SERDAR CABUK" <serdar.cabuk@o2.com.tr>                                         
                                         cc:     megaco@ietf.org                                                                 
                    04/03/2002           Subject:     Re: [Megaco] JAIN Megaco                                                   
                    06:12 PM                                                                                                     
                                                                                                                                 
                                                                                                                                 






Serdar,
           The JAIN MEGACO API document is in the development stage. A
majority
of the
  work has been completed. We expect it to go for JAIN community review
very
soon.
 Subsequent to the community review, it shall be put for public review and
Reference
Implementation shall be developed in parallel.

Rgds,

Vikas Bajaj





"SERDAR CABUK" <serdar.cabuk@o2.com.tr> on 04/03/2002 01:13:35 PM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  [Megaco] JAIN Megaco





Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



_______________________________________________
Megaco mailing list
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 Apr  3 11: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 LAA07370
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 11:00:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA04910
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 11:00: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 KAA01977;
	Wed, 3 Apr 2002 10:26: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 KAA01924
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 10:26:54 -0500 (EST)
Received: from postman ([217.31.228.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06010
	for <megaco@ietf.org>; Wed, 3 Apr 2002 10:26:51 -0500 (EST)
Subject: Re: [Megaco] JAIN Megaco
To: vbajaj@hss.hns.com
Cc: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.4  June 8, 2000
Message-ID: <OFAAEB0D68.FB80BBEA-ONC2256B90.005A049F@LocalDomain>
From: "SERDAR CABUK" <serdar.cabuk@o2.com.tr>
Date: Wed, 3 Apr 2002 18:24:33 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 04/03/2002
 06:25:08 PM
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


Thank you,

So what is the time frame of this process? Do you have any idea when the RI
will be opened for community review?

Regards,

Serdar Cabuk



                                                                                                                                 
                    vbajaj@hss.hns                                                                                               
                    .com                 To:     "SERDAR CABUK" <serdar.cabuk@o2.com.tr>                                         
                                         cc:     megaco@ietf.org                                                                 
                    04/03/2002           Subject:     Re: [Megaco] JAIN Megaco                                                   
                    06:12 PM                                                                                                     
                                                                                                                                 
                                                                                                                                 






Serdar,
           The JAIN MEGACO API document is in the development stage. A
majority
of the
  work has been completed. We expect it to go for JAIN community review
very
soon.
 Subsequent to the community review, it shall be put for public review and
Reference
Implementation shall be developed in parallel.

Rgds,

Vikas Bajaj





"SERDAR CABUK" <serdar.cabuk@o2.com.tr> on 04/03/2002 01:13:35 PM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  [Megaco] JAIN Megaco





Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



_______________________________________________
Megaco mailing list
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 Apr  3 11:26: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 LAA08170
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 11:26: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 LAA05298;
	Wed, 3 Apr 2002 11:02: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 LAA05270
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 11:02:11 -0500 (EST)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07431
	for <megaco@ietf.org>; Wed, 3 Apr 2002 11:01:55 -0500 (EST)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id LAA28558;
	Wed, 3 Apr 2002 11:01:05 -0500 (EST)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2ACAMHLB>; Wed, 3 Apr 2002 11:01:03 -0500
Message-ID: <29B5A21C13C8D51190F900805F65B4EC239F91@rndex50.ottawa.mitel.com>
From: "Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM>
To: vbajaj@hss.hns.com
Cc: megaco@ietf.org, "'SERDAR CABUK'" <serdar.cabuk@o2.com.tr>
Subject: RE: [Megaco] JAIN Megaco
Date: Wed, 3 Apr 2002 11:00:55 -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

... or even a copy for "sneak peak" (as opposed to review-ready) ...  

I would certainly be interested in getting any visibility currently available, as there is nothing accessible on the JAIN web site I could find.  

-- Peter Blatherwick

-----Original Message-----
From: SERDAR CABUK [mailto:serdar.cabuk@o2.com.tr]
Sent: April 3, 2002 11:25
To: vbajaj@hss.hns.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] JAIN Megaco



Thank you,

So what is the time frame of this process? Do you have any idea when the RI
will be opened for community review?

Regards,

Serdar Cabuk



                                                                                                                                 
                    vbajaj@hss.hns                                                                                               
                    .com                 To:     "SERDAR CABUK" <serdar.cabuk@o2.com.tr>                                         
                                         cc:     megaco@ietf.org                                                                 
                    04/03/2002           Subject:     Re: [Megaco] JAIN Megaco                                                   
                    06:12 PM                                                                                                     
                                                                                                                                 
                                                                                                                                 






Serdar,
           The JAIN MEGACO API document is in the development stage. A
majority
of the
  work has been completed. We expect it to go for JAIN community review
very
soon.
 Subsequent to the community review, it shall be put for public review and
Reference
Implementation shall be developed in parallel.

Rgds,

Vikas Bajaj





"SERDAR CABUK" <serdar.cabuk@o2.com.tr> on 04/03/2002 01:13:35 PM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  [Megaco] JAIN Megaco





Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



_______________________________________________
Megaco mailing 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 Apr  3 11:26: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 LAA08179
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 11:26:59 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA06781
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 11:27: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 LAA05298;
	Wed, 3 Apr 2002 11:02: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 LAA05270
	for <megaco@ns.ietf.org>; Wed, 3 Apr 2002 11:02:11 -0500 (EST)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07431
	for <megaco@ietf.org>; Wed, 3 Apr 2002 11:01:55 -0500 (EST)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id LAA28558;
	Wed, 3 Apr 2002 11:01:05 -0500 (EST)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2ACAMHLB>; Wed, 3 Apr 2002 11:01:03 -0500
Message-ID: <29B5A21C13C8D51190F900805F65B4EC239F91@rndex50.ottawa.mitel.com>
From: "Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM>
To: vbajaj@hss.hns.com
Cc: megaco@ietf.org, "'SERDAR CABUK'" <serdar.cabuk@o2.com.tr>
Subject: RE: [Megaco] JAIN Megaco
Date: Wed, 3 Apr 2002 11:00:55 -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

... or even a copy for "sneak peak" (as opposed to review-ready) ...  

I would certainly be interested in getting any visibility currently available, as there is nothing accessible on the JAIN web site I could find.  

-- Peter Blatherwick

-----Original Message-----
From: SERDAR CABUK [mailto:serdar.cabuk@o2.com.tr]
Sent: April 3, 2002 11:25
To: vbajaj@hss.hns.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] JAIN Megaco



Thank you,

So what is the time frame of this process? Do you have any idea when the RI
will be opened for community review?

Regards,

Serdar Cabuk



                                                                                                                                 
                    vbajaj@hss.hns                                                                                               
                    .com                 To:     "SERDAR CABUK" <serdar.cabuk@o2.com.tr>                                         
                                         cc:     megaco@ietf.org                                                                 
                    04/03/2002           Subject:     Re: [Megaco] JAIN Megaco                                                   
                    06:12 PM                                                                                                     
                                                                                                                                 
                                                                                                                                 






Serdar,
           The JAIN MEGACO API document is in the development stage. A
majority
of the
  work has been completed. We expect it to go for JAIN community review
very
soon.
 Subsequent to the community review, it shall be put for public review and
Reference
Implementation shall be developed in parallel.

Rgds,

Vikas Bajaj





"SERDAR CABUK" <serdar.cabuk@o2.com.tr> on 04/03/2002 01:13:35 PM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  [Megaco] JAIN Megaco





Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



_______________________________________________
Megaco mailing 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 Apr  3 17:08: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 RAA17328
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 17:08: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 QAA29755;
	Wed, 3 Apr 2002 16:50: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 QAA29722
	for <megaco@optimus.ietf.org>; Wed, 3 Apr 2002 16:50:28 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16909
	for <megaco@ietf.org>; Wed, 3 Apr 2002 16:50:24 -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 g33Lnti15725
	for <megaco@ietf.org>; Wed, 3 Apr 2002 16:49:56 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LAG1F>; Wed, 3 Apr 2002 16:49:58 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A246@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 3 Apr 2002 16:49:56 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Test Trunks
Sender: megaco-admin@ietf.org
Errors-To: 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 anyone aware of a package for test trunks?

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 Apr  3 17:08: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 RAA17338
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 17:08:17 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA01615
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 17:08: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 QAA29755;
	Wed, 3 Apr 2002 16:50: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 QAA29722
	for <megaco@optimus.ietf.org>; Wed, 3 Apr 2002 16:50:28 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16909
	for <megaco@ietf.org>; Wed, 3 Apr 2002 16:50:24 -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 g33Lnti15725
	for <megaco@ietf.org>; Wed, 3 Apr 2002 16:49:56 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LAG1F>; Wed, 3 Apr 2002 16:49:58 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A246@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 3 Apr 2002 16:49:56 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Test Trunks
Sender: megaco-admin@ietf.org
Errors-To: 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 anyone aware of a package for test trunks?

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 Apr  3 19:16: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 TAA19665
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 19:16: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 SAA07008;
	Wed, 3 Apr 2002 18: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 SAA06980
	for <megaco@optimus.ietf.org>; Wed, 3 Apr 2002 18:58:48 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19403
	for <megaco@ietf.org>; Wed, 3 Apr 2002 18:58: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 g33NwIS07174
	for <megaco@ietf.org>; Wed, 3 Apr 2002 18:58:18 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LAH4X>; Wed, 3 Apr 2002 18:58:19 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A248@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 3 Apr 2002 18:58:17 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] FW: [MMUSIC] Silence Suppression 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

Is this a workable assumption?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Wednesday, April 03, 2002 6:56 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Dan Firac; mmusic@ietf.org
Subject: Re: [MMUSIC] Silence Suppression Attribute 


If you're using RTP, it's assumed that silence suppression is possible (and
since receivers have to cope with packet loss anyway, this doesn't add any
significant complexity). 

Colin




--> "Tom-PT Taylor" writes:
>The caller supports G.711 with voice activity detection and silence
>suppression and would like to make that offer.  There is no PCM parameter
>indicating this mode of operation.
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: Wednesday, April 03, 2002 6:23 PM
>To: Dan Firac
>Cc: Taylor, Tom-PT [CAR:B800:EXCH]; mmusic@ietf.org
>Subject: Re: [MMUSIC] Silence Suppression Attribute 
>
>
>What would be the scenario where the new attribute is used? 
>Colin
>
>
>--> "Dan Firac" writes:
>>It's a very good ideea.
>>Anyway, why this attribute was defined for ATM transport type only?
>>Silence suppression, as you pointed below, is an attribute of a codec
>>and has nothing to do with transport.
>>
>>Dan Firac,
>>Software Engineer,
>>RedlineCommunications,
>>Romania.
>>
>>
>>
>>
>>----- Original Message -----
>>From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
>>To: <mmusic@ietf.org>; <megaco@ietf.org>
>>Sent: Wednesday, April 03, 2002 12:10 AM
>>Subject: [MMUSIC] Silence Suppression Attribute
>>
>>
>>> The issue of how to signal silence suppression capability keeps coming
up
>>on
>>> the Megaco list.  The situation is fairly complicated:
>>>  - some codecs come with a pre-defined capability for silence
>suppression.
>>> This capability can be invoked by the appropriate MIME type parameter as
>>> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to
RTP
>>> transport, arguably over UDP only.
>>>  - other codecs like G.711 have no such parameter, yet silence
>suppression
>>> is possible
>>>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
>>> transport only.
>>>
>>> How would people feel about allowing the a=silenceSupp parameter to be
>>used
>>> independently of the transport type?
>>>
>>> Tom Taylor
>>> taylor@nortelnetworks.com
>>> Ph. +1 613 736 0961 (ESN 396 1490)
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic

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


From daemon@optimus.ietf.org  Wed Apr  3 19:17: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 TAA19676
	for <megaco-archive@odin.ietf.org>; Wed, 3 Apr 2002 19:16:59 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA08381
	for megaco-archive@odin.ietf.org; Wed, 3 Apr 2002 19:17: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 SAA07008;
	Wed, 3 Apr 2002 18: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 SAA06980
	for <megaco@optimus.ietf.org>; Wed, 3 Apr 2002 18:58:48 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19403
	for <megaco@ietf.org>; Wed, 3 Apr 2002 18:58: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 g33NwIS07174
	for <megaco@ietf.org>; Wed, 3 Apr 2002 18:58:18 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LAH4X>; Wed, 3 Apr 2002 18:58:19 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A248@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 3 Apr 2002 18:58:17 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] FW: [MMUSIC] Silence Suppression 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

Is this a workable assumption?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Wednesday, April 03, 2002 6:56 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Dan Firac; mmusic@ietf.org
Subject: Re: [MMUSIC] Silence Suppression Attribute 


If you're using RTP, it's assumed that silence suppression is possible (and
since receivers have to cope with packet loss anyway, this doesn't add any
significant complexity). 

Colin




--> "Tom-PT Taylor" writes:
>The caller supports G.711 with voice activity detection and silence
>suppression and would like to make that offer.  There is no PCM parameter
>indicating this mode of operation.
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: Wednesday, April 03, 2002 6:23 PM
>To: Dan Firac
>Cc: Taylor, Tom-PT [CAR:B800:EXCH]; mmusic@ietf.org
>Subject: Re: [MMUSIC] Silence Suppression Attribute 
>
>
>What would be the scenario where the new attribute is used? 
>Colin
>
>
>--> "Dan Firac" writes:
>>It's a very good ideea.
>>Anyway, why this attribute was defined for ATM transport type only?
>>Silence suppression, as you pointed below, is an attribute of a codec
>>and has nothing to do with transport.
>>
>>Dan Firac,
>>Software Engineer,
>>RedlineCommunications,
>>Romania.
>>
>>
>>
>>
>>----- Original Message -----
>>From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
>>To: <mmusic@ietf.org>; <megaco@ietf.org>
>>Sent: Wednesday, April 03, 2002 12:10 AM
>>Subject: [MMUSIC] Silence Suppression Attribute
>>
>>
>>> The issue of how to signal silence suppression capability keeps coming
up
>>on
>>> the Megaco list.  The situation is fairly complicated:
>>>  - some codecs come with a pre-defined capability for silence
>suppression.
>>> This capability can be invoked by the appropriate MIME type parameter as
>>> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to
RTP
>>> transport, arguably over UDP only.
>>>  - other codecs like G.711 have no such parameter, yet silence
>suppression
>>> is possible
>>>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
>>> transport only.
>>>
>>> How would people feel about allowing the a=silenceSupp parameter to be
>>used
>>> independently of the transport type?
>>>
>>> Tom Taylor
>>> taylor@nortelnetworks.com
>>> Ph. +1 613 736 0961 (ESN 396 1490)
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic

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



From megaco-admin@ietf.org  Thu Apr  4 00:51: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 AAA26649
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 00:51: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 AAA23711;
	Thu, 4 Apr 2002 00:28: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 AAA23671
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 00:28:45 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26458
	for <megaco@ietf.org>; Thu, 4 Apr 2002 00:28:42 -0500 (EST)
From: vbajaj@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 g345Sp306320;
	Thu, 4 Apr 2002 10:58:51 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B91.001DD113 ; Thu, 4 Apr 2002 10:55:40 +0530
X-Lotus-FromDomain: HSS
To: "Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM>
cc: megaco@ietf.org, "'SERDAR CABUK'" <serdar.cabuk@o2.com.tr>
Message-ID: <65256B91.001DCE46.00@sandesh.hss.hns.com>
Date: Thu, 4 Apr 2002 10:58:06 +0530
Subject: RE: [Megaco] JAIN Megaco
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



Peter,
       A sneak peak may not be possible until community review is over. Once the
review is
 completed the document would be put for public review. Anybody can then provide
comments
 and the document can undergo change based on accepted comments. The current
plan is to
 put the document for community review by end of this month. Community review
typically takes
 around 20-21 days unless there are are major comments on it. Subsequent to that
the
document shall be put for public review. I can send a notification to the list
when that happens.

Rgds,

Vikas Bajaj





"Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM> on 04/03/2002 09:30:55 PM

To:   Vikas Bajaj/HSS@HSS
cc:   megaco@ietf.org, "'SERDAR CABUK'" <serdar.cabuk@o2.com.tr>

Subject:  RE: [Megaco] JAIN Megaco




... or even a copy for "sneak peak" (as opposed to review-ready) ...

I would certainly be interested in getting any visibility currently available,
as there is nothing accessible on the JAIN web site I could find.

-- Peter Blatherwick

-----Original Message-----
From: SERDAR CABUK [mailto:serdar.cabuk@o2.com.tr]
Sent: April 3, 2002 11:25
To: vbajaj@hss.hns.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] JAIN Megaco



Thank you,

So what is the time frame of this process? Do you have any idea when the RI
will be opened for community review?

Regards,

Serdar Cabuk




                    vbajaj@hss.hns
                    .com                 To:     "SERDAR CABUK"
<serdar.cabuk@o2.com.tr>
                                         cc:     megaco@ietf.org
                    04/03/2002           Subject:     Re: [Megaco] JAIN Megaco
                    06:12 PM








Serdar,
           The JAIN MEGACO API document is in the development stage. A
majority
of the
  work has been completed. We expect it to go for JAIN community review
very
soon.
 Subsequent to the community review, it shall be put for public review and
Reference
Implementation shall be developed in parallel.

Rgds,

Vikas Bajaj





"SERDAR CABUK" <serdar.cabuk@o2.com.tr> on 04/03/2002 01:13:35 PM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  [Megaco] JAIN Megaco





Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



_______________________________________________
Megaco mailing 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 Apr  4 00: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 AAA26658
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 00:51:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA24810
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 00: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 AAA23711;
	Thu, 4 Apr 2002 00:28: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 AAA23671
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 00:28:45 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26458
	for <megaco@ietf.org>; Thu, 4 Apr 2002 00:28:42 -0500 (EST)
From: vbajaj@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 g345Sp306320;
	Thu, 4 Apr 2002 10:58:51 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B91.001DD113 ; Thu, 4 Apr 2002 10:55:40 +0530
X-Lotus-FromDomain: HSS
To: "Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM>
cc: megaco@ietf.org, "'SERDAR CABUK'" <serdar.cabuk@o2.com.tr>
Message-ID: <65256B91.001DCE46.00@sandesh.hss.hns.com>
Date: Thu, 4 Apr 2002 10:58:06 +0530
Subject: RE: [Megaco] JAIN Megaco
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



Peter,
       A sneak peak may not be possible until community review is over. Once the
review is
 completed the document would be put for public review. Anybody can then provide
comments
 and the document can undergo change based on accepted comments. The current
plan is to
 put the document for community review by end of this month. Community review
typically takes
 around 20-21 days unless there are are major comments on it. Subsequent to that
the
document shall be put for public review. I can send a notification to the list
when that happens.

Rgds,

Vikas Bajaj





"Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM> on 04/03/2002 09:30:55 PM

To:   Vikas Bajaj/HSS@HSS
cc:   megaco@ietf.org, "'SERDAR CABUK'" <serdar.cabuk@o2.com.tr>

Subject:  RE: [Megaco] JAIN Megaco




... or even a copy for "sneak peak" (as opposed to review-ready) ...

I would certainly be interested in getting any visibility currently available,
as there is nothing accessible on the JAIN web site I could find.

-- Peter Blatherwick

-----Original Message-----
From: SERDAR CABUK [mailto:serdar.cabuk@o2.com.tr]
Sent: April 3, 2002 11:25
To: vbajaj@hss.hns.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] JAIN Megaco



Thank you,

So what is the time frame of this process? Do you have any idea when the RI
will be opened for community review?

Regards,

Serdar Cabuk




                    vbajaj@hss.hns
                    .com                 To:     "SERDAR CABUK"
<serdar.cabuk@o2.com.tr>
                                         cc:     megaco@ietf.org
                    04/03/2002           Subject:     Re: [Megaco] JAIN Megaco
                    06:12 PM








Serdar,
           The JAIN MEGACO API document is in the development stage. A
majority
of the
  work has been completed. We expect it to go for JAIN community review
very
soon.
 Subsequent to the community review, it shall be put for public review and
Reference
Implementation shall be developed in parallel.

Rgds,

Vikas Bajaj





"SERDAR CABUK" <serdar.cabuk@o2.com.tr> on 04/03/2002 01:13:35 PM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  [Megaco] JAIN Megaco





Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



_______________________________________________
Megaco mailing 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 Apr  4 02:37: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 CAA06114
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 02: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 CAA09311;
	Thu, 4 Apr 2002 02:18: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 CAA09244
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 02:18:37 -0500 (EST)
Received: from mxout2.netvision.net.il (mxout2.netvision.net.il [194.90.9.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05907;
	Thu, 4 Apr 2002 02:18:33 -0500 (EST)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout2.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GU100G998A3KE@mxout2.netvision.net.il>; Thu,
 04 Apr 2002 10:18:04 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <21HN1QJM>; Thu, 04 Apr 2002 10:16:52 +0300
Content-return: allowed
Date: Thu, 04 Apr 2002 10:16:50 +0300
From: Dan Elbert <delbert@radvision.com>
Subject: RE: [Megaco] Silence Suppression Attribute
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, mmusic@ietf.org,
        "'megaco@ietf.org'" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B018BBF53@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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

I think is a good idea
By the way, if an attribute is registred for use in SDP I don't think there
is a scope limitation, anybody can effectively use it.

Dan Elbert
RADVISION

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 12:11 AM
To: mmusic@ietf.org; 'megaco@ietf.org'
Subject: [Megaco] Silence Suppression Attribute


The issue of how to signal silence suppression capability keeps coming up on
the Megaco list.  The situation is fairly complicated:
 - some codecs come with a pre-defined capability for silence suppression.
This capability can be invoked by the appropriate MIME type parameter as
defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to RTP
transport, arguably over UDP only.
 - other codecs like G.711 have no such parameter, yet silence suppression
is possible
 - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
transport only.

How would people feel about allowing the a=silenceSupp parameter to be used
independently of the transport type?

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  Thu Apr  4 03:24: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 CAA06123
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 02:37:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA10327
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 02:37: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 CAA09311;
	Thu, 4 Apr 2002 02:18: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 CAA09244
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 02:18:37 -0500 (EST)
Received: from mxout2.netvision.net.il (mxout2.netvision.net.il [194.90.9.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05907;
	Thu, 4 Apr 2002 02:18:33 -0500 (EST)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout2.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GU100G998A3KE@mxout2.netvision.net.il>; Thu,
 04 Apr 2002 10:18:04 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <21HN1QJM>; Thu, 04 Apr 2002 10:16:52 +0300
Content-return: allowed
Date: Thu, 04 Apr 2002 10:16:50 +0300
From: Dan Elbert <delbert@radvision.com>
Subject: RE: [Megaco] Silence Suppression Attribute
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, mmusic@ietf.org,
        "'megaco@ietf.org'" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B018BBF53@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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

I think is a good idea
By the way, if an attribute is registred for use in SDP I don't think there
is a scope limitation, anybody can effectively use it.

Dan Elbert
RADVISION

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 12:11 AM
To: mmusic@ietf.org; 'megaco@ietf.org'
Subject: [Megaco] Silence Suppression Attribute


The issue of how to signal silence suppression capability keeps coming up on
the Megaco list.  The situation is fairly complicated:
 - some codecs come with a pre-defined capability for silence suppression.
This capability can be invoked by the appropriate MIME type parameter as
defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to RTP
transport, arguably over UDP only.
 - other codecs like G.711 have no such parameter, yet silence suppression
is possible
 - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
transport only.

How would people feel about allowing the a=silenceSupp parameter to be used
independently of the transport type?

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  Thu Apr  4 03:55: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 DAA07224
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 03: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 DAA13005;
	Thu, 4 Apr 2002 03:20: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 DAA12975
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 03:20:05 -0500 (EST)
Received: from mxout2.netvision.net.il (mxout2.netvision.net.il [194.90.9.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06824
	for <megaco@ietf.org>; Thu, 4 Apr 2002 03:20:03 -0500 (EST)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout2.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GU100G4WB4MUW@mxout2.netvision.net.il> for megaco@ietf.org;
 Thu, 04 Apr 2002 11:19:34 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <21HN1Q3X>; Thu, 04 Apr 2002 11:18:22 +0300
Content-return: allowed
Date: Thu, 04 Apr 2002 11:18:22 +0300
From: Dan Elbert <delbert@radvision.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B018BBF59@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
Subject: [Megaco] Do signals stop when termination is subtracted?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

According to the the spec:

-   When a provisioned Termination is Subtracted from a context, its
   property values shall revert to:

   *  the default value, if specified for the property and not
      overridden by provisioning,
   *  otherwise, the provisioned value.

The question is, what happens with signals playing on a termination when is
subtracted? Do they stop (as seems to be implied by "properties values
reverting to default" ) or do they keep playing?
Thanks

Dan Elbert
RADVISION

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


From daemon@optimus.ietf.org  Thu Apr  4 03:55: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 DAA07235
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 03:55:20 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA14627
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 03:55: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 DAA13005;
	Thu, 4 Apr 2002 03:20: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 DAA12975
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 03:20:05 -0500 (EST)
Received: from mxout2.netvision.net.il (mxout2.netvision.net.il [194.90.9.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06824
	for <megaco@ietf.org>; Thu, 4 Apr 2002 03:20:03 -0500 (EST)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout2.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GU100G4WB4MUW@mxout2.netvision.net.il> for megaco@ietf.org;
 Thu, 04 Apr 2002 11:19:34 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <21HN1Q3X>; Thu, 04 Apr 2002 11:18:22 +0300
Content-return: allowed
Date: Thu, 04 Apr 2002 11:18:22 +0300
From: Dan Elbert <delbert@radvision.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B018BBF59@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
Subject: [Megaco] Do signals stop when termination is subtracted?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

According to the the spec:

-   When a provisioned Termination is Subtracted from a context, its
   property values shall revert to:

   *  the default value, if specified for the property and not
      overridden by provisioning,
   *  otherwise, the provisioned value.

The question is, what happens with signals playing on a termination when is
subtracted? Do they stop (as seems to be implied by "properties values
reverting to default" ) or do they keep playing?
Thanks

Dan Elbert
RADVISION

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



From megaco-admin@ietf.org  Thu Apr  4 06:31: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 GAA09976
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 06:31: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 GAA21789;
	Thu, 4 Apr 2002 06:11: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 GAA21761
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 06:11:06 -0500 (EST)
Received: from web12608.mail.yahoo.com (web12608.mail.yahoo.com [216.136.173.231])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA09643
	for <megaco@ietf.org>; Thu, 4 Apr 2002 06:11:02 -0500 (EST)
Message-ID: <20020404111105.76481.qmail@web12608.mail.yahoo.com>
Received: from [203.26.41.49] by web12608.mail.yahoo.com via HTTP; Thu, 04 Apr 2002 03:11:05 PST
Date: Thu, 4 Apr 2002 03:11:05 -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: Unique ContextId and TerminationId?
Sender: megaco-admin@ietf.org
Errors-To: 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,

According to the spec, the ContextID is unique to
identify the action, but the context ID is assigned by
the MG. When the MGC sends a first action request to
the MG, it uses a null context ID. How can the MGC
maintain the action identification uniquely with the
null Context ID? How can the MGC match a reply action
to the original request action as the context ID has 
been changed (assigned by the MG)?

Also, the termination ID is provisioned at MG, does
the MGC has the knowledge of the termination IDs
before sending request, or does the MGC reply the MG
to assign the termination ID as well?

Thank you.

yh

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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


From daemon@optimus.ietf.org  Thu Apr  4 06:31: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 GAA09995
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 06:31:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA23117
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 06:31: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 GAA21789;
	Thu, 4 Apr 2002 06:11: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 GAA21761
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 06:11:06 -0500 (EST)
Received: from web12608.mail.yahoo.com (web12608.mail.yahoo.com [216.136.173.231])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA09643
	for <megaco@ietf.org>; Thu, 4 Apr 2002 06:11:02 -0500 (EST)
Message-ID: <20020404111105.76481.qmail@web12608.mail.yahoo.com>
Received: from [203.26.41.49] by web12608.mail.yahoo.com via HTTP; Thu, 04 Apr 2002 03:11:05 PST
Date: Thu, 4 Apr 2002 03:11:05 -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: Unique ContextId and TerminationId?
Sender: megaco-admin@ietf.org
Errors-To: 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,

According to the spec, the ContextID is unique to
identify the action, but the context ID is assigned by
the MG. When the MGC sends a first action request to
the MG, it uses a null context ID. How can the MGC
maintain the action identification uniquely with the
null Context ID? How can the MGC match a reply action
to the original request action as the context ID has 
been changed (assigned by the MG)?

Also, the termination ID is provisioned at MG, does
the MGC has the knowledge of the termination IDs
before sending request, or does the MGC reply the MG
to assign the termination ID as well?

Thank you.

yh

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From megaco-admin@ietf.org  Thu Apr  4 08:15: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 IAA12877
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 08:15: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 HAA27571;
	Thu, 4 Apr 2002 07:58: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 HAA27535
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 07:58:28 -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 HAA12294
	for <megaco@ietf.org>; Thu, 4 Apr 2002 07:58:25 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0SNZ>; Thu, 4 Apr 2002 07:57:54 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C61@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] Re: Unique ContextId and TerminationId?
Date: Thu, 4 Apr 2002 07:57:53 -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

As far as the Termination ID its something
agreed upon(provisioned) between the MG & MGC.

AS far as the first question, usually the MGC will
use CHOOSE for the Context and the MG will create 
a unique one, if I understand your question correctly.

Carl
-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 04, 2002 6:11 AM
To: megaco@ietf.org
Subject: [Megaco] Re: Unique ContextId and TerminationId?


Hi,

According to the spec, the ContextID is unique to
identify the action, but the context ID is assigned by
the MG. When the MGC sends a first action request to
the MG, it uses a null context ID. How can the MGC
maintain the action identification uniquely with the
null Context ID? How can the MGC match a reply action
to the original request action as the context ID has 
been changed (assigned by the MG)?

Also, the termination ID is provisioned at MG, does
the MGC has the knowledge of the termination IDs
before sending request, or does the MGC reply the MG
to assign the termination ID as well?

Thank you.

yh

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.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@optimus.ietf.org  Thu Apr  4 08:15: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 IAA12888
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 08:15:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA28952
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 08:15: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 HAA27571;
	Thu, 4 Apr 2002 07:58: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 HAA27535
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 07:58:28 -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 HAA12294
	for <megaco@ietf.org>; Thu, 4 Apr 2002 07:58:25 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0SNZ>; Thu, 4 Apr 2002 07:57:54 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C61@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] Re: Unique ContextId and TerminationId?
Date: Thu, 4 Apr 2002 07:57:53 -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

As far as the Termination ID its something
agreed upon(provisioned) between the MG & MGC.

AS far as the first question, usually the MGC will
use CHOOSE for the Context and the MG will create 
a unique one, if I understand your question correctly.

Carl
-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 04, 2002 6:11 AM
To: megaco@ietf.org
Subject: [Megaco] Re: Unique ContextId and TerminationId?


Hi,

According to the spec, the ContextID is unique to
identify the action, but the context ID is assigned by
the MG. When the MGC sends a first action request to
the MG, it uses a null context ID. How can the MGC
maintain the action identification uniquely with the
null Context ID? How can the MGC match a reply action
to the original request action as the context ID has 
been changed (assigned by the MG)?

Also, the termination ID is provisioned at MG, does
the MGC has the knowledge of the termination IDs
before sending request, or does the MGC reply the MG
to assign the termination ID as well?

Thank you.

yh

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.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  Thu Apr  4 09:07: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 JAA14901
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09: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 IAA01141;
	Thu, 4 Apr 2002 08:51: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 IAA01078
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 08:51:45 -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 IAA14233
	for <megaco@ietf.org>; Thu, 4 Apr 2002 08:51:37 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0S40>; Thu, 4 Apr 2002 08:51:09 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C63@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute
Date: Thu, 4 Apr 2002 08:51:09 -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

Could you clarify what the assumtion is,
Is it,
That its OK to assume that any MG should be able to handle 
Silent Suppression?


Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] FW: [MMUSIC] Silence Suppression Attribute


Is this a workable assumption?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Wednesday, April 03, 2002 6:56 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Dan Firac; mmusic@ietf.org
Subject: Re: [MMUSIC] Silence Suppression Attribute 


If you're using RTP, it's assumed that silence suppression is possible (and
since receivers have to cope with packet loss anyway, this doesn't add any
significant complexity). 

Colin




--> "Tom-PT Taylor" writes:
>The caller supports G.711 with voice activity detection and silence
>suppression and would like to make that offer.  There is no PCM parameter
>indicating this mode of operation.
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: Wednesday, April 03, 2002 6:23 PM
>To: Dan Firac
>Cc: Taylor, Tom-PT [CAR:B800:EXCH]; mmusic@ietf.org
>Subject: Re: [MMUSIC] Silence Suppression Attribute 
>
>
>What would be the scenario where the new attribute is used? 
>Colin
>
>
>--> "Dan Firac" writes:
>>It's a very good ideea.
>>Anyway, why this attribute was defined for ATM transport type only?
>>Silence suppression, as you pointed below, is an attribute of a codec
>>and has nothing to do with transport.
>>
>>Dan Firac,
>>Software Engineer,
>>RedlineCommunications,
>>Romania.
>>
>>
>>
>>
>>----- Original Message -----
>>From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
>>To: <mmusic@ietf.org>; <megaco@ietf.org>
>>Sent: Wednesday, April 03, 2002 12:10 AM
>>Subject: [MMUSIC] Silence Suppression Attribute
>>
>>
>>> The issue of how to signal silence suppression capability keeps coming
up
>>on
>>> the Megaco list.  The situation is fairly complicated:
>>>  - some codecs come with a pre-defined capability for silence
>suppression.
>>> This capability can be invoked by the appropriate MIME type parameter as
>>> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to
RTP
>>> transport, arguably over UDP only.
>>>  - other codecs like G.711 have no such parameter, yet silence
>suppression
>>> is possible
>>>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
>>> transport only.
>>>
>>> How would people feel about allowing the a=silenceSupp parameter to be
>>used
>>> independently of the transport type?
>>>
>>> Tom Taylor
>>> taylor@nortelnetworks.com
>>> Ph. +1 613 736 0961 (ESN 396 1490)
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic

_______________________________________________
Megaco mailing list
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 Apr  4 09: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 JAA14914
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:07:11 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA02655
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 09: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 IAA01141;
	Thu, 4 Apr 2002 08:51: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 IAA01078
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 08:51:45 -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 IAA14233
	for <megaco@ietf.org>; Thu, 4 Apr 2002 08:51:37 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0S40>; Thu, 4 Apr 2002 08:51:09 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C63@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute
Date: Thu, 4 Apr 2002 08:51:09 -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

Could you clarify what the assumtion is,
Is it,
That its OK to assume that any MG should be able to handle 
Silent Suppression?


Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] FW: [MMUSIC] Silence Suppression Attribute


Is this a workable assumption?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Wednesday, April 03, 2002 6:56 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Dan Firac; mmusic@ietf.org
Subject: Re: [MMUSIC] Silence Suppression Attribute 


If you're using RTP, it's assumed that silence suppression is possible (and
since receivers have to cope with packet loss anyway, this doesn't add any
significant complexity). 

Colin




--> "Tom-PT Taylor" writes:
>The caller supports G.711 with voice activity detection and silence
>suppression and would like to make that offer.  There is no PCM parameter
>indicating this mode of operation.
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: Wednesday, April 03, 2002 6:23 PM
>To: Dan Firac
>Cc: Taylor, Tom-PT [CAR:B800:EXCH]; mmusic@ietf.org
>Subject: Re: [MMUSIC] Silence Suppression Attribute 
>
>
>What would be the scenario where the new attribute is used? 
>Colin
>
>
>--> "Dan Firac" writes:
>>It's a very good ideea.
>>Anyway, why this attribute was defined for ATM transport type only?
>>Silence suppression, as you pointed below, is an attribute of a codec
>>and has nothing to do with transport.
>>
>>Dan Firac,
>>Software Engineer,
>>RedlineCommunications,
>>Romania.
>>
>>
>>
>>
>>----- Original Message -----
>>From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
>>To: <mmusic@ietf.org>; <megaco@ietf.org>
>>Sent: Wednesday, April 03, 2002 12:10 AM
>>Subject: [MMUSIC] Silence Suppression Attribute
>>
>>
>>> The issue of how to signal silence suppression capability keeps coming
up
>>on
>>> the Megaco list.  The situation is fairly complicated:
>>>  - some codecs come with a pre-defined capability for silence
>suppression.
>>> This capability can be invoked by the appropriate MIME type parameter as
>>> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to
RTP
>>> transport, arguably over UDP only.
>>>  - other codecs like G.711 have no such parameter, yet silence
>suppression
>>> is possible
>>>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
>>> transport only.
>>>
>>> How would people feel about allowing the a=silenceSupp parameter to be
>>used
>>> independently of the transport type?
>>>
>>> Tom Taylor
>>> taylor@nortelnetworks.com
>>> Ph. +1 613 736 0961 (ESN 396 1490)
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic

_______________________________________________
Megaco mailing list
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 Apr  4 09:09: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 JAA14963
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:09: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 IAA01371;
	Thu, 4 Apr 2002 08: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 IAA01338
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 08:56:35 -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 IAA14417
	for <megaco@ietf.org>; Thu, 4 Apr 2002 08:56:27 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g34Dtxj12197;
	Thu, 4 Apr 2002 08:55:59 -0500 (EST)
Received: from lucent.com ([192.11.62.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id IAA26289;
	Thu, 4 Apr 2002 08:56:42 -0500 (EST)
Message-ID: <3CAC5B58.7019BE56@lucent.com>
Date: Thu, 04 Apr 2002 08:55: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: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Test Trunks
References: <4D79C746863DD51197690002A52CDA0001E8A246@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------955703531AB9ACFD3E83FBA4"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------955703531AB9ACFD3E83FBA4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

We subitted a TD for trunk testing following T1. 207-2000  We originally
proposed doing the work in T1S1 and submitted it there since the tests
are only regionally standardized. We submitted to ITU Dublin for
information, but the experts in Dublin expressed a preference to have
the work done there and accepted it as a draft of a new annex (not yet
assigned a number).  So there is now an issue as to which group will
standardize it.  No further drafts have been submitted due to my being
busy with other issues.  Some others have expressed interest in working
with us on the details.  One key issue is how much is similar in other
countries and so whether any of the packages can be general.

Tom-PT Taylor wrote:

> Is anyone aware of a package for test trunks?
>
> 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

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------955703531AB9ACFD3E83FBA4
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------955703531AB9ACFD3E83FBA4--


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


From daemon@optimus.ietf.org  Thu Apr  4 09:09: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 JAA14976
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:09:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA02931
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 09:09: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 IAA01371;
	Thu, 4 Apr 2002 08: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 IAA01338
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 08:56:35 -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 IAA14417
	for <megaco@ietf.org>; Thu, 4 Apr 2002 08:56:27 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g34Dtxj12197;
	Thu, 4 Apr 2002 08:55:59 -0500 (EST)
Received: from lucent.com ([192.11.62.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id IAA26289;
	Thu, 4 Apr 2002 08:56:42 -0500 (EST)
Message-ID: <3CAC5B58.7019BE56@lucent.com>
Date: Thu, 04 Apr 2002 08:55: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: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Test Trunks
References: <4D79C746863DD51197690002A52CDA0001E8A246@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------955703531AB9ACFD3E83FBA4"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------955703531AB9ACFD3E83FBA4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

We subitted a TD for trunk testing following T1. 207-2000  We originally
proposed doing the work in T1S1 and submitted it there since the tests
are only regionally standardized. We submitted to ITU Dublin for
information, but the experts in Dublin expressed a preference to have
the work done there and accepted it as a draft of a new annex (not yet
assigned a number).  So there is now an issue as to which group will
standardize it.  No further drafts have been submitted due to my being
busy with other issues.  Some others have expressed interest in working
with us on the details.  One key issue is how much is similar in other
countries and so whether any of the packages can be general.

Tom-PT Taylor wrote:

> Is anyone aware of a package for test trunks?
>
> 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

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------955703531AB9ACFD3E83FBA4
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------955703531AB9ACFD3E83FBA4--


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



From megaco-admin@ietf.org  Thu Apr  4 09: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 JAA15544
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09: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 JAA02277;
	Thu, 4 Apr 2002 09:04: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 JAA02245
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 09:04:14 -0500 (EST)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14756
	for <megaco@ietf.org>; Thu, 4 Apr 2002 09:04:10 -0500 (EST)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id JAA23329;
	Thu, 4 Apr 2002 09:03:28 -0500 (EST)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2ACAM3L8>; Thu, 4 Apr 2002 09:03:28 -0500
Message-ID: <29B5A21C13C8D51190F900805F65B4EC239F9D@rndex50.ottawa.mitel.com>
From: "Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM>
To: "'vbajaj@hss.hns.com'" <vbajaj@hss.hns.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] JAIN Megaco
Date: Thu, 4 Apr 2002 09:03:26 -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 can send a notification to the list when that happens. ...

Please do.  Thanks for clarity on process (... and can't say we didn't try ;-)

-- Peter Blatherwick

-----Original Message-----
From: vbajaj@hss.hns.com [mailto:vbajaj@hss.hns.com]
Sent: April 4, 2002 00:28
To: Blatherwick, Peter
Cc: megaco@ietf.org; 'SERDAR CABUK'
Subject: RE: [Megaco] JAIN Megaco




Peter,
       A sneak peak may not be possible until community review is over. Once the
review is
 completed the document would be put for public review. Anybody can then provide
comments
 and the document can undergo change based on accepted comments. The current
plan is to
 put the document for community review by end of this month. Community review
typically takes
 around 20-21 days unless there are are major comments on it. Subsequent to that
the
document shall be put for public review. I can send a notification to the list
when that happens.

Rgds,

Vikas Bajaj





"Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM> on 04/03/2002 09:30:55 PM

To:   Vikas Bajaj/HSS@HSS
cc:   megaco@ietf.org, "'SERDAR CABUK'" <serdar.cabuk@o2.com.tr>

Subject:  RE: [Megaco] JAIN Megaco




... or even a copy for "sneak peak" (as opposed to review-ready) ...

I would certainly be interested in getting any visibility currently available,
as there is nothing accessible on the JAIN web site I could find.

-- Peter Blatherwick

-----Original Message-----
From: SERDAR CABUK [mailto:serdar.cabuk@o2.com.tr]
Sent: April 3, 2002 11:25
To: vbajaj@hss.hns.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] JAIN Megaco



Thank you,

So what is the time frame of this process? Do you have any idea when the RI
will be opened for community review?

Regards,

Serdar Cabuk




                    vbajaj@hss.hns
                    .com                 To:     "SERDAR CABUK"
<serdar.cabuk@o2.com.tr>
                                         cc:     megaco@ietf.org
                    04/03/2002           Subject:     Re: [Megaco] JAIN Megaco
                    06:12 PM








Serdar,
           The JAIN MEGACO API document is in the development stage. A
majority
of the
  work has been completed. We expect it to go for JAIN community review
very
soon.
 Subsequent to the community review, it shall be put for public review and
Reference
Implementation shall be developed in parallel.

Rgds,

Vikas Bajaj





"SERDAR CABUK" <serdar.cabuk@o2.com.tr> on 04/03/2002 01:13:35 PM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  [Megaco] JAIN Megaco





Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



_______________________________________________
Megaco mailing 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 Apr  4 09:24: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 JAA15554
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:24:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA03696
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 09: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 JAA02277;
	Thu, 4 Apr 2002 09:04: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 JAA02245
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 09:04:14 -0500 (EST)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14756
	for <megaco@ietf.org>; Thu, 4 Apr 2002 09:04:10 -0500 (EST)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id JAA23329;
	Thu, 4 Apr 2002 09:03:28 -0500 (EST)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2ACAM3L8>; Thu, 4 Apr 2002 09:03:28 -0500
Message-ID: <29B5A21C13C8D51190F900805F65B4EC239F9D@rndex50.ottawa.mitel.com>
From: "Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM>
To: "'vbajaj@hss.hns.com'" <vbajaj@hss.hns.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] JAIN Megaco
Date: Thu, 4 Apr 2002 09:03:26 -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 can send a notification to the list when that happens. ...

Please do.  Thanks for clarity on process (... and can't say we didn't try ;-)

-- Peter Blatherwick

-----Original Message-----
From: vbajaj@hss.hns.com [mailto:vbajaj@hss.hns.com]
Sent: April 4, 2002 00:28
To: Blatherwick, Peter
Cc: megaco@ietf.org; 'SERDAR CABUK'
Subject: RE: [Megaco] JAIN Megaco




Peter,
       A sneak peak may not be possible until community review is over. Once the
review is
 completed the document would be put for public review. Anybody can then provide
comments
 and the document can undergo change based on accepted comments. The current
plan is to
 put the document for community review by end of this month. Community review
typically takes
 around 20-21 days unless there are are major comments on it. Subsequent to that
the
document shall be put for public review. I can send a notification to the list
when that happens.

Rgds,

Vikas Bajaj





"Blatherwick, Peter" <Peter_Blatherwick@Mitel.COM> on 04/03/2002 09:30:55 PM

To:   Vikas Bajaj/HSS@HSS
cc:   megaco@ietf.org, "'SERDAR CABUK'" <serdar.cabuk@o2.com.tr>

Subject:  RE: [Megaco] JAIN Megaco




... or even a copy for "sneak peak" (as opposed to review-ready) ...

I would certainly be interested in getting any visibility currently available,
as there is nothing accessible on the JAIN web site I could find.

-- Peter Blatherwick

-----Original Message-----
From: SERDAR CABUK [mailto:serdar.cabuk@o2.com.tr]
Sent: April 3, 2002 11:25
To: vbajaj@hss.hns.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] JAIN Megaco



Thank you,

So what is the time frame of this process? Do you have any idea when the RI
will be opened for community review?

Regards,

Serdar Cabuk




                    vbajaj@hss.hns
                    .com                 To:     "SERDAR CABUK"
<serdar.cabuk@o2.com.tr>
                                         cc:     megaco@ietf.org
                    04/03/2002           Subject:     Re: [Megaco] JAIN Megaco
                    06:12 PM








Serdar,
           The JAIN MEGACO API document is in the development stage. A
majority
of the
  work has been completed. We expect it to go for JAIN community review
very
soon.
 Subsequent to the community review, it shall be put for public review and
Reference
Implementation shall be developed in parallel.

Rgds,

Vikas Bajaj





"SERDAR CABUK" <serdar.cabuk@o2.com.tr> on 04/03/2002 01:13:35 PM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  [Megaco] JAIN Megaco





Do you know the status of the JAIN Megaco referance implementation? Any
comments..

Serdar Cabuk



_______________________________________________
Megaco mailing 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 Apr  4 09:26: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 JAA15628
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:26: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 JAA03100;
	Thu, 4 Apr 2002 09:10: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 JAA03061
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 09:10:51 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15048
	for <megaco@ietf.org>; Thu, 4 Apr 2002 09:10:45 -0500 (EST)
From: sargupta@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 g34E7a315112;
	Thu, 4 Apr 2002 19:37:36 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B91.004D5294 ; Thu, 4 Apr 2002 19:34:34 +0530
X-Lotus-FromDomain: HSS
To: Carl Rutter <crutter@telica.com>
cc: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B91.004D51DA.00@sandesh.hss.hns.com>
Date: Thu, 4 Apr 2002 19:37:05 +0530
Subject: RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute
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
   I have a doubt in this assumption that a handling packet loss would have a
limit. I mean the MG (DSP) can handle the packet loss upto a certain extent only
and the silence period may be a long one. If the silence suppression is on and
the DSP is indicated so it will generate Comfort Noise, which it might not in
case of packet loss where it might try to replay/reconstruct the previous voice
frames.

Regards
Sarika






Carl Rutter <crutter@telica.com> on 04/04/2002 07:21:09 PM

To:   "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, "'megaco@ietf.org'"
      <megaco@ietf.org>
cc:    (bcc: Sarika Gupta/HSS)

Subject:  RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute




Could you clarify what the assumtion is,
Is it,
That its OK to assume that any MG should be able to handle
Silent Suppression?


Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] FW: [MMUSIC] Silence Suppression Attribute


Is this a workable assumption?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Wednesday, April 03, 2002 6:56 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Dan Firac; mmusic@ietf.org
Subject: Re: [MMUSIC] Silence Suppression Attribute


If you're using RTP, it's assumed that silence suppression is possible (and
since receivers have to cope with packet loss anyway, this doesn't add any
significant complexity).

Colin




--> "Tom-PT Taylor" writes:
>The caller supports G.711 with voice activity detection and silence
>suppression and would like to make that offer.  There is no PCM parameter
>indicating this mode of operation.
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: Wednesday, April 03, 2002 6:23 PM
>To: Dan Firac
>Cc: Taylor, Tom-PT [CAR:B800:EXCH]; mmusic@ietf.org
>Subject: Re: [MMUSIC] Silence Suppression Attribute
>
>
>What would be the scenario where the new attribute is used?
>Colin
>
>
>--> "Dan Firac" writes:
>>It's a very good ideea.
>>Anyway, why this attribute was defined for ATM transport type only?
>>Silence suppression, as you pointed below, is an attribute of a codec
>>and has nothing to do with transport.
>>
>>Dan Firac,
>>Software Engineer,
>>RedlineCommunications,
>>Romania.
>>
>>
>>
>>
>>----- Original Message -----
>>From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
>>To: <mmusic@ietf.org>; <megaco@ietf.org>
>>Sent: Wednesday, April 03, 2002 12:10 AM
>>Subject: [MMUSIC] Silence Suppression Attribute
>>
>>
>>> The issue of how to signal silence suppression capability keeps coming
up
>>on
>>> the Megaco list.  The situation is fairly complicated:
>>>  - some codecs come with a pre-defined capability for silence
>suppression.
>>> This capability can be invoked by the appropriate MIME type parameter as
>>> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to
RTP
>>> transport, arguably over UDP only.
>>>  - other codecs like G.711 have no such parameter, yet silence
>suppression
>>> is possible
>>>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
>>> transport only.
>>>
>>> How would people feel about allowing the a=silenceSupp parameter to be
>>used
>>> independently of the transport type?
>>>
>>> Tom Taylor
>>> taylor@nortelnetworks.com
>>> Ph. +1 613 736 0961 (ESN 396 1490)
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic

_______________________________________________
Megaco mailing 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 Apr  4 09:26: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 JAA15638
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:26:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA03842
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 09:26: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 JAA03100;
	Thu, 4 Apr 2002 09:10: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 JAA03061
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 09:10:51 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15048
	for <megaco@ietf.org>; Thu, 4 Apr 2002 09:10:45 -0500 (EST)
From: sargupta@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 g34E7a315112;
	Thu, 4 Apr 2002 19:37:36 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B91.004D5294 ; Thu, 4 Apr 2002 19:34:34 +0530
X-Lotus-FromDomain: HSS
To: Carl Rutter <crutter@telica.com>
cc: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Message-ID: <65256B91.004D51DA.00@sandesh.hss.hns.com>
Date: Thu, 4 Apr 2002 19:37:05 +0530
Subject: RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute
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
   I have a doubt in this assumption that a handling packet loss would have a
limit. I mean the MG (DSP) can handle the packet loss upto a certain extent only
and the silence period may be a long one. If the silence suppression is on and
the DSP is indicated so it will generate Comfort Noise, which it might not in
case of packet loss where it might try to replay/reconstruct the previous voice
frames.

Regards
Sarika






Carl Rutter <crutter@telica.com> on 04/04/2002 07:21:09 PM

To:   "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, "'megaco@ietf.org'"
      <megaco@ietf.org>
cc:    (bcc: Sarika Gupta/HSS)

Subject:  RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute




Could you clarify what the assumtion is,
Is it,
That its OK to assume that any MG should be able to handle
Silent Suppression?


Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] FW: [MMUSIC] Silence Suppression Attribute


Is this a workable assumption?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Wednesday, April 03, 2002 6:56 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Dan Firac; mmusic@ietf.org
Subject: Re: [MMUSIC] Silence Suppression Attribute


If you're using RTP, it's assumed that silence suppression is possible (and
since receivers have to cope with packet loss anyway, this doesn't add any
significant complexity).

Colin




--> "Tom-PT Taylor" writes:
>The caller supports G.711 with voice activity detection and silence
>suppression and would like to make that offer.  There is no PCM parameter
>indicating this mode of operation.
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: Wednesday, April 03, 2002 6:23 PM
>To: Dan Firac
>Cc: Taylor, Tom-PT [CAR:B800:EXCH]; mmusic@ietf.org
>Subject: Re: [MMUSIC] Silence Suppression Attribute
>
>
>What would be the scenario where the new attribute is used?
>Colin
>
>
>--> "Dan Firac" writes:
>>It's a very good ideea.
>>Anyway, why this attribute was defined for ATM transport type only?
>>Silence suppression, as you pointed below, is an attribute of a codec
>>and has nothing to do with transport.
>>
>>Dan Firac,
>>Software Engineer,
>>RedlineCommunications,
>>Romania.
>>
>>
>>
>>
>>----- Original Message -----
>>From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
>>To: <mmusic@ietf.org>; <megaco@ietf.org>
>>Sent: Wednesday, April 03, 2002 12:10 AM
>>Subject: [MMUSIC] Silence Suppression Attribute
>>
>>
>>> The issue of how to signal silence suppression capability keeps coming
up
>>on
>>> the Megaco list.  The situation is fairly complicated:
>>>  - some codecs come with a pre-defined capability for silence
>suppression.
>>> This capability can be invoked by the appropriate MIME type parameter as
>>> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to
RTP
>>> transport, arguably over UDP only.
>>>  - other codecs like G.711 have no such parameter, yet silence
>suppression
>>> is possible
>>>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
>>> transport only.
>>>
>>> How would people feel about allowing the a=silenceSupp parameter to be
>>used
>>> independently of the transport type?
>>>
>>> Tom Taylor
>>> taylor@nortelnetworks.com
>>> Ph. +1 613 736 0961 (ESN 396 1490)
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic

_______________________________________________
Megaco mailing 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 Apr  4 09: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 JAA15955
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:34: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 JAA03263;
	Thu, 4 Apr 2002 09:14: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 JAA03233
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 09:14:31 -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 JAA15225
	for <megaco@ietf.org>; Thu, 4 Apr 2002 09:14:27 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g34EDwq19260;
	Thu, 4 Apr 2002 09:13:58 -0500 (EST)
Received: from lucent.com (tla.lra.lucent.com [192.11.62.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA26689;
	Thu, 4 Apr 2002 09:14:42 -0500 (EST)
Message-ID: <3CAC5F7C.BB5F9F77@lucent.com>
Date: Thu, 04 Apr 2002 09:13:16 -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: Y Hu <yh86us@yahoo.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Re: Unique ContextId and TerminationId?
References: <20020404111105.76481.qmail@web12608.mail.yahoo.com>
Content-Type: multipart/mixed;
 boundary="------------069D0F92905821A60067A124"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------069D0F92905821A60067A124
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

MGC can Modify a termination using a NULL contextID.  NULL is not a
wildcard and MG does not choose a normal context id in this case.  The
termination is left in the NULL context.

Or MGC can Add a termination using a CHOOSE contextID.  In this case MG
generates a contextID that is unique to the MG and returns it in the
response.

The task of matching the response to the request is done by using the
transactionID (assigned by MGC) along with the fact that commands in a
transaction must be performed in order and the responses must follow the
same order.  Thus MGC can identify the command response that
corresponded to the command that used CHOOSE.

Y Hu wrote:

> Hi,
>
> According to the spec, the ContextID is unique to
> identify the action, but the context ID is assigned by
> the MG. When the MGC sends a first action request to
> the MG, it uses a null context ID. How can the MGC
> maintain the action identification uniquely with the
> null Context ID? How can the MGC match a reply action
> to the original request action as the context ID has
> been changed (assigned by the MG)?
>
> Also, the termination ID is provisioned at MG, does
> the MGC has the knowledge of the termination IDs
> before sending request, or does the MGC reply the MG
> to assign the termination ID as well?
>
> Thank you.
>
> yh
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Tax Center - online filing with TurboTax
> http://taxes.yahoo.com/
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------069D0F92905821A60067A124
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------069D0F92905821A60067A124--


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


From daemon@optimus.ietf.org  Thu Apr  4 09:34: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 JAA15964
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:34:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA04727
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 09: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 JAA03263;
	Thu, 4 Apr 2002 09:14: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 JAA03233
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 09:14:31 -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 JAA15225
	for <megaco@ietf.org>; Thu, 4 Apr 2002 09:14:27 -0500 (EST)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g34EDwq19260;
	Thu, 4 Apr 2002 09:13:58 -0500 (EST)
Received: from lucent.com (tla.lra.lucent.com [192.11.62.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA26689;
	Thu, 4 Apr 2002 09:14:42 -0500 (EST)
Message-ID: <3CAC5F7C.BB5F9F77@lucent.com>
Date: Thu, 04 Apr 2002 09:13:16 -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: Y Hu <yh86us@yahoo.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] Re: Unique ContextId and TerminationId?
References: <20020404111105.76481.qmail@web12608.mail.yahoo.com>
Content-Type: multipart/mixed;
 boundary="------------069D0F92905821A60067A124"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------069D0F92905821A60067A124
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

MGC can Modify a termination using a NULL contextID.  NULL is not a
wildcard and MG does not choose a normal context id in this case.  The
termination is left in the NULL context.

Or MGC can Add a termination using a CHOOSE contextID.  In this case MG
generates a contextID that is unique to the MG and returns it in the
response.

The task of matching the response to the request is done by using the
transactionID (assigned by MGC) along with the fact that commands in a
transaction must be performed in order and the responses must follow the
same order.  Thus MGC can identify the command response that
corresponded to the command that used CHOOSE.

Y Hu wrote:

> Hi,
>
> According to the spec, the ContextID is unique to
> identify the action, but the context ID is assigned by
> the MG. When the MGC sends a first action request to
> the MG, it uses a null context ID. How can the MGC
> maintain the action identification uniquely with the
> null Context ID? How can the MGC match a reply action
> to the original request action as the context ID has
> been changed (assigned by the MG)?
>
> Also, the termination ID is provisioned at MG, does
> the MGC has the knowledge of the termination IDs
> before sending request, or does the MGC reply the MG
> to assign the termination ID as well?
>
> Thank you.
>
> yh
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Tax Center - online filing with TurboTax
> http://taxes.yahoo.com/
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------069D0F92905821A60067A124
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------069D0F92905821A60067A124--


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



From megaco-admin@ietf.org  Thu Apr  4 09: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 JAA17349
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09: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 JAA04105;
	Thu, 4 Apr 2002 09: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 VAA13578
	for <megaco@optimus.ietf.org>; Wed, 3 Apr 2002 21:06:16 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21257;
	Wed, 3 Apr 2002 21:06:13 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.6/8.11.6) with ESMTP id g3424bj75993;
	Wed, 3 Apr 2002 18:04:37 -0800 (PST)
	(envelope-from casner@packetdesign.com)
Date: Wed, 3 Apr 2002 18:05:44 -0800 (PST)
From: Stephen Casner <casner@packetdesign.com>
To: Tom-PT Taylor <taylor@nortelnetworks.com>
cc: <mmusic@ietf.org>, <megaco@ietf.org>
In-Reply-To: <200204032356.g33NuL19000845@purple.nge.isi.edu>
Message-ID: <20020403165246.Q48839-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Megaco] Re: [MMUSIC] Silence Suppression 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

This reply is both to this thread in MMUSIC and to one from the Megaco
list titled "Local/Remote descriptors and Permanent terminations" that
Tom cc'd to me.

On Tue, 2 Apr 2002, Tom-PT Taylor wrote:

> The issue of how to signal silence suppression capability keeps coming up on
> the Megaco list.  The situation is fairly complicated:
>  - some codecs come with a pre-defined capability for silence suppression.
> This capability can be invoked by the appropriate MIME type parameter as
> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to RTP
> transport, arguably over UDP only.
>  - other codecs like G.711 have no such parameter, yet silence suppression
> is possible

As Colin said, for all RTP audio codecs, silence suppression is
assumed to be enabled.  Therefore, we clearly do not need an attribute
to enable silence suppression.  We may or may not need some attribute
to disable silence suppression, but I don't know what scenario
requires that.

A related discussion occurred on the AVT list in November, 2001, with
the subject line "Reg draft-ietf-avt-rtp-mime-05.txt".  At that time,
the sense I got was that some implementations could not handle
receiving an RTP stream with silence suppressed.  My reaction to that
was pretty strong:

    Silence suppression has been a fundamental part of RTP since the
    beginning.  That is why the RTP header carries both a sequence
    number and a timestamp.  Suppressing silence is one of the primary
    reasons for going to packet transmission of voice in the first
    place.  Furthermore, even if the transmitter does not suppress
    silence, the receiver must be prepared to handle the situation
    where there is a frame time for which no packet is present because
    packets may be lost.  Any implementation that has not been
    sufficiently developed to recover reasonably to such a situation
    should be flatly rejected.

Can you explain a situation that is a valid justification for
disabling silence suppression?

>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
> transport only.
>
> How would people feel about allowing the a=silenceSupp parameter to be used
> independently of the transport type?

It may have been a mistake to include the a=silenceSupp attribute for
ATM without considering the problem more generally.  I suspect that
RFC 3108 did not get much attention in MMUSIC because many of the
participants don't care much about ATM.


On Wed, 3 Apr 2002, Tom-PT Taylor wrote:

> To summarize: we are trying to define how to indicate that silence
> suppression is desired for a given audio flow.

More specifically, to indicate when silence suppression is NOT desired.

>  We could do it through an
> a=silenceSupp attribute, through codec-specific a=fmtp: parameters, or
> implicitly by specifying the Comfort Noise codec as an alternative.

We can't add fmtp parameters to an existing payload format after the
fact without incurring backwards compatibility problems.

It is reasonable to interpret the inclusion of the Comfort Noise codec
as a desire or willingness to suppress silence.  However, it is NOT
reasonable to interpret the omission of the Comfort Noise codec as an
indication that silence will not be suppressed.

> I think it's quite clear that we do NOT want to tie silence suppression to
> the TDM package.

What are the requirements for enabling or disabling silence suppression
when using TDM?  What does silence suppression mean when using TDM?

> The cleanest way would be to ensure that every codec where silence
> suppression might apply has a silence suppression parameter.  For RTP, this
> requires revisiting draft-ietf-avt-rtp-mime-06.txt, which is currently in
> IETF Last Call.

As I said above, adding such a parameter would create backwards
compatibility problems.  It's not just a matter of definition.  The
parameters belong to the payload format specification, not to the MIME
registration.

>  Not sure what we do about ATM: RFC 3108 defines a profile
> that just picks up the RTP mappings, so maybe it would also pick up the
> parameters defined in the MIME type registrations and payload format
> descriptions.  I find this whole area murky because theoretically there
> should be new MIME type registrations for each transport in order to reuse
> the profiles in SDP.

It should only be necessary to revise the MIME registrations for a new
transport if additional parameters, encoding considerations, etc, need
to be defined for that new transport.  Many of the MIME registrations
for RTP encodings only cover RTP transport and not email/http
transport because no file format has been defined for those encodings.

> A second possibility is to define the a=silenceSupp attribute for all
> transports, but specify that it takes second priority to a=fmtp parameters
> where these are defined.  This is probably the most practical route.

At MMUSIC in Minneapolis, the need for a "generic format parameters"
attribute was discussed, triggered by the need for a particular
payload type number to indicate the presence of voiceband data.

This would serve (at least at a syntactical level) as a place to put a
"please do not suppress silence" parameter, but since it is ignorable,
it would not guarantee that silence would not be suppressed.  As I
pointed out above, UDP does not guarantee to deliver a packet for
every frame time in any case.

							-- Steve



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


From daemon@optimus.ietf.org  Thu Apr  4 09: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 JAA17360
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:56:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA06096
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 09: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 JAA04105;
	Thu, 4 Apr 2002 09: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 VAA13578
	for <megaco@optimus.ietf.org>; Wed, 3 Apr 2002 21:06:16 -0500 (EST)
Received: from mailman.packetdesign.com (dns.packetdesign.com [65.192.41.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21257;
	Wed, 3 Apr 2002 21:06:13 -0500 (EST)
Received: from ash.packetdesign.com (ash.packetdesign.com [192.168.0.243])
	by mailman.packetdesign.com (8.11.6/8.11.6) with ESMTP id g3424bj75993;
	Wed, 3 Apr 2002 18:04:37 -0800 (PST)
	(envelope-from casner@packetdesign.com)
Date: Wed, 3 Apr 2002 18:05:44 -0800 (PST)
From: Stephen Casner <casner@packetdesign.com>
To: Tom-PT Taylor <taylor@nortelnetworks.com>
cc: <mmusic@ietf.org>, <megaco@ietf.org>
In-Reply-To: <200204032356.g33NuL19000845@purple.nge.isi.edu>
Message-ID: <20020403165246.Q48839-100000@ash.packetdesign.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Megaco] Re: [MMUSIC] Silence Suppression 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

This reply is both to this thread in MMUSIC and to one from the Megaco
list titled "Local/Remote descriptors and Permanent terminations" that
Tom cc'd to me.

On Tue, 2 Apr 2002, Tom-PT Taylor wrote:

> The issue of how to signal silence suppression capability keeps coming up on
> the Megaco list.  The situation is fairly complicated:
>  - some codecs come with a pre-defined capability for silence suppression.
> This capability can be invoked by the appropriate MIME type parameter as
> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to RTP
> transport, arguably over UDP only.
>  - other codecs like G.711 have no such parameter, yet silence suppression
> is possible

As Colin said, for all RTP audio codecs, silence suppression is
assumed to be enabled.  Therefore, we clearly do not need an attribute
to enable silence suppression.  We may or may not need some attribute
to disable silence suppression, but I don't know what scenario
requires that.

A related discussion occurred on the AVT list in November, 2001, with
the subject line "Reg draft-ietf-avt-rtp-mime-05.txt".  At that time,
the sense I got was that some implementations could not handle
receiving an RTP stream with silence suppressed.  My reaction to that
was pretty strong:

    Silence suppression has been a fundamental part of RTP since the
    beginning.  That is why the RTP header carries both a sequence
    number and a timestamp.  Suppressing silence is one of the primary
    reasons for going to packet transmission of voice in the first
    place.  Furthermore, even if the transmitter does not suppress
    silence, the receiver must be prepared to handle the situation
    where there is a frame time for which no packet is present because
    packets may be lost.  Any implementation that has not been
    sufficiently developed to recover reasonably to such a situation
    should be flatly rejected.

Can you explain a situation that is a valid justification for
disabling silence suppression?

>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
> transport only.
>
> How would people feel about allowing the a=silenceSupp parameter to be used
> independently of the transport type?

It may have been a mistake to include the a=silenceSupp attribute for
ATM without considering the problem more generally.  I suspect that
RFC 3108 did not get much attention in MMUSIC because many of the
participants don't care much about ATM.


On Wed, 3 Apr 2002, Tom-PT Taylor wrote:

> To summarize: we are trying to define how to indicate that silence
> suppression is desired for a given audio flow.

More specifically, to indicate when silence suppression is NOT desired.

>  We could do it through an
> a=silenceSupp attribute, through codec-specific a=fmtp: parameters, or
> implicitly by specifying the Comfort Noise codec as an alternative.

We can't add fmtp parameters to an existing payload format after the
fact without incurring backwards compatibility problems.

It is reasonable to interpret the inclusion of the Comfort Noise codec
as a desire or willingness to suppress silence.  However, it is NOT
reasonable to interpret the omission of the Comfort Noise codec as an
indication that silence will not be suppressed.

> I think it's quite clear that we do NOT want to tie silence suppression to
> the TDM package.

What are the requirements for enabling or disabling silence suppression
when using TDM?  What does silence suppression mean when using TDM?

> The cleanest way would be to ensure that every codec where silence
> suppression might apply has a silence suppression parameter.  For RTP, this
> requires revisiting draft-ietf-avt-rtp-mime-06.txt, which is currently in
> IETF Last Call.

As I said above, adding such a parameter would create backwards
compatibility problems.  It's not just a matter of definition.  The
parameters belong to the payload format specification, not to the MIME
registration.

>  Not sure what we do about ATM: RFC 3108 defines a profile
> that just picks up the RTP mappings, so maybe it would also pick up the
> parameters defined in the MIME type registrations and payload format
> descriptions.  I find this whole area murky because theoretically there
> should be new MIME type registrations for each transport in order to reuse
> the profiles in SDP.

It should only be necessary to revise the MIME registrations for a new
transport if additional parameters, encoding considerations, etc, need
to be defined for that new transport.  Many of the MIME registrations
for RTP encodings only cover RTP transport and not email/http
transport because no file format has been defined for those encodings.

> A second possibility is to define the a=silenceSupp attribute for all
> transports, but specify that it takes second priority to a=fmtp parameters
> where these are defined.  This is probably the most practical route.

At MMUSIC in Minneapolis, the need for a "generic format parameters"
attribute was discussed, triggered by the need for a particular
payload type number to indicate the presence of voiceband data.

This would serve (at least at a syntactical level) as a place to put a
"please do not suppress silence" parameter, but since it is ignorable,
it would not guarantee that silence would not be suppressed.  As I
pointed out above, UDP does not guarantee to deliver a packet for
every frame time in any case.

							-- Steve



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



From megaco-admin@ietf.org  Thu Apr  4 09:56: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 JAA17377
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:56: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 JAA03973;
	Thu, 4 Apr 2002 09:30: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 BAA08082
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 01:59:04 -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 BAA27342
	for <megaco@ietf.org>; Thu, 4 Apr 2002 01:59:01 -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 g346wUh05242
	for <megaco@ietf.org>; Thu, 4 Apr 2002 08:58:30 +0200 (MEST)
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 IAA04680
	for <megaco@ietf.org>; Thu, 4 Apr 2002 08:58:18 +0200 (MET DST)
Message-ID: <3CABF7A4.6958CBEC@alcatel.es>
Date: Thu, 04 Apr 2002 08:50:12 +0200
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 <megaco@ietf.org>
Subject: [Megaco] megaco sniffer
Content-Type: multipart/alternative;
 boundary="------------02DEC22EA1E998BF44D6E0EE"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

hi all,

Does anybody know where can I find a free downloadable sniffer
which interprets megaco protocol (unix based if possible)?

Thanks
Fernando


--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



--------------02DEC22EA1E998BF44D6E0EE
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>Does anybody know where can I find a free downloadable sniffer
<br>which interprets megaco protocol (unix based if possible)?
<p>Thanks
<br>Fernando
<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>

--------------02DEC22EA1E998BF44D6E0EE--



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


From daemon@optimus.ietf.org  Thu Apr  4 09:56: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 JAA17387
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 09:56:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA06110
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 09: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 JAA03973;
	Thu, 4 Apr 2002 09:30: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 BAA08082
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 01:59:04 -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 BAA27342
	for <megaco@ietf.org>; Thu, 4 Apr 2002 01:59:01 -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 g346wUh05242
	for <megaco@ietf.org>; Thu, 4 Apr 2002 08:58:30 +0200 (MEST)
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 IAA04680
	for <megaco@ietf.org>; Thu, 4 Apr 2002 08:58:18 +0200 (MET DST)
Message-ID: <3CABF7A4.6958CBEC@alcatel.es>
Date: Thu, 04 Apr 2002 08:50:12 +0200
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 <megaco@ietf.org>
Subject: [Megaco] megaco sniffer
Content-Type: multipart/alternative;
 boundary="------------02DEC22EA1E998BF44D6E0EE"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

hi all,

Does anybody know where can I find a free downloadable sniffer
which interprets megaco protocol (unix based if possible)?

Thanks
Fernando


--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



--------------02DEC22EA1E998BF44D6E0EE
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>Does anybody know where can I find a free downloadable sniffer
<br>which interprets megaco protocol (unix based if possible)?
<p>Thanks
<br>Fernando
<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>

--------------02DEC22EA1E998BF44D6E0EE--



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



From megaco-admin@ietf.org  Thu Apr  4 10:35: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 KAA18921
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 10:35: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 KAA08076;
	Thu, 4 Apr 2002 10: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 JAA05047
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 09:40:16 -0500 (EST)
Received: from ns1.ottawa.alcatel.ca (ns1.ottawa.alcatel.ca [192.75.23.67])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA16448
	for <megaco@ietf.org>; Thu, 4 Apr 2002 09:40:11 -0500 (EST)
Received: (qmail 20703 invoked from network); 4 Apr 2002 14:26:27 -0000
Received: from portal.ottawa.alcatel.ca (HELO mx1.ca.alcatel.com) (192.75.23.76)
  by ns1.ottawa.alcatel.ca with SMTP; 4 Apr 2002 14:26:27 -0000
Received: (qmail 14417 invoked from network); 4 Apr 2002 14:41:53 -0000
Received: (ofmipd 138.120.45.75); 4 Apr 2002 14:41:31 -0000
Received: from alcatel.com by castle.cid.alcatel.com (8.8.8+Sun/SMI-SVR4)
	id JAA05499; Thu, 4 Apr 2002 09:40:04 -0500 (EST)
Date: 4 Apr 2002 09:40:04 -0500
Message-ID: <3CAC65C4.738C58A5@alcatel.com>
From: "Nancy Devin" <nancy.devin@alcatel.com>
To: megaco@ietf.org
Organization: ALcatel CID
X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------028EA3CF7B3F930A2A62D68D"
Subject: [Megaco] Uniqueness of tone Id
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


Hello all,

The Tone Generator Package (Annex E.3) mentions that a tone Id should be
kept consistent with any tone generation for the same tone.  How should
this be interpreted.

Is it that for a given tone Id, the same frequency and cadance should be
use all the time.

Or is it that for a tone frequency and cadance, only one tone id is
defined.

The former interpretation would inforce that a tone Id is unique only
within the context of a package while the latter interpretation would
inforce that the tone Ids are uniqueley defined outside of packages.

Since I already found an example where two tone Ids are defined for a
given tone I am temted to go with the former interpretation but I would
like to have the opinion of others.

In Annex E.7, Call Progress Tones Generator Package, the dial tone has
the id 0x0030 while in the Basic Call Progress Tones Generator with
directionality, the tone Id corresponding to dial tone is 0x0040.

thanks in advance,
Nancy


--
Nancy Devin
Software Designer

Alcatel
600 March Road, P.O. Box 13600
Kanata, Ontario, Canada
K2K 2E6

Telephone: (613) 591-3600 x6897
Fax:       (613) 599-3609
Internet:  nancy.devin@alcatel.com



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Hello all,
<p>The Tone Generator Package (Annex E.3) mentions that a tone Id should
be kept consistent with any tone generation for the same tone.&nbsp; How
should this be interpreted.
<p>Is it that for a given tone Id, the same frequency and cadance should
be use all the time.
<p>Or is it that for a tone frequency and cadance, only one tone id is
defined.
<p>The former interpretation would inforce that a tone Id is unique only
within the context of a package while the latter interpretation would inforce
that the tone Ids are uniqueley defined outside of packages.
<p>Since I already found an example where two tone Ids are defined for
a given tone I am temted to go with the former interpretation but I would
like to have the opinion of others.
<p>In Annex E.7, Call Progress Tones Generator Package, the dial tone has
the id 0x0030 while in the Basic Call Progress Tones Generator with directionality,
the tone Id corresponding to dial tone is 0x0040.
<p>thanks in advance,
<br>Nancy
<br>&nbsp;
<pre>--&nbsp;
Nancy Devin
Software Designer

Alcatel
600 March Road, P.O. Box 13600
Kanata, Ontario, Canada
K2K 2E6

Telephone: (613) 591-3600 x6897
Fax:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (613) 599-3609
Internet:&nbsp; nancy.devin@alcatel.com</pre>
&nbsp;</html>

--------------028EA3CF7B3F930A2A62D68D--



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


From daemon@optimus.ietf.org  Thu Apr  4 10:35: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 KAA18931
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 10:35:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA09454
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 10:35: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 KAA08076;
	Thu, 4 Apr 2002 10: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 JAA05047
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 09:40:16 -0500 (EST)
Received: from ns1.ottawa.alcatel.ca (ns1.ottawa.alcatel.ca [192.75.23.67])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA16448
	for <megaco@ietf.org>; Thu, 4 Apr 2002 09:40:11 -0500 (EST)
Received: (qmail 20703 invoked from network); 4 Apr 2002 14:26:27 -0000
Received: from portal.ottawa.alcatel.ca (HELO mx1.ca.alcatel.com) (192.75.23.76)
  by ns1.ottawa.alcatel.ca with SMTP; 4 Apr 2002 14:26:27 -0000
Received: (qmail 14417 invoked from network); 4 Apr 2002 14:41:53 -0000
Received: (ofmipd 138.120.45.75); 4 Apr 2002 14:41:31 -0000
Received: from alcatel.com by castle.cid.alcatel.com (8.8.8+Sun/SMI-SVR4)
	id JAA05499; Thu, 4 Apr 2002 09:40:04 -0500 (EST)
Date: 4 Apr 2002 09:40:04 -0500
Message-ID: <3CAC65C4.738C58A5@alcatel.com>
From: "Nancy Devin" <nancy.devin@alcatel.com>
To: megaco@ietf.org
Organization: ALcatel CID
X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------028EA3CF7B3F930A2A62D68D"
Subject: [Megaco] Uniqueness of tone Id
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


Hello all,

The Tone Generator Package (Annex E.3) mentions that a tone Id should be
kept consistent with any tone generation for the same tone.  How should
this be interpreted.

Is it that for a given tone Id, the same frequency and cadance should be
use all the time.

Or is it that for a tone frequency and cadance, only one tone id is
defined.

The former interpretation would inforce that a tone Id is unique only
within the context of a package while the latter interpretation would
inforce that the tone Ids are uniqueley defined outside of packages.

Since I already found an example where two tone Ids are defined for a
given tone I am temted to go with the former interpretation but I would
like to have the opinion of others.

In Annex E.7, Call Progress Tones Generator Package, the dial tone has
the id 0x0030 while in the Basic Call Progress Tones Generator with
directionality, the tone Id corresponding to dial tone is 0x0040.

thanks in advance,
Nancy


--
Nancy Devin
Software Designer

Alcatel
600 March Road, P.O. Box 13600
Kanata, Ontario, Canada
K2K 2E6

Telephone: (613) 591-3600 x6897
Fax:       (613) 599-3609
Internet:  nancy.devin@alcatel.com



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Hello all,
<p>The Tone Generator Package (Annex E.3) mentions that a tone Id should
be kept consistent with any tone generation for the same tone.&nbsp; How
should this be interpreted.
<p>Is it that for a given tone Id, the same frequency and cadance should
be use all the time.
<p>Or is it that for a tone frequency and cadance, only one tone id is
defined.
<p>The former interpretation would inforce that a tone Id is unique only
within the context of a package while the latter interpretation would inforce
that the tone Ids are uniqueley defined outside of packages.
<p>Since I already found an example where two tone Ids are defined for
a given tone I am temted to go with the former interpretation but I would
like to have the opinion of others.
<p>In Annex E.7, Call Progress Tones Generator Package, the dial tone has
the id 0x0030 while in the Basic Call Progress Tones Generator with directionality,
the tone Id corresponding to dial tone is 0x0040.
<p>thanks in advance,
<br>Nancy
<br>&nbsp;
<pre>--&nbsp;
Nancy Devin
Software Designer

Alcatel
600 March Road, P.O. Box 13600
Kanata, Ontario, Canada
K2K 2E6

Telephone: (613) 591-3600 x6897
Fax:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (613) 599-3609
Internet:&nbsp; nancy.devin@alcatel.com</pre>
&nbsp;</html>

--------------028EA3CF7B3F930A2A62D68D--



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



From megaco-admin@ietf.org  Thu Apr  4 10: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 KAA19967
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 10:54: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 KAA09687;
	Thu, 4 Apr 2002 10: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 KAA09660
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 10:39:40 -0500 (EST)
Received: from demetrius.hosting.pacbell.net (demetrius.hosting.pacbell.net [216.100.99.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19231
	for <megaco@ietf.org>; Thu, 4 Apr 2002 10:39:37 -0500 (EST)
Received: from thomas ([12.36.125.1])
	by demetrius.hosting.pacbell.net
	id KAA02576; Thu, 4 Apr 2002 10:39:16 -0500 (EST)
	[ConcentricHost SMTP Relay 1.14]
From: "Thomas Huang" <thuang@codentnetworks.com>
To: "Fernando Vallejo Lazaro" <Fernando.Vallejo_Lazaro@alcatel.es>,
        "Megaco" <megaco@ietf.org>
Subject: RE: [Megaco] megaco sniffer
Date: Thu, 4 Apr 2002 07:39:22 -0800
Message-ID: <NGEKIGCNLLCKKDMGGBHLKELDCBAA.thuang@codentnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0000_01C1DBAB.D62CB7F0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <3CABF7A4.6958CBEC@alcatel.es>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: megaco-admin@ietf.org
Errors-To: 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_0000_01C1DBAB.D62CB7F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am interested too. Please copy any response to me too.
Thanks
Thomas
PS: do you know any free megaco free software that I could build and look
at?

  -----Original Message-----
  From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fernando Vallejo Lazaro
  Sent: Wednesday, April 03, 2002 10:50 PM
  To: Megaco
  Subject: [Megaco] megaco sniffer


  hi all,
  Does anybody know where can I find a free downloadable sniffer
  which interprets megaco protocol (unix based if possible)?

  Thanks
  Fernando


--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL


------=_NextPart_000_0000_01C1DBAB.D62CB7F0
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D375463715-04042002><FONT face=3DArial color=3D#0000ff =
size=3D2>I am=20
interested too. Please copy any response to me too.</FONT></SPAN></DIV>
<DIV><SPAN class=3D375463715-04042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Thanks</FONT></SPAN></DIV>
<DIV><SPAN class=3D375463715-04042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Thomas</FONT></SPAN></DIV>
<DIV><SPAN class=3D375463715-04042002><FONT face=3DArial color=3D#0000ff =
size=3D2>PS: do=20
you know any free megaco free software that I could build and look=20
at?</FONT></SPAN></DIV>
<DIV><SPAN class=3D375463715-04042002></SPAN>&nbsp;</DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
megaco-admin@ietf.org=20
  [mailto:megaco-admin@ietf.org]<B>On Behalf Of </B>Fernando Vallejo=20
  Lazaro<BR><B>Sent:</B> Wednesday, April 03, 2002 10:50 =
PM<BR><B>To:</B>=20
  Megaco<BR><B>Subject:</B> [Megaco] megaco =
sniffer<BR><BR></FONT></DIV>hi all,=20
  <P>Does anybody know where can I find a free downloadable sniffer =
<BR>which=20
  interprets megaco protocol (unix based if possible)?=20
  <P>Thanks <BR>Fernando <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;=20
</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0000_01C1DBAB.D62CB7F0--


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


From daemon@optimus.ietf.org  Thu Apr  4 10:54: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 KAA19978
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 10:54:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA10588
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 10:54: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 KAA09687;
	Thu, 4 Apr 2002 10: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 KAA09660
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 10:39:40 -0500 (EST)
Received: from demetrius.hosting.pacbell.net (demetrius.hosting.pacbell.net [216.100.99.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19231
	for <megaco@ietf.org>; Thu, 4 Apr 2002 10:39:37 -0500 (EST)
Received: from thomas ([12.36.125.1])
	by demetrius.hosting.pacbell.net
	id KAA02576; Thu, 4 Apr 2002 10:39:16 -0500 (EST)
	[ConcentricHost SMTP Relay 1.14]
From: "Thomas Huang" <thuang@codentnetworks.com>
To: "Fernando Vallejo Lazaro" <Fernando.Vallejo_Lazaro@alcatel.es>,
        "Megaco" <megaco@ietf.org>
Subject: RE: [Megaco] megaco sniffer
Date: Thu, 4 Apr 2002 07:39:22 -0800
Message-ID: <NGEKIGCNLLCKKDMGGBHLKELDCBAA.thuang@codentnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0000_01C1DBAB.D62CB7F0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <3CABF7A4.6958CBEC@alcatel.es>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: megaco-admin@ietf.org
Errors-To: 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_0000_01C1DBAB.D62CB7F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am interested too. Please copy any response to me too.
Thanks
Thomas
PS: do you know any free megaco free software that I could build and look
at?

  -----Original Message-----
  From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fernando Vallejo Lazaro
  Sent: Wednesday, April 03, 2002 10:50 PM
  To: Megaco
  Subject: [Megaco] megaco sniffer


  hi all,
  Does anybody know where can I find a free downloadable sniffer
  which interprets megaco protocol (unix based if possible)?

  Thanks
  Fernando


--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL


------=_NextPart_000_0000_01C1DBAB.D62CB7F0
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D375463715-04042002><FONT face=3DArial color=3D#0000ff =
size=3D2>I am=20
interested too. Please copy any response to me too.</FONT></SPAN></DIV>
<DIV><SPAN class=3D375463715-04042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Thanks</FONT></SPAN></DIV>
<DIV><SPAN class=3D375463715-04042002><FONT face=3DArial color=3D#0000ff =

size=3D2>Thomas</FONT></SPAN></DIV>
<DIV><SPAN class=3D375463715-04042002><FONT face=3DArial color=3D#0000ff =
size=3D2>PS: do=20
you know any free megaco free software that I could build and look=20
at?</FONT></SPAN></DIV>
<DIV><SPAN class=3D375463715-04042002></SPAN>&nbsp;</DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
megaco-admin@ietf.org=20
  [mailto:megaco-admin@ietf.org]<B>On Behalf Of </B>Fernando Vallejo=20
  Lazaro<BR><B>Sent:</B> Wednesday, April 03, 2002 10:50 =
PM<BR><B>To:</B>=20
  Megaco<BR><B>Subject:</B> [Megaco] megaco =
sniffer<BR><BR></FONT></DIV>hi all,=20
  <P>Does anybody know where can I find a free downloadable sniffer =
<BR>which=20
  interprets megaco protocol (unix based if possible)?=20
  <P>Thanks <BR>Fernando <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;=20
</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0000_01C1DBAB.D62CB7F0--


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



From megaco-admin@ietf.org  Thu Apr  4 10:57: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 KAA20103
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 10: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 KAA09388;
	Thu, 4 Apr 2002 10:35: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 KAA09357
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 10:34:58 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18895
	for <megaco@ietf.org>; Thu, 4 Apr 2002 10:34: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 g34FYPP24962
	for <megaco@ietf.org>; Thu, 4 Apr 2002 10:34:26 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LAQN1>; Thu, 4 Apr 2002 10:34:28 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A253@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] FW: [MMUSIC] Silence Suppression Attribute
Date: Thu, 4 Apr 2002 10:34: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

That's right.  In fact, Stephen Casner made the point forcefully: the real
issue is how to turn off silence suppression (if there is a requirement).
Dan Firac has expressed such a requirement on the MMUSIC list.  We'll see
what comes of the discussion.

-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Thursday, April 04, 2002 8:51 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; 'megaco@ietf.org'
Subject: RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute


Could you clarify what the assumtion is,
Is it,
That its OK to assume that any MG should be able to handle 
Silent Suppression?


Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] FW: [MMUSIC] Silence Suppression Attribute


Is this a workable assumption?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Wednesday, April 03, 2002 6:56 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Dan Firac; mmusic@ietf.org
Subject: Re: [MMUSIC] Silence Suppression Attribute 


If you're using RTP, it's assumed that silence suppression is possible (and
since receivers have to cope with packet loss anyway, this doesn't add any
significant complexity). 

Colin




--> "Tom-PT Taylor" writes:
>The caller supports G.711 with voice activity detection and silence
>suppression and would like to make that offer.  There is no PCM parameter
>indicating this mode of operation.
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: Wednesday, April 03, 2002 6:23 PM
>To: Dan Firac
>Cc: Taylor, Tom-PT [CAR:B800:EXCH]; mmusic@ietf.org
>Subject: Re: [MMUSIC] Silence Suppression Attribute 
>
>
>What would be the scenario where the new attribute is used? 
>Colin
>
>
>--> "Dan Firac" writes:
>>It's a very good ideea.
>>Anyway, why this attribute was defined for ATM transport type only?
>>Silence suppression, as you pointed below, is an attribute of a codec
>>and has nothing to do with transport.
>>
>>Dan Firac,
>>Software Engineer,
>>RedlineCommunications,
>>Romania.
>>
>>
>>
>>
>>----- Original Message -----
>>From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
>>To: <mmusic@ietf.org>; <megaco@ietf.org>
>>Sent: Wednesday, April 03, 2002 12:10 AM
>>Subject: [MMUSIC] Silence Suppression Attribute
>>
>>
>>> The issue of how to signal silence suppression capability keeps coming
up
>>on
>>> the Megaco list.  The situation is fairly complicated:
>>>  - some codecs come with a pre-defined capability for silence
>suppression.
>>> This capability can be invoked by the appropriate MIME type parameter as
>>> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to
RTP
>>> transport, arguably over UDP only.
>>>  - other codecs like G.711 have no such parameter, yet silence
>suppression
>>> is possible
>>>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
>>> transport only.
>>>
>>> How would people feel about allowing the a=silenceSupp parameter to be
>>used
>>> independently of the transport type?
>>>
>>> Tom Taylor
>>> taylor@nortelnetworks.com
>>> Ph. +1 613 736 0961 (ESN 396 1490)
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic

_______________________________________________
Megaco mailing list
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 Apr  4 10: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 KAA20116
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 10:57:09 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA10728
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 10:57: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 KAA09388;
	Thu, 4 Apr 2002 10:35: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 KAA09357
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 10:34:58 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18895
	for <megaco@ietf.org>; Thu, 4 Apr 2002 10:34: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 g34FYPP24962
	for <megaco@ietf.org>; Thu, 4 Apr 2002 10:34:26 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LAQN1>; Thu, 4 Apr 2002 10:34:28 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A253@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] FW: [MMUSIC] Silence Suppression Attribute
Date: Thu, 4 Apr 2002 10:34: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

That's right.  In fact, Stephen Casner made the point forcefully: the real
issue is how to turn off silence suppression (if there is a requirement).
Dan Firac has expressed such a requirement on the MMUSIC list.  We'll see
what comes of the discussion.

-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Thursday, April 04, 2002 8:51 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; 'megaco@ietf.org'
Subject: RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute


Could you clarify what the assumtion is,
Is it,
That its OK to assume that any MG should be able to handle 
Silent Suppression?


Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] FW: [MMUSIC] Silence Suppression Attribute


Is this a workable assumption?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Wednesday, April 03, 2002 6:56 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Dan Firac; mmusic@ietf.org
Subject: Re: [MMUSIC] Silence Suppression Attribute 


If you're using RTP, it's assumed that silence suppression is possible (and
since receivers have to cope with packet loss anyway, this doesn't add any
significant complexity). 

Colin




--> "Tom-PT Taylor" writes:
>The caller supports G.711 with voice activity detection and silence
>suppression and would like to make that offer.  There is no PCM parameter
>indicating this mode of operation.
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: Wednesday, April 03, 2002 6:23 PM
>To: Dan Firac
>Cc: Taylor, Tom-PT [CAR:B800:EXCH]; mmusic@ietf.org
>Subject: Re: [MMUSIC] Silence Suppression Attribute 
>
>
>What would be the scenario where the new attribute is used? 
>Colin
>
>
>--> "Dan Firac" writes:
>>It's a very good ideea.
>>Anyway, why this attribute was defined for ATM transport type only?
>>Silence suppression, as you pointed below, is an attribute of a codec
>>and has nothing to do with transport.
>>
>>Dan Firac,
>>Software Engineer,
>>RedlineCommunications,
>>Romania.
>>
>>
>>
>>
>>----- Original Message -----
>>From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
>>To: <mmusic@ietf.org>; <megaco@ietf.org>
>>Sent: Wednesday, April 03, 2002 12:10 AM
>>Subject: [MMUSIC] Silence Suppression Attribute
>>
>>
>>> The issue of how to signal silence suppression capability keeps coming
up
>>on
>>> the Megaco list.  The situation is fairly complicated:
>>>  - some codecs come with a pre-defined capability for silence
>suppression.
>>> This capability can be invoked by the appropriate MIME type parameter as
>>> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to
RTP
>>> transport, arguably over UDP only.
>>>  - other codecs like G.711 have no such parameter, yet silence
>suppression
>>> is possible
>>>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
>>> transport only.
>>>
>>> How would people feel about allowing the a=silenceSupp parameter to be
>>used
>>> independently of the transport type?
>>>
>>> Tom Taylor
>>> taylor@nortelnetworks.com
>>> Ph. +1 613 736 0961 (ESN 396 1490)
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic

_______________________________________________
Megaco mailing list
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 Apr  4 11:17: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 LAA20987
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 11:17: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 LAA11546;
	Thu, 4 Apr 2002 11:03: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 LAA11517
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 11:03:19 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20388
	for <megaco@ietf.org>; Thu, 4 Apr 2002 11:03:16 -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 g34G2lJ11617
	for <megaco@ietf.org>; Thu, 4 Apr 2002 11:02:48 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LARL3>; Thu, 4 Apr 2002 11:02:49 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A256@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] Re: Unique ContextId and TerminationId?
Date: Thu, 4 Apr 2002 11:02: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

On your first point, the matching is done via the TransactionID.  The reply
to the transaction is matched against the request and the returned contextID
is picked up based on the position of the action in the response.

On your second point, the MGC has to be provisioned with at least some
knowledge of terminationIDs in the MG, so it knows how to handle calls
involving them and so it can route to them.

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 04, 2002 6:11 AM
To: megaco@ietf.org
Subject: [Megaco] Re: Unique ContextId and TerminationId?


Hi,

According to the spec, the ContextID is unique to
identify the action, but the context ID is assigned by
the MG. When the MGC sends a first action request to
the MG, it uses a null context ID. How can the MGC
maintain the action identification uniquely with the
null Context ID? How can the MGC match a reply action
to the original request action as the context ID has 
been changed (assigned by the MG)?

Also, the termination ID is provisioned at MG, does
the MGC has the knowledge of the termination IDs
before sending request, or does the MGC reply the MG
to assign the termination ID as well?

Thank you.

yh

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.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@optimus.ietf.org  Thu Apr  4 11:17: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 LAA20998
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 11:17:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA12149
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 11:17: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 LAA11546;
	Thu, 4 Apr 2002 11:03: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 LAA11517
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 11:03:19 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20388
	for <megaco@ietf.org>; Thu, 4 Apr 2002 11:03:16 -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 g34G2lJ11617
	for <megaco@ietf.org>; Thu, 4 Apr 2002 11:02:48 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LARL3>; Thu, 4 Apr 2002 11:02:49 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A256@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] Re: Unique ContextId and TerminationId?
Date: Thu, 4 Apr 2002 11:02: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

On your first point, the matching is done via the TransactionID.  The reply
to the transaction is matched against the request and the returned contextID
is picked up based on the position of the action in the response.

On your second point, the MGC has to be provisioned with at least some
knowledge of terminationIDs in the MG, so it knows how to handle calls
involving them and so it can route to them.

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 04, 2002 6:11 AM
To: megaco@ietf.org
Subject: [Megaco] Re: Unique ContextId and TerminationId?


Hi,

According to the spec, the ContextID is unique to
identify the action, but the context ID is assigned by
the MG. When the MGC sends a first action request to
the MG, it uses a null context ID. How can the MGC
maintain the action identification uniquely with the
null Context ID? How can the MGC match a reply action
to the original request action as the context ID has 
been changed (assigned by the MG)?

Also, the termination ID is provisioned at MG, does
the MGC has the knowledge of the termination IDs
before sending request, or does the MGC reply the MG
to assign the termination ID as well?

Thank you.

yh

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.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  Thu Apr  4 11:19: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 LAA21066
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 11:19: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 KAA10942;
	Thu, 4 Apr 2002 10:59: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 KAA10913
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 10:59:39 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20234
	for <megaco@ietf.org>; Thu, 4 Apr 2002 10:59: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 g34Fx8J11243
	for <megaco@ietf.org>; Thu, 4 Apr 2002 10:59:08 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LARG4>; Thu, 4 Apr 2002 10:59:10 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A255@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Dan Elbert'" <delbert@radvision.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Do signals stop when termination is subtracted?
Date: Thu, 4 Apr 2002 10:59:07 -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

They stop.  This is equivalent to a replacement of the Signals Descriptor.

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Thursday, April 04, 2002 3:18 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Do signals stop when termination is subtracted?


According to the the spec:

-   When a provisioned Termination is Subtracted from a context, its
   property values shall revert to:

   *  the default value, if specified for the property and not
      overridden by provisioning,
   *  otherwise, the provisioned value.

The question is, what happens with signals playing on a termination when is
subtracted? Do they stop (as seems to be implied by "properties values
reverting to default" ) or do they keep playing?
Thanks

Dan Elbert
RADVISION

_______________________________________________
Megaco mailing list
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 Apr  4 11:19: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 LAA21076
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 11:19:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA12263
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 11:19: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 KAA10942;
	Thu, 4 Apr 2002 10:59: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 KAA10913
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 10:59:39 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20234
	for <megaco@ietf.org>; Thu, 4 Apr 2002 10:59: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 g34Fx8J11243
	for <megaco@ietf.org>; Thu, 4 Apr 2002 10:59:08 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LARG4>; Thu, 4 Apr 2002 10:59:10 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A255@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Dan Elbert'" <delbert@radvision.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] Do signals stop when termination is subtracted?
Date: Thu, 4 Apr 2002 10:59:07 -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

They stop.  This is equivalent to a replacement of the Signals Descriptor.

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Thursday, April 04, 2002 3:18 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Do signals stop when termination is subtracted?


According to the the spec:

-   When a provisioned Termination is Subtracted from a context, its
   property values shall revert to:

   *  the default value, if specified for the property and not
      overridden by provisioning,
   *  otherwise, the provisioned value.

The question is, what happens with signals playing on a termination when is
subtracted? Do they stop (as seems to be implied by "properties values
reverting to default" ) or do they keep playing?
Thanks

Dan Elbert
RADVISION

_______________________________________________
Megaco mailing list
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 Apr  4 11:26: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 LAA21318
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 11:26: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 LAA11736;
	Thu, 4 Apr 2002 11:08: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 LAA11704
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 11:08:23 -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 LAA20617
	for <megaco@ietf.org>; Thu, 4 Apr 2002 11:08:19 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0TN8>; Thu, 4 Apr 2002 11:07:52 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C73@wench>
From: Carl Rutter <crutter@telica.com>
To: "'sargupta@hss.hns.com'" <sargupta@hss.hns.com>,
        Carl Rutter
	 <crutter@telica.com>
Cc: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute
Date: Thu, 4 Apr 2002 11:07:48 -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'll have to agree with Sarika on this
that from the DSPs perspective 
they are different cases as he stated.

-----Original Message-----
From: sargupta@hss.hns.com [mailto:sargupta@hss.hns.com]
Sent: Thursday, April 04, 2002 9:07 AM
To: Carl Rutter
Cc: 'Tom-PT Taylor'; 'megaco@ietf.org'
Subject: RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute




Hi
   I have a doubt in this assumption that a handling packet loss would have
a
limit. I mean the MG (DSP) can handle the packet loss upto a certain extent
only
and the silence period may be a long one. If the silence suppression is on
and
the DSP is indicated so it will generate Comfort Noise, which it might not
in
case of packet loss where it might try to replay/reconstruct the previous
voice
frames.

Regards
Sarika






Carl Rutter <crutter@telica.com> on 04/04/2002 07:21:09 PM

To:   "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, "'megaco@ietf.org'"
      <megaco@ietf.org>
cc:    (bcc: Sarika Gupta/HSS)

Subject:  RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute




Could you clarify what the assumtion is,
Is it,
That its OK to assume that any MG should be able to handle
Silent Suppression?


Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] FW: [MMUSIC] Silence Suppression Attribute


Is this a workable assumption?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Wednesday, April 03, 2002 6:56 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Dan Firac; mmusic@ietf.org
Subject: Re: [MMUSIC] Silence Suppression Attribute


If you're using RTP, it's assumed that silence suppression is possible (and
since receivers have to cope with packet loss anyway, this doesn't add any
significant complexity).

Colin




--> "Tom-PT Taylor" writes:
>The caller supports G.711 with voice activity detection and silence
>suppression and would like to make that offer.  There is no PCM parameter
>indicating this mode of operation.
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: Wednesday, April 03, 2002 6:23 PM
>To: Dan Firac
>Cc: Taylor, Tom-PT [CAR:B800:EXCH]; mmusic@ietf.org
>Subject: Re: [MMUSIC] Silence Suppression Attribute
>
>
>What would be the scenario where the new attribute is used?
>Colin
>
>
>--> "Dan Firac" writes:
>>It's a very good ideea.
>>Anyway, why this attribute was defined for ATM transport type only?
>>Silence suppression, as you pointed below, is an attribute of a codec
>>and has nothing to do with transport.
>>
>>Dan Firac,
>>Software Engineer,
>>RedlineCommunications,
>>Romania.
>>
>>
>>
>>
>>----- Original Message -----
>>From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
>>To: <mmusic@ietf.org>; <megaco@ietf.org>
>>Sent: Wednesday, April 03, 2002 12:10 AM
>>Subject: [MMUSIC] Silence Suppression Attribute
>>
>>
>>> The issue of how to signal silence suppression capability keeps coming
up
>>on
>>> the Megaco list.  The situation is fairly complicated:
>>>  - some codecs come with a pre-defined capability for silence
>suppression.
>>> This capability can be invoked by the appropriate MIME type parameter as
>>> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to
RTP
>>> transport, arguably over UDP only.
>>>  - other codecs like G.711 have no such parameter, yet silence
>suppression
>>> is possible
>>>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
>>> transport only.
>>>
>>> How would people feel about allowing the a=silenceSupp parameter to be
>>used
>>> independently of the transport type?
>>>
>>> Tom Taylor
>>> taylor@nortelnetworks.com
>>> Ph. +1 613 736 0961 (ESN 396 1490)
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic

_______________________________________________
Megaco mailing 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 Apr  4 11:26: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 LAA21328
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 11:26:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA12502
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 11: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 LAA11736;
	Thu, 4 Apr 2002 11:08: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 LAA11704
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 11:08:23 -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 LAA20617
	for <megaco@ietf.org>; Thu, 4 Apr 2002 11:08:19 -0500 (EST)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <GQDA0TN8>; Thu, 4 Apr 2002 11:07:52 -0500
Message-ID: <2415C206C515244DBFB12EC0C064A448404C73@wench>
From: Carl Rutter <crutter@telica.com>
To: "'sargupta@hss.hns.com'" <sargupta@hss.hns.com>,
        Carl Rutter
	 <crutter@telica.com>
Cc: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute
Date: Thu, 4 Apr 2002 11:07:48 -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'll have to agree with Sarika on this
that from the DSPs perspective 
they are different cases as he stated.

-----Original Message-----
From: sargupta@hss.hns.com [mailto:sargupta@hss.hns.com]
Sent: Thursday, April 04, 2002 9:07 AM
To: Carl Rutter
Cc: 'Tom-PT Taylor'; 'megaco@ietf.org'
Subject: RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute




Hi
   I have a doubt in this assumption that a handling packet loss would have
a
limit. I mean the MG (DSP) can handle the packet loss upto a certain extent
only
and the silence period may be a long one. If the silence suppression is on
and
the DSP is indicated so it will generate Comfort Noise, which it might not
in
case of packet loss where it might try to replay/reconstruct the previous
voice
frames.

Regards
Sarika






Carl Rutter <crutter@telica.com> on 04/04/2002 07:21:09 PM

To:   "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, "'megaco@ietf.org'"
      <megaco@ietf.org>
cc:    (bcc: Sarika Gupta/HSS)

Subject:  RE: [Megaco] FW: [MMUSIC] Silence Suppression Attribute




Could you clarify what the assumtion is,
Is it,
That its OK to assume that any MG should be able to handle
Silent Suppression?


Carl

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 6:58 PM
To: 'megaco@ietf.org'
Subject: [Megaco] FW: [MMUSIC] Silence Suppression Attribute


Is this a workable assumption?

-----Original Message-----
From: Colin Perkins [mailto:csp@isi.edu]
Sent: Wednesday, April 03, 2002 6:56 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: Dan Firac; mmusic@ietf.org
Subject: Re: [MMUSIC] Silence Suppression Attribute


If you're using RTP, it's assumed that silence suppression is possible (and
since receivers have to cope with packet loss anyway, this doesn't add any
significant complexity).

Colin




--> "Tom-PT Taylor" writes:
>The caller supports G.711 with voice activity detection and silence
>suppression and would like to make that offer.  There is no PCM parameter
>indicating this mode of operation.
>
>-----Original Message-----
>From: Colin Perkins [mailto:csp@isi.edu]
>Sent: Wednesday, April 03, 2002 6:23 PM
>To: Dan Firac
>Cc: Taylor, Tom-PT [CAR:B800:EXCH]; mmusic@ietf.org
>Subject: Re: [MMUSIC] Silence Suppression Attribute
>
>
>What would be the scenario where the new attribute is used?
>Colin
>
>
>--> "Dan Firac" writes:
>>It's a very good ideea.
>>Anyway, why this attribute was defined for ATM transport type only?
>>Silence suppression, as you pointed below, is an attribute of a codec
>>and has nothing to do with transport.
>>
>>Dan Firac,
>>Software Engineer,
>>RedlineCommunications,
>>Romania.
>>
>>
>>
>>
>>----- Original Message -----
>>From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
>>To: <mmusic@ietf.org>; <megaco@ietf.org>
>>Sent: Wednesday, April 03, 2002 12:10 AM
>>Subject: [MMUSIC] Silence Suppression Attribute
>>
>>
>>> The issue of how to signal silence suppression capability keeps coming
up
>>on
>>> the Megaco list.  The situation is fairly complicated:
>>>  - some codecs come with a pre-defined capability for silence
>suppression.
>>> This capability can be invoked by the appropriate MIME type parameter as
>>> defined in draft-ietf-avt-rtp-mime-06.txt.  That draft is specific to
RTP
>>> transport, arguably over UDP only.
>>>  - other codecs like G.711 have no such parameter, yet silence
>suppression
>>> is possible
>>>  - RFC 3108 defined an a=silenceSupp attribute, but it applies to ATM
>>> transport only.
>>>
>>> How would people feel about allowing the a=silenceSupp parameter to be
>>used
>>> independently of the transport type?
>>>
>>> Tom Taylor
>>> taylor@nortelnetworks.com
>>> Ph. +1 613 736 0961 (ESN 396 1490)
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mmusic
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic

_______________________________________________
Megaco mailing 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 Apr  4 12:01: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 MAA22831
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 12:01: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 LAA13971;
	Thu, 4 Apr 2002 11:43: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 LAA13882
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 11:43:02 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22049
	for <megaco@ietf.org>; Thu, 4 Apr 2002 11:42: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 g34GgTv17790
	for <megaco@ietf.org>; Thu, 4 Apr 2002 11:42:30 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LATD8>; Thu, 4 Apr 2002 11:42:31 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A259@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 4 Apr 2002 11:42:22 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] List Membership Availability
Sender: megaco-admin@ietf.org
Errors-To: 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 trying to get a list of Megaco E-mail members by E-mail for
administrative purposes and was unable to do so.  I checked the relevant
privacy option by web and discovered to my surprise that the list is
available only to me (if I figure out the syntax).  I have three choices:
 - membership list is available to anyone
 - membership list is available to list members using their passwords
 - membership list is available to administrator only using password

What do you want me to set?

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 Apr  4 12:01: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 MAA22848
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 12:01:06 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA15943
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 12:01: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 LAA13971;
	Thu, 4 Apr 2002 11:43: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 LAA13882
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 11:43:02 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22049
	for <megaco@ietf.org>; Thu, 4 Apr 2002 11:42: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 g34GgTv17790
	for <megaco@ietf.org>; Thu, 4 Apr 2002 11:42:30 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LATD8>; Thu, 4 Apr 2002 11:42:31 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A259@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 4 Apr 2002 11:42:22 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] List Membership Availability
Sender: megaco-admin@ietf.org
Errors-To: 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 trying to get a list of Megaco E-mail members by E-mail for
administrative purposes and was unable to do so.  I checked the relevant
privacy option by web and discovered to my surprise that the list is
available only to me (if I figure out the syntax).  I have three choices:
 - membership list is available to anyone
 - membership list is available to list members using their passwords
 - membership list is available to administrator only using password

What do you want me to set?

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 Apr  4 12:22: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 MAA24110
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 12:22: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 MAA16524;
	Thu, 4 Apr 2002 12:04: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 MAA16492
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 12:04:36 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23122
	for <megaco@ietf.org>; Thu, 4 Apr 2002 12:04:32 -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 g34H45v19428
	for <megaco@ietf.org>; Thu, 4 Apr 2002 12:04:05 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LATXB>; Thu, 4 Apr 2002 12:04:07 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A25A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 4 Apr 2002 12:04:03 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] List Membership Availability
Sender: megaco-admin@ietf.org
Errors-To: 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 responses I've had so far all say I keep the list available only to
myself.  Scott Bradner advises me open availability is not an option.  I
will leave things as they are.

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 Apr  4 12:22: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 MAA24121
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 12:22:32 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA17750
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 12: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 MAA16524;
	Thu, 4 Apr 2002 12:04: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 MAA16492
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 12:04:36 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23122
	for <megaco@ietf.org>; Thu, 4 Apr 2002 12:04:32 -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 g34H45v19428
	for <megaco@ietf.org>; Thu, 4 Apr 2002 12:04:05 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LATXB>; Thu, 4 Apr 2002 12:04:07 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A25A@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 4 Apr 2002 12:04:03 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] List Membership Availability
Sender: megaco-admin@ietf.org
Errors-To: 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 responses I've had so far all say I keep the list available only to
myself.  Scott Bradner advises me open availability is not an option.  I
will leave things as they are.

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 Apr  4 12: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 MAA24337
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 12:26: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 MAA17086;
	Thu, 4 Apr 2002 12: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 MAA17053
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 12:11:18 -0500 (EST)
Received: from mail.integralaccess.com (mail.integralaccess.com [63.160.25.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23581
	for <megaco@ietf.org>; Thu, 4 Apr 2002 12:11:14 -0500 (EST)
Received: from MTAM [192.168.250.69] by mail.integralaccess.com with ESMTP
  (SMTPD32-7.05) id A905266F00DC; Thu, 04 Apr 2002 12:10:29 -0500
From: "Mimi Tam" <mtam@integralaccess.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
Subject: RE: [Megaco] List Membership Availability
Date: Thu, 4 Apr 2002 12:10:26 -0500
Message-ID: <002f01c1dbfb$9da40190$45faa8c0@MTAM>
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 V6.00.2600.0000
Importance: Normal
In-Reply-To: <4D79C746863DD51197690002A52CDA0001E8A259@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

I'd vote for the 1st choice:

 - membership list is available to anyone

Thanks...Mimi Tam

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Tom-PT Taylor
Sent: Thursday, April 04, 2002 11:42 AM
To: 'megaco@ietf.org'
Subject: [Megaco] List Membership Availability


I was trying to get a list of Megaco E-mail members by E-mail for
administrative purposes and was unable to do so.  I checked the relevant
privacy option by web and discovered to my surprise that the list is
available only to me (if I figure out the syntax).  I have three
choices:
 - membership list is available to anyone
 - membership list is available to list members using their passwords
 - membership list is available to administrator only using password

What do you want me to set?

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  Thu Apr  4 12:26: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 MAA24348
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 12:26:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA18069
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 12: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 MAA17086;
	Thu, 4 Apr 2002 12: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 MAA17053
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 12:11:18 -0500 (EST)
Received: from mail.integralaccess.com (mail.integralaccess.com [63.160.25.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23581
	for <megaco@ietf.org>; Thu, 4 Apr 2002 12:11:14 -0500 (EST)
Received: from MTAM [192.168.250.69] by mail.integralaccess.com with ESMTP
  (SMTPD32-7.05) id A905266F00DC; Thu, 04 Apr 2002 12:10:29 -0500
From: "Mimi Tam" <mtam@integralaccess.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
Subject: RE: [Megaco] List Membership Availability
Date: Thu, 4 Apr 2002 12:10:26 -0500
Message-ID: <002f01c1dbfb$9da40190$45faa8c0@MTAM>
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 V6.00.2600.0000
Importance: Normal
In-Reply-To: <4D79C746863DD51197690002A52CDA0001E8A259@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

I'd vote for the 1st choice:

 - membership list is available to anyone

Thanks...Mimi Tam

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Tom-PT Taylor
Sent: Thursday, April 04, 2002 11:42 AM
To: 'megaco@ietf.org'
Subject: [Megaco] List Membership Availability


I was trying to get a list of Megaco E-mail members by E-mail for
administrative purposes and was unable to do so.  I checked the relevant
privacy option by web and discovered to my surprise that the list is
available only to me (if I figure out the syntax).  I have three
choices:
 - membership list is available to anyone
 - membership list is available to list members using their passwords
 - membership list is available to administrator only using password

What do you want me to set?

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  Thu Apr  4 12:58: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 MAA28398
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 12:58: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 MAA19358;
	Thu, 4 Apr 2002 12:42: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 MAA19310
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 12:42:15 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24986
	for <megaco@ietf.org>; Thu, 4 Apr 2002 12:42:13 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.10.2/8.10.2) id g34HgFI15837;
	Thu, 4 Apr 2002 12:42:15 -0500 (EST)
Date: Thu, 4 Apr 2002 12:42:15 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200204041742.g34HgFI15837@newdev.harvard.edu>
To: megaco@ietf.org, mtam@integralaccess.com, taylor@nortelnetworks.com
Subject: RE: [Megaco] List Membership Availability
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

>  - membership list is available to anyone

the IESG is not happy with this spammer-support option

Scott

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


From daemon@optimus.ietf.org  Thu Apr  4 12:58: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 MAA28407
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 12:58:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA20203
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 12: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 MAA19358;
	Thu, 4 Apr 2002 12:42: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 MAA19310
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 12:42:15 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24986
	for <megaco@ietf.org>; Thu, 4 Apr 2002 12:42:13 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.10.2/8.10.2) id g34HgFI15837;
	Thu, 4 Apr 2002 12:42:15 -0500 (EST)
Date: Thu, 4 Apr 2002 12:42:15 -0500 (EST)
From: Scott  Bradner <sob@harvard.edu>
Message-Id: <200204041742.g34HgFI15837@newdev.harvard.edu>
To: megaco@ietf.org, mtam@integralaccess.com, taylor@nortelnetworks.com
Subject: RE: [Megaco] List Membership Availability
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

>  - membership list is available to anyone

the IESG is not happy with this spammer-support option

Scott

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



From megaco-admin@ietf.org  Thu Apr  4 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 OAA05906
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 14:37: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 OAA25748;
	Thu, 4 Apr 2002 14:17: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 OAA25720
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 14:16:58 -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 OAA04796
	for <megaco@ietf.org>; Thu, 4 Apr 2002 14:16:49 -0500 (EST)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.37 2002/04/01 17:50:55 root Exp $) with ESMTP id g34JI1v15714
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:18:01 GMT
Received: from fmsmsxvs042.fm.intel.com (fmsmsxv042-1.fm.intel.com [132.233.48.110])
	by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.15 2002/04/01 17:51:48 root Exp $) with SMTP id g34JI0m25810
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:18:00 GMT
Received: from FMSMSX017.fm.intel.com ([132.233.42.196])
 by fmsmsxvs042.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002040411202908479
 for <megaco@ietf.org>; Thu, 04 Apr 2002 11:20:29 -0800
Received: by fmsmsx017.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <HWMJJM9J>; Thu, 4 Apr 2002 11:16:43 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D501874813B@FMSMSX37>
From: "Kaul, Bharat" <bharat@trillium.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] List Membership Availability
Date: Thu, 4 Apr 2002 11:16:33 -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 am ok with 2 & 3 in that order. Not ok with 1

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, April 04, 2002 8:42 AM
To: 'megaco@ietf.org'
Subject: [Megaco] List Membership Availability


I was trying to get a list of Megaco E-mail members by E-mail for
administrative purposes and was unable to do so.  I checked the relevant
privacy option by web and discovered to my surprise that the list is
available only to me (if I figure out the syntax).  I have three choices:
 - membership list is available to anyone
 - membership list is available to list members using their passwords
 - membership list is available to administrator only using password

What do you want me to set?

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  Thu Apr  4 14:39: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 OAA06017
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 14:39: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 OAA25706;
	Thu, 4 Apr 2002 14:16: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 OAA25678
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 14:16:49 -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 OAA04792
	for <megaco@ietf.org>; Thu, 4 Apr 2002 14:16:46 -0500 (EST)
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g34JGB501032;
	Thu, 4 Apr 2002 14:16:12 -0500 (EST)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GVX405LS>; Thu, 4 Apr 2002 14:16:12 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C02B3AF8C@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: Nancy Devin <nancy.devin@alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Uniqueness of tone Id
Date: Thu, 4 Apr 2002 14:16:10 -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

Many tones are physically the same, but have different meanings given the
context they are used in.  Also, the same (logical) tone can have different
physical characteristics, dependent upon the region in which the tone is
being generated.  As a good example, consider ringback when you make a local
call, versus ringback when you call overseas.

So linking tone ID to the actual physical definition of the tone is contrary
to how the tone definitions have been done in H.248.  The packages have
defined signals based on their logical definition, not their physical
definition.  So both definitions presented are not correct.  For a
particular request of a signal, the MG should know how to generate that
signal.  I can envision an MG that provides more than one toneset, and which
termination a given signal is being played upon would indicate which toneset
to use.

So, I would take the first definition, and append "for a given termination"
to it:

"For a given tone Id, the same frequency and cadance should be used all the
time for a given termination."

Kevin

-----Original Message-----
From: Nancy Devin [mailto:nancy.devin@alcatel.com]
Sent: Thursday, April 04, 2002 9:40 AM
To: megaco@ietf.org
Subject: [Megaco] Uniqueness of tone Id


  
Hello all, 
The Tone Generator Package (Annex E.3) mentions that a tone Id should be
kept consistent with any tone generation for the same tone.  How should this
be interpreted. 
Is it that for a given tone Id, the same frequency and cadance should be use
all the time. 
Or is it that for a tone frequency and cadance, only one tone id is defined.

The former interpretation would inforce that a tone Id is unique only within
the context of a package while the latter interpretation would inforce that
the tone Ids are uniqueley defined outside of packages. 
Since I already found an example where two tone Ids are defined for a given
tone I am temted to go with the former interpretation but I would like to
have the opinion of others. 
In Annex E.7, Call Progress Tones Generator Package, the dial tone has the
id 0x0030 while in the Basic Call Progress Tones Generator with
directionality, the tone Id corresponding to dial tone is 0x0040. 
thanks in advance, 
Nancy 
  
-- 
Nancy Devin
Software Designer

Alcatel
600 March Road, P.O. Box 13600
Kanata, Ontario, Canada
K2K 2E6

Telephone: (613) 591-3600 x6897
Fax:       (613) 599-3609
Internet:  nancy.devin@alcatel.com
  

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


From daemon@optimus.ietf.org  Thu Apr  4 14:39: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 OAA06028
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 14:39:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA27262
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 14:39: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 OAA25706;
	Thu, 4 Apr 2002 14:16: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 OAA25678
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 14:16:49 -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 OAA04792
	for <megaco@ietf.org>; Thu, 4 Apr 2002 14:16:46 -0500 (EST)
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g34JGB501032;
	Thu, 4 Apr 2002 14:16:12 -0500 (EST)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GVX405LS>; Thu, 4 Apr 2002 14:16:12 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C02B3AF8C@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: Nancy Devin <nancy.devin@alcatel.com>, megaco@ietf.org
Subject: RE: [Megaco] Uniqueness of tone Id
Date: Thu, 4 Apr 2002 14:16:10 -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

Many tones are physically the same, but have different meanings given the
context they are used in.  Also, the same (logical) tone can have different
physical characteristics, dependent upon the region in which the tone is
being generated.  As a good example, consider ringback when you make a local
call, versus ringback when you call overseas.

So linking tone ID to the actual physical definition of the tone is contrary
to how the tone definitions have been done in H.248.  The packages have
defined signals based on their logical definition, not their physical
definition.  So both definitions presented are not correct.  For a
particular request of a signal, the MG should know how to generate that
signal.  I can envision an MG that provides more than one toneset, and which
termination a given signal is being played upon would indicate which toneset
to use.

So, I would take the first definition, and append "for a given termination"
to it:

"For a given tone Id, the same frequency and cadance should be used all the
time for a given termination."

Kevin

-----Original Message-----
From: Nancy Devin [mailto:nancy.devin@alcatel.com]
Sent: Thursday, April 04, 2002 9:40 AM
To: megaco@ietf.org
Subject: [Megaco] Uniqueness of tone Id


  
Hello all, 
The Tone Generator Package (Annex E.3) mentions that a tone Id should be
kept consistent with any tone generation for the same tone.  How should this
be interpreted. 
Is it that for a given tone Id, the same frequency and cadance should be use
all the time. 
Or is it that for a tone frequency and cadance, only one tone id is defined.

The former interpretation would inforce that a tone Id is unique only within
the context of a package while the latter interpretation would inforce that
the tone Ids are uniqueley defined outside of packages. 
Since I already found an example where two tone Ids are defined for a given
tone I am temted to go with the former interpretation but I would like to
have the opinion of others. 
In Annex E.7, Call Progress Tones Generator Package, the dial tone has the
id 0x0030 while in the Basic Call Progress Tones Generator with
directionality, the tone Id corresponding to dial tone is 0x0040. 
thanks in advance, 
Nancy 
  
-- 
Nancy Devin
Software Designer

Alcatel
600 March Road, P.O. Box 13600
Kanata, Ontario, Canada
K2K 2E6

Telephone: (613) 591-3600 x6897
Fax:       (613) 599-3609
Internet:  nancy.devin@alcatel.com
  

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



From megaco-admin@ietf.org  Thu Apr  4 14: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 OAA06510
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 14: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 OAA27007;
	Thu, 4 Apr 2002 14:35: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 OAA26978
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 14:35:23 -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 OAA05840
	for <megaco@ietf.org>; Thu, 4 Apr 2002 14:35:14 -0500 (EST)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.37 2002/04/01 17:50:55 root Exp $) with ESMTP id g34JaWV27817
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:36:32 GMT
Received: from fmsmsxvs041.fm.intel.com (fmsmsxv041-1.fm.intel.com [132.233.48.109])
	by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.15 2002/04/01 17:51:48 root Exp $) with SMTP id g34JaVC12794
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:36:31 GMT
Received: from fmsmsx019.fm.intel.com ([132.233.42.130])
 by fmsmsxvs041.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002040411354418516
 for <megaco@ietf.org>; Thu, 04 Apr 2002 11:35:44 -0800
Received: by fmsmsx019.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <H303JCCK>; Thu, 4 Apr 2002 11:35:14 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D50153F5D47@FMSMSX37>
From: "Jaiswal, Vivek" <v_jaiswal@trillium.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 4 Apr 2002 11:35:04 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] IPv4-IPv6 interworking in 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

Hi
If the MGC1 asks the MG to build association with MGC2, it will provide the
transport address of MGC2 using the "mgcIdToTry" field. This may be as a
part of handoff or service change reply. 

Now, lets assume that the MG has support for only IPv4. And MGC has support
for only IPv6. And both were talking through a inter-working device.

In such a scenario, the "mgcIdToTry" field would be carrying a IPv6 address.
How do we handle this in MEGACO?

Vivek 
 

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


From daemon@optimus.ietf.org  Thu Apr  4 14: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 OAA06522
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 14:56:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA27844
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 14:56: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 OAA27007;
	Thu, 4 Apr 2002 14:35: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 OAA26978
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 14:35:23 -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 OAA05840
	for <megaco@ietf.org>; Thu, 4 Apr 2002 14:35:14 -0500 (EST)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.37 2002/04/01 17:50:55 root Exp $) with ESMTP id g34JaWV27817
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:36:32 GMT
Received: from fmsmsxvs041.fm.intel.com (fmsmsxv041-1.fm.intel.com [132.233.48.109])
	by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.15 2002/04/01 17:51:48 root Exp $) with SMTP id g34JaVC12794
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:36:31 GMT
Received: from fmsmsx019.fm.intel.com ([132.233.42.130])
 by fmsmsxvs041.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002040411354418516
 for <megaco@ietf.org>; Thu, 04 Apr 2002 11:35:44 -0800
Received: by fmsmsx019.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <H303JCCK>; Thu, 4 Apr 2002 11:35:14 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D50153F5D47@FMSMSX37>
From: "Jaiswal, Vivek" <v_jaiswal@trillium.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 4 Apr 2002 11:35:04 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] IPv4-IPv6 interworking in 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

Hi
If the MGC1 asks the MG to build association with MGC2, it will provide the
transport address of MGC2 using the "mgcIdToTry" field. This may be as a
part of handoff or service change reply. 

Now, lets assume that the MG has support for only IPv4. And MGC has support
for only IPv6. And both were talking through a inter-working device.

In such a scenario, the "mgcIdToTry" field would be carrying a IPv6 address.
How do we handle this in MEGACO?

Vivek 
 

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



From megaco-admin@ietf.org  Thu Apr  4 15:03: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 PAA06746
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 15:03: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 OAA27395;
	Thu, 4 Apr 2002 14:43: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 OAA27364
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 14:43:43 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06101
	for <megaco@ietf.org>; Thu, 4 Apr 2002 14:43: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 g34JhAP25909
	for <megaco@ietf.org>; Thu, 4 Apr 2002 14:43:11 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LAYNA>; Thu, 4 Apr 2002 14:43:13 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A262@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Jaiswal, Vivek'" <v_jaiswal@trillium.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] IPv4-IPv6 interworking in MEGACO
Date: Thu, 4 Apr 2002 14:43:09 -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 is a logical necessity that something in the path be application-aware
AND able to translate from IPv6 to IPv4.  That would likely be the
interworking box at the moment, or the MGC using the Midcom protocol in the
future.  I don't think it's a Megaco issue.

-----Original Message-----
From: Jaiswal, Vivek [mailto:v_jaiswal@trillium.com]
Sent: Thursday, April 04, 2002 2:35 PM
To: 'megaco@ietf.org'
Subject: [Megaco] IPv4-IPv6 interworking in MEGACO


Hi
If the MGC1 asks the MG to build association with MGC2, it will provide the
transport address of MGC2 using the "mgcIdToTry" field. This may be as a
part of handoff or service change reply. 

Now, lets assume that the MG has support for only IPv4. And MGC has support
for only IPv6. And both were talking through a inter-working device.

In such a scenario, the "mgcIdToTry" field would be carrying a IPv6 address.
How do we handle this in MEGACO?

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@optimus.ietf.org  Thu Apr  4 15:03: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 PAA06756
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 15:03:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA28554
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 15:03: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 OAA27395;
	Thu, 4 Apr 2002 14:43: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 OAA27364
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 14:43:43 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06101
	for <megaco@ietf.org>; Thu, 4 Apr 2002 14:43: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 g34JhAP25909
	for <megaco@ietf.org>; Thu, 4 Apr 2002 14:43:11 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LAYNA>; Thu, 4 Apr 2002 14:43:13 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A262@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Jaiswal, Vivek'" <v_jaiswal@trillium.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] IPv4-IPv6 interworking in MEGACO
Date: Thu, 4 Apr 2002 14:43:09 -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 is a logical necessity that something in the path be application-aware
AND able to translate from IPv6 to IPv4.  That would likely be the
interworking box at the moment, or the MGC using the Midcom protocol in the
future.  I don't think it's a Megaco issue.

-----Original Message-----
From: Jaiswal, Vivek [mailto:v_jaiswal@trillium.com]
Sent: Thursday, April 04, 2002 2:35 PM
To: 'megaco@ietf.org'
Subject: [Megaco] IPv4-IPv6 interworking in MEGACO


Hi
If the MGC1 asks the MG to build association with MGC2, it will provide the
transport address of MGC2 using the "mgcIdToTry" field. This may be as a
part of handoff or service change reply. 

Now, lets assume that the MG has support for only IPv4. And MGC has support
for only IPv6. And both were talking through a inter-working device.

In such a scenario, the "mgcIdToTry" field would be carrying a IPv6 address.
How do we handle this in MEGACO?

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@optimus.ietf.org  Thu Apr  4 15: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 OAA05917
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 14:37:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA27090
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 14:37: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 OAA25748;
	Thu, 4 Apr 2002 14:17: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 OAA25720
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 14:16:58 -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 OAA04796
	for <megaco@ietf.org>; Thu, 4 Apr 2002 14:16:49 -0500 (EST)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.37 2002/04/01 17:50:55 root Exp $) with ESMTP id g34JI1v15714
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:18:01 GMT
Received: from fmsmsxvs042.fm.intel.com (fmsmsxv042-1.fm.intel.com [132.233.48.110])
	by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.15 2002/04/01 17:51:48 root Exp $) with SMTP id g34JI0m25810
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:18:00 GMT
Received: from FMSMSX017.fm.intel.com ([132.233.42.196])
 by fmsmsxvs042.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002040411202908479
 for <megaco@ietf.org>; Thu, 04 Apr 2002 11:20:29 -0800
Received: by fmsmsx017.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <HWMJJM9J>; Thu, 4 Apr 2002 11:16:43 -0800
Message-ID: <F1CE15E08172D4119247009027AE9D501874813B@FMSMSX37>
From: "Kaul, Bharat" <bharat@trillium.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] List Membership Availability
Date: Thu, 4 Apr 2002 11:16:33 -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 am ok with 2 & 3 in that order. Not ok with 1

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Thursday, April 04, 2002 8:42 AM
To: 'megaco@ietf.org'
Subject: [Megaco] List Membership Availability


I was trying to get a list of Megaco E-mail members by E-mail for
administrative purposes and was unable to do so.  I checked the relevant
privacy option by web and discovered to my surprise that the list is
available only to me (if I figure out the syntax).  I have three choices:
 - membership list is available to anyone
 - membership list is available to list members using their passwords
 - membership list is available to administrator only using password

What do you want me to set?

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  Thu Apr  4 18:22: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 SAA12525
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 18: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 RAA08773;
	Thu, 4 Apr 2002 17:56: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 RAA08748
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 17:56:30 -0500 (EST)
Received: from web12603.mail.yahoo.com (web12603.mail.yahoo.com [216.136.173.226])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11911
	for <megaco@ietf.org>; Thu, 4 Apr 2002 17:56:25 -0500 (EST)
Message-ID: <20020404225628.33441.qmail@web12603.mail.yahoo.com>
Received: from [203.26.41.49] by web12603.mail.yahoo.com via HTTP; Thu, 04 Apr 2002 14:56:28 PST
Date: Thu, 4 Apr 2002 14:56:28 -0800 (PST)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
Cc: Tom-PT Taylor <taylor@nortelnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] Re: Unique ContextId and TerminationId?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Thanks Tom and Terry,

> On your second point, the MGC has to be provisioned 
> with at least some knowledge of terminationIDs in
the > MG, so it knows how to handle calls involving
them 
> and so it can route to them.

In other words, the termination ID is assigned by the
MGC actually, thus it maintains its uniqueness through
out the whole process unlike the context ID. Is that
correct?

Thank you.

At 11:02 AM 4/04/2002 -0500, Tom-PT Taylor wrote:
On your first point, the matching is done via the
TransactionID.  The reply
to the transaction is matched against the request and
the returned contextID
is picked up based on the position of the action in
the response.

On your second point, the MGC has to be provisioned
with at least some
knowledge of terminationIDs in the MG, so it knows how
to handle calls
involving them and so it can route to them.

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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


From daemon@optimus.ietf.org  Thu Apr  4 18:22: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 SAA12536
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 18:22:21 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA10243
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 18: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 RAA08773;
	Thu, 4 Apr 2002 17:56: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 RAA08748
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 17:56:30 -0500 (EST)
Received: from web12603.mail.yahoo.com (web12603.mail.yahoo.com [216.136.173.226])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11911
	for <megaco@ietf.org>; Thu, 4 Apr 2002 17:56:25 -0500 (EST)
Message-ID: <20020404225628.33441.qmail@web12603.mail.yahoo.com>
Received: from [203.26.41.49] by web12603.mail.yahoo.com via HTTP; Thu, 04 Apr 2002 14:56:28 PST
Date: Thu, 4 Apr 2002 14:56:28 -0800 (PST)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
Cc: Tom-PT Taylor <taylor@nortelnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] Re: Unique ContextId and TerminationId?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Thanks Tom and Terry,

> On your second point, the MGC has to be provisioned 
> with at least some knowledge of terminationIDs in
the > MG, so it knows how to handle calls involving
them 
> and so it can route to them.

In other words, the termination ID is assigned by the
MGC actually, thus it maintains its uniqueness through
out the whole process unlike the context ID. Is that
correct?

Thank you.

At 11:02 AM 4/04/2002 -0500, Tom-PT Taylor wrote:
On your first point, the matching is done via the
TransactionID.  The reply
to the transaction is matched against the request and
the returned contextID
is picked up based on the position of the action in
the response.

On your second point, the MGC has to be provisioned
with at least some
knowledge of terminationIDs in the MG, so it knows how
to handle calls
involving them and so it can route to them.

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From megaco-admin@ietf.org  Thu Apr  4 18:36: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 SAA12758
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 18:36: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 SAA10175;
	Thu, 4 Apr 2002 18:20: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 SAA10142
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 18:20:36 -0500 (EST)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12503
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:20:30 -0500 (EST)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g34NKRT14950
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:20:27 -0500 (EST)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Date: Thu, 4 Apr 2002 18:20:46 -0500
Message-ID: <003601c1dc2f$59922c50$368910ac@Bala>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0037_01C1DC05.70BC2450"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Subject: [Megaco] Caller Id
Sender: megaco-admin@ietf.org
Errors-To: 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_0037_01C1DC05.70BC2450
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi,
 
Could anyone point me to the package that has the support for Caller ID?
I could not find it from the RFC3015 and the annexures (till M.2).
 
Thanks in advance for your replies.
 
-- Bala

------=_NextPart_000_0037_01C1DC05.70BC2450
Content-Type: text/html;
	charset="US-ASCII"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D489351623-04042002><FONT=20
face=3D"Goudy Old Style">Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=3D489351623-04042002><FONT=20
face=3D"Goudy Old Style"></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D489351623-04042002><FONT face=3D"Goudy Old =
Style">Could anyone=20
point me&nbsp;to the&nbsp;package that has the support for Caller ID? I =
could=20
not find it from the RFC3015 and the annexures (till =
M.2).</FONT></SPAN></DIV>
<DIV><SPAN class=3D489351623-04042002><FONT=20
face=3D"Goudy Old Style"></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D489351623-04042002><FONT face=3D"Goudy Old =
Style">Thanks in=20
advance for your replies.</FONT></SPAN></DIV>
<DIV><FONT face=3D"Goudy Old Style"></FONT>&nbsp;</DIV>
<DIV align=3Dleft><SPAN class=3D489351623-04042002><FONT face=3D"Goudy =
Old Style">--=20
</FONT></SPAN><FONT face=3D"Goudy Old =
Style">Bala</FONT></DIV></BODY></HTML>

------=_NextPart_000_0037_01C1DC05.70BC2450--


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


From daemon@optimus.ietf.org  Thu Apr  4 18:36: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 SAA12771
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 18:36:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA11073
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 18:37: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 SAA10175;
	Thu, 4 Apr 2002 18:20: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 SAA10142
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 18:20:36 -0500 (EST)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12503
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:20:30 -0500 (EST)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g34NKRT14950
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:20:27 -0500 (EST)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Date: Thu, 4 Apr 2002 18:20:46 -0500
Message-ID: <003601c1dc2f$59922c50$368910ac@Bala>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0037_01C1DC05.70BC2450"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Subject: [Megaco] Caller Id
Sender: megaco-admin@ietf.org
Errors-To: 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_0037_01C1DC05.70BC2450
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi,
 
Could anyone point me to the package that has the support for Caller ID?
I could not find it from the RFC3015 and the annexures (till M.2).
 
Thanks in advance for your replies.
 
-- Bala

------=_NextPart_000_0037_01C1DC05.70BC2450
Content-Type: text/html;
	charset="US-ASCII"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D489351623-04042002><FONT=20
face=3D"Goudy Old Style">Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=3D489351623-04042002><FONT=20
face=3D"Goudy Old Style"></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D489351623-04042002><FONT face=3D"Goudy Old =
Style">Could anyone=20
point me&nbsp;to the&nbsp;package that has the support for Caller ID? I =
could=20
not find it from the RFC3015 and the annexures (till =
M.2).</FONT></SPAN></DIV>
<DIV><SPAN class=3D489351623-04042002><FONT=20
face=3D"Goudy Old Style"></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D489351623-04042002><FONT face=3D"Goudy Old =
Style">Thanks in=20
advance for your replies.</FONT></SPAN></DIV>
<DIV><FONT face=3D"Goudy Old Style"></FONT>&nbsp;</DIV>
<DIV align=3Dleft><SPAN class=3D489351623-04042002><FONT face=3D"Goudy =
Old Style">--=20
</FONT></SPAN><FONT face=3D"Goudy Old =
Style">Bala</FONT></DIV></BODY></HTML>

------=_NextPart_000_0037_01C1DC05.70BC2450--


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



From megaco-admin@ietf.org  Thu Apr  4 18:54: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 SAA13080
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 18:54: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 SAA11172;
	Thu, 4 Apr 2002 18:39: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 SAA11141
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 18:39:09 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12829
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:39:04 -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 g34NcVv14997
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:38:31 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LA8P1>; Thu, 4 Apr 2002 18:38:33 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A266@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Date: Thu, 4 Apr 2002 18:38:32 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: Unique ContextId and TerminationId?
Sender: megaco-admin@ietf.org
Errors-To: 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're talking physical terminations here, I assume.  I'll put it this way:
the MG is provisioned with the terminationIDs.  The MGC also knows the
terminationIDs, and can specify them in its requests.  If the terminations
concerned are lines, the MGC has to have a table matching up the line
terminationIDs with telephone numbers and all sorts of other information.
If the terminations are trunks, the MGC has to have (conceptually) a list of
which terminationIDs belong to which trunk groups.  I'm using the traffic
engineering definition of a trunk group here, as a set of circuits all
eligible to carry the same parcel of traffic.

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 04, 2002 5:56 PM
To: megaco@ietf.org
Cc: Taylor, Tom-PT [CAR:B800:EXCH]
Subject: Re: Unique ContextId and TerminationId?


Thanks Tom and Terry,

> On your second point, the MGC has to be provisioned 
> with at least some knowledge of terminationIDs in
the > MG, so it knows how to handle calls involving
them 
> and so it can route to them.

In other words, the termination ID is assigned by the
MGC actually, thus it maintains its uniqueness through
out the whole process unlike the context ID. Is that
correct?

Thank you.

At 11:02 AM 4/04/2002 -0500, Tom-PT Taylor wrote:
On your first point, the matching is done via the
TransactionID.  The reply
to the transaction is matched against the request and
the returned contextID
is picked up based on the position of the action in
the response.

On your second point, the MGC has to be provisioned
with at least some
knowledge of terminationIDs in the MG, so it knows how
to handle calls
involving them and so it can route to them.

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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


From daemon@optimus.ietf.org  Thu Apr  4 18:54: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 SAA13090
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 18:54:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA11986
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 18:54: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 SAA11172;
	Thu, 4 Apr 2002 18:39: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 SAA11141
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 18:39:09 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12829
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:39:04 -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 g34NcVv14997
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:38:31 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LA8P1>; Thu, 4 Apr 2002 18:38:33 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A266@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Date: Thu, 4 Apr 2002 18:38:32 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: Unique ContextId and TerminationId?
Sender: megaco-admin@ietf.org
Errors-To: 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're talking physical terminations here, I assume.  I'll put it this way:
the MG is provisioned with the terminationIDs.  The MGC also knows the
terminationIDs, and can specify them in its requests.  If the terminations
concerned are lines, the MGC has to have a table matching up the line
terminationIDs with telephone numbers and all sorts of other information.
If the terminations are trunks, the MGC has to have (conceptually) a list of
which terminationIDs belong to which trunk groups.  I'm using the traffic
engineering definition of a trunk group here, as a set of circuits all
eligible to carry the same parcel of traffic.

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 04, 2002 5:56 PM
To: megaco@ietf.org
Cc: Taylor, Tom-PT [CAR:B800:EXCH]
Subject: Re: Unique ContextId and TerminationId?


Thanks Tom and Terry,

> On your second point, the MGC has to be provisioned 
> with at least some knowledge of terminationIDs in
the > MG, so it knows how to handle calls involving
them 
> and so it can route to them.

In other words, the termination ID is assigned by the
MGC actually, thus it maintains its uniqueness through
out the whole process unlike the context ID. Is that
correct?

Thank you.

At 11:02 AM 4/04/2002 -0500, Tom-PT Taylor wrote:
On your first point, the matching is done via the
TransactionID.  The reply
to the transaction is matched against the request and
the returned contextID
is picked up based on the position of the action in
the response.

On your second point, the MGC has to be provisioned
with at least some
knowledge of terminationIDs in the MG, so it knows how
to handle calls
involving them and so it can route to them.

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From megaco-admin@ietf.org  Thu Apr  4 18: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 SAA13195
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 18:59: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 SAA11341;
	Thu, 4 Apr 2002 18: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 SAA11309
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 18:41:08 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12859
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:41: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 g34NeZv15030
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:40:35 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LA8PL>; Thu, 4 Apr 2002 18:40:37 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A267@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] Caller Id
Date: Thu, 4 Apr 2002 18:40:36 -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 is in the enhanced alerting package, which has just gone to the IESG.

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Thursday, April 04, 2002 6:21 PM
To: megaco@ietf.org
Subject: [Megaco] Caller Id


Hi,
 
Could anyone point me to the package that has the support for Caller ID? I
could not find it from the RFC3015 and the annexures (till M.2).
 
Thanks in advance for your replies.
 
-- Bala

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


From daemon@optimus.ietf.org  Thu Apr  4 18:59: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 SAA13206
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 18:59:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA12115
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 18:59: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 SAA11341;
	Thu, 4 Apr 2002 18: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 SAA11309
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 18:41:08 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12859
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:41: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 g34NeZv15030
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:40:35 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LA8PL>; Thu, 4 Apr 2002 18:40:37 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A267@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] Caller Id
Date: Thu, 4 Apr 2002 18:40:36 -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 is in the enhanced alerting package, which has just gone to the IESG.

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Thursday, April 04, 2002 6:21 PM
To: megaco@ietf.org
Subject: [Megaco] Caller Id


Hi,
 
Could anyone point me to the package that has the support for Caller ID? I
could not find it from the RFC3015 and the annexures (till M.2).
 
Thanks in advance for your replies.
 
-- Bala

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



From megaco-admin@ietf.org  Thu Apr  4 19:07: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 TAA13389
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 19:07: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 SAA11951;
	Thu, 4 Apr 2002 18:53: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 SAA11918
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 18:53:36 -0500 (EST)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13047
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:53:33 -0500 (EST)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g34NrTT25240
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:53:29 -0500 (EST)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Subject: RE: [Megaco] Caller Id
Date: Thu, 4 Apr 2002 18:53:48 -0500
Message-ID: <004a01c1dc33$f6a473a0$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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <4D79C746863DD51197690002A52CDA0001E8A267@zcard0kc.ca.nortel.com>
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

Thanks Tom, any idea on when it would be RFC-ed?

-- Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Tom-PT Taylor
Sent: Thursday, April 04, 2002 6:41 PM
To: 'Balasubramanian Pitchandi'; megaco@ietf.org
Subject: RE: [Megaco] Caller Id



It is in the enhanced alerting package, which has just gone to the IESG.

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Thursday, April 04, 2002 6:21 PM
To: megaco@ietf.org
Subject: [Megaco] Caller Id


Hi,
 
Could anyone point me to the package that has the support for Caller ID?
I could not find it from the RFC3015 and the annexures (till M.2).
 
Thanks in advance for your replies.
 
-- 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  Thu Apr  4 19:07: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 TAA13400
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 19:07:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA12822
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 19:08: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 SAA11951;
	Thu, 4 Apr 2002 18:53: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 SAA11918
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 18:53:36 -0500 (EST)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13047
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:53:33 -0500 (EST)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g34NrTT25240
	for <megaco@ietf.org>; Thu, 4 Apr 2002 18:53:29 -0500 (EST)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Subject: RE: [Megaco] Caller Id
Date: Thu, 4 Apr 2002 18:53:48 -0500
Message-ID: <004a01c1dc33$f6a473a0$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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <4D79C746863DD51197690002A52CDA0001E8A267@zcard0kc.ca.nortel.com>
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

Thanks Tom, any idea on when it would be RFC-ed?

-- Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Tom-PT Taylor
Sent: Thursday, April 04, 2002 6:41 PM
To: 'Balasubramanian Pitchandi'; megaco@ietf.org
Subject: RE: [Megaco] Caller Id



It is in the enhanced alerting package, which has just gone to the IESG.

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Thursday, April 04, 2002 6:21 PM
To: megaco@ietf.org
Subject: [Megaco] Caller Id


Hi,
 
Could anyone point me to the package that has the support for Caller ID?
I could not find it from the RFC3015 and the annexures (till M.2).
 
Thanks in advance for your replies.
 
-- 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  Thu Apr  4 19: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 TAA13656
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 19:18: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 TAA12761;
	Thu, 4 Apr 2002 19:05: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 TAA12731
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 19:05:39 -0500 (EST)
Received: from web13206.mail.yahoo.com (web13206.mail.yahoo.com [216.136.174.191])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA13317
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:05:36 -0500 (EST)
Message-ID: <20020405000537.23993.qmail@web13206.mail.yahoo.com>
Received: from [47.234.0.52] by web13206.mail.yahoo.com via HTTP; Thu, 04 Apr 2002 16:05:37 PST
Date: Thu, 4 Apr 2002 16:05:37 -0800 (PST)
From: Mc Keny <mckenys@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] Unsuscribe 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

 
 

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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


From daemon@optimus.ietf.org  Thu Apr  4 19: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 TAA13666
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 19:18:18 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA13312
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 19:18: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 TAA12761;
	Thu, 4 Apr 2002 19:05: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 TAA12731
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 19:05:39 -0500 (EST)
Received: from web13206.mail.yahoo.com (web13206.mail.yahoo.com [216.136.174.191])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA13317
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:05:36 -0500 (EST)
Message-ID: <20020405000537.23993.qmail@web13206.mail.yahoo.com>
Received: from [47.234.0.52] by web13206.mail.yahoo.com via HTTP; Thu, 04 Apr 2002 16:05:37 PST
Date: Thu, 4 Apr 2002 16:05:37 -0800 (PST)
From: Mc Keny <mckenys@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] Unsuscribe 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

 
 

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From megaco-admin@ietf.org  Thu Apr  4 19:48: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 TAA14207
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 19:48: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 TAA14392;
	Thu, 4 Apr 2002 19:33: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 TAA14365
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 19:33:24 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14042
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:33:20 -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 g350Wpv17570
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:32:51 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LA8Y3>; Thu, 4 Apr 2002 19:32:53 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A268@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] Caller Id
Date: Thu, 4 Apr 2002 19:32: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

Typically four weeks to IESG approval.  Then it's a matter of the RFC
Editor's queue for the actual RFC number -- perhaps 3 months.

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Thursday, April 04, 2002 6:54 PM
To: megaco@ietf.org
Subject: RE: [Megaco] Caller Id


Thanks Tom, any idea on when it would be RFC-ed?

-- Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Tom-PT Taylor
Sent: Thursday, April 04, 2002 6:41 PM
To: 'Balasubramanian Pitchandi'; megaco@ietf.org
Subject: RE: [Megaco] Caller Id



It is in the enhanced alerting package, which has just gone to the IESG.

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Thursday, April 04, 2002 6:21 PM
To: megaco@ietf.org
Subject: [Megaco] Caller Id


Hi,
 
Could anyone point me to the package that has the support for Caller ID?
I could not find it from the RFC3015 and the annexures (till M.2).
 
Thanks in advance for your replies.
 
-- 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

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


From daemon@optimus.ietf.org  Thu Apr  4 19:48: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 TAA14217
	for <megaco-archive@odin.ietf.org>; Thu, 4 Apr 2002 19:48:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA14893
	for megaco-archive@odin.ietf.org; Thu, 4 Apr 2002 19:48: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 TAA14392;
	Thu, 4 Apr 2002 19:33: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 TAA14365
	for <megaco@optimus.ietf.org>; Thu, 4 Apr 2002 19:33:24 -0500 (EST)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14042
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:33:20 -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 g350Wpv17570
	for <megaco@ietf.org>; Thu, 4 Apr 2002 19:32:51 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LA8Y3>; Thu, 4 Apr 2002 19:32:53 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A268@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Balasubramanian Pitchandi'" <bs@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] Caller Id
Date: Thu, 4 Apr 2002 19:32: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

Typically four weeks to IESG approval.  Then it's a matter of the RFC
Editor's queue for the actual RFC number -- perhaps 3 months.

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Thursday, April 04, 2002 6:54 PM
To: megaco@ietf.org
Subject: RE: [Megaco] Caller Id


Thanks Tom, any idea on when it would be RFC-ed?

-- Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Tom-PT Taylor
Sent: Thursday, April 04, 2002 6:41 PM
To: 'Balasubramanian Pitchandi'; megaco@ietf.org
Subject: RE: [Megaco] Caller Id



It is in the enhanced alerting package, which has just gone to the IESG.

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Thursday, April 04, 2002 6:21 PM
To: megaco@ietf.org
Subject: [Megaco] Caller Id


Hi,
 
Could anyone point me to the package that has the support for Caller ID?
I could not find it from the RFC3015 and the annexures (till M.2).
 
Thanks in advance for your replies.
 
-- 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

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



From megaco-admin@ietf.org  Fri Apr  5 12:28: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 MAA10850
	for <megaco-archive@odin.ietf.org>; Fri, 5 Apr 2002 12:28: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 MAA15116;
	Fri, 5 Apr 2002 12:10: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 MAA15084
	for <megaco@optimus.ietf.org>; Fri, 5 Apr 2002 12:10:34 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10323
	for <megaco@ietf.org>; Fri, 5 Apr 2002 12:10:27 -0500 (EST)
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 g35HA1x12239
	for <megaco@ietf.org>; Fri, 5 Apr 2002 11:10:01 -0600 (CST)
Received: from cls7ws1.ssd.usa.alcatel.com (cls7ws1.ssd.usa.alcatel.com [143.209.236.42])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g35H9rO29346
	for <megaco@ietf.org>; Fri, 5 Apr 2002 11:09:53 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1])
	by cls7ws1.ssd.usa.alcatel.com (8.9.3+Sun/8.9.1) with ESMTP id LAA06283
	for <megaco@ietf.org>; Fri, 5 Apr 2002 11:09:46 -0600 (CST)
Message-ID: <3CADDA59.A482EB4A@alcatel.com>
Date: Fri, 05 Apr 2002 11:09:46 -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="------------A110CB7D1EE26F3FCF72AC7A"
Subject: [Megaco] Annex E: RTP package Statistics Delay
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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




   Delay
        StatisticID:delay (0x0008)

        Requests the current value of packet propagation delay
        expressed in timestamp units. Same as average latency.

Where is "average latency" defined in the Standard?

Is TimeStamp units the following?

   TimeStamp            = Date "T" Time ; per ISO 8601:1988
      ; Date = yyyymmdd
   Date                 = 8(DIGIT)
      ; Time = hhmmssss
   Time                 = 8(DIGIT)


Do we really intend for this to be timestamp units or just msec?

In the example

             Statistics { rtp/ps=1200,  ; packets sent
                          nt/os=62300, ; octets sent
                          rtp/pr=700, ; packets received
                          nt/or=45100, ; octets received
                          rtp/pl=0.2,  ; % packet loss
                          rtp/jit=20,
                          rtp/delay=40 } ; avg latency  //  Doesn't look
like timestamp at all.

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



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<p>&nbsp;
<br>&nbsp;&nbsp; Delay
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; StatisticID:delay (0x0008)
<br>&nbsp;
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Requests the current value
of packet propagation delay
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; expressed in timestamp units.
<b>Same as average latency.</b>
<p>Where is "average latency" defined in the Standard?
<p>Is TimeStamp units the following?
<p>&nbsp;&nbsp; TimeStamp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= Date "T" Time ; per ISO 8601:1988
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; Date = yyyymmdd
<br>&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= 8(DIGIT)
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; Time = hhmmssss
<br>&nbsp;&nbsp; Time&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= 8(DIGIT)
<br>&nbsp;
<p>Do we really intend for this to be timestamp units or just msec?
<p>In the example
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Statistics { rtp/ps=1200,&nbsp; ; packets sent
<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;
nt/os=62300, ; octets sent
<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;
rtp/pr=700, ; packets received
<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;
nt/or=45100, ; octets received
<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;
rtp/pl=0.2,&nbsp; ; % packet loss
<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;
rtp/jit=20,
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>&nbsp;&nbsp;&nbsp;&nbsp;
rtp/delay=40 } ; avg latency&nbsp; //&nbsp; Doesn't look like timestamp
at all.</b><b></b>
<p><b>Thanks</b>
<br><b>Chuong</b>
<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>

--------------A110CB7D1EE26F3FCF72AC7A--


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


From daemon@optimus.ietf.org  Fri Apr  5 12:28: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 MAA10864
	for <megaco-archive@odin.ietf.org>; Fri, 5 Apr 2002 12:28:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA15901
	for megaco-archive@odin.ietf.org; Fri, 5 Apr 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 MAA15116;
	Fri, 5 Apr 2002 12:10: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 MAA15084
	for <megaco@optimus.ietf.org>; Fri, 5 Apr 2002 12:10:34 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10323
	for <megaco@ietf.org>; Fri, 5 Apr 2002 12:10:27 -0500 (EST)
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 g35HA1x12239
	for <megaco@ietf.org>; Fri, 5 Apr 2002 11:10:01 -0600 (CST)
Received: from cls7ws1.ssd.usa.alcatel.com (cls7ws1.ssd.usa.alcatel.com [143.209.236.42])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g35H9rO29346
	for <megaco@ietf.org>; Fri, 5 Apr 2002 11:09:53 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1])
	by cls7ws1.ssd.usa.alcatel.com (8.9.3+Sun/8.9.1) with ESMTP id LAA06283
	for <megaco@ietf.org>; Fri, 5 Apr 2002 11:09:46 -0600 (CST)
Message-ID: <3CADDA59.A482EB4A@alcatel.com>
Date: Fri, 05 Apr 2002 11:09:46 -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="------------A110CB7D1EE26F3FCF72AC7A"
Subject: [Megaco] Annex E: RTP package Statistics Delay
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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




   Delay
        StatisticID:delay (0x0008)

        Requests the current value of packet propagation delay
        expressed in timestamp units. Same as average latency.

Where is "average latency" defined in the Standard?

Is TimeStamp units the following?

   TimeStamp            = Date "T" Time ; per ISO 8601:1988
      ; Date = yyyymmdd
   Date                 = 8(DIGIT)
      ; Time = hhmmssss
   Time                 = 8(DIGIT)


Do we really intend for this to be timestamp units or just msec?

In the example

             Statistics { rtp/ps=1200,  ; packets sent
                          nt/os=62300, ; octets sent
                          rtp/pr=700, ; packets received
                          nt/or=45100, ; octets received
                          rtp/pl=0.2,  ; % packet loss
                          rtp/jit=20,
                          rtp/delay=40 } ; avg latency  //  Doesn't look
like timestamp at all.

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



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<p>&nbsp;
<br>&nbsp;&nbsp; Delay
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; StatisticID:delay (0x0008)
<br>&nbsp;
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Requests the current value
of packet propagation delay
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; expressed in timestamp units.
<b>Same as average latency.</b>
<p>Where is "average latency" defined in the Standard?
<p>Is TimeStamp units the following?
<p>&nbsp;&nbsp; TimeStamp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= Date "T" Time ; per ISO 8601:1988
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; Date = yyyymmdd
<br>&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= 8(DIGIT)
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; Time = hhmmssss
<br>&nbsp;&nbsp; Time&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= 8(DIGIT)
<br>&nbsp;
<p>Do we really intend for this to be timestamp units or just msec?
<p>In the example
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Statistics { rtp/ps=1200,&nbsp; ; packets sent
<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;
nt/os=62300, ; octets sent
<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;
rtp/pr=700, ; packets received
<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;
nt/or=45100, ; octets received
<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;
rtp/pl=0.2,&nbsp; ; % packet loss
<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;
rtp/jit=20,
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>&nbsp;&nbsp;&nbsp;&nbsp;
rtp/delay=40 } ; avg latency&nbsp; //&nbsp; Doesn't look like timestamp
at all.</b><b></b>
<p><b>Thanks</b>
<br><b>Chuong</b>
<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>

--------------A110CB7D1EE26F3FCF72AC7A--


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



From megaco-admin@ietf.org  Fri Apr  5 21:12: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 VAA17637
	for <megaco-archive@odin.ietf.org>; Fri, 5 Apr 2002 21:12: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 UAA12111;
	Fri, 5 Apr 2002 20:59: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 UAA12085
	for <megaco@optimus.ietf.org>; Fri, 5 Apr 2002 20:59:30 -0500 (EST)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17374
	for <megaco@ietf.org>; Fri, 5 Apr 2002 20:59:23 -0500 (EST)
Received: from koshy ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GU4IR600.W1I for
          <megaco@ietf.org>; Sat, 6 Apr 2002 09:57:06 +0800 
Message-ID: <00c001c1dd0e$e6444900$32180b0a@huawei.com>
From: "Koshy" <koshy@huawei.com>
To: <megaco@ietf.org>
Date: Sat, 6 Apr 2002 10:01:00 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00BD_01C1DD51.F456C020"
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
Subject: [Megaco] H248 Annex K
Sender: megaco-admin@ietf.org
Errors-To: 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_00BD_01C1DD51.F456C020
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Could any one tell what is the status of =
draft-ietf-megaco-h248k-00(annex K).

Also is it possible to play an announcement a number of times, with a =
time
gap between each announcement?

Thanks in advance

Regards
Koshy

------=_NextPart_000_00BD_01C1DD51.F456C020
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.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#c0dcc0>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Could any one tell w</FONT><FONT =
face=3DArial=20
size=3D2>hat is the status of draft-ietf-megaco-h248k-00(annex =
K).</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Also is it possible to play an =
announcement a=20
number of times, with a time</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>gap between each =
announcement?</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>Regards</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Koshy</FONT></DIV></BODY></HTML>

------=_NextPart_000_00BD_01C1DD51.F456C020--


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


From daemon@optimus.ietf.org  Fri Apr  5 21:12: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 VAA17648
	for <megaco-archive@odin.ietf.org>; Fri, 5 Apr 2002 21:12:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA12894
	for megaco-archive@odin.ietf.org; Fri, 5 Apr 2002 21: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 UAA12111;
	Fri, 5 Apr 2002 20:59: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 UAA12085
	for <megaco@optimus.ietf.org>; Fri, 5 Apr 2002 20:59:30 -0500 (EST)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17374
	for <megaco@ietf.org>; Fri, 5 Apr 2002 20:59:23 -0500 (EST)
Received: from koshy ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GU4IR600.W1I for
          <megaco@ietf.org>; Sat, 6 Apr 2002 09:57:06 +0800 
Message-ID: <00c001c1dd0e$e6444900$32180b0a@huawei.com>
From: "Koshy" <koshy@huawei.com>
To: <megaco@ietf.org>
Date: Sat, 6 Apr 2002 10:01:00 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00BD_01C1DD51.F456C020"
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
Subject: [Megaco] H248 Annex K
Sender: megaco-admin@ietf.org
Errors-To: 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_00BD_01C1DD51.F456C020
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Could any one tell what is the status of =
draft-ietf-megaco-h248k-00(annex K).

Also is it possible to play an announcement a number of times, with a =
time
gap between each announcement?

Thanks in advance

Regards
Koshy

------=_NextPart_000_00BD_01C1DD51.F456C020
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.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#c0dcc0>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Could any one tell w</FONT><FONT =
face=3DArial=20
size=3D2>hat is the status of draft-ietf-megaco-h248k-00(annex =
K).</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Also is it possible to play an =
announcement a=20
number of times, with a time</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>gap between each =
announcement?</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>Regards</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Koshy</FONT></DIV></BODY></HTML>

------=_NextPart_000_00BD_01C1DD51.F456C020--


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



From megaco-admin@ietf.org  Sat Apr  6 14:37: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 OAA14557
	for <megaco-archive@odin.ietf.org>; Sat, 6 Apr 2002 14: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 NAA28923;
	Sat, 6 Apr 2002 13: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 NAA28890
	for <megaco@ns.ietf.org>; Sat, 6 Apr 2002 13:51:35 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14087
	for <megaco@ietf.org>; Sat, 6 Apr 2002 13:51:32 -0500 (EST)
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 g36Ip4x12631
	for <megaco@ietf.org>; Sat, 6 Apr 2002 12:51:04 -0600 (CST)
Received: from cls6ws1.ssd.usa.alcatel.com (cls6ws1.ssd.usa.alcatel.com [143.209.236.39])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g36IosO26653
	for <megaco@ietf.org>; Sat, 6 Apr 2002 12:50:54 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1])
	by cls6ws1.ssd.usa.alcatel.com (8.9.3+Sun/8.9.1) with ESMTP id MAA18951
	for <megaco@ietf.org>; Sat, 6 Apr 2002 12:50:24 -0600 (CST)
Message-ID: <3CAF4370.E8E40403@alcatel.com>
Date: Sat, 06 Apr 2002 12:50:24 -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] Sending wildcard response in Audit commands
References: <20020323180504.27187.qmail@web8101.in.yahoo.com>
Content-Type: multipart/alternative;
 boundary="------------DF3134DE5D894AF6DEA86F4E"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


Sorry for the late response.
I was trying to catch w/all the emails on this subject and make sure
I understand what is really
being discussed here.

So after all the discussion, the issue seems to be that MG developer is
afraid
of the complexity.  Well by default Megaco is a very complex (others have
less nice words) Standard
to implement.

Well, I am from the MGC side and I have argued about making stuffs
simpilier for MGC side
to implement and had lost.

For the "the more experiencd on the list", well I don't know if I can be
considered that.
But I was the one that asked for the "W" response.

I originally wanted it for a wildcard response for a Subtract ALL.
Then I wanted to use it for a wildcard response for AuditValue for a
wildcard terminationID (span/T1/E1)
to find whether the span/T1/E1 is IN-SERVICE or Out-of-Service.

If all the terminations for that span happens to be in the NULL context and
all IN-SERVICE,
I only want to get 1 AuditValue command response.
If not, I get multiple AuditValue command for each termination (but since
all in 1 transaction).
Also using wildcard responses for ServiceChange.


But then I realized that in V1, we can't just do an AuditValue for
terminationState which is now
allowed in V2.

Whether something in the Standard is too complicated to implement or not -
especially to a particular MG/MGC implementators/vendors should be the last
thing used to justify for disallowing it in the Standard.

If you think something is too complex to support then don't support it.
You already have the profile feature to tell others what you can or cannot
support.
If you get something you don't support, just return "NOT SUPPORTED".

But I also agreed w/you on the complexity of using wildcard for AuditValue
to audit too much
stuffs where the responses might be to complicate to parse out the correct
information at the MGC side.
I never intended to use the wildcard response for anything else as
indicated above.
But as Standard goes, once something is defined it must work for all
command and be generic.

But since the MGC side is driving the AuditValue request, I assume
MGC implementor would want
to implement the request something as simple as possible to guarantee
1) maximun interopability w/different MG vendor (for a particular type of
MG)
2) getting the precise  response from MG for easy processing at MGC.

Well I hope this help
Chuong


SHRI KUMAR wrote:

> Hi Kevin
>
> That is exactly what I wanted to know. Is there
> somebody on the MGC side who finds worth in the
> wildcard responses.
>
> Well at least the more experienced on the list should
> be able to reply about the reasons for providing a
> feature. At least one typical case where the wildcard
> response is sufficient and the MGC wouldn't need to
> know individual responses. At least we haven't seen
> anything supporting this even at the MEGACO interops.
>
> THis is important from the MG developer's point of
> view. Handling wildcard terminations is already a
> complex note, extending such a feature would be more
> complex, but is it worth adding this to MG.
>
> Thanks in adv if you can help..
> -SHRI KUMAR
>
>  --- Kevin Boyle <kboyle@nortelnetworks.com> wrote: >
> It largely depends on your particular
> > implementation, and the function in
> > question, whether getting individual responses is
> > required, or if the
> > wildcard response is sufficient.
> >
> > Kevin
> >
> > -----Original Message-----
> > From: SHRI KUMAR [mailto:manikaran1947@yahoo.co.in]
> > Sent: Friday, March 22, 2002 3:05 AM
> > To: SHRI KUMAR; Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: megaco@ietf.org
> > Subject: RE: [Megaco] Sending wildcard response in
> > Audit commands
> >
> >
> > Hi
> >
> > Yet no reply on this one?
> >  --- SHRI KUMAR <manikaran1947@yahoo.co.in> wrote: >
> > Hello Tom
> > >
> > > It would make "more" or "only" sense with Audit
> > > capability.
> > > But, even with Audit Cap, I think MGC would like
> > to
> > > know the capabilities of each termination
> > > individually
> > > or as a group (wildcarded) if the set of
> > > terminations
> > > have similar capabilities.
> > >
> > > Any comments....
> > >
> > > Njoy
> > >
> > >  --- Tom-PT Taylor <taylor@nortelnetworks.com>
> > > wrote:
> > > >
> > > > It can be useful to determine the range of
> > options
> > > > supported.  It would make
> > > > more sense with AuditCapability that AuditValue
> > > for
> > > > that reason.
> > > >
> > > > -----Original Message-----
> > > > From: SHRI KUMAR
> > > [mailto:manikaran1947@yahoo.co.in]
> > > > Sent: Friday, March 15, 2002 11:14 AM
> > > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > > Cc: megaco@ietf.org
> > > > Subject: RE: [Megaco] Sending wildcard response
> > in
> > > > Audit commands
> > > >
> > > >
> > > > Hi Tom/ List
> > > >
> > > > I have a question about the very sanctity of
> > > > wildcarded responses. The RFC says about the
> > > > wildcard
> > > > responses:
> > > > "This convention may reduce the volume of data
> > > > required to audit a group of terminations".
> > > > But, it seems the UNION of the responses for
> > > > individual terminations would change the
> > semantics
> > > > of
> > > > the information in audit responses...by
> > de-linking
> > > > it
> > > > from individual terminations and linking it to a
> > > > wildcarded
> > > > term name. Can somebody identify what use is
> > this
> > > > information to an MGC ?
> > > >
> > > > What does a MGC do with a wildcarded UNION
> > > response
> > > > like:
> > > > Context = *{
> > > >    AuditValue = T*{
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p1=a, p2=b,c, p3=d }
> > > >          }
> > > >       }
> > > >    }
> > > > }
> > > > or
> > > > Context = *{
> > > >    AuditValue = T*{
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p1=a, p2=b }
> > > >          }
> > > >       },
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p2=c, p3=d }
> > > >          }
> > > >       }
> > > >    }
> > > > }
> > > >
> > > > The MGC will ultimately need to know:
> > > > Context = *{
> > > >    AuditValue = Ta{
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p1=a, p2=b }
> > > >          }
> > > >       },
> > > >    AuditValue = Tb{
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p2=c, p3=d }
> > > >          }
> > > >       }
> > > >    }
> > > > }
> > > > unless we have a situation where, both Ta and Tb
> > > > have
> > > > only p1=a and p2=b and the response is:
> > > > Context = *{
> > > >    AuditValue = T*{
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p1=a, p2=b }
> > > >          }
> > > >       }
> > > >    }
> > > > }
> > > >
> > > > Except for this last special situation where all
> > > > descriptors with properties and property values
> > > are
> > > > similar on all resolved terminations, I don't
> > see
> > > > any
> > > > value in sending a wild-carded response.
> > > >
> > > > Rgds,
> > > > Manikaran
> > > >
> > > >
> > > > Tom P. Taylor wrote....
> > > > >OK, let's clean this one up.  Currently the one
> > > > >example shown in the text
> > > > >(section 7.2.5) is this:
> > > > >
> > > > >  "The command:
> > > > >
> > > > Context=*{W-AuditValue=t1/*{Audit{Packages}}
> > > > >   Returns:
> > > >
> > > > >Context=*{W-AuditValue=t1/*{Packages{aaa,bbb}}"
> > > >
> > > > >where t1/1 and t1/2 both support the two
> > packages
> > > > >shown.
> > > >
> > > > >Unfortunately this doesn't resolve the question
> > > of
> > > > >whether aggregation is at
> > > > >the atomic level, since both terminations would
> > > > give
> > > > >the same result.
> > > > >Similarly, section 6.2.2 is ambiguous, because
> > it
> > > > is
> > > > >too abstract:
> > > >
> > > > >"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.
> > >
> > > > >Wildcard response may be
> > > > >particularly useful in the Audit commands."
> > > >
> > > > >On a close reading of this last, however, I am
> > > > >inclined to believe that it
> > > > >is the descriptors which are repeated.  The
> > > phrase
> >
> === message truncated ===
>
> ________________________________________________________________________
> For live cricket scores download  Yahoo! Score Tracker
>  at: http://in.sports.yahoo.com/cricket/tracker.html
>
> _______________________________________________
> 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 ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Sorry for the late response.
<br>I was trying to catch w/all the emails on this subject and make sure
I&nbsp;understand what is really
<br>being discussed here.
<p>So after all the discussion, the issue seems to be that MG&nbsp;developer
is afraid
<br>of the complexity.&nbsp; Well by default Megaco is a very complex (others
have less nice words) Standard
<br>to implement.
<p>Well, I&nbsp;am from the MGC&nbsp;side and I&nbsp;have argued about
making stuffs simpilier for MGC side
<br>to implement and had lost.
<p>For the "the more experiencd on the list", well I&nbsp;don't know if
I can be considered that.
<br>But I was the one that asked for the "W" response.
<p>I&nbsp;originally wanted it for a wildcard response for a Subtract ALL.
<br>Then I wanted to use it for a wildcard response for AuditValue for
a wildcard terminationID (span/T1/E1)
<br>to find whether the span/T1/E1 is IN-SERVICE or Out-of-Service.
<p>If all the terminations for that span happens to be in the NULL&nbsp;context
and all IN-SERVICE,
<br>I only want to get 1 AuditValue command response.
<br>If not, I get multiple AuditValue command for each termination (but
since all in 1 transaction).
<br>Also using wildcard responses for ServiceChange.
<br>&nbsp;
<p>But then I&nbsp;realized that in V1, we can't just do an AuditValue
for terminationState which is now
<br>allowed in V2.
<p>Whether something in the Standard is too complicated to implement or
not -&nbsp; especially to a particular MG/MGC implementators/vendors should
be the last thing used to justify for disallowing it in the Standard.
<p>If you think something is too complex to support then don't support
it.
<br>You already have the profile feature to tell others what you can or
cannot support.
<br>If you get something you don't support, just return "NOT SUPPORTED".
<p>But I&nbsp;also agreed w/you on the complexity of using wildcard for
AuditValue to audit too much
<br>stuffs where the responses might be to complicate to parse out the
correct information at the MGC side.
<br>I&nbsp;never intended to use the wildcard response for anything else
as indicated above.
<br>But as Standard goes, once something is defined it must work for all
command and be generic.
<p>But since the MGC side is driving the AuditValue request, I&nbsp;assume
MGC&nbsp;implementor would want
<br>to implement the request something as simple as possible to guarantee
<br>1) maximun interopability w/different MG&nbsp;vendor (for a particular
type of MG)
<br>2) getting the precise&nbsp; response from MG for easy processing at
MGC.
<p>Well I&nbsp;hope this help
<br>Chuong
<br>&nbsp;
<p>SHRI KUMAR wrote:
<blockquote TYPE=CITE>Hi Kevin
<p>That is exactly what I wanted to know. Is there
<br>somebody on the MGC side who finds worth in the
<br>wildcard responses.
<p>Well at least the more experienced on the list should
<br>be able to reply about the reasons for providing a
<br>feature. At least one typical case where the wildcard
<br>response is sufficient and the MGC wouldn't need to
<br>know individual responses. At least we haven't seen
<br>anything supporting this even at the MEGACO interops.
<p>THis is important from the MG developer's point of
<br>view. Handling wildcard terminations is already a
<br>complex note, extending such a feature would be more
<br>complex, but is it worth adding this to MG.
<p>Thanks in adv if you can help..
<br>-SHRI KUMAR
<p>&nbsp;--- Kevin Boyle &lt;kboyle@nortelnetworks.com> wrote: >
<br>It largely depends on your particular
<br>> implementation, and the function in
<br>> question, whether getting individual responses is
<br>> required, or if the
<br>> wildcard response is sufficient.
<br>>
<br>> Kevin
<br>>
<br>> -----Original Message-----
<br>> From: SHRI KUMAR [<a href="mailto:manikaran1947@yahoo.co.in">mailto:manikaran1947@yahoo.co.in</a>]
<br>> Sent: Friday, March 22, 2002 3:05 AM
<br>> To: SHRI KUMAR; Taylor, Tom-PT [CAR:B800:EXCH]
<br>> Cc: megaco@ietf.org
<br>> Subject: RE: [Megaco] Sending wildcard response in
<br>> Audit commands
<br>>
<br>>
<br>> Hi
<br>>
<br>> Yet no reply on this one?
<br>>&nbsp; --- SHRI KUMAR &lt;manikaran1947@yahoo.co.in> wrote: >
<br>> Hello Tom
<br>> >
<br>> > It would make "more" or "only" sense with Audit
<br>> > capability.
<br>> > But, even with Audit Cap, I think MGC would like
<br>> to
<br>> > know the capabilities of each termination
<br>> > individually
<br>> > or as a group (wildcarded) if the set of
<br>> > terminations
<br>> > have similar capabilities.
<br>> >
<br>> > Any comments....
<br>> >
<br>> > Njoy
<br>> >
<br>> >&nbsp; --- Tom-PT Taylor &lt;taylor@nortelnetworks.com>
<br>> > wrote:
<br>> > >
<br>> > > It can be useful to determine the range of
<br>> options
<br>> > > supported.&nbsp; It would make
<br>> > > more sense with AuditCapability that AuditValue
<br>> > for
<br>> > > that reason.
<br>> > >
<br>> > > -----Original Message-----
<br>> > > From: SHRI KUMAR
<br>> > [<a href="mailto:manikaran1947@yahoo.co.in">mailto:manikaran1947@yahoo.co.in</a>]
<br>> > > Sent: Friday, March 15, 2002 11:14 AM
<br>> > > To: Taylor, Tom-PT [CAR:B800:EXCH]
<br>> > > Cc: megaco@ietf.org
<br>> > > Subject: RE: [Megaco] Sending wildcard response
<br>> in
<br>> > > Audit commands
<br>> > >
<br>> > >
<br>> > > Hi Tom/ List
<br>> > >
<br>> > > I have a question about the very sanctity of
<br>> > > wildcarded responses. The RFC says about the
<br>> > > wildcard
<br>> > > responses:
<br>> > > "This convention may reduce the volume of data
<br>> > > required to audit a group of terminations".
<br>> > > But, it seems the UNION of the responses for
<br>> > > individual terminations would change the
<br>> semantics
<br>> > > of
<br>> > > the information in audit responses...by
<br>> de-linking
<br>> > > it
<br>> > > from individual terminations and linking it to a
<br>> > > wildcarded
<br>> > > term name. Can somebody identify what use is
<br>> this
<br>> > > information to an MGC ?
<br>> > >
<br>> > > What does a MGC do with a wildcarded UNION
<br>> > response
<br>> > > like:
<br>> > > Context = *{
<br>> > >&nbsp;&nbsp;&nbsp; AuditValue = T*{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p1=a, p2=b,c, p3=d }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp; }
<br>> > > }
<br>> > > or
<br>> > > Context = *{
<br>> > >&nbsp;&nbsp;&nbsp; AuditValue = T*{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p1=a, p2=b }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; },
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p2=c, p3=d }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp; }
<br>> > > }
<br>> > >
<br>> > > The MGC will ultimately need to know:
<br>> > > Context = *{
<br>> > >&nbsp;&nbsp;&nbsp; AuditValue = Ta{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p1=a, p2=b }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; },
<br>> > >&nbsp;&nbsp;&nbsp; AuditValue = Tb{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p2=c, p3=d }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp; }
<br>> > > }
<br>> > > unless we have a situation where, both Ta and Tb
<br>> > > have
<br>> > > only p1=a and p2=b and the response is:
<br>> > > Context = *{
<br>> > >&nbsp;&nbsp;&nbsp; AuditValue = T*{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p1=a, p2=b }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp; }
<br>> > > }
<br>> > >
<br>> > > Except for this last special situation where all
<br>> > > descriptors with properties and property values
<br>> > are
<br>> > > similar on all resolved terminations, I don't
<br>> see
<br>> > > any
<br>> > > value in sending a wild-carded response.
<br>> > >
<br>> > > Rgds,
<br>> > > Manikaran
<br>> > >
<br>> > >
<br>> > > Tom P. Taylor wrote....
<br>> > > >OK, let's clean this one up.&nbsp; Currently the one
<br>> > > >example shown in the text
<br>> > > >(section 7.2.5) is this:
<br>> > > >
<br>> > > >&nbsp; "The command:
<br>> > > >
<br>> > > Context=*{W-AuditValue=t1/*{Audit{Packages}}
<br>> > > >&nbsp;&nbsp; Returns:
<br>> > >
<br>> > > >Context=*{W-AuditValue=t1/*{Packages{aaa,bbb}}"
<br>> > >
<br>> > > >where t1/1 and t1/2 both support the two
<br>> packages
<br>> > > >shown.
<br>> > >
<br>> > > >Unfortunately this doesn't resolve the question
<br>> > of
<br>> > > >whether aggregation is at
<br>> > > >the atomic level, since both terminations would
<br>> > > give
<br>> > > >the same result.
<br>> > > >Similarly, section 6.2.2 is ambiguous, because
<br>> it
<br>> > > is
<br>> > > >too abstract:
<br>> > >
<br>> > > >"If individual responses are not required, a
<br>> > > wildcard
<br>> > > >response may be
<br>> > > >requested.&nbsp; In such a case, a single response
<br>> is
<br>> > > >generated, which contains
<br>> > > >the UNION of all of the individual responses
<br>> > which
<br>> > > >otherwise would have been
<br>> > > >generated, with duplicate values suppressed.
<br>> > For
<br>> > > >instance, given a
<br>> > > >Termination Ta with properties p1=a, p2=b and
<br>> > > >Termination Tb with properties
<br>> > > >p2=c, p3=d, a UNION response would consist of a
<br>> > > >wildcarded TerminationId and
<br>> > > >the sequence of properties p1=a, p2=b,c and
<br>> p3=d.
<br>> >
<br>> > > >Wildcard response may be
<br>> > > >particularly useful in the Audit commands."
<br>> > >
<br>> > > >On a close reading of this last, however, I am
<br>> > > >inclined to believe that it
<br>> > > >is the descriptors which are repeated.&nbsp; The
<br>> > phrase
<br>>
<br>=== message truncated ===
<p>________________________________________________________________________
<br>For live cricket scores download&nbsp; Yahoo! Score Tracker
<br>&nbsp;at: <a href="http://in.sports.yahoo.com/cricket/tracker.html">http://in.sports.yahoo.com/cricket/tracker.html</a>
<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>

--------------DF3134DE5D894AF6DEA86F4E--


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


From daemon@ns.ietf.org  Sat Apr  6 14:37: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 OAA14570
	for <megaco-archive@odin.ietf.org>; Sat, 6 Apr 2002 14:37:39 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA01118
	for megaco-archive@odin.ietf.org; Sat, 6 Apr 2002 14:37: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 NAA28923;
	Sat, 6 Apr 2002 13: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 NAA28890
	for <megaco@ns.ietf.org>; Sat, 6 Apr 2002 13:51:35 -0500 (EST)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14087
	for <megaco@ietf.org>; Sat, 6 Apr 2002 13:51:32 -0500 (EST)
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 g36Ip4x12631
	for <megaco@ietf.org>; Sat, 6 Apr 2002 12:51:04 -0600 (CST)
Received: from cls6ws1.ssd.usa.alcatel.com (cls6ws1.ssd.usa.alcatel.com [143.209.236.39])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g36IosO26653
	for <megaco@ietf.org>; Sat, 6 Apr 2002 12:50:54 -0600 (CST)
Received: from alcatel.com (localhost [127.0.0.1])
	by cls6ws1.ssd.usa.alcatel.com (8.9.3+Sun/8.9.1) with ESMTP id MAA18951
	for <megaco@ietf.org>; Sat, 6 Apr 2002 12:50:24 -0600 (CST)
Message-ID: <3CAF4370.E8E40403@alcatel.com>
Date: Sat, 06 Apr 2002 12:50:24 -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] Sending wildcard response in Audit commands
References: <20020323180504.27187.qmail@web8101.in.yahoo.com>
Content-Type: multipart/alternative;
 boundary="------------DF3134DE5D894AF6DEA86F4E"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


Sorry for the late response.
I was trying to catch w/all the emails on this subject and make sure
I understand what is really
being discussed here.

So after all the discussion, the issue seems to be that MG developer is
afraid
of the complexity.  Well by default Megaco is a very complex (others have
less nice words) Standard
to implement.

Well, I am from the MGC side and I have argued about making stuffs
simpilier for MGC side
to implement and had lost.

For the "the more experiencd on the list", well I don't know if I can be
considered that.
But I was the one that asked for the "W" response.

I originally wanted it for a wildcard response for a Subtract ALL.
Then I wanted to use it for a wildcard response for AuditValue for a
wildcard terminationID (span/T1/E1)
to find whether the span/T1/E1 is IN-SERVICE or Out-of-Service.

If all the terminations for that span happens to be in the NULL context and
all IN-SERVICE,
I only want to get 1 AuditValue command response.
If not, I get multiple AuditValue command for each termination (but since
all in 1 transaction).
Also using wildcard responses for ServiceChange.


But then I realized that in V1, we can't just do an AuditValue for
terminationState which is now
allowed in V2.

Whether something in the Standard is too complicated to implement or not -
especially to a particular MG/MGC implementators/vendors should be the last
thing used to justify for disallowing it in the Standard.

If you think something is too complex to support then don't support it.
You already have the profile feature to tell others what you can or cannot
support.
If you get something you don't support, just return "NOT SUPPORTED".

But I also agreed w/you on the complexity of using wildcard for AuditValue
to audit too much
stuffs where the responses might be to complicate to parse out the correct
information at the MGC side.
I never intended to use the wildcard response for anything else as
indicated above.
But as Standard goes, once something is defined it must work for all
command and be generic.

But since the MGC side is driving the AuditValue request, I assume
MGC implementor would want
to implement the request something as simple as possible to guarantee
1) maximun interopability w/different MG vendor (for a particular type of
MG)
2) getting the precise  response from MG for easy processing at MGC.

Well I hope this help
Chuong


SHRI KUMAR wrote:

> Hi Kevin
>
> That is exactly what I wanted to know. Is there
> somebody on the MGC side who finds worth in the
> wildcard responses.
>
> Well at least the more experienced on the list should
> be able to reply about the reasons for providing a
> feature. At least one typical case where the wildcard
> response is sufficient and the MGC wouldn't need to
> know individual responses. At least we haven't seen
> anything supporting this even at the MEGACO interops.
>
> THis is important from the MG developer's point of
> view. Handling wildcard terminations is already a
> complex note, extending such a feature would be more
> complex, but is it worth adding this to MG.
>
> Thanks in adv if you can help..
> -SHRI KUMAR
>
>  --- Kevin Boyle <kboyle@nortelnetworks.com> wrote: >
> It largely depends on your particular
> > implementation, and the function in
> > question, whether getting individual responses is
> > required, or if the
> > wildcard response is sufficient.
> >
> > Kevin
> >
> > -----Original Message-----
> > From: SHRI KUMAR [mailto:manikaran1947@yahoo.co.in]
> > Sent: Friday, March 22, 2002 3:05 AM
> > To: SHRI KUMAR; Taylor, Tom-PT [CAR:B800:EXCH]
> > Cc: megaco@ietf.org
> > Subject: RE: [Megaco] Sending wildcard response in
> > Audit commands
> >
> >
> > Hi
> >
> > Yet no reply on this one?
> >  --- SHRI KUMAR <manikaran1947@yahoo.co.in> wrote: >
> > Hello Tom
> > >
> > > It would make "more" or "only" sense with Audit
> > > capability.
> > > But, even with Audit Cap, I think MGC would like
> > to
> > > know the capabilities of each termination
> > > individually
> > > or as a group (wildcarded) if the set of
> > > terminations
> > > have similar capabilities.
> > >
> > > Any comments....
> > >
> > > Njoy
> > >
> > >  --- Tom-PT Taylor <taylor@nortelnetworks.com>
> > > wrote:
> > > >
> > > > It can be useful to determine the range of
> > options
> > > > supported.  It would make
> > > > more sense with AuditCapability that AuditValue
> > > for
> > > > that reason.
> > > >
> > > > -----Original Message-----
> > > > From: SHRI KUMAR
> > > [mailto:manikaran1947@yahoo.co.in]
> > > > Sent: Friday, March 15, 2002 11:14 AM
> > > > To: Taylor, Tom-PT [CAR:B800:EXCH]
> > > > Cc: megaco@ietf.org
> > > > Subject: RE: [Megaco] Sending wildcard response
> > in
> > > > Audit commands
> > > >
> > > >
> > > > Hi Tom/ List
> > > >
> > > > I have a question about the very sanctity of
> > > > wildcarded responses. The RFC says about the
> > > > wildcard
> > > > responses:
> > > > "This convention may reduce the volume of data
> > > > required to audit a group of terminations".
> > > > But, it seems the UNION of the responses for
> > > > individual terminations would change the
> > semantics
> > > > of
> > > > the information in audit responses...by
> > de-linking
> > > > it
> > > > from individual terminations and linking it to a
> > > > wildcarded
> > > > term name. Can somebody identify what use is
> > this
> > > > information to an MGC ?
> > > >
> > > > What does a MGC do with a wildcarded UNION
> > > response
> > > > like:
> > > > Context = *{
> > > >    AuditValue = T*{
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p1=a, p2=b,c, p3=d }
> > > >          }
> > > >       }
> > > >    }
> > > > }
> > > > or
> > > > Context = *{
> > > >    AuditValue = T*{
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p1=a, p2=b }
> > > >          }
> > > >       },
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p2=c, p3=d }
> > > >          }
> > > >       }
> > > >    }
> > > > }
> > > >
> > > > The MGC will ultimately need to know:
> > > > Context = *{
> > > >    AuditValue = Ta{
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p1=a, p2=b }
> > > >          }
> > > >       },
> > > >    AuditValue = Tb{
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p2=c, p3=d }
> > > >          }
> > > >       }
> > > >    }
> > > > }
> > > > unless we have a situation where, both Ta and Tb
> > > > have
> > > > only p1=a and p2=b and the response is:
> > > > Context = *{
> > > >    AuditValue = T*{
> > > >       Media{
> > > >          Stream= 1{
> > > >             LocalControl{ p1=a, p2=b }
> > > >          }
> > > >       }
> > > >    }
> > > > }
> > > >
> > > > Except for this last special situation where all
> > > > descriptors with properties and property values
> > > are
> > > > similar on all resolved terminations, I don't
> > see
> > > > any
> > > > value in sending a wild-carded response.
> > > >
> > > > Rgds,
> > > > Manikaran
> > > >
> > > >
> > > > Tom P. Taylor wrote....
> > > > >OK, let's clean this one up.  Currently the one
> > > > >example shown in the text
> > > > >(section 7.2.5) is this:
> > > > >
> > > > >  "The command:
> > > > >
> > > > Context=*{W-AuditValue=t1/*{Audit{Packages}}
> > > > >   Returns:
> > > >
> > > > >Context=*{W-AuditValue=t1/*{Packages{aaa,bbb}}"
> > > >
> > > > >where t1/1 and t1/2 both support the two
> > packages
> > > > >shown.
> > > >
> > > > >Unfortunately this doesn't resolve the question
> > > of
> > > > >whether aggregation is at
> > > > >the atomic level, since both terminations would
> > > > give
> > > > >the same result.
> > > > >Similarly, section 6.2.2 is ambiguous, because
> > it
> > > > is
> > > > >too abstract:
> > > >
> > > > >"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.
> > >
> > > > >Wildcard response may be
> > > > >particularly useful in the Audit commands."
> > > >
> > > > >On a close reading of this last, however, I am
> > > > >inclined to believe that it
> > > > >is the descriptors which are repeated.  The
> > > phrase
> >
> === message truncated ===
>
> ________________________________________________________________________
> For live cricket scores download  Yahoo! Score Tracker
>  at: http://in.sports.yahoo.com/cricket/tracker.html
>
> _______________________________________________
> 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 ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Sorry for the late response.
<br>I was trying to catch w/all the emails on this subject and make sure
I&nbsp;understand what is really
<br>being discussed here.
<p>So after all the discussion, the issue seems to be that MG&nbsp;developer
is afraid
<br>of the complexity.&nbsp; Well by default Megaco is a very complex (others
have less nice words) Standard
<br>to implement.
<p>Well, I&nbsp;am from the MGC&nbsp;side and I&nbsp;have argued about
making stuffs simpilier for MGC side
<br>to implement and had lost.
<p>For the "the more experiencd on the list", well I&nbsp;don't know if
I can be considered that.
<br>But I was the one that asked for the "W" response.
<p>I&nbsp;originally wanted it for a wildcard response for a Subtract ALL.
<br>Then I wanted to use it for a wildcard response for AuditValue for
a wildcard terminationID (span/T1/E1)
<br>to find whether the span/T1/E1 is IN-SERVICE or Out-of-Service.
<p>If all the terminations for that span happens to be in the NULL&nbsp;context
and all IN-SERVICE,
<br>I only want to get 1 AuditValue command response.
<br>If not, I get multiple AuditValue command for each termination (but
since all in 1 transaction).
<br>Also using wildcard responses for ServiceChange.
<br>&nbsp;
<p>But then I&nbsp;realized that in V1, we can't just do an AuditValue
for terminationState which is now
<br>allowed in V2.
<p>Whether something in the Standard is too complicated to implement or
not -&nbsp; especially to a particular MG/MGC implementators/vendors should
be the last thing used to justify for disallowing it in the Standard.
<p>If you think something is too complex to support then don't support
it.
<br>You already have the profile feature to tell others what you can or
cannot support.
<br>If you get something you don't support, just return "NOT SUPPORTED".
<p>But I&nbsp;also agreed w/you on the complexity of using wildcard for
AuditValue to audit too much
<br>stuffs where the responses might be to complicate to parse out the
correct information at the MGC side.
<br>I&nbsp;never intended to use the wildcard response for anything else
as indicated above.
<br>But as Standard goes, once something is defined it must work for all
command and be generic.
<p>But since the MGC side is driving the AuditValue request, I&nbsp;assume
MGC&nbsp;implementor would want
<br>to implement the request something as simple as possible to guarantee
<br>1) maximun interopability w/different MG&nbsp;vendor (for a particular
type of MG)
<br>2) getting the precise&nbsp; response from MG for easy processing at
MGC.
<p>Well I&nbsp;hope this help
<br>Chuong
<br>&nbsp;
<p>SHRI KUMAR wrote:
<blockquote TYPE=CITE>Hi Kevin
<p>That is exactly what I wanted to know. Is there
<br>somebody on the MGC side who finds worth in the
<br>wildcard responses.
<p>Well at least the more experienced on the list should
<br>be able to reply about the reasons for providing a
<br>feature. At least one typical case where the wildcard
<br>response is sufficient and the MGC wouldn't need to
<br>know individual responses. At least we haven't seen
<br>anything supporting this even at the MEGACO interops.
<p>THis is important from the MG developer's point of
<br>view. Handling wildcard terminations is already a
<br>complex note, extending such a feature would be more
<br>complex, but is it worth adding this to MG.
<p>Thanks in adv if you can help..
<br>-SHRI KUMAR
<p>&nbsp;--- Kevin Boyle &lt;kboyle@nortelnetworks.com> wrote: >
<br>It largely depends on your particular
<br>> implementation, and the function in
<br>> question, whether getting individual responses is
<br>> required, or if the
<br>> wildcard response is sufficient.
<br>>
<br>> Kevin
<br>>
<br>> -----Original Message-----
<br>> From: SHRI KUMAR [<a href="mailto:manikaran1947@yahoo.co.in">mailto:manikaran1947@yahoo.co.in</a>]
<br>> Sent: Friday, March 22, 2002 3:05 AM
<br>> To: SHRI KUMAR; Taylor, Tom-PT [CAR:B800:EXCH]
<br>> Cc: megaco@ietf.org
<br>> Subject: RE: [Megaco] Sending wildcard response in
<br>> Audit commands
<br>>
<br>>
<br>> Hi
<br>>
<br>> Yet no reply on this one?
<br>>&nbsp; --- SHRI KUMAR &lt;manikaran1947@yahoo.co.in> wrote: >
<br>> Hello Tom
<br>> >
<br>> > It would make "more" or "only" sense with Audit
<br>> > capability.
<br>> > But, even with Audit Cap, I think MGC would like
<br>> to
<br>> > know the capabilities of each termination
<br>> > individually
<br>> > or as a group (wildcarded) if the set of
<br>> > terminations
<br>> > have similar capabilities.
<br>> >
<br>> > Any comments....
<br>> >
<br>> > Njoy
<br>> >
<br>> >&nbsp; --- Tom-PT Taylor &lt;taylor@nortelnetworks.com>
<br>> > wrote:
<br>> > >
<br>> > > It can be useful to determine the range of
<br>> options
<br>> > > supported.&nbsp; It would make
<br>> > > more sense with AuditCapability that AuditValue
<br>> > for
<br>> > > that reason.
<br>> > >
<br>> > > -----Original Message-----
<br>> > > From: SHRI KUMAR
<br>> > [<a href="mailto:manikaran1947@yahoo.co.in">mailto:manikaran1947@yahoo.co.in</a>]
<br>> > > Sent: Friday, March 15, 2002 11:14 AM
<br>> > > To: Taylor, Tom-PT [CAR:B800:EXCH]
<br>> > > Cc: megaco@ietf.org
<br>> > > Subject: RE: [Megaco] Sending wildcard response
<br>> in
<br>> > > Audit commands
<br>> > >
<br>> > >
<br>> > > Hi Tom/ List
<br>> > >
<br>> > > I have a question about the very sanctity of
<br>> > > wildcarded responses. The RFC says about the
<br>> > > wildcard
<br>> > > responses:
<br>> > > "This convention may reduce the volume of data
<br>> > > required to audit a group of terminations".
<br>> > > But, it seems the UNION of the responses for
<br>> > > individual terminations would change the
<br>> semantics
<br>> > > of
<br>> > > the information in audit responses...by
<br>> de-linking
<br>> > > it
<br>> > > from individual terminations and linking it to a
<br>> > > wildcarded
<br>> > > term name. Can somebody identify what use is
<br>> this
<br>> > > information to an MGC ?
<br>> > >
<br>> > > What does a MGC do with a wildcarded UNION
<br>> > response
<br>> > > like:
<br>> > > Context = *{
<br>> > >&nbsp;&nbsp;&nbsp; AuditValue = T*{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p1=a, p2=b,c, p3=d }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp; }
<br>> > > }
<br>> > > or
<br>> > > Context = *{
<br>> > >&nbsp;&nbsp;&nbsp; AuditValue = T*{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p1=a, p2=b }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; },
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p2=c, p3=d }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp; }
<br>> > > }
<br>> > >
<br>> > > The MGC will ultimately need to know:
<br>> > > Context = *{
<br>> > >&nbsp;&nbsp;&nbsp; AuditValue = Ta{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p1=a, p2=b }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; },
<br>> > >&nbsp;&nbsp;&nbsp; AuditValue = Tb{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p2=c, p3=d }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp; }
<br>> > > }
<br>> > > unless we have a situation where, both Ta and Tb
<br>> > > have
<br>> > > only p1=a and p2=b and the response is:
<br>> > > Context = *{
<br>> > >&nbsp;&nbsp;&nbsp; AuditValue = T*{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Media{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream=
1{
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
LocalControl{ p1=a, p2=b }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }
<br>> > >&nbsp;&nbsp;&nbsp; }
<br>> > > }
<br>> > >
<br>> > > Except for this last special situation where all
<br>> > > descriptors with properties and property values
<br>> > are
<br>> > > similar on all resolved terminations, I don't
<br>> see
<br>> > > any
<br>> > > value in sending a wild-carded response.
<br>> > >
<br>> > > Rgds,
<br>> > > Manikaran
<br>> > >
<br>> > >
<br>> > > Tom P. Taylor wrote....
<br>> > > >OK, let's clean this one up.&nbsp; Currently the one
<br>> > > >example shown in the text
<br>> > > >(section 7.2.5) is this:
<br>> > > >
<br>> > > >&nbsp; "The command:
<br>> > > >
<br>> > > Context=*{W-AuditValue=t1/*{Audit{Packages}}
<br>> > > >&nbsp;&nbsp; Returns:
<br>> > >
<br>> > > >Context=*{W-AuditValue=t1/*{Packages{aaa,bbb}}"
<br>> > >
<br>> > > >where t1/1 and t1/2 both support the two
<br>> packages
<br>> > > >shown.
<br>> > >
<br>> > > >Unfortunately this doesn't resolve the question
<br>> > of
<br>> > > >whether aggregation is at
<br>> > > >the atomic level, since both terminations would
<br>> > > give
<br>> > > >the same result.
<br>> > > >Similarly, section 6.2.2 is ambiguous, because
<br>> it
<br>> > > is
<br>> > > >too abstract:
<br>> > >
<br>> > > >"If individual responses are not required, a
<br>> > > wildcard
<br>> > > >response may be
<br>> > > >requested.&nbsp; In such a case, a single response
<br>> is
<br>> > > >generated, which contains
<br>> > > >the UNION of all of the individual responses
<br>> > which
<br>> > > >otherwise would have been
<br>> > > >generated, with duplicate values suppressed.
<br>> > For
<br>> > > >instance, given a
<br>> > > >Termination Ta with properties p1=a, p2=b and
<br>> > > >Termination Tb with properties
<br>> > > >p2=c, p3=d, a UNION response would consist of a
<br>> > > >wildcarded TerminationId and
<br>> > > >the sequence of properties p1=a, p2=b,c and
<br>> p3=d.
<br>> >
<br>> > > >Wildcard response may be
<br>> > > >particularly useful in the Audit commands."
<br>> > >
<br>> > > >On a close reading of this last, however, I am
<br>> > > >inclined to believe that it
<br>> > > >is the descriptors which are repeated.&nbsp; The
<br>> > phrase
<br>>
<br>=== message truncated ===
<p>________________________________________________________________________
<br>For live cricket scores download&nbsp; Yahoo! Score Tracker
<br>&nbsp;at: <a href="http://in.sports.yahoo.com/cricket/tracker.html">http://in.sports.yahoo.com/cricket/tracker.html</a>
<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>

--------------DF3134DE5D894AF6DEA86F4E--


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



From megaco-admin@ietf.org  Sun Apr  7 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 JAA26619
	for <megaco-archive@odin.ietf.org>; Sun, 7 Apr 2002 09:43:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21675;
	Sun, 7 Apr 2002 09:28:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21647
	for <megaco@optimus.ietf.org>; Sun, 7 Apr 2002 09:28:52 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26450
	for <megaco@ietf.org>; Sun, 7 Apr 2002 09:28:49 -0400 (EDT)
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 g37DSJO03573
	for <megaco@ietf.org>; Sun, 7 Apr 2002 09:28:19 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LB617>; Sun, 7 Apr 2002 09:28:21 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A287@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Koshy'" <koshy@huawei.com>, megaco@ietf.org
Subject: RE: [Megaco] H248 Annex K
Date: Sun, 7 Apr 2002 09:28:26 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


I forgot to say that Annex K does allow you to play an announcement a number
of times, but any gap between repetitions has to be an integral part of the
announcement.  You cannot specify the gap separately.

For a more complete announcement capability, see Annex M.1 at
ftp://standards.nortelnetworks.com/megaco/docs/Current/ITU-SG16/ITU%20Last%2
0Call/

-----Original Message-----
From: Taylor, Tom-PT [CAR:B800:EXCH] 
Sent: Sunday, April 07, 2002 9:22 AM
To: 'Koshy'; megaco@ietf.org
Subject: RE: [Megaco] H248 Annex K



The I-D was allowed to expire.  The Annex was approved by the ITU-T.  You
can find a copy at
ftp://standards.nortelnetworks.com/megaco/docs/Approved/

-----Original Message-----
From: Koshy [mailto:koshy@huawei.com]
Sent: Friday, April 05, 2002 9:01 PM
To: megaco@ietf.org
Subject: [Megaco] H248 Annex K


Hi,

Could any one tell what is the status of draft-ietf-megaco-h248k-00(annex
K).

Also is it possible to play an announcement a number of times, with a time
gap between each announcement?

Thanks in advance

Regards
Koshy

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


From daemon@optimus.ietf.org  Sun Apr  7 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 JAA26629
	for <megaco-archive@odin.ietf.org>; Sun, 7 Apr 2002 09:43:49 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA22508
	for megaco-archive@odin.ietf.org; Sun, 7 Apr 2002 09:43:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21675;
	Sun, 7 Apr 2002 09:28:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21647
	for <megaco@optimus.ietf.org>; Sun, 7 Apr 2002 09:28:52 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26450
	for <megaco@ietf.org>; Sun, 7 Apr 2002 09:28:49 -0400 (EDT)
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 g37DSJO03573
	for <megaco@ietf.org>; Sun, 7 Apr 2002 09:28:19 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LB617>; Sun, 7 Apr 2002 09:28:21 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A287@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Koshy'" <koshy@huawei.com>, megaco@ietf.org
Subject: RE: [Megaco] H248 Annex K
Date: Sun, 7 Apr 2002 09:28:26 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


I forgot to say that Annex K does allow you to play an announcement a number
of times, but any gap between repetitions has to be an integral part of the
announcement.  You cannot specify the gap separately.

For a more complete announcement capability, see Annex M.1 at
ftp://standards.nortelnetworks.com/megaco/docs/Current/ITU-SG16/ITU%20Last%2
0Call/

-----Original Message-----
From: Taylor, Tom-PT [CAR:B800:EXCH] 
Sent: Sunday, April 07, 2002 9:22 AM
To: 'Koshy'; megaco@ietf.org
Subject: RE: [Megaco] H248 Annex K



The I-D was allowed to expire.  The Annex was approved by the ITU-T.  You
can find a copy at
ftp://standards.nortelnetworks.com/megaco/docs/Approved/

-----Original Message-----
From: Koshy [mailto:koshy@huawei.com]
Sent: Friday, April 05, 2002 9:01 PM
To: megaco@ietf.org
Subject: [Megaco] H248 Annex K


Hi,

Could any one tell what is the status of draft-ietf-megaco-h248k-00(annex
K).

Also is it possible to play an announcement a number of times, with a time
gap between each announcement?

Thanks in advance

Regards
Koshy

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



From megaco-admin@ietf.org  Sun Apr  7 09:44: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 JAA26651
	for <megaco-archive@odin.ietf.org>; Sun, 7 Apr 2002 09:44:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21505;
	Sun, 7 Apr 2002 09:23:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21477
	for <megaco@optimus.ietf.org>; Sun, 7 Apr 2002 09:23:03 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26407
	for <megaco@ietf.org>; Sun, 7 Apr 2002 09:23:00 -0400 (EDT)
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 g37DMPO03509
	for <megaco@ietf.org>; Sun, 7 Apr 2002 09:22:25 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LB614>; Sun, 7 Apr 2002 09:22:27 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A286@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Koshy'" <koshy@huawei.com>, megaco@ietf.org
Subject: RE: [Megaco] H248 Annex K
Date: Sun, 7 Apr 2002 09:22:32 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


The I-D was allowed to expire.  The Annex was approved by the ITU-T.  You
can find a copy at
ftp://standards.nortelnetworks.com/megaco/docs/Approved/

-----Original Message-----
From: Koshy [mailto:koshy@huawei.com]
Sent: Friday, April 05, 2002 9:01 PM
To: megaco@ietf.org
Subject: [Megaco] H248 Annex K


Hi,

Could any one tell what is the status of draft-ietf-megaco-h248k-00(annex
K).

Also is it possible to play an announcement a number of times, with a time
gap between each announcement?

Thanks in advance

Regards
Koshy

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


From daemon@optimus.ietf.org  Sun Apr  7 09:44: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 JAA26665
	for <megaco-archive@odin.ietf.org>; Sun, 7 Apr 2002 09:44:04 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA22566
	for megaco-archive@odin.ietf.org; Sun, 7 Apr 2002 09:44:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21505;
	Sun, 7 Apr 2002 09:23:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21477
	for <megaco@optimus.ietf.org>; Sun, 7 Apr 2002 09:23:03 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26407
	for <megaco@ietf.org>; Sun, 7 Apr 2002 09:23:00 -0400 (EDT)
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 g37DMPO03509
	for <megaco@ietf.org>; Sun, 7 Apr 2002 09:22:25 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LB614>; Sun, 7 Apr 2002 09:22:27 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A286@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Koshy'" <koshy@huawei.com>, megaco@ietf.org
Subject: RE: [Megaco] H248 Annex K
Date: Sun, 7 Apr 2002 09:22:32 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


The I-D was allowed to expire.  The Annex was approved by the ITU-T.  You
can find a copy at
ftp://standards.nortelnetworks.com/megaco/docs/Approved/

-----Original Message-----
From: Koshy [mailto:koshy@huawei.com]
Sent: Friday, April 05, 2002 9:01 PM
To: megaco@ietf.org
Subject: [Megaco] H248 Annex K


Hi,

Could any one tell what is the status of draft-ietf-megaco-h248k-00(annex
K).

Also is it possible to play an announcement a number of times, with a time
gap between each announcement?

Thanks in advance

Regards
Koshy

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



From megaco-admin@ietf.org  Sun Apr  7 15:58: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 PAA00223
	for <megaco-archive@odin.ietf.org>; Sun, 7 Apr 2002 15:58:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA05620;
	Sun, 7 Apr 2002 15:40:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA28632
	for <megaco@optimus.ietf.org>; Sun, 7 Apr 2002 12:04:29 -0400 (EDT)
Received: from iisc.ernet.in (iisc.ernet.in [144.16.64.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27976
	for <megaco@ietf.org>; Sun, 7 Apr 2002 12:04:23 -0400 (EDT)
Received: from eis.iisc.ernet.in (eis.iisc.ernet.in [144.16.64.5])
	by iisc.ernet.in (8.9.2/8.9.0) with SMTP id VAA47867
	for <megaco@ietf.org>; Sun, 7 Apr 2002 21:43:13 +0530 (IST)
Received: by eis.iisc.ernet.in (SMI-8.6/SMI-4.1)
	id VAA29196; Sun, 7 Apr 2002 21:34:22 +0530
From: anand@eis.iisc.ernet.in (SVR Anand)
Message-Id: <200204071604.VAA29196@eis.iisc.ernet.in>
To: megaco@ietf.org
Date: Sun, 7 Apr 2002 21:34:22 +0530 (GMT+05:30)
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Q.1224 and 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,

Can I notionally map terminology, and the approach, between Q.1224 and 
rfc3015 when it comes to realizing IN CS2 ? Is the following table ok ?

Megaco                  Q.1224
--------                ------

MGC                     SCF
terminations            legs
contexts                CSA     

MG                      SSF/CCF


I will be thankful if you can clarify my understanding.

Anand


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


From daemon@optimus.ietf.org  Sun Apr  7 15:58: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 PAA00234
	for <megaco-archive@odin.ietf.org>; Sun, 7 Apr 2002 15:58:01 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA05999
	for megaco-archive@odin.ietf.org; Sun, 7 Apr 2002 15:58:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA05620;
	Sun, 7 Apr 2002 15:40:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA28632
	for <megaco@optimus.ietf.org>; Sun, 7 Apr 2002 12:04:29 -0400 (EDT)
Received: from iisc.ernet.in (iisc.ernet.in [144.16.64.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27976
	for <megaco@ietf.org>; Sun, 7 Apr 2002 12:04:23 -0400 (EDT)
Received: from eis.iisc.ernet.in (eis.iisc.ernet.in [144.16.64.5])
	by iisc.ernet.in (8.9.2/8.9.0) with SMTP id VAA47867
	for <megaco@ietf.org>; Sun, 7 Apr 2002 21:43:13 +0530 (IST)
Received: by eis.iisc.ernet.in (SMI-8.6/SMI-4.1)
	id VAA29196; Sun, 7 Apr 2002 21:34:22 +0530
From: anand@eis.iisc.ernet.in (SVR Anand)
Message-Id: <200204071604.VAA29196@eis.iisc.ernet.in>
To: megaco@ietf.org
Date: Sun, 7 Apr 2002 21:34:22 +0530 (GMT+05:30)
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Q.1224 and 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,

Can I notionally map terminology, and the approach, between Q.1224 and 
rfc3015 when it comes to realizing IN CS2 ? Is the following table ok ?

Megaco                  Q.1224
--------                ------

MGC                     SCF
terminations            legs
contexts                CSA     

MG                      SSF/CCF


I will be thankful if you can clarify my understanding.

Anand


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



From megaco-admin@ietf.org  Mon Apr  8 00:15: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 AAA06809
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 00:15:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA24403;
	Sun, 7 Apr 2002 23:53:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA24374
	for <megaco@optimus.ietf.org>; Sun, 7 Apr 2002 23:53:01 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06554
	for <megaco@ietf.org>; Sun, 7 Apr 2002 23:52:56 -0400 (EDT)
From: rezhirpavai@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 g383qn308373;
	Mon, 8 Apr 2002 09:22:54 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B95.001508CA ; Mon, 8 Apr 2002 09:19:45 +0530
X-Lotus-FromDomain: HSS
To: anand@eis.iisc.ernet.in (SVR Anand)
cc: megaco@ietf.org
Message-ID: <65256B95.0015085C.00@sandesh.hss.hns.com>
Date: Mon, 8 Apr 2002 09:22:18 +0530
Subject: Re: [Megaco] Q.1224 and Megaco
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



Hello Anand,
     The MG entity applies signals and detects events on terminations as
instructured by MGC. MG does not do the call control functionality. The MGC does
the CCF and SSF functionality. "Terminations" donot exactly map on to the legs
of Q.1224 as in Megaco there could be two physical terminations in one context,
without any ephemeral terminations for hair pin connections, but in Q.1224, the
existence of PL is required for a two party CVS to be complete. Contexts put all
terminations related to that call together. For Call Waiting type of scenario,
there would be two contexts existing and the termination is moved from context
to other. Hence context could map to CS rather than CSA.

Regards,
- R. Ezhirpavai





anand@eis.iisc.ernet.in (SVR Anand) on 04/07/2002 09:34:22 PM

To:   megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  [Megaco] Q.1224 and Megaco




Hi,

Can I notionally map terminology, and the approach, between Q.1224 and
rfc3015 when it comes to realizing IN CS2 ? Is the following table ok ?

Megaco                  Q.1224
--------                ------

MGC                     SCF
terminations            legs
contexts                CSA

MG                      SSF/CCF


I will be thankful if you can clarify my understanding.

Anand


_______________________________________________
Megaco mailing list
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 Apr  8 00:15: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 AAA06820
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 00:15:14 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA25584
	for megaco-archive@odin.ietf.org; Mon, 8 Apr 2002 00:15:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA24403;
	Sun, 7 Apr 2002 23:53:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA24374
	for <megaco@optimus.ietf.org>; Sun, 7 Apr 2002 23:53:01 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06554
	for <megaco@ietf.org>; Sun, 7 Apr 2002 23:52:56 -0400 (EDT)
From: rezhirpavai@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 g383qn308373;
	Mon, 8 Apr 2002 09:22:54 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B95.001508CA ; Mon, 8 Apr 2002 09:19:45 +0530
X-Lotus-FromDomain: HSS
To: anand@eis.iisc.ernet.in (SVR Anand)
cc: megaco@ietf.org
Message-ID: <65256B95.0015085C.00@sandesh.hss.hns.com>
Date: Mon, 8 Apr 2002 09:22:18 +0530
Subject: Re: [Megaco] Q.1224 and Megaco
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



Hello Anand,
     The MG entity applies signals and detects events on terminations as
instructured by MGC. MG does not do the call control functionality. The MGC does
the CCF and SSF functionality. "Terminations" donot exactly map on to the legs
of Q.1224 as in Megaco there could be two physical terminations in one context,
without any ephemeral terminations for hair pin connections, but in Q.1224, the
existence of PL is required for a two party CVS to be complete. Contexts put all
terminations related to that call together. For Call Waiting type of scenario,
there would be two contexts existing and the termination is moved from context
to other. Hence context could map to CS rather than CSA.

Regards,
- R. Ezhirpavai





anand@eis.iisc.ernet.in (SVR Anand) on 04/07/2002 09:34:22 PM

To:   megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  [Megaco] Q.1224 and Megaco




Hi,

Can I notionally map terminology, and the approach, between Q.1224 and
rfc3015 when it comes to realizing IN CS2 ? Is the following table ok ?

Megaco                  Q.1224
--------                ------

MGC                     SCF
terminations            legs
contexts                CSA

MG                      SSF/CCF


I will be thankful if you can clarify my understanding.

Anand


_______________________________________________
Megaco mailing list
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 Apr  8 06:04: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 GAA18925
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 06:04:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22903;
	Mon, 8 Apr 2002 05:49:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22876
	for <megaco@optimus.ietf.org>; Mon, 8 Apr 2002 05:49:01 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18692
	for <megaco@ietf.org>; Mon, 8 Apr 2002 05:48:57 -0400 (EDT)
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 CAA25117
	for <megaco@ietf.org>; Mon, 8 Apr 2002 02:48:55 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 8 Apr 2002 09:48:56 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 CAA15988
	for <megaco@ietf.org>; Mon, 8 Apr 2002 02:48:54 -0700 (PDT)
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 CAA28419
	for <megaco@ietf.org>; Mon, 8 Apr 2002 02:48:54 -0700 (PDT)
Received: from lucent.com (chickasaw.india.ascend.com [135.254.196.183])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id PAA06254
	for <megaco@ietf.org>; Mon, 8 Apr 2002 15:17:33 +0530 (IST)
Message-ID: <3CB16946.D469356B@lucent.com>
Date: Mon, 08 Apr 2002 15:26:22 +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 list <megaco@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Error code for termination out of service..
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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


If MGC adds a termination which is out of service(eg. framing Error on the t1 line) to a context. should MG return an Error. If yes,
can someone tell me the Error Code which needs to be returned by the MG. I could not find a matching Error code for the same in
Annex L.
 
 Second way could be to accept the message indicating MG has brought up the voip call and on the termination which is out of
service.

Ideally, this should not happen as MGC should be knowing termination status. But, if it happens what should MG do ?

Regards,
Shambhu

-- 
-------------------------------------------------------------------
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  Mon Apr  8 06:04: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 GAA18938
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 06:04:52 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA23861
	for megaco-archive@odin.ietf.org; Mon, 8 Apr 2002 06:04:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22903;
	Mon, 8 Apr 2002 05:49:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22876
	for <megaco@optimus.ietf.org>; Mon, 8 Apr 2002 05:49:01 -0400 (EDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18692
	for <megaco@ietf.org>; Mon, 8 Apr 2002 05:48:57 -0400 (EDT)
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 CAA25117
	for <megaco@ietf.org>; Mon, 8 Apr 2002 02:48:55 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 8 Apr 2002 09:48:56 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 CAA15988
	for <megaco@ietf.org>; Mon, 8 Apr 2002 02:48:54 -0700 (PDT)
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 CAA28419
	for <megaco@ietf.org>; Mon, 8 Apr 2002 02:48:54 -0700 (PDT)
Received: from lucent.com (chickasaw.india.ascend.com [135.254.196.183])
	by india.ascend.com (8.8.8+Sun/8.8.8) with ESMTP id PAA06254
	for <megaco@ietf.org>; Mon, 8 Apr 2002 15:17:33 +0530 (IST)
Message-ID: <3CB16946.D469356B@lucent.com>
Date: Mon, 08 Apr 2002 15:26:22 +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 list <megaco@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Error code for termination out of service..
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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


If MGC adds a termination which is out of service(eg. framing Error on the t1 line) to a context. should MG return an Error. If yes,
can someone tell me the Error Code which needs to be returned by the MG. I could not find a matching Error code for the same in
Annex L.
 
 Second way could be to accept the message indicating MG has brought up the voip call and on the termination which is out of
service.

Ideally, this should not happen as MGC should be knowing termination status. But, if it happens what should MG do ?

Regards,
Shambhu

-- 
-------------------------------------------------------------------
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  Mon Apr  8 09: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 JAA22249
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 09:05:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01711;
	Mon, 8 Apr 2002 08:46:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01681
	for <megaco@ns.ietf.org>; Mon, 8 Apr 2002 08:46:40 -0400 (EDT)
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 IAA21762
	for <megaco@ietf.org>; Mon, 8 Apr 2002 08:46:37 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g38Ck8C05479;
	Mon, 8 Apr 2002 08:46:08 -0400 (EDT)
Received: from lucent.com ([192.11.175.176])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id IAA24741;
	Mon, 8 Apr 2002 08:46:46 -0400 (EDT)
Message-ID: <3CB190E8.AAD7E969@lucent.com>
Date: Mon, 08 Apr 2002 08:45:28 -0400
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: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Annex E: RTP package Statistics Delay
References: <3CADDA59.A482EB4A@alcatel.com>
Content-Type: multipart/mixed;
 boundary="------------5BF47D29B0E6A6D7E2230B15"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------5BF47D29B0E6A6D7E2230B15
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think that this means RTP timestamp units rather than TimeStamp
strings.

"Chuong N. Nguyen" wrote:

>
>
>
>    Delay
>         StatisticID:delay (0x0008)
>
>         Requests the current value of packet propagation delay
>         expressed in timestamp units. Same as average latency.
>
> Where is "average latency" defined in the Standard?
>
> Is TimeStamp units the following?
>
>    TimeStamp            = Date "T" Time ; per ISO 8601:1988
>       ; Date = yyyymmdd
>    Date                 = 8(DIGIT)
>       ; Time = hhmmssss
>    Time                 = 8(DIGIT)
>
>
> Do we really intend for this to be timestamp units or just msec?
>
> In the example
>
>              Statistics { rtp/ps=1200,  ; packets sent
>                           nt/os=62300, ; octets sent
>                           rtp/pr=700, ; packets received
>                           nt/or=45100, ; octets received
>                           rtp/pl=0.2,  ; % packet loss
>                           rtp/jit=20,
>                           rtp/delay=40 } ; avg latency  //  Doesn't
> look like timestamp at all.
>
> 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 ****
>
>

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------5BF47D29B0E6A6D7E2230B15
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------5BF47D29B0E6A6D7E2230B15--


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


From daemon@ns.ietf.org  Mon Apr  8 09:05: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 JAA22259
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 09:05:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA02788
	for megaco-archive@odin.ietf.org; Mon, 8 Apr 2002 09:05:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01711;
	Mon, 8 Apr 2002 08:46:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01681
	for <megaco@ns.ietf.org>; Mon, 8 Apr 2002 08:46:40 -0400 (EDT)
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 IAA21762
	for <megaco@ietf.org>; Mon, 8 Apr 2002 08:46:37 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g38Ck8C05479;
	Mon, 8 Apr 2002 08:46:08 -0400 (EDT)
Received: from lucent.com ([192.11.175.176])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id IAA24741;
	Mon, 8 Apr 2002 08:46:46 -0400 (EDT)
Message-ID: <3CB190E8.AAD7E969@lucent.com>
Date: Mon, 08 Apr 2002 08:45:28 -0400
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: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Annex E: RTP package Statistics Delay
References: <3CADDA59.A482EB4A@alcatel.com>
Content-Type: multipart/mixed;
 boundary="------------5BF47D29B0E6A6D7E2230B15"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------5BF47D29B0E6A6D7E2230B15
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think that this means RTP timestamp units rather than TimeStamp
strings.

"Chuong N. Nguyen" wrote:

>
>
>
>    Delay
>         StatisticID:delay (0x0008)
>
>         Requests the current value of packet propagation delay
>         expressed in timestamp units. Same as average latency.
>
> Where is "average latency" defined in the Standard?
>
> Is TimeStamp units the following?
>
>    TimeStamp            = Date "T" Time ; per ISO 8601:1988
>       ; Date = yyyymmdd
>    Date                 = 8(DIGIT)
>       ; Time = hhmmssss
>    Time                 = 8(DIGIT)
>
>
> Do we really intend for this to be timestamp units or just msec?
>
> In the example
>
>              Statistics { rtp/ps=1200,  ; packets sent
>                           nt/os=62300, ; octets sent
>                           rtp/pr=700, ; packets received
>                           nt/or=45100, ; octets received
>                           rtp/pl=0.2,  ; % packet loss
>                           rtp/jit=20,
>                           rtp/delay=40 } ; avg latency  //  Doesn't
> look like timestamp at all.
>
> 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 ****
>
>

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------5BF47D29B0E6A6D7E2230B15
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------5BF47D29B0E6A6D7E2230B15--


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



From megaco-admin@ietf.org  Mon Apr  8 09:33: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 JAA23119
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 09:33:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03496;
	Mon, 8 Apr 2002 09:18:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA19620
	for <megaco@optimus.ietf.org>; Mon, 8 Apr 2002 04:36:31 -0400 (EDT)
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 EAA17928
	for <megaco@ietf.org>; Mon, 8 Apr 2002 04:36:26 -0400 (EDT)
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 g388XAN00917
	for <megaco@ietf.org>; Mon, 8 Apr 2002 17:33:18 +0900 (KST)
Received: from PC ([150.150.59.156])
          by lgekrhqmh01.lge.com (Lotus Domino Release 5.07a)
          with SMTP id 2002040817342945:78326 ;
          Mon, 8 Apr 2002 17:34:29 +0900 
Message-ID: <005601c1ded8$0755f2e0$9c3b9696@PC>
From: =?ks_c_5601-1987?B?v8C787z2?= <osangsu@lge.com>
To: <megaco@ietf.org>
Date: Mon, 8 Apr 2002 17:33:15 +0900
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MIMETrack: Itemize by SMTP Server on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 04/08/2002 05:34:29 PM,
	Serialize by Router on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 04/08/2002 05:36:57 PM,
	Serialize complete at 04/08/2002 05:36:57 PM
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0053_01C1DF23.77235C20"
Subject: [Megaco] Question the T.30 FAX protocals in 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

This is a multi-part message in MIME format.

------=_NextPart_000_0053_01C1DF23.77235C20
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

SGkgQWxsDQoNClRoZXJlIGFyZSBtYW55IGV4YW1wbGVzIGluIHRoZSBULjM4IEZBWCBwcm90b2Nh
bCBTRFAgYW5kIGNhbGxmbG93Lg0KSSBjb3VsZG4ndCBmaW5kIGFueXdoZXJlIFQuMzAgRkFYIHBy
b3RvY2FsIFNEUCBleGFtcGxlIGFuZCBjYWxsZmxvdy4gDQoNCjEuIFNob3VsZCAgdGhlIFQuMzAg
RkFYIHByb3RvY2FsIGNhbGxmbG93IGNvbnRyb2xlZCBieSBNR0MgPw0KICAgIEluIHRoZSBkcmFm
dC1pZXRmLW1lZ2Fjby1oMjQ4Zi0wMS50eHQgLCB0aGF0IGlzIGFtYmlndWl0eSwgIEkgdGhpbmsN
Cg0KMi4gaWYgTUdDIG11c3QgY29udHJvbCBULjMwIEZBWCBjYWxsZmxvdywgQXVkaXQgQ29tbWFu
ZCB3aWxsIGJlIHNlbnQgIHRvIE1HcyBieSBNR0MNCiAgIEhvdyBDb3VsZCBNR0Mgc3RydWN0dXJl
IGNvbW1hbmQgPyAgICAgd2hpY2ggY29tbWFuZHMgYXJlIHJpZ2h0ID8gZWcxIG9yIGVnMiA/DQoN
CiAgIGVnMSkNCiAgIE1FR0FDTy8xIFsyMDcuMTc2LjQ3Ljg5XTogMjcwMDANCiAgIFRyYW5zYWN0
aW9uID0gMTIzNCB7DQogICAgICAgQ29udGV4dCA9IDEgIHsNCiAgICAgICAgICAgQXVkaXRWYWx1
ZT0gYWFsbjAwMDB7QXVkaXQge01lZGlhfSB9DQogICAgICAgICAgfQ0KICAgfQ0KDQogICBlZzIp
DQogICBNRUdBQ08vMSBbMjA3LjE3Ni40Ny44OV06IDI3MDAwDQogICBUcmFuc2FjdGlvbiA9IDEy
MzQgew0KICAgICAgIENvbnRleHQgPSAqIHsNCiAgICAgICAgICAgQXVkaXRWYWx1ZT0gUk9PVCB7
QXVkaXQge01lZGlhfSB9DQogICAgICAgICAgfQ0KICAgfQ0KICAgDQozLiBIb3cgTUdzIGNvdWxk
IG1ha2UgdGhhdCdzIHJlcGx5ID8gIA0KICANCg0KQ291bGQgeW91IGdpdmUgbWUgc29tZSBhZHZp
Y2UgPw0KDQpUaGFua3MsDQpzc2hha28NCiAgDQogICAgDQo=

------=_NextPart_000_0053_01C1DF23.77235C20
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWtzX2NfNTYwMS0xOTg3Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1T
SFRNTCA2LjAwLjI3MTUuNDAwIiBuYW1lPUdFTkVSQVRPUj4NCjxTVFlMRT48L1NUWUxFPg0KPC9I
RUFEPg0KPEJPRFkgYmdDb2xvcj0jZmZmZmZmPg0KPERJVj48Rk9OVCBzaXplPTI+SGkgQWxsPC9G
T05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48
Rk9OVCBzaXplPTI+VGhlcmUgYXJlIG1hbnkgZXhhbXBsZXMmbmJzcDtpbiB0aGUmbmJzcDtULjM4
IEZBWCBwcm90b2NhbCBTRFAgDQphbmQgY2FsbGZsb3cuPC9GT05UPjwvRElWPg0KPERJVj48Rk9O
VCBzaXplPTI+SSBjb3VsZG4ndCZuYnNwO2ZpbmQgYW55d2hlcmUgVC4zMCBGQVggcHJvdG9jYWwm
bmJzcDtTRFAgDQpleGFtcGxlIGFuZCBjYWxsZmxvdy4mbmJzcDs8L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4xLiZu
YnNwO1Nob3VsZCZuYnNwOyB0aGUgVC4zMCBGQVggcHJvdG9jYWwgDQpjYWxsZmxvdyZuYnNwO2Nv
bnRyb2xlZCBieSBNR0MgPzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyZu
YnNwOyZuYnNwOyBJbjwvRk9OVD4mbmJzcDs8Rk9OVCBzaXplPTI+dGhlIA0KZHJhZnQtaWV0Zi1t
ZWdhY28taDI0OGYtMDEudHh0Jm5ic3A7LCB0aGF0IGlzIGFtYmlndWl0eSwgJm5ic3A7SSANCnRo
aW5rPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0K
PERJVj48Rk9OVCBzaXplPTI+Mi4gaWYgTUdDIG11c3QgY29udHJvbCBULjMwIEZBWCBjYWxsZmxv
dywgQXVkaXQgQ29tbWFuZCB3aWxsIA0KYmUmbmJzcDtzZW50ICZuYnNwO3RvJm5ic3A7TUdzIGJ5
IE1HQzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyZuYnNwOyZuYnNwO0hv
dyANCkNvdWxkJm5ic3A7TUdDJm5ic3A7c3RydWN0dXJlJm5ic3A7Y29tbWFuZCA/IA0KJm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7d2hpY2gmbmJzcDtjb21tYW5kcyZuYnNwO2FyZSByaWdodCZuYnNw
Oz8gZWcxIG9yIGVnMiANCj88L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+
Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4mbmJzcDsmbmJzcDsmbmJzcDs8L0ZPTlQ+
PEZPTlQgc2l6ZT0yPmVnMSk8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4mbmJzcDsm
bmJzcDsgTUVHQUNPLzEgWzIwNy4xNzYuNDcuODldOiAyNzAwMDxCUj4mbmJzcDsmbmJzcDsgDQpU
cmFuc2FjdGlvbiA9IDEyMzQgezxCUj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgQ29udGV4dCA9IDEmbmJzcDsgDQp7PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBBdWRpdFZhbHVlPSANCmFhbG4wMDAwe0F1
ZGl0IHtNZWRpYX0gDQp9PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyB9PEJSPiZuYnNwOyZuYnNwOyANCn08L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4mbmJz
cDsmbmJzcDsgZWcyKTwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyZuYnNw
OyBNRUdBQ08vMSBbMjA3LjE3Ni40Ny44OV06IDI3MDAwPEJSPiZuYnNwOyZuYnNwOyANClRyYW5z
YWN0aW9uID0gMTIzNCB7PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBD
b250ZXh0ID0gKiANCns8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEF1ZGl0VmFsdWU9IA0KUk9PVCB7QXVkaXQge01lZGlhfSB9
PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyANCn08QlI+Jm5ic3A7Jm5ic3A7IH08L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4m
bmJzcDsmbmJzcDsgPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+My4mbmJzcDtIb3cm
bmJzcDtNR3MgY291bGQmbmJzcDttYWtlJm5ic3A7dGhhdCdzIHJlcGx5IA0KPyZuYnNwOyZuYnNw
OzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyA8L0ZPTlQ+PC9ESVY+DQo8
RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5D
b3VsZCB5b3UgZ2l2ZSBtZSBzb21lIGFkdmljZSZuYnNwOz88L0ZPTlQ+PC9ESVY+DQo8RElWPjxG
T05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5UaGFua3Ms
PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+c3NoYWtvPC9GT05UPjwvRElWPg0KPERJ
Vj48Rk9OVCBzaXplPTI+Jm5ic3A7Jm5ic3A7PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXpl
PTI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PC9GT05UPjwvRElWPjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_000_0053_01C1DF23.77235C20--



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


From daemon@ns.ietf.org  Mon Apr  8 09:33: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 JAA23132
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 09:33:46 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA04859
	for megaco-archive@odin.ietf.org; Mon, 8 Apr 2002 09:33:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03496;
	Mon, 8 Apr 2002 09:18:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA19620
	for <megaco@optimus.ietf.org>; Mon, 8 Apr 2002 04:36:31 -0400 (EDT)
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 EAA17928
	for <megaco@ietf.org>; Mon, 8 Apr 2002 04:36:26 -0400 (EDT)
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 g388XAN00917
	for <megaco@ietf.org>; Mon, 8 Apr 2002 17:33:18 +0900 (KST)
Received: from PC ([150.150.59.156])
          by lgekrhqmh01.lge.com (Lotus Domino Release 5.07a)
          with SMTP id 2002040817342945:78326 ;
          Mon, 8 Apr 2002 17:34:29 +0900 
Message-ID: <005601c1ded8$0755f2e0$9c3b9696@PC>
From: =?ks_c_5601-1987?B?v8C787z2?= <osangsu@lge.com>
To: <megaco@ietf.org>
Date: Mon, 8 Apr 2002 17:33:15 +0900
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MIMETrack: Itemize by SMTP Server on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 04/08/2002 05:34:29 PM,
	Serialize by Router on LGEKRHQMH01/LGE/LG Group(Release 5.07a |May 14, 2001) at
 04/08/2002 05:36:57 PM,
	Serialize complete at 04/08/2002 05:36:57 PM
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0053_01C1DF23.77235C20"
Subject: [Megaco] Question the T.30 FAX protocals in 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

This is a multi-part message in MIME format.

------=_NextPart_000_0053_01C1DF23.77235C20
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

SGkgQWxsDQoNClRoZXJlIGFyZSBtYW55IGV4YW1wbGVzIGluIHRoZSBULjM4IEZBWCBwcm90b2Nh
bCBTRFAgYW5kIGNhbGxmbG93Lg0KSSBjb3VsZG4ndCBmaW5kIGFueXdoZXJlIFQuMzAgRkFYIHBy
b3RvY2FsIFNEUCBleGFtcGxlIGFuZCBjYWxsZmxvdy4gDQoNCjEuIFNob3VsZCAgdGhlIFQuMzAg
RkFYIHByb3RvY2FsIGNhbGxmbG93IGNvbnRyb2xlZCBieSBNR0MgPw0KICAgIEluIHRoZSBkcmFm
dC1pZXRmLW1lZ2Fjby1oMjQ4Zi0wMS50eHQgLCB0aGF0IGlzIGFtYmlndWl0eSwgIEkgdGhpbmsN
Cg0KMi4gaWYgTUdDIG11c3QgY29udHJvbCBULjMwIEZBWCBjYWxsZmxvdywgQXVkaXQgQ29tbWFu
ZCB3aWxsIGJlIHNlbnQgIHRvIE1HcyBieSBNR0MNCiAgIEhvdyBDb3VsZCBNR0Mgc3RydWN0dXJl
IGNvbW1hbmQgPyAgICAgd2hpY2ggY29tbWFuZHMgYXJlIHJpZ2h0ID8gZWcxIG9yIGVnMiA/DQoN
CiAgIGVnMSkNCiAgIE1FR0FDTy8xIFsyMDcuMTc2LjQ3Ljg5XTogMjcwMDANCiAgIFRyYW5zYWN0
aW9uID0gMTIzNCB7DQogICAgICAgQ29udGV4dCA9IDEgIHsNCiAgICAgICAgICAgQXVkaXRWYWx1
ZT0gYWFsbjAwMDB7QXVkaXQge01lZGlhfSB9DQogICAgICAgICAgfQ0KICAgfQ0KDQogICBlZzIp
DQogICBNRUdBQ08vMSBbMjA3LjE3Ni40Ny44OV06IDI3MDAwDQogICBUcmFuc2FjdGlvbiA9IDEy
MzQgew0KICAgICAgIENvbnRleHQgPSAqIHsNCiAgICAgICAgICAgQXVkaXRWYWx1ZT0gUk9PVCB7
QXVkaXQge01lZGlhfSB9DQogICAgICAgICAgfQ0KICAgfQ0KICAgDQozLiBIb3cgTUdzIGNvdWxk
IG1ha2UgdGhhdCdzIHJlcGx5ID8gIA0KICANCg0KQ291bGQgeW91IGdpdmUgbWUgc29tZSBhZHZp
Y2UgPw0KDQpUaGFua3MsDQpzc2hha28NCiAgDQogICAgDQo=

------=_NextPart_000_0053_01C1DF23.77235C20
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWtzX2NfNTYwMS0xOTg3Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1T
SFRNTCA2LjAwLjI3MTUuNDAwIiBuYW1lPUdFTkVSQVRPUj4NCjxTVFlMRT48L1NUWUxFPg0KPC9I
RUFEPg0KPEJPRFkgYmdDb2xvcj0jZmZmZmZmPg0KPERJVj48Rk9OVCBzaXplPTI+SGkgQWxsPC9G
T05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48
Rk9OVCBzaXplPTI+VGhlcmUgYXJlIG1hbnkgZXhhbXBsZXMmbmJzcDtpbiB0aGUmbmJzcDtULjM4
IEZBWCBwcm90b2NhbCBTRFAgDQphbmQgY2FsbGZsb3cuPC9GT05UPjwvRElWPg0KPERJVj48Rk9O
VCBzaXplPTI+SSBjb3VsZG4ndCZuYnNwO2ZpbmQgYW55d2hlcmUgVC4zMCBGQVggcHJvdG9jYWwm
bmJzcDtTRFAgDQpleGFtcGxlIGFuZCBjYWxsZmxvdy4mbmJzcDs8L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4xLiZu
YnNwO1Nob3VsZCZuYnNwOyB0aGUgVC4zMCBGQVggcHJvdG9jYWwgDQpjYWxsZmxvdyZuYnNwO2Nv
bnRyb2xlZCBieSBNR0MgPzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyZu
YnNwOyZuYnNwOyBJbjwvRk9OVD4mbmJzcDs8Rk9OVCBzaXplPTI+dGhlIA0KZHJhZnQtaWV0Zi1t
ZWdhY28taDI0OGYtMDEudHh0Jm5ic3A7LCB0aGF0IGlzIGFtYmlndWl0eSwgJm5ic3A7SSANCnRo
aW5rPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0K
PERJVj48Rk9OVCBzaXplPTI+Mi4gaWYgTUdDIG11c3QgY29udHJvbCBULjMwIEZBWCBjYWxsZmxv
dywgQXVkaXQgQ29tbWFuZCB3aWxsIA0KYmUmbmJzcDtzZW50ICZuYnNwO3RvJm5ic3A7TUdzIGJ5
IE1HQzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyZuYnNwOyZuYnNwO0hv
dyANCkNvdWxkJm5ic3A7TUdDJm5ic3A7c3RydWN0dXJlJm5ic3A7Y29tbWFuZCA/IA0KJm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7d2hpY2gmbmJzcDtjb21tYW5kcyZuYnNwO2FyZSByaWdodCZuYnNw
Oz8gZWcxIG9yIGVnMiANCj88L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+
Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4mbmJzcDsmbmJzcDsmbmJzcDs8L0ZPTlQ+
PEZPTlQgc2l6ZT0yPmVnMSk8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4mbmJzcDsm
bmJzcDsgTUVHQUNPLzEgWzIwNy4xNzYuNDcuODldOiAyNzAwMDxCUj4mbmJzcDsmbmJzcDsgDQpU
cmFuc2FjdGlvbiA9IDEyMzQgezxCUj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgQ29udGV4dCA9IDEmbmJzcDsgDQp7PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBBdWRpdFZhbHVlPSANCmFhbG4wMDAwe0F1
ZGl0IHtNZWRpYX0gDQp9PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyB9PEJSPiZuYnNwOyZuYnNwOyANCn08L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4mbmJz
cDsmbmJzcDsgZWcyKTwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyZuYnNw
OyBNRUdBQ08vMSBbMjA3LjE3Ni40Ny44OV06IDI3MDAwPEJSPiZuYnNwOyZuYnNwOyANClRyYW5z
YWN0aW9uID0gMTIzNCB7PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBD
b250ZXh0ID0gKiANCns8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEF1ZGl0VmFsdWU9IA0KUk9PVCB7QXVkaXQge01lZGlhfSB9
PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyANCn08QlI+Jm5ic3A7Jm5ic3A7IH08L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4m
bmJzcDsmbmJzcDsgPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+My4mbmJzcDtIb3cm
bmJzcDtNR3MgY291bGQmbmJzcDttYWtlJm5ic3A7dGhhdCdzIHJlcGx5IA0KPyZuYnNwOyZuYnNw
OzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyA8L0ZPTlQ+PC9ESVY+DQo8
RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5D
b3VsZCB5b3UgZ2l2ZSBtZSBzb21lIGFkdmljZSZuYnNwOz88L0ZPTlQ+PC9ESVY+DQo8RElWPjxG
T05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5UaGFua3Ms
PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+c3NoYWtvPC9GT05UPjwvRElWPg0KPERJ
Vj48Rk9OVCBzaXplPTI+Jm5ic3A7Jm5ic3A7PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXpl
PTI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PC9GT05UPjwvRElWPjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_000_0053_01C1DF23.77235C20--



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



From megaco-admin@ietf.org  Mon Apr  8 09: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 JAA23159
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 09:35:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03542;
	Mon, 8 Apr 2002 09:18:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03510
	for <megaco@ns.ietf.org>; Mon, 8 Apr 2002 09:18:41 -0400 (EDT)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22676
	for <megaco@ietf.org>; Mon, 8 Apr 2002 09:18:39 -0400 (EDT)
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 g38DIBV07498
	for <megaco@ietf.org>; Mon, 8 Apr 2002 08:18:11 -0500 (CDT)
Received: from cls7ws1.ssd.usa.alcatel.com (cls7ws1.ssd.usa.alcatel.com [143.209.236.42])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g38DHfO17008
	for <megaco@ietf.org>; Mon, 8 Apr 2002 08:17:41 -0500 (CDT)
Received: from alcatel.com (localhost [127.0.0.1])
	by cls7ws1.ssd.usa.alcatel.com (8.9.3+Sun/8.9.1) with ESMTP id IAA08560
	for <megaco@ietf.org>; Mon, 8 Apr 2002 08:17:32 -0500 (CDT)
Message-ID: <3CB1986B.3D762BD0@alcatel.com>
Date: Mon, 08 Apr 2002 08:17:32 -0500
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] Annex E: RTP package Statistics Delay
References: <3CADDA59.A482EB4A@alcatel.com> <3CB190E8.AAD7E969@lucent.com>
Content-Type: multipart/alternative;
 boundary="------------ADD8CFAF9E8BA381A5399A13"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


What is RTP timestamp units and where can I get the official definition for
it?

Also in Annex C C.1 General Media Attributes

  +-------------------+------+-------------+---------------------------+
  | PropDelay         | 100E | Unsigned    | Propagation Delay:        |
  |                   |      | Integer     | 0..65535                  |
  +-------------------+------+-------------+---------------------------+
  | Maximum propagation delay in milliseconds for the bearer           |
  | connection between two  media gateways. The maximum delay will be  |
  | dependent on the bearer technology.                                |

So do they both mean the same thing so they should both have the same units
- msec?

Thanks
Chuong



Terry L Anderson wrote:

> I think that this means RTP timestamp units rather than TimeStamp
> strings.
>
> "Chuong N. Nguyen" wrote:
>
> >
> >
> >
> >    Delay
> >         StatisticID:delay (0x0008)
> >
> >         Requests the current value of packet propagation delay
> >         expressed in timestamp units. Same as average latency.
> >
> > Where is "average latency" defined in the Standard?
> >
> > Is TimeStamp units the following?
> >
> >    TimeStamp            = Date "T" Time ; per ISO 8601:1988
> >       ; Date = yyyymmdd
> >    Date                 = 8(DIGIT)
> >       ; Time = hhmmssss
> >    Time                 = 8(DIGIT)
> >
> >
> > Do we really intend for this to be timestamp units or just msec?
> >
> > In the example
> >
> >              Statistics { rtp/ps=1200,  ; packets sent
> >                           nt/os=62300, ; octets sent
> >                           rtp/pr=700, ; packets received
> >                           nt/or=45100, ; octets received
> >                           rtp/pl=0.2,  ; % packet loss
> >                           rtp/jit=20,
> >                           rtp/delay=40 } ; avg latency  //  Doesn't
> > look like timestamp at all.
> >
> > 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 ****
> >
> >
>
> --
> -------------------------------------------------------
> Terry L Anderson, DMTS                   tla@lucent.com
> Lucent Technologies /INS/ Voice over IP Access Networks
> Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
> Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
> 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 ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>What is RTP timestamp units and where can I&nbsp;get the official definition
for it?
<p>Also in Annex C C.1 General Media Attributes
<p>&nbsp; +-------------------+------+-------------+---------------------------+
<br>&nbsp; | PropDelay&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| 100E | Unsigned&nbsp;&nbsp;&nbsp; | Propagation Delay:&nbsp;&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;&nbsp;&nbsp;&nbsp;&nbsp; | Integer&nbsp;&nbsp;&nbsp;&nbsp; | 0..65535&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|
<br>&nbsp; +-------------------+------+-------------+---------------------------+
<br>&nbsp; | Maximum propagation delay in milliseconds for the bearer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|
<br>&nbsp; | connection between two&nbsp; media gateways. The maximum delay
will be&nbsp; |
<br>&nbsp; | dependent on the bearer technology.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|
<p>So do they both mean the same thing so they should both have the same
units - msec?
<p>Thanks
<br>Chuong
<br>&nbsp;
<br>&nbsp;
<p>Terry L Anderson wrote:
<blockquote TYPE=CITE>I think that this means RTP timestamp units rather
than TimeStamp
<br>strings.
<p>"Chuong N. Nguyen" wrote:
<p>>
<br>>
<br>>
<br>>&nbsp;&nbsp;&nbsp; Delay
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; StatisticID:delay
(0x0008)
<br>>
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Requests the current
value of packet propagation delay
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; expressed in timestamp
units. Same as average latency.
<br>>
<br>> Where is "average latency" defined in the Standard?
<br>>
<br>> Is TimeStamp units the following?
<br>>
<br>>&nbsp;&nbsp;&nbsp; TimeStamp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= Date "T" Time ; per ISO 8601:1988
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; Date = yyyymmdd
<br>>&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= 8(DIGIT)
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; Time = hhmmssss
<br>>&nbsp;&nbsp;&nbsp; Time&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= 8(DIGIT)
<br>>
<br>>
<br>> Do we really intend for this to be timestamp units or just msec?
<br>>
<br>> In the example
<br>>
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Statistics { rtp/ps=1200,&nbsp; ; packets sent
<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;
nt/os=62300, ; octets sent
<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;
rtp/pr=700, ; packets received
<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;
nt/or=45100, ; octets received
<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;
rtp/pl=0.2,&nbsp; ; % packet loss
<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;
rtp/jit=20,
<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;
rtp/delay=40 } ; avg latency&nbsp; //&nbsp; Doesn't
<br>> look like timestamp at all.
<br>>
<br>> Thanks
<br>> Chuong
<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>>
<p>--
<br>-------------------------------------------------------
<br>Terry L Anderson, DMTS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
tla@lucent.com
<br>Lucent Technologies /INS/ Voice over IP Access Networks
<br>Rm 2B-121,&nbsp;&nbsp; 600 Mountain Ave, Murray Hill, NJ 07974
<br>Voice:908 582-7013&nbsp; FAX:908 582-6226&nbsp;&nbsp; Org:18E75000000
<br><a href="http://its.lucent.com/~tla">http://its.lucent.com/~tla</a>&nbsp;
(Lucent internal)
<br><a href="http://www.gti.net/tla">http://www.gti.net/tla</a>
<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>

--------------ADD8CFAF9E8BA381A5399A13--


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


From daemon@ns.ietf.org  Mon Apr  8 09:35: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 JAA23170
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 09:35:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA04960
	for megaco-archive@odin.ietf.org; Mon, 8 Apr 2002 09:35:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03542;
	Mon, 8 Apr 2002 09:18:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA03510
	for <megaco@ns.ietf.org>; Mon, 8 Apr 2002 09:18:41 -0400 (EDT)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22676
	for <megaco@ietf.org>; Mon, 8 Apr 2002 09:18:39 -0400 (EDT)
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 g38DIBV07498
	for <megaco@ietf.org>; Mon, 8 Apr 2002 08:18:11 -0500 (CDT)
Received: from cls7ws1.ssd.usa.alcatel.com (cls7ws1.ssd.usa.alcatel.com [143.209.236.42])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g38DHfO17008
	for <megaco@ietf.org>; Mon, 8 Apr 2002 08:17:41 -0500 (CDT)
Received: from alcatel.com (localhost [127.0.0.1])
	by cls7ws1.ssd.usa.alcatel.com (8.9.3+Sun/8.9.1) with ESMTP id IAA08560
	for <megaco@ietf.org>; Mon, 8 Apr 2002 08:17:32 -0500 (CDT)
Message-ID: <3CB1986B.3D762BD0@alcatel.com>
Date: Mon, 08 Apr 2002 08:17:32 -0500
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] Annex E: RTP package Statistics Delay
References: <3CADDA59.A482EB4A@alcatel.com> <3CB190E8.AAD7E969@lucent.com>
Content-Type: multipart/alternative;
 boundary="------------ADD8CFAF9E8BA381A5399A13"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


What is RTP timestamp units and where can I get the official definition for
it?

Also in Annex C C.1 General Media Attributes

  +-------------------+------+-------------+---------------------------+
  | PropDelay         | 100E | Unsigned    | Propagation Delay:        |
  |                   |      | Integer     | 0..65535                  |
  +-------------------+------+-------------+---------------------------+
  | Maximum propagation delay in milliseconds for the bearer           |
  | connection between two  media gateways. The maximum delay will be  |
  | dependent on the bearer technology.                                |

So do they both mean the same thing so they should both have the same units
- msec?

Thanks
Chuong



Terry L Anderson wrote:

> I think that this means RTP timestamp units rather than TimeStamp
> strings.
>
> "Chuong N. Nguyen" wrote:
>
> >
> >
> >
> >    Delay
> >         StatisticID:delay (0x0008)
> >
> >         Requests the current value of packet propagation delay
> >         expressed in timestamp units. Same as average latency.
> >
> > Where is "average latency" defined in the Standard?
> >
> > Is TimeStamp units the following?
> >
> >    TimeStamp            = Date "T" Time ; per ISO 8601:1988
> >       ; Date = yyyymmdd
> >    Date                 = 8(DIGIT)
> >       ; Time = hhmmssss
> >    Time                 = 8(DIGIT)
> >
> >
> > Do we really intend for this to be timestamp units or just msec?
> >
> > In the example
> >
> >              Statistics { rtp/ps=1200,  ; packets sent
> >                           nt/os=62300, ; octets sent
> >                           rtp/pr=700, ; packets received
> >                           nt/or=45100, ; octets received
> >                           rtp/pl=0.2,  ; % packet loss
> >                           rtp/jit=20,
> >                           rtp/delay=40 } ; avg latency  //  Doesn't
> > look like timestamp at all.
> >
> > 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 ****
> >
> >
>
> --
> -------------------------------------------------------
> Terry L Anderson, DMTS                   tla@lucent.com
> Lucent Technologies /INS/ Voice over IP Access Networks
> Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
> Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
> 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 ****



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>What is RTP timestamp units and where can I&nbsp;get the official definition
for it?
<p>Also in Annex C C.1 General Media Attributes
<p>&nbsp; +-------------------+------+-------------+---------------------------+
<br>&nbsp; | PropDelay&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| 100E | Unsigned&nbsp;&nbsp;&nbsp; | Propagation Delay:&nbsp;&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;&nbsp;&nbsp;&nbsp;&nbsp; | Integer&nbsp;&nbsp;&nbsp;&nbsp; | 0..65535&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|
<br>&nbsp; +-------------------+------+-------------+---------------------------+
<br>&nbsp; | Maximum propagation delay in milliseconds for the bearer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|
<br>&nbsp; | connection between two&nbsp; media gateways. The maximum delay
will be&nbsp; |
<br>&nbsp; | dependent on the bearer technology.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|
<p>So do they both mean the same thing so they should both have the same
units - msec?
<p>Thanks
<br>Chuong
<br>&nbsp;
<br>&nbsp;
<p>Terry L Anderson wrote:
<blockquote TYPE=CITE>I think that this means RTP timestamp units rather
than TimeStamp
<br>strings.
<p>"Chuong N. Nguyen" wrote:
<p>>
<br>>
<br>>
<br>>&nbsp;&nbsp;&nbsp; Delay
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; StatisticID:delay
(0x0008)
<br>>
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Requests the current
value of packet propagation delay
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; expressed in timestamp
units. Same as average latency.
<br>>
<br>> Where is "average latency" defined in the Standard?
<br>>
<br>> Is TimeStamp units the following?
<br>>
<br>>&nbsp;&nbsp;&nbsp; TimeStamp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= Date "T" Time ; per ISO 8601:1988
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; Date = yyyymmdd
<br>>&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= 8(DIGIT)
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ; Time = hhmmssss
<br>>&nbsp;&nbsp;&nbsp; Time&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
= 8(DIGIT)
<br>>
<br>>
<br>> Do we really intend for this to be timestamp units or just msec?
<br>>
<br>> In the example
<br>>
<br>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Statistics { rtp/ps=1200,&nbsp; ; packets sent
<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;
nt/os=62300, ; octets sent
<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;
rtp/pr=700, ; packets received
<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;
nt/or=45100, ; octets received
<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;
rtp/pl=0.2,&nbsp; ; % packet loss
<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;
rtp/jit=20,
<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;
rtp/delay=40 } ; avg latency&nbsp; //&nbsp; Doesn't
<br>> look like timestamp at all.
<br>>
<br>> Thanks
<br>> Chuong
<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>>
<p>--
<br>-------------------------------------------------------
<br>Terry L Anderson, DMTS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
tla@lucent.com
<br>Lucent Technologies /INS/ Voice over IP Access Networks
<br>Rm 2B-121,&nbsp;&nbsp; 600 Mountain Ave, Murray Hill, NJ 07974
<br>Voice:908 582-7013&nbsp; FAX:908 582-6226&nbsp;&nbsp; Org:18E75000000
<br><a href="http://its.lucent.com/~tla">http://its.lucent.com/~tla</a>&nbsp;
(Lucent internal)
<br><a href="http://www.gti.net/tla">http://www.gti.net/tla</a>
<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>

--------------ADD8CFAF9E8BA381A5399A13--


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



From megaco-admin@ietf.org  Mon Apr  8 11:40: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 LAA27329
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 11:40:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13722;
	Mon, 8 Apr 2002 11:19:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13692
	for <megaco@ns.ietf.org>; Mon, 8 Apr 2002 11:19:54 -0400 (EDT)
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 LAA26713
	for <megaco@ietf.org>; Mon, 8 Apr 2002 11:19:47 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g38FJnu08398;
	Mon, 8 Apr 2002 11:19:49 -0400 (EDT)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA02203;
	Mon, 8 Apr 2002 11:20:32 -0400 (EDT)
Message-ID: <3CB1B51F.2FB1001@lucent.com>
Date: Mon, 08 Apr 2002 11:19:59 -0400
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: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Annex E: RTP package Statistics Delay
References: <3CADDA59.A482EB4A@alcatel.com> <3CB190E8.AAD7E969@lucent.com> <3CB1986B.3D762BD0@alcatel.com>
Content-Type: multipart/mixed;
 boundary="------------725944CA6D1A6DC85B2ED72F"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------725944CA6D1A6DC85B2ED72F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

According to RFC 1889, the RTP timestamp interval varies with the
payload and is specified in the payload spec but is usually the sampling
interval, eg. 1/8000 sec for most audio codecs.  Note that latency can
be calculated from RTCP reports which use this same unit.

I assume that Annex C's PropDelay is the sender's estimate for a maximum
value of latency that should be encountered, but is given in millisec,
possibly to be independent of payload type(?).

"Chuong N. Nguyen" wrote:

>
> What is RTP timestamp units and where can I get the official
> definition for it?
>
> Also in Annex C C.1 General Media Attributes
>
>
> +-------------------+------+-------------+---------------------------+
>
>   | PropDelay         | 100E | Unsigned    | Propagation Delay:
> |
>   |                   |      | Integer     | 0..65535
> |
>
> +-------------------+------+-------------+---------------------------+
>
>   | Maximum propagation delay in milliseconds for the bearer
> |
>   | connection between two  media gateways. The maximum delay will be
> |
>   | dependent on the bearer technology.
> |
>
> So do they both mean the same thing so they should both have the same
> units - msec?
>
> Thanks
> Chuong
>
>
>
> Terry L Anderson wrote:
>
>> I think that this means RTP timestamp units rather than TimeStamp
>> strings.
>>
>> "Chuong N. Nguyen" wrote:
>>
>> >
>> >
>> >
>> >    Delay
>> >         StatisticID:delay (0x0008)
>> >
>> >         Requests the current value of packet propagation delay
>> >         expressed in timestamp units. Same as average latency.
>> >
>> > Where is "average latency" defined in the Standard?
>> >
>> > Is TimeStamp units the following?
>> >
>> >    TimeStamp            = Date "T" Time ; per ISO 8601:1988
>> >       ; Date = yyyymmdd
>> >    Date                 = 8(DIGIT)
>> >       ; Time = hhmmssss
>> >    Time                 = 8(DIGIT)
>> >
>> >
>> > Do we really intend for this to be timestamp units or just msec?
>> >
>> > In the example
>> >
>> >              Statistics { rtp/ps=1200,  ; packets sent
>> >                           nt/os=62300, ; octets sent
>> >                           rtp/pr=700, ; packets received
>> >                           nt/or=45100, ; octets received
>> >                           rtp/pl=0.2,  ; % packet loss
>> >                           rtp/jit=20,
>> >                           rtp/delay=40 } ; avg latency  //
>> Doesn't
>> > look like timestamp at all.
>> >
>> > 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
>> ****
>> >
>> >
>>
>> --
>> -------------------------------------------------------
>> Terry L Anderson, DMTS                   tla@lucent.com
>> Lucent Technologies /INS/ Voice over IP Access Networks
>> Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
>> Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
>> 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 ****
>
>

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------725944CA6D1A6DC85B2ED72F
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------725944CA6D1A6DC85B2ED72F--


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


From daemon@ns.ietf.org  Mon Apr  8 11:40: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 LAA27339
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 11:40:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA15596
	for megaco-archive@odin.ietf.org; Mon, 8 Apr 2002 11:40:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13722;
	Mon, 8 Apr 2002 11:19:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13692
	for <megaco@ns.ietf.org>; Mon, 8 Apr 2002 11:19:54 -0400 (EDT)
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 LAA26713
	for <megaco@ietf.org>; Mon, 8 Apr 2002 11:19:47 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g38FJnu08398;
	Mon, 8 Apr 2002 11:19:49 -0400 (EDT)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA02203;
	Mon, 8 Apr 2002 11:20:32 -0400 (EDT)
Message-ID: <3CB1B51F.2FB1001@lucent.com>
Date: Mon, 08 Apr 2002 11:19:59 -0400
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: "Chuong N. Nguyen" <Chuong.Nguyen@alcatel.com>
CC: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] Annex E: RTP package Statistics Delay
References: <3CADDA59.A482EB4A@alcatel.com> <3CB190E8.AAD7E969@lucent.com> <3CB1986B.3D762BD0@alcatel.com>
Content-Type: multipart/mixed;
 boundary="------------725944CA6D1A6DC85B2ED72F"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------725944CA6D1A6DC85B2ED72F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

According to RFC 1889, the RTP timestamp interval varies with the
payload and is specified in the payload spec but is usually the sampling
interval, eg. 1/8000 sec for most audio codecs.  Note that latency can
be calculated from RTCP reports which use this same unit.

I assume that Annex C's PropDelay is the sender's estimate for a maximum
value of latency that should be encountered, but is given in millisec,
possibly to be independent of payload type(?).

"Chuong N. Nguyen" wrote:

>
> What is RTP timestamp units and where can I get the official
> definition for it?
>
> Also in Annex C C.1 General Media Attributes
>
>
> +-------------------+------+-------------+---------------------------+
>
>   | PropDelay         | 100E | Unsigned    | Propagation Delay:
> |
>   |                   |      | Integer     | 0..65535
> |
>
> +-------------------+------+-------------+---------------------------+
>
>   | Maximum propagation delay in milliseconds for the bearer
> |
>   | connection between two  media gateways. The maximum delay will be
> |
>   | dependent on the bearer technology.
> |
>
> So do they both mean the same thing so they should both have the same
> units - msec?
>
> Thanks
> Chuong
>
>
>
> Terry L Anderson wrote:
>
>> I think that this means RTP timestamp units rather than TimeStamp
>> strings.
>>
>> "Chuong N. Nguyen" wrote:
>>
>> >
>> >
>> >
>> >    Delay
>> >         StatisticID:delay (0x0008)
>> >
>> >         Requests the current value of packet propagation delay
>> >         expressed in timestamp units. Same as average latency.
>> >
>> > Where is "average latency" defined in the Standard?
>> >
>> > Is TimeStamp units the following?
>> >
>> >    TimeStamp            = Date "T" Time ; per ISO 8601:1988
>> >       ; Date = yyyymmdd
>> >    Date                 = 8(DIGIT)
>> >       ; Time = hhmmssss
>> >    Time                 = 8(DIGIT)
>> >
>> >
>> > Do we really intend for this to be timestamp units or just msec?
>> >
>> > In the example
>> >
>> >              Statistics { rtp/ps=1200,  ; packets sent
>> >                           nt/os=62300, ; octets sent
>> >                           rtp/pr=700, ; packets received
>> >                           nt/or=45100, ; octets received
>> >                           rtp/pl=0.2,  ; % packet loss
>> >                           rtp/jit=20,
>> >                           rtp/delay=40 } ; avg latency  //
>> Doesn't
>> > look like timestamp at all.
>> >
>> > 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
>> ****
>> >
>> >
>>
>> --
>> -------------------------------------------------------
>> Terry L Anderson, DMTS                   tla@lucent.com
>> Lucent Technologies /INS/ Voice over IP Access Networks
>> Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
>> Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
>> 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 ****
>
>

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------725944CA6D1A6DC85B2ED72F
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------725944CA6D1A6DC85B2ED72F--


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



From megaco-admin@ietf.org  Mon Apr  8 11: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 LAA27685
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 11:50:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14187;
	Mon, 8 Apr 2002 11:29:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14156
	for <megaco@ns.ietf.org>; Mon, 8 Apr 2002 11:29:32 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27008
	for <megaco@ietf.org>; Mon, 8 Apr 2002 11:29:27 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g38FSri18093
	for <megaco@ietf.org>; Mon, 8 Apr 2002 11:28:54 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LCGV4>; Mon, 8 Apr 2002 11:28:53 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A295@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>,
        "'itu-sg16@mailbag.intel.com'"
	 <itu-sg16@echo.jf.intel.com>
Date: Mon, 8 Apr 2002 11:28:51 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Application-Specific Megaco Error Codes
Sender: megaco-admin@ietf.org
Errors-To: 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 has been bothering me for quite a while that we have no guidelines for
the numbering of error codes, so they could be all over the map.  For
example, I created codes in the NAS packages starting with 100, simply
because this was the first example of package-documented error codes.  Since
these codes were not yet registered with IANA, it may not be too late to
enforce the following convention, following the precedent set by H.,248
Annex M.1:

Proposal: application-specific error codes are assigned consecutive values
starting at 600.

Following on this proposal, I am changing the NAS error codes to 613-616
from 100-103.

Comments?

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  Mon Apr  8 11: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 LAA27700
	for <megaco-archive@odin.ietf.org>; Mon, 8 Apr 2002 11:50:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA16450
	for megaco-archive@odin.ietf.org; Mon, 8 Apr 2002 11:50:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14187;
	Mon, 8 Apr 2002 11:29:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14156
	for <megaco@ns.ietf.org>; Mon, 8 Apr 2002 11:29:32 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27008
	for <megaco@ietf.org>; Mon, 8 Apr 2002 11:29:27 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g38FSri18093
	for <megaco@ietf.org>; Mon, 8 Apr 2002 11:28:54 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LCGV4>; Mon, 8 Apr 2002 11:28:53 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A295@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>,
        "'itu-sg16@mailbag.intel.com'"
	 <itu-sg16@echo.jf.intel.com>
Date: Mon, 8 Apr 2002 11:28:51 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Application-Specific Megaco Error Codes
Sender: megaco-admin@ietf.org
Errors-To: 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 has been bothering me for quite a while that we have no guidelines for
the numbering of error codes, so they could be all over the map.  For
example, I created codes in the NAS packages starting with 100, simply
because this was the first example of package-documented error codes.  Since
these codes were not yet registered with IANA, it may not be too late to
enforce the following convention, following the precedent set by H.,248
Annex M.1:

Proposal: application-specific error codes are assigned consecutive values
starting at 600.

Following on this proposal, I am changing the NAS error codes to 613-616
from 100-103.

Comments?

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 Apr  9 07:50: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 HAA02399
	for <megaco-archive@odin.ietf.org>; Tue, 9 Apr 2002 07:50:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA10913;
	Tue, 9 Apr 2002 07:22:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA10886
	for <megaco@optimus.ietf.org>; Tue, 9 Apr 2002 07:22:55 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02025
	for <megaco@ietf.org>; Tue, 9 Apr 2002 07:22:52 -0400 (EDT)
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 g39BMq3G027501
	for <megaco@ietf.org>; Tue, 9 Apr 2002 13:22:52 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g39BMqUD007976
	for <megaco@ietf.org>; Tue, 9 Apr 2002 14:22:52 +0300 (EET DST)
Message-ID: <3CB2CF0D.D32374BE@lmf.ericsson.se>
Date: Tue, 09 Apr 2002 14:22:54 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (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] Bit order
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 clarification question:

Annex B.3 says:

>B.3     Hexadecimal octet coding
>    Hexadecimal octet coding is a means for representing a string of
>   octets as a string of hexadecimal digits, with two digits
>   representing each octet. This octet encoding should be used when
>   encoding octet strings in the text version of the protocol.
>   For each octet, the 8-bit sequence is encoded as two hexadecimal
>   digits. Bit 0 is the first transmitted; bit 7 is the last.
>   Bits 7-4 are encoded as the first hexadecimal digit, with Bit 7 as
>   MSB and Bit 4 as LSB. Bits 3-0 are encoded as the second hexadecimal

>   digit, with Bit 3 as MSB and Bit 0 as LSB.        Examples:
>   Octet bit pattern                   Hexadecimal coding
>   00011011                            D8
>   11100100                            27
>   10000011 10100010 11001000 00001001 C1451390


My problem is understanding this.  The examples could help a if I it was
shown in the text which bit is bit 0 etc.  What I would like to know/see
is the
example(s) changed to help my understanding, something like this:

   Octet bit pattern (bits:01234567)   Hexadecimal coding
   00011011                            D8
   11100100                            27
   10000011 10100010 11001000 00001001 C1451390

The above bit order (from 0 (LSB) to 7 (MSB)) is what I suspect it
should be, that's why it is in the example.

Regards,

Christer Holmberg
Ericsson Finland



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


From daemon@optimus.ietf.org  Tue Apr  9 07:50: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 HAA02409
	for <megaco-archive@odin.ietf.org>; Tue, 9 Apr 2002 07:50:34 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA12488
	for megaco-archive@odin.ietf.org; Tue, 9 Apr 2002 07:50:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA10913;
	Tue, 9 Apr 2002 07:22:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA10886
	for <megaco@optimus.ietf.org>; Tue, 9 Apr 2002 07:22:55 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02025
	for <megaco@ietf.org>; Tue, 9 Apr 2002 07:22:52 -0400 (EDT)
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 g39BMq3G027501
	for <megaco@ietf.org>; Tue, 9 Apr 2002 13:22:52 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g39BMqUD007976
	for <megaco@ietf.org>; Tue, 9 Apr 2002 14:22:52 +0300 (EET DST)
Message-ID: <3CB2CF0D.D32374BE@lmf.ericsson.se>
Date: Tue, 09 Apr 2002 14:22:54 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (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] Bit order
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 clarification question:

Annex B.3 says:

>B.3     Hexadecimal octet coding
>    Hexadecimal octet coding is a means for representing a string of
>   octets as a string of hexadecimal digits, with two digits
>   representing each octet. This octet encoding should be used when
>   encoding octet strings in the text version of the protocol.
>   For each octet, the 8-bit sequence is encoded as two hexadecimal
>   digits. Bit 0 is the first transmitted; bit 7 is the last.
>   Bits 7-4 are encoded as the first hexadecimal digit, with Bit 7 as
>   MSB and Bit 4 as LSB. Bits 3-0 are encoded as the second hexadecimal

>   digit, with Bit 3 as MSB and Bit 0 as LSB.        Examples:
>   Octet bit pattern                   Hexadecimal coding
>   00011011                            D8
>   11100100                            27
>   10000011 10100010 11001000 00001001 C1451390


My problem is understanding this.  The examples could help a if I it was
shown in the text which bit is bit 0 etc.  What I would like to know/see
is the
example(s) changed to help my understanding, something like this:

   Octet bit pattern (bits:01234567)   Hexadecimal coding
   00011011                            D8
   11100100                            27
   10000011 10100010 11001000 00001001 C1451390

The above bit order (from 0 (LSB) to 7 (MSB)) is what I suspect it
should be, that's why it is in the example.

Regards,

Christer Holmberg
Ericsson Finland



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



From megaco-admin@ietf.org  Tue Apr  9 08:57: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 IAA03749
	for <megaco-archive@odin.ietf.org>; Tue, 9 Apr 2002 08:57:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15127;
	Tue, 9 Apr 2002 08:35:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA27170
	for <megaco@optimus.ietf.org>; Mon, 8 Apr 2002 21:02:15 -0400 (EDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11821;
	Mon, 8 Apr 2002 21:02:11 -0400 (EDT)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g3911hON029218;
	Mon, 8 Apr 2002 18:01:43 -0700 (PDT)
Received: from RKUMARW2K (dhcp-128-107-141-83.cisco.com [128.107.141.83]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id SAA28929; Mon, 8 Apr 2002 18:01:41 -0700 (PDT)
Reply-To: <rkumar@cisco.com>
From: "Rajesh Kumar" <rkumar@cisco.com>
To: "Stephen Casner" <casner@packetdesign.com>,
        "Tom-PT Taylor" <taylor@nortelnetworks.com>
Cc: <mmusic@ietf.org>, <megaco@ietf.org>
Date: Mon, 8 Apr 2002 18:01:42 -0700
Message-ID: <HKENKJNMHBIBLCDGOHAFGELICAAA.rkumar@cisco.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)
In-Reply-To: <20020403165246.Q48839-100000@ash.packetdesign.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Subject: [Megaco] RE: [MMUSIC] Silence Suppression 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: 7bit

> -----Original Message-----
> From: mmusic-admin@ietf.org [mailto:mmusic-admin@ietf.org]On Behalf Of
> Stephen Casner
> Sent: Wednesday, April 03, 2002 6:06 PM
> To: Tom-PT Taylor
> Cc: mmusic@ietf.org; megaco@ietf.org
> Subject: Re: [MMUSIC] Silence Suppression Attribute

<snip>

> It may have been a mistake to include the a=silenceSupp attribute for
> ATM without considering the problem more generally.  I suspect that
> RFC 3108 did not get much attention in MMUSIC because many of the
> participants don't care much about ATM.

Steve,
A little bit of history on why there is a silence suppression attribute for
ATM in RFC3108. Let us look at AAL2 first, and then at AAL1.

If you look at the AAL2 profiles in ITU I.366.2, it is possible to support
PCM or ADPCM without silence suppression. Supporting silence suppression is
not mandatory for all AAL2 connections along the lines of the "strong
requirement" you quoted for silence suppression in the RTP context.

Why would I.366.2 make it optional for AAL2, and not mandatory as you made
it for RTP? Here is a possible justification: The optional nature of silence
suppression might be taken advantage of to reduce DSP costs. PCM without
silence suppression does not need a DSP, ADPCM without silence suppression
can be implemented in a non-DSP hardwired processor.

Now, moving from AAL2 to AAL1: it goes without saying that silence
suppression is completely optional in the AAL1 context. It is rarely used
with PCMU/PCMA on AAL1, however, there is nothing to preclude its use
(except there exists no SID mechanism for AAL1, as there exists for AAL2).

Does the inclusion of this attribute in the ATM context seem more reasonable
in this light now?

Rajesh





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


From daemon@optimus.ietf.org  Tue Apr  9 08:57: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 IAA03770
	for <megaco-archive@odin.ietf.org>; Tue, 9 Apr 2002 08:57:33 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA16158
	for megaco-archive@odin.ietf.org; Tue, 9 Apr 2002 08:57:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15127;
	Tue, 9 Apr 2002 08:35:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA27170
	for <megaco@optimus.ietf.org>; Mon, 8 Apr 2002 21:02:15 -0400 (EDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11821;
	Mon, 8 Apr 2002 21:02:11 -0400 (EDT)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g3911hON029218;
	Mon, 8 Apr 2002 18:01:43 -0700 (PDT)
Received: from RKUMARW2K (dhcp-128-107-141-83.cisco.com [128.107.141.83]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id SAA28929; Mon, 8 Apr 2002 18:01:41 -0700 (PDT)
Reply-To: <rkumar@cisco.com>
From: "Rajesh Kumar" <rkumar@cisco.com>
To: "Stephen Casner" <casner@packetdesign.com>,
        "Tom-PT Taylor" <taylor@nortelnetworks.com>
Cc: <mmusic@ietf.org>, <megaco@ietf.org>
Date: Mon, 8 Apr 2002 18:01:42 -0700
Message-ID: <HKENKJNMHBIBLCDGOHAFGELICAAA.rkumar@cisco.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)
In-Reply-To: <20020403165246.Q48839-100000@ash.packetdesign.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Subject: [Megaco] RE: [MMUSIC] Silence Suppression 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: 7bit

> -----Original Message-----
> From: mmusic-admin@ietf.org [mailto:mmusic-admin@ietf.org]On Behalf Of
> Stephen Casner
> Sent: Wednesday, April 03, 2002 6:06 PM
> To: Tom-PT Taylor
> Cc: mmusic@ietf.org; megaco@ietf.org
> Subject: Re: [MMUSIC] Silence Suppression Attribute

<snip>

> It may have been a mistake to include the a=silenceSupp attribute for
> ATM without considering the problem more generally.  I suspect that
> RFC 3108 did not get much attention in MMUSIC because many of the
> participants don't care much about ATM.

Steve,
A little bit of history on why there is a silence suppression attribute for
ATM in RFC3108. Let us look at AAL2 first, and then at AAL1.

If you look at the AAL2 profiles in ITU I.366.2, it is possible to support
PCM or ADPCM without silence suppression. Supporting silence suppression is
not mandatory for all AAL2 connections along the lines of the "strong
requirement" you quoted for silence suppression in the RTP context.

Why would I.366.2 make it optional for AAL2, and not mandatory as you made
it for RTP? Here is a possible justification: The optional nature of silence
suppression might be taken advantage of to reduce DSP costs. PCM without
silence suppression does not need a DSP, ADPCM without silence suppression
can be implemented in a non-DSP hardwired processor.

Now, moving from AAL2 to AAL1: it goes without saying that silence
suppression is completely optional in the AAL1 context. It is rarely used
with PCMU/PCMA on AAL1, however, there is nothing to preclude its use
(except there exists no SID mechanism for AAL1, as there exists for AAL2).

Does the inclusion of this attribute in the ATM context seem more reasonable
in this light now?

Rajesh





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



From daemon@optimus.ietf.org  Tue Apr  9 08:57: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 IAA03768
	for <megaco-archive@odin.ietf.org>; Tue, 9 Apr 2002 08:57:33 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA16157
	for megaco-archive@odin.ietf.org; Tue, 9 Apr 2002 08:57:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15151;
	Tue, 9 Apr 2002 08:35:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA28034
	for <megaco@optimus.ietf.org>; Mon, 8 Apr 2002 21:12:32 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12170;
	Mon, 8 Apr 2002 21:12:29 -0400 (EDT)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g391BlCl014975;
	Mon, 8 Apr 2002 18:11:47 -0700 (PDT)
Received: from RKUMARW2K (dhcp-128-107-141-83.cisco.com [128.107.141.83]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id SAA04196; Mon, 8 Apr 2002 18:12:00 -0700 (PDT)
Reply-To: <rkumar@cisco.com>
From: "Rajesh Kumar" <rkumar@cisco.com>
To: "Mmusic@Ietf. Org" <mmusic@ietf.org>, "Megaco@Ietf. Org" <megaco@ietf.org>,
        "Stephen Casner" <casner@packetdesign.com>,
        "Tom-PT Taylor" <taylor@nortelnetworks.com>
Date: Mon, 8 Apr 2002 18:12:01 -0700
Message-ID: <HKENKJNMHBIBLCDGOHAFOELKCAAA.rkumar@cisco.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.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Subject: [Megaco] RFC 3108 passed without adequate scrutiny?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

> -----Original Message-----
> From: mmusic-admin@ietf.org [mailto:mmusic-admin@ietf.org]On Behalf Of
> Stephen Casner
> Sent: Wednesday, April 03, 2002 6:06 PM
> To: Tom-PT Taylor
> Cc: mmusic@ietf.org; megaco@ietf.org
> Subject: Re: [MMUSIC] Silence Suppression Attribute

<snip>

> It may have been a mistake to include the a=silenceSupp attribute for
> ATM without considering the problem more generally. I suspect that
> RFC 3108 did not get much attention in MMUSIC because many of the
> participants don't care much about ATM.

Another point on "rfc3108 passing without due scrutiny": There was a lively
discussion on the ATM SDP issues both on 'cnfcntrl' mailing list (which
preceded the present one), and on a separate mailing list "atmsdp" dedicated
to this subject. I think I made it a point to cross-copy cnfcntrl@ietf.org
on all messages. Please read on for a justification of the silence
suppression parameter in rfc3108, which should be obvious to all ATM folks:

Steve,
A little bit of history on why there is a silence suppression attribute for
ATM in RFC3108. Let us look at AAL2 first, and then at AAL1.

If you look at the AAL2 profiles in ITU I.366.2, it is possible to support
PCM or ADPCM without silence suppression. Supporting silence suppression is
not mandatory for all AAL2 connections along the lines of the "strong
requirement" you quoted for silence suppression in the RTP context.

Why would I.366.2 make it optional for AAL2, and not mandatory as you made
it for RTP? Here is a possible justification: The optional nature of silence
suppression might be taken advantage of to reduce DSP costs. PCM without
silence suppression does not need a DSP, ADPCM without silence suppression
can be implemented in a non-DSP hardwired processor.

Now, moving from AAL2 to AAL1: it goes without saying that silence
suppression is completely optional in the AAL1 context. It is rarely used
with PCMU/PCMA on AAL1, however, there is nothing to preclude its use
(except there exists no SID mechanism for AAL1, as there exists for AAL2).

Does the inclusion of this attribute in the ATM context seem more reasonable
in this light now?
Rajesh
------------
Rajesh Kumar
Cisco Systems



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



From megaco-admin@ietf.org  Tue Apr  9 09:54: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 IAA03750
	for <megaco-archive@odin.ietf.org>; Tue, 9 Apr 2002 08:57:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15151;
	Tue, 9 Apr 2002 08:35:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA28034
	for <megaco@optimus.ietf.org>; Mon, 8 Apr 2002 21:12:32 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12170;
	Mon, 8 Apr 2002 21:12:29 -0400 (EDT)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g391BlCl014975;
	Mon, 8 Apr 2002 18:11:47 -0700 (PDT)
Received: from RKUMARW2K (dhcp-128-107-141-83.cisco.com [128.107.141.83]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id SAA04196; Mon, 8 Apr 2002 18:12:00 -0700 (PDT)
Reply-To: <rkumar@cisco.com>
From: "Rajesh Kumar" <rkumar@cisco.com>
To: "Mmusic@Ietf. Org" <mmusic@ietf.org>, "Megaco@Ietf. Org" <megaco@ietf.org>,
        "Stephen Casner" <casner@packetdesign.com>,
        "Tom-PT Taylor" <taylor@nortelnetworks.com>
Date: Mon, 8 Apr 2002 18:12:01 -0700
Message-ID: <HKENKJNMHBIBLCDGOHAFOELKCAAA.rkumar@cisco.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.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Content-Transfer-Encoding: 7bit
Subject: [Megaco] RFC 3108 passed without adequate scrutiny?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

> -----Original Message-----
> From: mmusic-admin@ietf.org [mailto:mmusic-admin@ietf.org]On Behalf Of
> Stephen Casner
> Sent: Wednesday, April 03, 2002 6:06 PM
> To: Tom-PT Taylor
> Cc: mmusic@ietf.org; megaco@ietf.org
> Subject: Re: [MMUSIC] Silence Suppression Attribute

<snip>

> It may have been a mistake to include the a=silenceSupp attribute for
> ATM without considering the problem more generally. I suspect that
> RFC 3108 did not get much attention in MMUSIC because many of the
> participants don't care much about ATM.

Another point on "rfc3108 passing without due scrutiny": There was a lively
discussion on the ATM SDP issues both on 'cnfcntrl' mailing list (which
preceded the present one), and on a separate mailing list "atmsdp" dedicated
to this subject. I think I made it a point to cross-copy cnfcntrl@ietf.org
on all messages. Please read on for a justification of the silence
suppression parameter in rfc3108, which should be obvious to all ATM folks:

Steve,
A little bit of history on why there is a silence suppression attribute for
ATM in RFC3108. Let us look at AAL2 first, and then at AAL1.

If you look at the AAL2 profiles in ITU I.366.2, it is possible to support
PCM or ADPCM without silence suppression. Supporting silence suppression is
not mandatory for all AAL2 connections along the lines of the "strong
requirement" you quoted for silence suppression in the RTP context.

Why would I.366.2 make it optional for AAL2, and not mandatory as you made
it for RTP? Here is a possible justification: The optional nature of silence
suppression might be taken advantage of to reduce DSP costs. PCM without
silence suppression does not need a DSP, ADPCM without silence suppression
can be implemented in a non-DSP hardwired processor.

Now, moving from AAL2 to AAL1: it goes without saying that silence
suppression is completely optional in the AAL1 context. It is rarely used
with PCMU/PCMA on AAL1, however, there is nothing to preclude its use
(except there exists no SID mechanism for AAL1, as there exists for AAL2).

Does the inclusion of this attribute in the ATM context seem more reasonable
in this light now?
Rajesh
------------
Rajesh Kumar
Cisco Systems



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


From megaco-admin@ietf.org  Tue Apr  9 10:12: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 KAA06085
	for <megaco-archive@odin.ietf.org>; Tue, 9 Apr 2002 10:12:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20249;
	Tue, 9 Apr 2002 09:51:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20176
	for <megaco@optimus.ietf.org>; Tue, 9 Apr 2002 09:51:51 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05392;
	Tue, 9 Apr 2002 09:51:48 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g39DpEg14362;
	Tue, 9 Apr 2002 09:51:14 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LCZDT>; Tue, 9 Apr 2002 09:51:14 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2A2@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>,
        "'mmusic@ietf.org'"
	 <mmusic@ietf.org>
Date: Tue, 9 Apr 2002 09:51:10 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] FW: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.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

I have recycled this document at last.  Material relating to Nx64 kbit/s or
multilink operation has been stripped out, and material relating to H.320
and H.324 sessions has been modified to conform to the latest views of how
Megaco operates.  I forgot to put in the MIME registrations for audio/PCMU,
audio/PCMA, audio/G726xx, and application/octet-stream all over TDM
transport, but I'll do that on the next pass.

I sent a copy to Jim Renkel, who had urged that requirements for
CAS-signalled TDM be taken into account when I first presented this to
MMUSIC.  I have no idea what additional requirements he has in mind, but
I'll see.  In the meantime, does anyone else have comments?  We need this
for NAS operation.

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Tuesday, April 09, 2002 8:41 AM
Subject: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Conventions for the use of the Session Description

                          Protocol (SDP)for Digital Circuit Connections
	Author(s)	: T. Taylor
	Filename	: draft-taylor-mmusic-sdp-tdm-01.txt
	Pages		: 14
	Date		: 08-Apr-02
	
This document describes conventions for using the Session 
Description Protocol (SDP) for controlling digital circuits.  These 
conventions describe 
- circuit addressing conventions for use on the SDP 'c=' line 
- content of the 'm=' line(s) for digital circuits 
- attributes to convey the parameters contained within the Bearer 
Capability, Low Layer Compatibility, and High Layer Compatibility 
Information Elements of ITU-T Recommendation Q.931. 
These conventions have been defined for use in media gateway 
control, particularly in support of NAS operation, but may also be 
used by IP-based call signalling schemes (SIP, BICC) to control 
media exchange over digital circuits.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-taylor-mmusic-sdp-tdm-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


-----
To: 
Subject: 
Date: Tue, 9 Apr 2002 09:51:14 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)



begin 600 ATT64470
M0V]N=&5N="UT>7!E.B!M97-S86=E+V5X=&5R;F%L+6)O9'D[#0H)86-C97-S
M+71Y<&4](FUA:6PM<V5R=F5R(CL-"@ES97)V97(](FUA:6QS97)V0&EE=&8N
M;W)G(@T*#0I#;VYT96YT+51Y<&4Z('1E>'0O<&QA:6X-"D-O;G1E;G0M240Z
M"3PR,#`R,#0P.#$R,C8U,"Y)+41`:65T9BYO<F<^#0H-"D5.0T]$24Y'(&UI
M;64-"D9)3$4@+VEN=&5R;F5T+61R869T<R]D<F%F="UT87EL;W(M;6UU<VEC
1+7-D<"UT9&TM,#$N='AT#0H=
`
end

begin 600 draft-taylor-mmusic-sdp-tdm-01.url
M6TEN=&5R;F5T4VAO<G1C=71=#0I54DP]9G1P.B\O9G1P+FEE=&8N;W)G+VEN
M=&5R;F5T+61R869T<R]D<F%F="UT87EL;W(M;6UU<VEC+7-D<"UT9&TM,#$-
!"@==
`
end

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


From daemon@optimus.ietf.org  Tue Apr  9 10:12: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 KAA06096
	for <megaco-archive@odin.ietf.org>; Tue, 9 Apr 2002 10:12:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA22179
	for megaco-archive@odin.ietf.org; Tue, 9 Apr 2002 10:13:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20249;
	Tue, 9 Apr 2002 09:51:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20176
	for <megaco@optimus.ietf.org>; Tue, 9 Apr 2002 09:51:51 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05392;
	Tue, 9 Apr 2002 09:51:48 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g39DpEg14362;
	Tue, 9 Apr 2002 09:51:14 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LCZDT>; Tue, 9 Apr 2002 09:51:14 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2A2@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>,
        "'mmusic@ietf.org'"
	 <mmusic@ietf.org>
Date: Tue, 9 Apr 2002 09:51:10 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] FW: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.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

I have recycled this document at last.  Material relating to Nx64 kbit/s or
multilink operation has been stripped out, and material relating to H.320
and H.324 sessions has been modified to conform to the latest views of how
Megaco operates.  I forgot to put in the MIME registrations for audio/PCMU,
audio/PCMA, audio/G726xx, and application/octet-stream all over TDM
transport, but I'll do that on the next pass.

I sent a copy to Jim Renkel, who had urged that requirements for
CAS-signalled TDM be taken into account when I first presented this to
MMUSIC.  I have no idea what additional requirements he has in mind, but
I'll see.  In the meantime, does anyone else have comments?  We need this
for NAS operation.

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Tuesday, April 09, 2002 8:41 AM
Subject: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Conventions for the use of the Session Description

                          Protocol (SDP)for Digital Circuit Connections
	Author(s)	: T. Taylor
	Filename	: draft-taylor-mmusic-sdp-tdm-01.txt
	Pages		: 14
	Date		: 08-Apr-02
	
This document describes conventions for using the Session 
Description Protocol (SDP) for controlling digital circuits.  These 
conventions describe 
- circuit addressing conventions for use on the SDP 'c=' line 
- content of the 'm=' line(s) for digital circuits 
- attributes to convey the parameters contained within the Bearer 
Capability, Low Layer Compatibility, and High Layer Compatibility 
Information Elements of ITU-T Recommendation Q.931. 
These conventions have been defined for use in media gateway 
control, particularly in support of NAS operation, but may also be 
used by IP-based call signalling schemes (SIP, BICC) to control 
media exchange over digital circuits.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-taylor-mmusic-sdp-tdm-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


-----
To: 
Subject: 
Date: Tue, 9 Apr 2002 09:51:14 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)



begin 600 ATT64470
M0V]N=&5N="UT>7!E.B!M97-S86=E+V5X=&5R;F%L+6)O9'D[#0H)86-C97-S
M+71Y<&4](FUA:6PM<V5R=F5R(CL-"@ES97)V97(](FUA:6QS97)V0&EE=&8N
M;W)G(@T*#0I#;VYT96YT+51Y<&4Z('1E>'0O<&QA:6X-"D-O;G1E;G0M240Z
M"3PR,#`R,#0P.#$R,C8U,"Y)+41`:65T9BYO<F<^#0H-"D5.0T]$24Y'(&UI
M;64-"D9)3$4@+VEN=&5R;F5T+61R869T<R]D<F%F="UT87EL;W(M;6UU<VEC
1+7-D<"UT9&TM,#$N='AT#0H=
`
end

begin 600 draft-taylor-mmusic-sdp-tdm-01.url
M6TEN=&5R;F5T4VAO<G1C=71=#0I54DP]9G1P.B\O9G1P+FEE=&8N;W)G+VEN
M=&5R;F5T+61R869T<R]D<F%F="UT87EL;W(M;6UU<VEC+7-D<"UT9&TM,#$-
!"@==
`
end

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



From megaco-admin@ietf.org  Tue Apr  9 11:47: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 LAA09798
	for <megaco-archive@odin.ietf.org>; Tue, 9 Apr 2002 11:47:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA26711;
	Tue, 9 Apr 2002 11:23:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA26682
	for <megaco@optimus.ietf.org>; Tue, 9 Apr 2002 11:23:41 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08840
	for <megaco@ietf.org>; Tue, 9 Apr 2002 11:23:38 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g39FN8g22069
	for <megaco@ietf.org>; Tue, 9 Apr 2002 11:23:08 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LC71Y>; Tue, 9 Apr 2002 11:23:09 -0400
Received: from zcars0mt.ca.nortel.com ([47.129.242.181]) by zcard00n.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id HLDCAH63; Tue, 9 Apr 2002 10:09:59 -0400
Received: from ecarsbbb.nortelnetworks.com (ecarsbbb.nortelnetworks.com [47.248.0.35])
	by zcars0mt.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with SMTP id g39E9oq09427;
	Tue, 9 Apr 2002 10:09:50 -0400 (EDT)
Received: from optimus.ietf.org (ietf.org [132.151.1.19]) by ecarsbbb.nortelnetworks.com with SMTP (MailShield v1.5); Tue, 09 Apr 2002 10:09:53 -0500
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20225;
	Tue, 9 Apr 2002 09:51:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20176
	for <megaco@optimus.ietf.org>; Tue, 9 Apr 2002 09:51:51 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05392;
	Tue, 9 Apr 2002 09:51:48 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g39DpEg14362;
	Tue, 9 Apr 2002 09:51:14 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LCZDT>; Tue, 9 Apr 2002 09:51:14 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2A3@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 9 Apr 2002 11:23:07 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Resend: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.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

Apologies to those who received my previous message successfully.  I have
been getting a series of rejection messages from companies whose mail
servers won't accept messages with URL attachments like the one the IETF
sticks on to its announcements.
-------------
I have recycled this document at last.  Material relating to Nx64 kbit/s or
multilink operation has been stripped out, and material relating to H.320
and H.324 sessions has been modified to conform to the latest views of how
Megaco operates.  I forgot to put in the MIME registrations for audio/PCMU,
audio/PCMA, audio/G726xx, and application/octet-stream all over TDM
transport, but I'll do that on the next pass.

I sent a copy to Jim Renkel, who had urged that requirements for
CAS-signalled TDM be taken into account when I first presented this to
MMUSIC.  I have no idea what additional requirements he has in mind, but
I'll see.  In the meantime, does anyone else have comments?  We need this
for NAS operation.

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Tuesday, April 09, 2002 8:41 AM
Subject: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Conventions for the use of the Session Description

                          Protocol (SDP)for Digital Circuit Connections
	Author(s)	: T. Taylor
	Filename	: draft-taylor-mmusic-sdp-tdm-01.txt
	Pages		: 14
	Date		: 08-Apr-02
	
This document describes conventions for using the Session 
Description Protocol (SDP) for controlling digital circuits.  These 
conventions describe 
- circuit addressing conventions for use on the SDP 'c=' line 
- content of the 'm=' line(s) for digital circuits 
- attributes to convey the parameters contained within the Bearer 
Capability, Low Layer Compatibility, and High Layer Compatibility 
Information Elements of ITU-T Recommendation Q.931. 
These conventions have been defined for use in media gateway 
control, particularly in support of NAS operation, but may also be 
used by IP-based call signalling schemes (SIP, BICC) to control 
media exchange over digital circuits.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt


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


From daemon@optimus.ietf.org  Tue Apr  9 11:47: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 LAA09810
	for <megaco-archive@odin.ietf.org>; Tue, 9 Apr 2002 11:47:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA28694
	for megaco-archive@odin.ietf.org; Tue, 9 Apr 2002 11:47:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA26711;
	Tue, 9 Apr 2002 11:23:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA26682
	for <megaco@optimus.ietf.org>; Tue, 9 Apr 2002 11:23:41 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08840
	for <megaco@ietf.org>; Tue, 9 Apr 2002 11:23:38 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g39FN8g22069
	for <megaco@ietf.org>; Tue, 9 Apr 2002 11:23:08 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LC71Y>; Tue, 9 Apr 2002 11:23:09 -0400
Received: from zcars0mt.ca.nortel.com ([47.129.242.181]) by zcard00n.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id HLDCAH63; Tue, 9 Apr 2002 10:09:59 -0400
Received: from ecarsbbb.nortelnetworks.com (ecarsbbb.nortelnetworks.com [47.248.0.35])
	by zcars0mt.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with SMTP id g39E9oq09427;
	Tue, 9 Apr 2002 10:09:50 -0400 (EDT)
Received: from optimus.ietf.org (ietf.org [132.151.1.19]) by ecarsbbb.nortelnetworks.com with SMTP (MailShield v1.5); Tue, 09 Apr 2002 10:09:53 -0500
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20225;
	Tue, 9 Apr 2002 09:51:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20176
	for <megaco@optimus.ietf.org>; Tue, 9 Apr 2002 09:51:51 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05392;
	Tue, 9 Apr 2002 09:51:48 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g39DpEg14362;
	Tue, 9 Apr 2002 09:51:14 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LCZDT>; Tue, 9 Apr 2002 09:51:14 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2A3@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 9 Apr 2002 11:23:07 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Resend: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.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

Apologies to those who received my previous message successfully.  I have
been getting a series of rejection messages from companies whose mail
servers won't accept messages with URL attachments like the one the IETF
sticks on to its announcements.
-------------
I have recycled this document at last.  Material relating to Nx64 kbit/s or
multilink operation has been stripped out, and material relating to H.320
and H.324 sessions has been modified to conform to the latest views of how
Megaco operates.  I forgot to put in the MIME registrations for audio/PCMU,
audio/PCMA, audio/G726xx, and application/octet-stream all over TDM
transport, but I'll do that on the next pass.

I sent a copy to Jim Renkel, who had urged that requirements for
CAS-signalled TDM be taken into account when I first presented this to
MMUSIC.  I have no idea what additional requirements he has in mind, but
I'll see.  In the meantime, does anyone else have comments?  We need this
for NAS operation.

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Tuesday, April 09, 2002 8:41 AM
Subject: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Conventions for the use of the Session Description

                          Protocol (SDP)for Digital Circuit Connections
	Author(s)	: T. Taylor
	Filename	: draft-taylor-mmusic-sdp-tdm-01.txt
	Pages		: 14
	Date		: 08-Apr-02
	
This document describes conventions for using the Session 
Description Protocol (SDP) for controlling digital circuits.  These 
conventions describe 
- circuit addressing conventions for use on the SDP 'c=' line 
- content of the 'm=' line(s) for digital circuits 
- attributes to convey the parameters contained within the Bearer 
Capability, Low Layer Compatibility, and High Layer Compatibility 
Information Elements of ITU-T Recommendation Q.931. 
These conventions have been defined for use in media gateway 
control, particularly in support of NAS operation, but may also be 
used by IP-based call signalling schemes (SIP, BICC) to control 
media exchange over digital circuits.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt


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



From megaco-admin@ietf.org  Wed Apr 10 06:40: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 GAA14957
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 06:40:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA11103;
	Wed, 10 Apr 2002 06:08:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA11074
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 06:08:18 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14661
	for <megaco@ietf.org>; Wed, 10 Apr 2002 06:08:12 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002268718@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Wed, 10 Apr 2002 15:56:22 +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 g3AA7RU20218;
	Wed, 10 Apr 2002 15:37:27 +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, 10 Apr 2002 15:35:33 +0530
Message-Id: <001b01c1e077$415f9e00$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] Modify a Termination with Modem
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 a Modem be applied to a Termination which is in a NULL Context.
Syntax supports that.

That is, MGC can send the following packet to MG:

Transaction = 1 {
   Context = - {
      Modify = TermA { Modem = V18 }
}
}

Or Modem can be applied to a termination which is in a context.

If Modem is applied to a termination which is in a context, then Modem can
be
removed from a termination by subtracting that termination from a context.

But if it possible to apply a Modem to a Termination which is in  NULL
Context, how
can MGC remove the Modem from that termination. Because Modifying a
Termination with a
NULL Modem is not supported according to Syntax.

Thanks & Regards,
Sudhir


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


From daemon@optimus.ietf.org  Wed Apr 10 06:40: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 GAA14968
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 06:40:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA12490
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 06:40:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA11103;
	Wed, 10 Apr 2002 06:08:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA11074
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 06:08:18 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14661
	for <megaco@ietf.org>; Wed, 10 Apr 2002 06:08:12 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002268718@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Wed, 10 Apr 2002 15:56:22 +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 g3AA7RU20218;
	Wed, 10 Apr 2002 15:37:27 +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, 10 Apr 2002 15:35:33 +0530
Message-Id: <001b01c1e077$415f9e00$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] Modify a Termination with Modem
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 a Modem be applied to a Termination which is in a NULL Context.
Syntax supports that.

That is, MGC can send the following packet to MG:

Transaction = 1 {
   Context = - {
      Modify = TermA { Modem = V18 }
}
}

Or Modem can be applied to a termination which is in a context.

If Modem is applied to a termination which is in a context, then Modem can
be
removed from a termination by subtracting that termination from a context.

But if it possible to apply a Modem to a Termination which is in  NULL
Context, how
can MGC remove the Modem from that termination. Because Modifying a
Termination with a
NULL Modem is not supported according to Syntax.

Thanks & Regards,
Sudhir


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



From megaco-admin@ietf.org  Wed Apr 10 07:36: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 HAA15478
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 07:36:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14062;
	Wed, 10 Apr 2002 07:20:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14036
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 07:20:13 -0400 (EDT)
Received: from mxout1.netvision.net.il (mxout1.netvision.net.il [194.90.9.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15330
	for <megaco@ietf.org>; Wed, 10 Apr 2002 07:20:08 -0400 (EDT)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout1.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GUC00IE2NGNBG@mxout1.netvision.net.il> for megaco@ietf.org;
 Wed, 10 Apr 2002 14:19:35 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <2SJYP4TC>; Wed, 10 Apr 2002 14:18:23 +0300
Content-return: allowed
Date: Wed, 10 Apr 2002 14:18:23 +0300
From: Dan Elbert <delbert@radvision.com>
Subject: RE: [Megaco] Disabling all Events
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B018BBF88@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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

You are supposed to send empty event list

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events  {}           ; just events token
        }
    }
}

this will disable all event detection

Dan Elbert
RADVISION


-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 2:14 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Disabling all Events


Hi,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

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 Apr 10 07: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 HAA15487
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 07:36:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA14958
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 07:36:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14062;
	Wed, 10 Apr 2002 07:20:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14036
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 07:20:13 -0400 (EDT)
Received: from mxout1.netvision.net.il (mxout1.netvision.net.il [194.90.9.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15330
	for <megaco@ietf.org>; Wed, 10 Apr 2002 07:20:08 -0400 (EDT)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout1.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GUC00IE2NGNBG@mxout1.netvision.net.il> for megaco@ietf.org;
 Wed, 10 Apr 2002 14:19:35 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <2SJYP4TC>; Wed, 10 Apr 2002 14:18:23 +0300
Content-return: allowed
Date: Wed, 10 Apr 2002 14:18:23 +0300
From: Dan Elbert <delbert@radvision.com>
Subject: RE: [Megaco] Disabling all Events
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B018BBF88@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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

You are supposed to send empty event list

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events  {}           ; just events token
        }
    }
}

this will disable all event detection

Dan Elbert
RADVISION


-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 2:14 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Disabling all Events


Hi,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

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 Apr 10 07:36: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 HAA15510
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 07:36:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA13944;
	Wed, 10 Apr 2002 07:17:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA13914
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 07:17:04 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15308
	for <megaco@ietf.org>; Wed, 10 Apr 2002 07:16:59 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002269178@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Wed, 10 Apr 2002 17:05:00 +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 g3ABG4U26446;
	Wed, 10 Apr 2002 16:46:04 +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, 10 Apr 2002 16:44:10 +0530
Message-Id: <002301c1e080$d79fe2e0$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] Disabling all Events
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

Thanks,
Sudhir


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


From daemon@optimus.ietf.org  Wed Apr 10 07:36: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 HAA15523
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 07:36:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA15007
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 07:36:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA13944;
	Wed, 10 Apr 2002 07:17:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA13914
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 07:17:04 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15308
	for <megaco@ietf.org>; Wed, 10 Apr 2002 07:16:59 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002269178@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Wed, 10 Apr 2002 17:05:00 +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 g3ABG4U26446;
	Wed, 10 Apr 2002 16:46:04 +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, 10 Apr 2002 16:44:10 +0530
Message-Id: <002301c1e080$d79fe2e0$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] Disabling all Events
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

Thanks,
Sudhir


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



From megaco-admin@ietf.org  Wed Apr 10 08:06: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 IAA15931
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:06:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA15279;
	Wed, 10 Apr 2002 07:46:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA15250
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 07:46:02 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15633
	for <megaco@ietf.org>; Wed, 10 Apr 2002 07:45:57 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002269414@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Wed, 10 Apr 2002 17:34:19 +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 g3ABjNU29486;
	Wed, 10 Apr 2002 17:15:23 +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, 10 Apr 2002 17:13:30 +0530
Message-Id: <002401c1e084$f028dfc0$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] Deleting DigitMap from a Termination
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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, 

Is MGC can delete the DigitMap that is already defined using the 
following packet:

Transaction = 1 {
   Context = - {
      Modify = TermA {
         DigitMap = Dmap1 { }  ; empty value for a name
      }
   }
}

Thanks,
Sudhir


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


From daemon@optimus.ietf.org  Wed Apr 10 08:06: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 IAA15945
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:06:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA16688
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 08:06:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA15279;
	Wed, 10 Apr 2002 07:46:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA15250
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 07:46:02 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15633
	for <megaco@ietf.org>; Wed, 10 Apr 2002 07:45:57 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002269414@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Wed, 10 Apr 2002 17:34:19 +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 g3ABjNU29486;
	Wed, 10 Apr 2002 17:15:23 +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, 10 Apr 2002 17:13:30 +0530
Message-Id: <002401c1e084$f028dfc0$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] Deleting DigitMap from a Termination
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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, 

Is MGC can delete the DigitMap that is already defined using the 
following packet:

Transaction = 1 {
   Context = - {
      Modify = TermA {
         DigitMap = Dmap1 { }  ; empty value for a name
      }
   }
}

Thanks,
Sudhir


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



From megaco-admin@ietf.org  Wed Apr 10 08:21: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 IAA16437
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:21:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA16563;
	Wed, 10 Apr 2002 08:04:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA16536
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:03:56 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15914
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:03:52 -0400 (EDT)
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 g3AC3MI08202
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:03:22 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LD36J>; Wed, 10 Apr 2002 08:03:24 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2B3@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] Modify a Termination with Modem
Date: Wed, 10 Apr 2002 08:03:25 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

On this particular item, I would point out that the Modem descriptor is
being deprecated in v2.  You should use the modem attribute in Annex C or
draft-taylor-mmusic-sdp-tdm-xx (once it is approved) instead.  I note that I
should add codepoints for all the modems currently supported by Megaco to
that latter document.

Aside from that, it seems to me a good general principle that the only
descriptors you can modify in the NULL context are those for Signals and
Events, and I even wonder about Signals.  Other people may want to comment.

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 6:06 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Modify a Termination with Modem


Hi,

Can a Modem be applied to a Termination which is in a NULL Context.
Syntax supports that.

That is, MGC can send the following packet to MG:

Transaction = 1 {
   Context = - {
      Modify = TermA { Modem = V18 }
}
}

Or Modem can be applied to a termination which is in a context.

If Modem is applied to a termination which is in a context, then Modem can
be
removed from a termination by subtracting that termination from a context.

But if it possible to apply a Modem to a Termination which is in  NULL
Context, how
can MGC remove the Modem from that termination. Because Modifying a
Termination with a
NULL Modem is not supported according to Syntax.

Thanks & Regards,
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 Apr 10 08:21: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 IAA16451
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:21:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA17574
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 08:21:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA16563;
	Wed, 10 Apr 2002 08:04:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA16536
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:03:56 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15914
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:03:52 -0400 (EDT)
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 g3AC3MI08202
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:03:22 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LD36J>; Wed, 10 Apr 2002 08:03:24 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2B3@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] Modify a Termination with Modem
Date: Wed, 10 Apr 2002 08:03:25 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

On this particular item, I would point out that the Modem descriptor is
being deprecated in v2.  You should use the modem attribute in Annex C or
draft-taylor-mmusic-sdp-tdm-xx (once it is approved) instead.  I note that I
should add codepoints for all the modems currently supported by Megaco to
that latter document.

Aside from that, it seems to me a good general principle that the only
descriptors you can modify in the NULL context are those for Signals and
Events, and I even wonder about Signals.  Other people may want to comment.

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 6:06 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Modify a Termination with Modem


Hi,

Can a Modem be applied to a Termination which is in a NULL Context.
Syntax supports that.

That is, MGC can send the following packet to MG:

Transaction = 1 {
   Context = - {
      Modify = TermA { Modem = V18 }
}
}

Or Modem can be applied to a termination which is in a context.

If Modem is applied to a termination which is in a context, then Modem can
be
removed from a termination by subtracting that termination from a context.

But if it possible to apply a Modem to a Termination which is in  NULL
Context, how
can MGC remove the Modem from that termination. Because Modifying a
Termination with a
NULL Modem is not supported according to Syntax.

Thanks & Regards,
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 Apr 10 08: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 IAA16699
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:31:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17131;
	Wed, 10 Apr 2002 08:13:26 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17111
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:13:24 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16176;
	Wed, 10 Apr 2002 08:13:19 -0400 (EDT)
Message-Id: <200204101213.IAA16176@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: megaco@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 10 Apr 2002 08:13:19 -0400
Subject: [Megaco] I-D ACTION:draft-ietf-megaco-naspkg-04.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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Media Gateway Control Working Group of the IETF.

	Title		: Megaco/H.248 NAS Package
	Author(s)	: J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam
	Filename	: draft-ietf-megaco-naspkg-04.txt
	Pages		: 18
	Date		: 09-Apr-02
	
This document is intended to satisfy the requirements in section 
11.2.5 of the Megaco/H.248 requirements document.  It defines five 
packages: 
- the base NAS package contains properties and events supported by 
all NAS terminations; 
- the NAS Incoming package contains properties and events  
supported by NAS terminations involved in calls initiated by the 
circuit network; 
- the NAS Outgoing package contains properties supported by NAS 
terminations involved in calls outgoing to the circuit network; 
- the NAS Control package contains an event supported by a NAS 
Control termination, which allows the MG to indicate a request to 
initiate a data connection to a terminal served by the switched 
circuit network; 
- the NAS ROOT package contains properties supported by an MG which 
is also capable of supporting at least the NAS and NAS Incoming 
packages.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-megaco-naspkg-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020409132359.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-megaco-naspkg-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020409132359.I-D@ietf.org>

--OtherAccess--

--NextPart--



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


From daemon@optimus.ietf.org  Wed Apr 10 08:31: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 IAA16708
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:31:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA18200
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 08:31:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17131;
	Wed, 10 Apr 2002 08:13:26 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17111
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:13:24 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16176;
	Wed, 10 Apr 2002 08:13:19 -0400 (EDT)
Message-Id: <200204101213.IAA16176@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: megaco@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 10 Apr 2002 08:13:19 -0400
Subject: [Megaco] I-D ACTION:draft-ietf-megaco-naspkg-04.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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Media Gateway Control Working Group of the IETF.

	Title		: Megaco/H.248 NAS Package
	Author(s)	: J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam
	Filename	: draft-ietf-megaco-naspkg-04.txt
	Pages		: 18
	Date		: 09-Apr-02
	
This document is intended to satisfy the requirements in section 
11.2.5 of the Megaco/H.248 requirements document.  It defines five 
packages: 
- the base NAS package contains properties and events supported by 
all NAS terminations; 
- the NAS Incoming package contains properties and events  
supported by NAS terminations involved in calls initiated by the 
circuit network; 
- the NAS Outgoing package contains properties supported by NAS 
terminations involved in calls outgoing to the circuit network; 
- the NAS Control package contains an event supported by a NAS 
Control termination, which allows the MG to indicate a request to 
initiate a data connection to a terminal served by the switched 
circuit network; 
- the NAS ROOT package contains properties supported by an MG which 
is also capable of supporting at least the NAS and NAS Incoming 
packages.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-megaco-naspkg-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020409132359.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-megaco-naspkg-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020409132359.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From megaco-admin@ietf.org  Wed Apr 10 08:37: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 IAA17088
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:37:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17486;
	Wed, 10 Apr 2002 08:18:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17457
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:18:37 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16382
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:18:32 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUCQ3100.9GG for
          <megaco@ietf.org>; Wed, 10 Apr 2002 20:16:13 +0800 
Message-ID: <00a901c1e089$fe410560$26280b0a@huawei.com.cn>
From: "ding" <dingwh@huawei.com>
To: <megaco@ietf.org>
Date: Wed, 10 Apr 2002 20:19:42 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00A6_01C1E0CD.0C537C80"
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
Subject: [Megaco] use of EventBufferDescriptor
Sender: megaco-admin@ietf.org
Errors-To: 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_00A6_01C1E0CD.0C537C80
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

aGksDQoNCnN1cHBvc2UgTUcgcmVjZWl2ZXMgYSBFdmVudEJ1ZmZlckRlc2NyaXB0b3IgYW5kIGEg
RXZlbnREZXNjcmlwdG9yIGF0IHRoZSBzYW1lIHRpbWUsIGFuZCBNRydzIGV2ZW50IGJ1ZmZlciBx
dWV1ZShGSUZPIHF1ZXVlKSBpcyBlbXB0eS4gbm93IGlmIHNvbWUgdXNlciBldmVudCBpcyByZWNv
Z25pemVkIGluIHRoZSBFdmVudEJ1ZmZlckRlc2NyaXB0b3IoYW5kIG5vdCByZWNvZ25pemVkIGlu
IHRoZSBFdmVudERlc2NyaXB0b3IpLCBzaG91bGQgTUcgZGlzY2FyZCB0aGUgdXNlciBldmVudCBv
ciBzZW5kIGl0IHRvIHRoZSBGSUZPIHF1ZXVlPw0KDQpJIHRoaW5rIGl0IHNob3VsZCBiZSBkaXNj
YXJkZWQsIGFtIGkgcmlnaHQ/DQoNCnRoYW5rcy4NCg==

------=_NextPart_000_00A6_01C1E0CD.0C537C80
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5oaSw8L0ZPTlQ+PC9ESVY+
DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5zdXBwb3NlJm5ic3A7TUcgcmVjZWl2ZXMgYSBFdmVu
dEJ1ZmZlckRlc2NyaXB0b3IgYW5kIGEgRXZlbnREZXNjcmlwdG9yIGF0IA0KdGhlIHNhbWUgdGlt
ZSwgYW5kIE1HJ3MgZXZlbnQgYnVmZmVyIHF1ZXVlKEZJRk8gcXVldWUpIGlzIGVtcHR5LiZuYnNw
O25vdyBpZiANCnNvbWUgdXNlciBldmVudCBpcyByZWNvZ25pemVkIGluIHRoZSBFdmVudEJ1ZmZl
ckRlc2NyaXB0b3IoYW5kIG5vdCByZWNvZ25pemVkIGluIA0KdGhlIEV2ZW50RGVzY3JpcHRvciks
IHNob3VsZCBNRyBkaXNjYXJkIHRoZSB1c2VyIGV2ZW50IG9yIHNlbmQgaXQgdG8gdGhlIEZJRk8g
DQpxdWV1ZT88L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5JIHRo
aW5rIGl0IHNob3VsZCBiZSBkaXNjYXJkZWQsIGFtIGkgcmlnaHQ/PC9GT05UPjwvRElWPg0KPERJ
Vj4mbmJzcDs8L0RJVj4NCjxESVY+dGhhbmtzLjwvRElWPjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_000_00A6_01C1E0CD.0C537C80--


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


From daemon@optimus.ietf.org  Wed Apr 10 08:37: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 IAA17100
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:37:06 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA18778
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 08:37:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17486;
	Wed, 10 Apr 2002 08:18:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17457
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:18:37 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16382
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:18:32 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUCQ3100.9GG for
          <megaco@ietf.org>; Wed, 10 Apr 2002 20:16:13 +0800 
Message-ID: <00a901c1e089$fe410560$26280b0a@huawei.com.cn>
From: "ding" <dingwh@huawei.com>
To: <megaco@ietf.org>
Date: Wed, 10 Apr 2002 20:19:42 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00A6_01C1E0CD.0C537C80"
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
Subject: [Megaco] use of EventBufferDescriptor
Sender: megaco-admin@ietf.org
Errors-To: 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_00A6_01C1E0CD.0C537C80
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

aGksDQoNCnN1cHBvc2UgTUcgcmVjZWl2ZXMgYSBFdmVudEJ1ZmZlckRlc2NyaXB0b3IgYW5kIGEg
RXZlbnREZXNjcmlwdG9yIGF0IHRoZSBzYW1lIHRpbWUsIGFuZCBNRydzIGV2ZW50IGJ1ZmZlciBx
dWV1ZShGSUZPIHF1ZXVlKSBpcyBlbXB0eS4gbm93IGlmIHNvbWUgdXNlciBldmVudCBpcyByZWNv
Z25pemVkIGluIHRoZSBFdmVudEJ1ZmZlckRlc2NyaXB0b3IoYW5kIG5vdCByZWNvZ25pemVkIGlu
IHRoZSBFdmVudERlc2NyaXB0b3IpLCBzaG91bGQgTUcgZGlzY2FyZCB0aGUgdXNlciBldmVudCBv
ciBzZW5kIGl0IHRvIHRoZSBGSUZPIHF1ZXVlPw0KDQpJIHRoaW5rIGl0IHNob3VsZCBiZSBkaXNj
YXJkZWQsIGFtIGkgcmlnaHQ/DQoNCnRoYW5rcy4NCg==

------=_NextPart_000_00A6_01C1E0CD.0C537C80
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5oaSw8L0ZPTlQ+PC9ESVY+
DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5zdXBwb3NlJm5ic3A7TUcgcmVjZWl2ZXMgYSBFdmVu
dEJ1ZmZlckRlc2NyaXB0b3IgYW5kIGEgRXZlbnREZXNjcmlwdG9yIGF0IA0KdGhlIHNhbWUgdGlt
ZSwgYW5kIE1HJ3MgZXZlbnQgYnVmZmVyIHF1ZXVlKEZJRk8gcXVldWUpIGlzIGVtcHR5LiZuYnNw
O25vdyBpZiANCnNvbWUgdXNlciBldmVudCBpcyByZWNvZ25pemVkIGluIHRoZSBFdmVudEJ1ZmZl
ckRlc2NyaXB0b3IoYW5kIG5vdCByZWNvZ25pemVkIGluIA0KdGhlIEV2ZW50RGVzY3JpcHRvciks
IHNob3VsZCBNRyBkaXNjYXJkIHRoZSB1c2VyIGV2ZW50IG9yIHNlbmQgaXQgdG8gdGhlIEZJRk8g
DQpxdWV1ZT88L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5JIHRo
aW5rIGl0IHNob3VsZCBiZSBkaXNjYXJkZWQsIGFtIGkgcmlnaHQ/PC9GT05UPjwvRElWPg0KPERJ
Vj4mbmJzcDs8L0RJVj4NCjxESVY+dGhhbmtzLjwvRElWPjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_000_00A6_01C1E0CD.0C537C80--


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



From megaco-admin@ietf.org  Wed Apr 10 08:58: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 IAA17645
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:58:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18906;
	Wed, 10 Apr 2002 08:38:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18872
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:38:46 -0400 (EDT)
Received: from blaze.hcltech.com (pop.hclt-guindy.co.in [203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17296
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:38:40 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id SAA11884;
	Wed, 10 Apr 2002 18:07:07 +0530
Message-ID: <3CB4116B.B375D20@netlab.hcltech.com>
Date: Wed, 10 Apr 2002 15:48:19 +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: ding <dingwh@huawei.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] use of EventBufferDescriptor
References: <00a901c1e089$fe410560$26280b0a@huawei.com.cn>
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 Ding,
	My answer is inline.

> ding wrote:
> 
> hi,
> 
> suppose MG receives a EventBufferDescriptor and a EventDescriptor at the same
> time, and MG's event buffer queue(FIFO queue) is empty. now if some user event

We search for the event against EventBufferDescriptor only if EventBufferControl
is LockStep mode and EventsDescriptor is not active.

> is recognized in the EventBufferDescriptor(and not recognized in the
> EventDescriptor), should MG discard the user event or send it to the FIFO
> queue?

So, if EventBufferControl is LockStep mode &&
                 EventsDescriptor is not active &&
                      event is found in EventBufferDescriptor
    then
       send it to the FIFO queue.

> 
> I think it should be discarded, am i right?
> 
> thanks.

Regds.,
Giri

-- 

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 Extn. 233
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  Wed Apr 10 08:58: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 IAA17654
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:58:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA19835
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 08:58:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18906;
	Wed, 10 Apr 2002 08:38:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18872
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:38:46 -0400 (EDT)
Received: from blaze.hcltech.com (pop.hclt-guindy.co.in [203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17296
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:38:40 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id SAA11884;
	Wed, 10 Apr 2002 18:07:07 +0530
Message-ID: <3CB4116B.B375D20@netlab.hcltech.com>
Date: Wed, 10 Apr 2002 15:48:19 +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: ding <dingwh@huawei.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] use of EventBufferDescriptor
References: <00a901c1e089$fe410560$26280b0a@huawei.com.cn>
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 Ding,
	My answer is inline.

> ding wrote:
> 
> hi,
> 
> suppose MG receives a EventBufferDescriptor and a EventDescriptor at the same
> time, and MG's event buffer queue(FIFO queue) is empty. now if some user event

We search for the event against EventBufferDescriptor only if EventBufferControl
is LockStep mode and EventsDescriptor is not active.

> is recognized in the EventBufferDescriptor(and not recognized in the
> EventDescriptor), should MG discard the user event or send it to the FIFO
> queue?

So, if EventBufferControl is LockStep mode &&
                 EventsDescriptor is not active &&
                      event is found in EventBufferDescriptor
    then
       send it to the FIFO queue.

> 
> I think it should be discarded, am i right?
> 
> thanks.

Regds.,
Giri

-- 

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 Extn. 233
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  Wed Apr 10 08:58: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 IAA17673
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:58:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18996;
	Wed, 10 Apr 2002 08:40:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18965
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:40:26 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17349
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:40:18 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002269813@fsnt.future.futsoft.com>;
 Wed, 10 Apr 2002 18:26:52 +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 g3ACbvU00405;
	Wed, 10 Apr 2002 18:07:57 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: "'Dan Elbert'" <delbert@radvision.com>, <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Subject: RE: [Megaco] Disabling all Events
Date: Wed, 10 Apr 2002 18:06:03 +0530
Message-Id: <002701c1e08c$47ead4a0$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
In-Reply-To: <EE5AF23B5764D511A6B900508BB82A0B018BBF88@nt-mail.radvision.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 Dan,
According to ABNF Syntax,

eventsDescriptor     = EventsToken [ EQUAL RequestID LBRKT
                       requestedEvent *( COMMA requestedEvent ) RBRKT ]

So "Events {}" is not according to syntax.

But for signals, "Signals {}" is a valid.

Reply back.
Thanks,
Sudhir

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Wednesday, April 10, 2002 4:48 PM
To: 'sudhirk@future.futsoft.com'; 'megaco@ietf.org'
Subject: RE: [Megaco] Disabling all Events


You are supposed to send empty event list

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events  {}           ; just events token
        }
    }
}

this will disable all event detection

Dan Elbert
RADVISION


-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 2:14 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Disabling all Events


Hi,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

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 Apr 10 08:58: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 IAA17684
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 08:58:18 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA19856
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 08:58:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18996;
	Wed, 10 Apr 2002 08:40:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18965
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:40:26 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17349
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:40:18 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002269813@fsnt.future.futsoft.com>;
 Wed, 10 Apr 2002 18:26:52 +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 g3ACbvU00405;
	Wed, 10 Apr 2002 18:07:57 +0530
Reply-To: <sudhirk@future.futsoft.com>
From: "Sudhir Kumar Appana" <sudhirk@future.futsoft.com>
To: "'Dan Elbert'" <delbert@radvision.com>, <megaco@ietf.org>
Cc: "Sudhir \(E-mail\)" <sudhirk@future.futsoft.com>
Subject: RE: [Megaco] Disabling all Events
Date: Wed, 10 Apr 2002 18:06:03 +0530
Message-Id: <002701c1e08c$47ead4a0$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
In-Reply-To: <EE5AF23B5764D511A6B900508BB82A0B018BBF88@nt-mail.radvision.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 Dan,
According to ABNF Syntax,

eventsDescriptor     = EventsToken [ EQUAL RequestID LBRKT
                       requestedEvent *( COMMA requestedEvent ) RBRKT ]

So "Events {}" is not according to syntax.

But for signals, "Signals {}" is a valid.

Reply back.
Thanks,
Sudhir

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Wednesday, April 10, 2002 4:48 PM
To: 'sudhirk@future.futsoft.com'; 'megaco@ietf.org'
Subject: RE: [Megaco] Disabling all Events


You are supposed to send empty event list

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events  {}           ; just events token
        }
    }
}

this will disable all event detection

Dan Elbert
RADVISION


-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 2:14 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Disabling all Events


Hi,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

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 Apr 10 09:19: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 JAA18350
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 09:19:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA19604;
	Wed, 10 Apr 2002 08:54:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA19575
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:54:24 -0400 (EDT)
Received: from mxout2.netvision.net.il (mxout2.netvision.net.il [194.90.9.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17561
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:54:19 -0400 (EDT)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout2.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GUC008OARTRMU@mxout2.netvision.net.il> for megaco@ietf.org;
 Wed, 10 Apr 2002 15:53:51 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <2SJYPV3T>; Wed, 10 Apr 2002 15:52:34 +0300
Content-return: allowed
Date: Wed, 10 Apr 2002 15:52:34 +0300
From: Dan Elbert <delbert@radvision.com>
Subject: RE: [Megaco] Disabling all Events
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Message-id: <EE5AF23B5764D511A6B900508BB82A0B018BBF8C@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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

You are right, sorry to confuse you.

Dan

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 3:36 PM
To: 'Dan Elbert'; megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: RE: [Megaco] Disabling all Events


Hi Dan,
According to ABNF Syntax,

eventsDescriptor     = EventsToken [ EQUAL RequestID LBRKT
                       requestedEvent *( COMMA requestedEvent ) RBRKT ]

So "Events {}" is not according to syntax.

But for signals, "Signals {}" is a valid.

Reply back.
Thanks,
Sudhir

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Wednesday, April 10, 2002 4:48 PM
To: 'sudhirk@future.futsoft.com'; 'megaco@ietf.org'
Subject: RE: [Megaco] Disabling all Events


You are supposed to send empty event list

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events  {}           ; just events token
        }
    }
}

this will disable all event detection

Dan Elbert
RADVISION


-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 2:14 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Disabling all Events


Hi,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

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 Apr 10 09:19: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 JAA18360
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 09:19:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA21299
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 09:19:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA19604;
	Wed, 10 Apr 2002 08:54:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA19575
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 08:54:24 -0400 (EDT)
Received: from mxout2.netvision.net.il (mxout2.netvision.net.il [194.90.9.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17561
	for <megaco@ietf.org>; Wed, 10 Apr 2002 08:54:19 -0400 (EDT)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout2.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GUC008OARTRMU@mxout2.netvision.net.il> for megaco@ietf.org;
 Wed, 10 Apr 2002 15:53:51 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <2SJYPV3T>; Wed, 10 Apr 2002 15:52:34 +0300
Content-return: allowed
Date: Wed, 10 Apr 2002 15:52:34 +0300
From: Dan Elbert <delbert@radvision.com>
Subject: RE: [Megaco] Disabling all Events
To: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Message-id: <EE5AF23B5764D511A6B900508BB82A0B018BBF8C@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
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

You are right, sorry to confuse you.

Dan

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 3:36 PM
To: 'Dan Elbert'; megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: RE: [Megaco] Disabling all Events


Hi Dan,
According to ABNF Syntax,

eventsDescriptor     = EventsToken [ EQUAL RequestID LBRKT
                       requestedEvent *( COMMA requestedEvent ) RBRKT ]

So "Events {}" is not according to syntax.

But for signals, "Signals {}" is a valid.

Reply back.
Thanks,
Sudhir

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Wednesday, April 10, 2002 4:48 PM
To: 'sudhirk@future.futsoft.com'; 'megaco@ietf.org'
Subject: RE: [Megaco] Disabling all Events


You are supposed to send empty event list

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events  {}           ; just events token
        }
    }
}

this will disable all event detection

Dan Elbert
RADVISION


-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 2:14 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Disabling all Events


Hi,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

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 Apr 10 09:23: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 JAA18429
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 09:23:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20477;
	Wed, 10 Apr 2002 09:03:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20449
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 09:03:56 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17787
	for <megaco@ietf.org>; Wed, 10 Apr 2002 09:03:50 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUCS6I00.JGA; Wed,
          10 Apr 2002 21:01:30 +0800 
Message-ID: <017601c1e090$51d04280$26280b0a@huawei.com.cn>
From: "ding" <dingwh@huawei.com>
To: <girirs@netlab.hcltech.com>
Cc: <megaco@ietf.org>
References: <00a901c1e089$fe410560$26280b0a@huawei.com.cn> <3CB4116B.B375D20@netlab.hcltech.com>
Subject: Re: [Megaco] use of EventBufferDescriptor
Date: Wed, 10 Apr 2002 21:04:59 +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 JAA20450
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

my understanding is that 

when EventBufferControl is LockStep mode &&
                  EventsDescriptor is not active &&
                       event is found in EventBufferDescriptor

the mode to process user event equal to the mode in MGCP when

endpoint is in notification state &&
                QuarantineHandling is "process" and "step".

do you think so?



----- Original Message ----- 
From: Giri Rajasekhar Saladi <girirs@netlab.hcltech.com>
To: ding <dingwh@huawei.com>
Cc: <megaco@ietf.org>
Sent: Wednesday, April 10, 2002 6:18 PM
Subject: Re: [Megaco] use of EventBufferDescriptor


> Hi Ding,
> My answer is inline.
> 
> > ding wrote:
> > 
> > hi,
> > 
> > suppose MG receives a EventBufferDescriptor and a EventDescriptor at the same
> > time, and MG's event buffer queue(FIFO queue) is empty. now if some user event
> 
> We search for the event against EventBufferDescriptor only if EventBufferControl
> is LockStep mode and EventsDescriptor is not active.
> 
> > is recognized in the EventBufferDescriptor(and not recognized in the
> > EventDescriptor), should MG discard the user event or send it to the FIFO
> > queue?
> 
> So, if EventBufferControl is LockStep mode &&
>                  EventsDescriptor is not active &&
>                       event is found in EventBufferDescriptor
>     then
>        send it to the FIFO queue.
> 
> > 
> > I think it should be discarded, am i right?
> > 
> > thanks.
> 
> Regds.,
> Giri
> 
> -- 
> 
> 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 Extn. 233
> 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

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


From daemon@optimus.ietf.org  Wed Apr 10 09:23: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 JAA18442
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 09:23:09 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA21397
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 09:23:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20477;
	Wed, 10 Apr 2002 09:03:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA20449
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 09:03:56 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17787
	for <megaco@ietf.org>; Wed, 10 Apr 2002 09:03:50 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUCS6I00.JGA; Wed,
          10 Apr 2002 21:01:30 +0800 
Message-ID: <017601c1e090$51d04280$26280b0a@huawei.com.cn>
From: "ding" <dingwh@huawei.com>
To: <girirs@netlab.hcltech.com>
Cc: <megaco@ietf.org>
References: <00a901c1e089$fe410560$26280b0a@huawei.com.cn> <3CB4116B.B375D20@netlab.hcltech.com>
Subject: Re: [Megaco] use of EventBufferDescriptor
Date: Wed, 10 Apr 2002 21:04:59 +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 JAA20450
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

my understanding is that 

when EventBufferControl is LockStep mode &&
                  EventsDescriptor is not active &&
                       event is found in EventBufferDescriptor

the mode to process user event equal to the mode in MGCP when

endpoint is in notification state &&
                QuarantineHandling is "process" and "step".

do you think so?



----- Original Message ----- 
From: Giri Rajasekhar Saladi <girirs@netlab.hcltech.com>
To: ding <dingwh@huawei.com>
Cc: <megaco@ietf.org>
Sent: Wednesday, April 10, 2002 6:18 PM
Subject: Re: [Megaco] use of EventBufferDescriptor


> Hi Ding,
> My answer is inline.
> 
> > ding wrote:
> > 
> > hi,
> > 
> > suppose MG receives a EventBufferDescriptor and a EventDescriptor at the same
> > time, and MG's event buffer queue(FIFO queue) is empty. now if some user event
> 
> We search for the event against EventBufferDescriptor only if EventBufferControl
> is LockStep mode and EventsDescriptor is not active.
> 
> > is recognized in the EventBufferDescriptor(and not recognized in the
> > EventDescriptor), should MG discard the user event or send it to the FIFO
> > queue?
> 
> So, if EventBufferControl is LockStep mode &&
>                  EventsDescriptor is not active &&
>                       event is found in EventBufferDescriptor
>     then
>        send it to the FIFO queue.
> 
> > 
> > I think it should be discarded, am i right?
> > 
> > thanks.
> 
> Regds.,
> Giri
> 
> -- 
> 
> 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 Extn. 233
> 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

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



From megaco-admin@ietf.org  Wed Apr 10 10:06: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 KAA19845
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 10:06:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA22815;
	Wed, 10 Apr 2002 09:46:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA22778
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 09:46:20 -0400 (EDT)
Received: from postman ([217.31.228.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19107
	for <megaco@ietf.org>; Wed, 10 Apr 2002 09:46:12 -0400 (EDT)
To: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.4  June 8, 2000
Message-ID: <OF44639D33.154B9FA5-ONC2256B97.004B1528@LocalDomain>
From: "SERDAR CABUK" <serdar.cabuk@o2.com.tr>
Date: Wed, 10 Apr 2002 16:43:48 +0300
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 04/10/2002
 04:44:28 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Megaco] A quick 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


Hi,

Suppose that mode of the physical termination A is set to "receive only",
but the topology describer is telling that the connection between the
termination A and ephemeral B is send-receive, thus two way. Is this an
error, or will the termination simply not forward the incoming traffic from
B to its outgoing line?

Any comments..

Thanx

Serdar Cabuk


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


From daemon@optimus.ietf.org  Wed Apr 10 10:06: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 KAA19856
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 10:06:05 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA24212
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 10:06:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA22815;
	Wed, 10 Apr 2002 09:46:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA22778
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 09:46:20 -0400 (EDT)
Received: from postman ([217.31.228.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19107
	for <megaco@ietf.org>; Wed, 10 Apr 2002 09:46:12 -0400 (EDT)
To: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.4  June 8, 2000
Message-ID: <OF44639D33.154B9FA5-ONC2256B97.004B1528@LocalDomain>
From: "SERDAR CABUK" <serdar.cabuk@o2.com.tr>
Date: Wed, 10 Apr 2002 16:43:48 +0300
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 04/10/2002
 04:44:28 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Megaco] A quick 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


Hi,

Suppose that mode of the physical termination A is set to "receive only",
but the topology describer is telling that the connection between the
termination A and ephemeral B is send-receive, thus two way. Is this an
error, or will the termination simply not forward the incoming traffic from
B to its outgoing line?

Any comments..

Thanx

Serdar Cabuk


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



From megaco-admin@ietf.org  Wed Apr 10 11: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 LAA22563
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 11:39:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27852;
	Wed, 10 Apr 2002 11:11:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27801
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 11:11:53 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21904
	for <megaco@ietf.org>; Wed, 10 Apr 2002 11:11:47 -0400 (EDT)
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 g3AFBII00786
	for <megaco@ietf.org>; Wed, 10 Apr 2002 11:11:19 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LDVAW>; Wed, 10 Apr 2002 11:11:20 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2B7@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'SERDAR CABUK'" <serdar.cabuk@o2.com.tr>, megaco@ietf.org
Subject: RE: [Megaco] A quick question
Date: Wed, 10 Apr 2002 11:11:23 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Topology describes what will happen IF media flows are sent through the
context.  Mode determines at a particular termination for a particular
stream whether that termination passes media flows in a given direction.  So
the situation you cite is not an error and your second alternative applies.

-----Original Message-----
From: SERDAR CABUK [mailto:serdar.cabuk@o2.com.tr]
Sent: Wednesday, April 10, 2002 9:44 AM
To: megaco@ietf.org
Subject: [Megaco] A quick question



Hi,

Suppose that mode of the physical termination A is set to "receive only",
but the topology describer is telling that the connection between the
termination A and ephemeral B is send-receive, thus two way. Is this an
error, or will the termination simply not forward the incoming traffic from
B to its outgoing line?

Any comments..

Thanx

Serdar Cabuk


_______________________________________________
Megaco mailing list
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 Apr 10 11:39: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 LAA22575
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 11:39:46 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA29668
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 11:39:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27852;
	Wed, 10 Apr 2002 11:11:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27801
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 11:11:53 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21904
	for <megaco@ietf.org>; Wed, 10 Apr 2002 11:11:47 -0400 (EDT)
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 g3AFBII00786
	for <megaco@ietf.org>; Wed, 10 Apr 2002 11:11:19 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LDVAW>; Wed, 10 Apr 2002 11:11:20 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2B7@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'SERDAR CABUK'" <serdar.cabuk@o2.com.tr>, megaco@ietf.org
Subject: RE: [Megaco] A quick question
Date: Wed, 10 Apr 2002 11:11:23 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Topology describes what will happen IF media flows are sent through the
context.  Mode determines at a particular termination for a particular
stream whether that termination passes media flows in a given direction.  So
the situation you cite is not an error and your second alternative applies.

-----Original Message-----
From: SERDAR CABUK [mailto:serdar.cabuk@o2.com.tr]
Sent: Wednesday, April 10, 2002 9:44 AM
To: megaco@ietf.org
Subject: [Megaco] A quick question



Hi,

Suppose that mode of the physical termination A is set to "receive only",
but the topology describer is telling that the connection between the
termination A and ephemeral B is send-receive, thus two way. Is this an
error, or will the termination simply not forward the incoming traffic from
B to its outgoing line?

Any comments..

Thanx

Serdar Cabuk


_______________________________________________
Megaco mailing list
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 Apr 10 11:43: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 LAA22679
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 11:43:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28547;
	Wed, 10 Apr 2002 11:26:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28516
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 11:26:50 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22265
	for <megaco@ietf.org>; Wed, 10 Apr 2002 11:26:44 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3AFQGZ28229
	for <megaco@ietf.org>; Wed, 10 Apr 2002 11:26:16 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LDVQ5>; Wed, 10 Apr 2002 11:26:15 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2B9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: megaco@ietf.org
Cc: "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
        "'vbajaj@hss.hns.com'" <vbajaj@hss.hns.com>,
        "'Blatherwick, Peter'" <Peter_Blatherwick@Mitel.COM>,
        "Kevin Boyle"<kboyle@nortelnetworks.com>
Subject: RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00.
	 txt
Date: Wed, 10 Apr 2002 11:26:14 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

I don't feel as if I had a strong enough response to actually create a WG
item, yet at the same time there is definitely a set of interested parties.
What I propose is that those of you who are interested form a design team to
come up with recommendations:
  a) for changes to the protocol specification (in the form of Implementor's
Guide items, if we can get away with it)
  b) for new document(s).

-----Original Message-----
From: Blatherwick, Peter [mailto:Peter_Blatherwick@Mitel.COM]
Sent: Monday, April 01, 2002 12:42 PM
To: 'vbajaj@hss.hns.com'; Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'Jean-Luc.Lecuyer@alcatel.fr'; megaco@ietf.org
Subject: RE: [Megaco] Status of
draft-hss-megaco-control-state-machine-00. txt


I agree this should be a WG item, one way or another -- separate doc or
folded in to main protocol, perhaps updates to base protocol doc + an
Informational doc.  Its important to correct interop and affects basic use
of the protocol.  

Don't think this should be a large task however.  If it gets too large we
have likely made it too complicated, and I just don't think it really need
to be.  

My $0.02. 
-- Peter Blatherwick

-----Original Message-----
From: vbajaj@hss.hns.com [mailto:vbajaj@hss.hns.com]
Sent: March 31, 2002 23:46
To: Tom-PT Taylor
Cc: 'Jean-Luc.Lecuyer@alcatel.fr'; megaco@ietf.org
Subject: RE: [Megaco] Status of
draft-hss-megaco-control-state-machine-00. txt




Tom,
        I think it is absolutely necessary to take this activity as a WG
work
item. This area needs
  to be addressed to avoid interoperability issues later.

Rgds,

Vikas Bajaj





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 03/29/2002 09:22:32 PM

To:   "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
      megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00.
txt




Could I have opinions from the WG on whether we should be producing a
document on control associations and the signalling associated with control
state transitions as a WG work item?  I assume the work would be Standards
Track because it would specify normative behaviour on the signalling side.
As an alternative, if the impact on the base specification wouldn't be too
large, we could simply add the conclusions to the Implementor's Guide.

-----Original Message-----
From: Jean-Luc.Lecuyer@alcatel.fr [mailto:Jean-Luc.Lecuyer@alcatel.fr]
Sent: Friday, March 29, 2002 4:11 AM
To: megaco@ietf.org
Subject: [Megaco] Status of
draft-hss-megaco-control-state-machine-00.txt




What is the status of the document
"draft-hss-megaco-control-state-machine-00.txt"
which expired in February ?

Thank-you
Jean-Luc
----------------------------------------------------------------------------
----------------
Jean-Luc.Lecuyer :         VND/E10 VS  BU R&D//CCPD Lannion
Full telephone number :                                         33 (0)2 96
04 77 09
Full fax number :                                                        33
(0)2 96 04 72 35
Email :
jean-luc.lecuyer@alcatel.fr
----------------------------------------------------------------------------
-----------------



_______________________________________________
Megaco mailing 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 Apr 10 11:43: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 LAA22692
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 11:43:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA29904
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 11:43:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28547;
	Wed, 10 Apr 2002 11:26:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA28516
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 11:26:50 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22265
	for <megaco@ietf.org>; Wed, 10 Apr 2002 11:26:44 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3AFQGZ28229
	for <megaco@ietf.org>; Wed, 10 Apr 2002 11:26:16 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LDVQ5>; Wed, 10 Apr 2002 11:26:15 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2B9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: megaco@ietf.org
Cc: "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
        "'vbajaj@hss.hns.com'" <vbajaj@hss.hns.com>,
        "'Blatherwick, Peter'" <Peter_Blatherwick@Mitel.COM>,
        "Kevin Boyle"<kboyle@nortelnetworks.com>
Subject: RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00.
	 txt
Date: Wed, 10 Apr 2002 11:26:14 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

I don't feel as if I had a strong enough response to actually create a WG
item, yet at the same time there is definitely a set of interested parties.
What I propose is that those of you who are interested form a design team to
come up with recommendations:
  a) for changes to the protocol specification (in the form of Implementor's
Guide items, if we can get away with it)
  b) for new document(s).

-----Original Message-----
From: Blatherwick, Peter [mailto:Peter_Blatherwick@Mitel.COM]
Sent: Monday, April 01, 2002 12:42 PM
To: 'vbajaj@hss.hns.com'; Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'Jean-Luc.Lecuyer@alcatel.fr'; megaco@ietf.org
Subject: RE: [Megaco] Status of
draft-hss-megaco-control-state-machine-00. txt


I agree this should be a WG item, one way or another -- separate doc or
folded in to main protocol, perhaps updates to base protocol doc + an
Informational doc.  Its important to correct interop and affects basic use
of the protocol.  

Don't think this should be a large task however.  If it gets too large we
have likely made it too complicated, and I just don't think it really need
to be.  

My $0.02. 
-- Peter Blatherwick

-----Original Message-----
From: vbajaj@hss.hns.com [mailto:vbajaj@hss.hns.com]
Sent: March 31, 2002 23:46
To: Tom-PT Taylor
Cc: 'Jean-Luc.Lecuyer@alcatel.fr'; megaco@ietf.org
Subject: RE: [Megaco] Status of
draft-hss-megaco-control-state-machine-00. txt




Tom,
        I think it is absolutely necessary to take this activity as a WG
work
item. This area needs
  to be addressed to avoid interoperability issues later.

Rgds,

Vikas Bajaj





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 03/29/2002 09:22:32 PM

To:   "'Jean-Luc.Lecuyer@alcatel.fr'" <Jean-Luc.Lecuyer@alcatel.fr>,
      megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  RE: [Megaco] Status of draft-hss-megaco-control-state-machine-00.
txt




Could I have opinions from the WG on whether we should be producing a
document on control associations and the signalling associated with control
state transitions as a WG work item?  I assume the work would be Standards
Track because it would specify normative behaviour on the signalling side.
As an alternative, if the impact on the base specification wouldn't be too
large, we could simply add the conclusions to the Implementor's Guide.

-----Original Message-----
From: Jean-Luc.Lecuyer@alcatel.fr [mailto:Jean-Luc.Lecuyer@alcatel.fr]
Sent: Friday, March 29, 2002 4:11 AM
To: megaco@ietf.org
Subject: [Megaco] Status of
draft-hss-megaco-control-state-machine-00.txt




What is the status of the document
"draft-hss-megaco-control-state-machine-00.txt"
which expired in February ?

Thank-you
Jean-Luc
----------------------------------------------------------------------------
----------------
Jean-Luc.Lecuyer :         VND/E10 VS  BU R&D//CCPD Lannion
Full telephone number :                                         33 (0)2 96
04 77 09
Full fax number :                                                        33
(0)2 96 04 72 35
Email :
jean-luc.lecuyer@alcatel.fr
----------------------------------------------------------------------------
-----------------



_______________________________________________
Megaco mailing 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 Apr 10 12:19: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 MAA24121
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 12:19:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA00562;
	Wed, 10 Apr 2002 11:55:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA00524
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 11:54:53 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23304
	for <megaco@ietf.org>; Wed, 10 Apr 2002 11:54:41 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002271257@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Wed, 10 Apr 2002 21:43:03 +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 g3AFs8U13114;
	Wed, 10 Apr 2002 21:24:08 +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, 10 Apr 2002 21:22:13 +0530
Message-Id: <003201c1e0a7$afc57c40$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] Subtracting all terminations in all contexts
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,

From the RFC 3015, section 7.2.3 (Subtract), it was given that
"ALL may be used as the ContextID as well as the TerminationId in a
Subtract, which would have the effect of deleting all contexts,
deleting all ephemeral terminations, and returning all physical
terminations to Null context. Subtract of termination from the
NULL context is not allowed."

I have doubt regarding this. Can MGC send the following request packet
to MG:

Transaction = 1 {
   Context = * {     ; ALL Context Id
      Subtract = *   ; ALL Termination Id
      }
}

I want to Subtract the corresponding ADDed Terminations from the
corresponding created Contexts. Is the above packet correct.

Consider for example, two terminations TermA and TermB are ADDed in a
context 22.
To subtract both terminations from that context, Can MGC send following
packet:

Transaction = 1 {
   Context = 22

      Subtract = *   ; ALL Termination Id
      }
}

In the above packet, what could '*' indicates. Whether it indicates all the
terminations
that are present in the context 22 or all the terminations in the whole
Gateway.
From the RFC, it was given that "Subtract of termination from the
NULL context is not allowed".

In the above packet, I have given ALL Termination Id to subtract TermA and
TermB.
Is that OK.

Please reply back.

Thanks & Regards,
Sudhir


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


From daemon@optimus.ietf.org  Wed Apr 10 12:19: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 MAA24131
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 12:19:46 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA03409
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 12:19:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA00562;
	Wed, 10 Apr 2002 11:55:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA00524
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 11:54:53 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23304
	for <megaco@ietf.org>; Wed, 10 Apr 2002 11:54:41 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002271257@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Wed, 10 Apr 2002 21:43:03 +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 g3AFs8U13114;
	Wed, 10 Apr 2002 21:24:08 +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, 10 Apr 2002 21:22:13 +0530
Message-Id: <003201c1e0a7$afc57c40$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] Subtracting all terminations in all contexts
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,

From the RFC 3015, section 7.2.3 (Subtract), it was given that
"ALL may be used as the ContextID as well as the TerminationId in a
Subtract, which would have the effect of deleting all contexts,
deleting all ephemeral terminations, and returning all physical
terminations to Null context. Subtract of termination from the
NULL context is not allowed."

I have doubt regarding this. Can MGC send the following request packet
to MG:

Transaction = 1 {
   Context = * {     ; ALL Context Id
      Subtract = *   ; ALL Termination Id
      }
}

I want to Subtract the corresponding ADDed Terminations from the
corresponding created Contexts. Is the above packet correct.

Consider for example, two terminations TermA and TermB are ADDed in a
context 22.
To subtract both terminations from that context, Can MGC send following
packet:

Transaction = 1 {
   Context = 22

      Subtract = *   ; ALL Termination Id
      }
}

In the above packet, what could '*' indicates. Whether it indicates all the
terminations
that are present in the context 22 or all the terminations in the whole
Gateway.
From the RFC, it was given that "Subtract of termination from the
NULL context is not allowed".

In the above packet, I have given ALL Termination Id to subtract TermA and
TermB.
Is that OK.

Please reply back.

Thanks & Regards,
Sudhir


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



From megaco-admin@ietf.org  Wed Apr 10 12:31: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 MAA24582
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 12:31:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA03033;
	Wed, 10 Apr 2002 12:12:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA03003
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 12:12:21 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23862
	for <megaco@ietf.org>; Wed, 10 Apr 2002 12:12:13 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3AGBjZ01707
	for <megaco@ietf.org>; Wed, 10 Apr 2002 12:11:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LDW5T>; Wed, 10 Apr 2002 12:11:45 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2BB@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] Subtracting all terminations in all contexts
Date: Wed, 10 Apr 2002 12:11:44 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

These operations look OK to me.  Don't let the busines of the NULL context
distract you: ALL does not include the NULL context, so you are not
violating anything if you set context to ALL in your subtraction.

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 11:52 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Subtracting all terminations in all contexts


Hi,

From the RFC 3015, section 7.2.3 (Subtract), it was given that
"ALL may be used as the ContextID as well as the TerminationId in a
Subtract, which would have the effect of deleting all contexts,
deleting all ephemeral terminations, and returning all physical
terminations to Null context. Subtract of termination from the
NULL context is not allowed."

I have doubt regarding this. Can MGC send the following request packet
to MG:

Transaction = 1 {
   Context = * {     ; ALL Context Id
      Subtract = *   ; ALL Termination Id
      }
}

I want to Subtract the corresponding ADDed Terminations from the
corresponding created Contexts. Is the above packet correct.

Consider for example, two terminations TermA and TermB are ADDed in a
context 22.
To subtract both terminations from that context, Can MGC send following
packet:

Transaction = 1 {
   Context = 22

      Subtract = *   ; ALL Termination Id
      }
}

In the above packet, what could '*' indicates. Whether it indicates all the
terminations
that are present in the context 22 or all the terminations in the whole
Gateway.
From the RFC, it was given that "Subtract of termination from the
NULL context is not allowed".

In the above packet, I have given ALL Termination Id to subtract TermA and
TermB.
Is that OK.

Please reply back.

Thanks & Regards,
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 Apr 10 12:31: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 MAA24593
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 12:31:08 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA04002
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 12:31:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA03033;
	Wed, 10 Apr 2002 12:12:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA03003
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 12:12:21 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23862
	for <megaco@ietf.org>; Wed, 10 Apr 2002 12:12:13 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3AGBjZ01707
	for <megaco@ietf.org>; Wed, 10 Apr 2002 12:11:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LDW5T>; Wed, 10 Apr 2002 12:11:45 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2BB@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] Subtracting all terminations in all contexts
Date: Wed, 10 Apr 2002 12:11:44 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

These operations look OK to me.  Don't let the busines of the NULL context
distract you: ALL does not include the NULL context, so you are not
violating anything if you set context to ALL in your subtraction.

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 11:52 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Subtracting all terminations in all contexts


Hi,

From the RFC 3015, section 7.2.3 (Subtract), it was given that
"ALL may be used as the ContextID as well as the TerminationId in a
Subtract, which would have the effect of deleting all contexts,
deleting all ephemeral terminations, and returning all physical
terminations to Null context. Subtract of termination from the
NULL context is not allowed."

I have doubt regarding this. Can MGC send the following request packet
to MG:

Transaction = 1 {
   Context = * {     ; ALL Context Id
      Subtract = *   ; ALL Termination Id
      }
}

I want to Subtract the corresponding ADDed Terminations from the
corresponding created Contexts. Is the above packet correct.

Consider for example, two terminations TermA and TermB are ADDed in a
context 22.
To subtract both terminations from that context, Can MGC send following
packet:

Transaction = 1 {
   Context = 22

      Subtract = *   ; ALL Termination Id
      }
}

In the above packet, what could '*' indicates. Whether it indicates all the
terminations
that are present in the context 22 or all the terminations in the whole
Gateway.
From the RFC, it was given that "Subtract of termination from the
NULL context is not allowed".

In the above packet, I have given ALL Termination Id to subtract TermA and
TermB.
Is that OK.

Please reply back.

Thanks & Regards,
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 Apr 10 13:12: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 NAA25519
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 13:12:35 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04929;
	Wed, 10 Apr 2002 12:51:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04900
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 12:51:09 -0400 (EDT)
Received: from zrtps0kn.nortelnetworks.com (zrtps0kn.nortelnetworks.com [47.140.192.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25029
	for <megaco@ietf.org>; Wed, 10 Apr 2002 12:51:06 -0400 (EDT)
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3AGoOg01430;
	Wed, 10 Apr 2002 12:50:29 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2T2KRL6Q>; Wed, 10 Apr 2002 12:50:26 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C02CAAABF@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: sudhirk@future.futsoft.com, megaco@ietf.org
Subject: RE: [Megaco] Subtracting all terminations in all contexts
Date: Wed, 10 Apr 2002 12:50:30 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Other than missing the brackets for the subtract command your assertions
below are correct.  This message:

T=1{C=*{S=*{}}}

means subtract all terminations from all contexts, and this message:

T=1{C=22{S=*{}}}

means subtract all terminations from context 22.

Note that the first message above will return an error if all the
terminations in the MG are in the NULL context.

Kevin

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 11:52 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Subtracting all terminations in all contexts


Hi,

From the RFC 3015, section 7.2.3 (Subtract), it was given that
"ALL may be used as the ContextID as well as the TerminationId in a
Subtract, which would have the effect of deleting all contexts,
deleting all ephemeral terminations, and returning all physical
terminations to Null context. Subtract of termination from the
NULL context is not allowed."

I have doubt regarding this. Can MGC send the following request packet
to MG:

Transaction = 1 {
   Context = * {     ; ALL Context Id
      Subtract = *   ; ALL Termination Id
      }
}

I want to Subtract the corresponding ADDed Terminations from the
corresponding created Contexts. Is the above packet correct.

Consider for example, two terminations TermA and TermB are ADDed in a
context 22.
To subtract both terminations from that context, Can MGC send following
packet:

Transaction = 1 {
   Context = 22

      Subtract = *   ; ALL Termination Id
      }
}

In the above packet, what could '*' indicates. Whether it indicates all the
terminations
that are present in the context 22 or all the terminations in the whole
Gateway.
From the RFC, it was given that "Subtract of termination from the
NULL context is not allowed".

In the above packet, I have given ALL Termination Id to subtract TermA and
TermB.
Is that OK.

Please reply back.

Thanks & Regards,
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 Apr 10 13:12: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 NAA25534
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 13:12:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA06266
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 13:12:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04929;
	Wed, 10 Apr 2002 12:51:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04900
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 12:51:09 -0400 (EDT)
Received: from zrtps0kn.nortelnetworks.com (zrtps0kn.nortelnetworks.com [47.140.192.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25029
	for <megaco@ietf.org>; Wed, 10 Apr 2002 12:51:06 -0400 (EDT)
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3AGoOg01430;
	Wed, 10 Apr 2002 12:50:29 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2T2KRL6Q>; Wed, 10 Apr 2002 12:50:26 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C02CAAABF@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: sudhirk@future.futsoft.com, megaco@ietf.org
Subject: RE: [Megaco] Subtracting all terminations in all contexts
Date: Wed, 10 Apr 2002 12:50:30 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Other than missing the brackets for the subtract command your assertions
below are correct.  This message:

T=1{C=*{S=*{}}}

means subtract all terminations from all contexts, and this message:

T=1{C=22{S=*{}}}

means subtract all terminations from context 22.

Note that the first message above will return an error if all the
terminations in the MG are in the NULL context.

Kevin

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 11:52 AM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] Subtracting all terminations in all contexts


Hi,

From the RFC 3015, section 7.2.3 (Subtract), it was given that
"ALL may be used as the ContextID as well as the TerminationId in a
Subtract, which would have the effect of deleting all contexts,
deleting all ephemeral terminations, and returning all physical
terminations to Null context. Subtract of termination from the
NULL context is not allowed."

I have doubt regarding this. Can MGC send the following request packet
to MG:

Transaction = 1 {
   Context = * {     ; ALL Context Id
      Subtract = *   ; ALL Termination Id
      }
}

I want to Subtract the corresponding ADDed Terminations from the
corresponding created Contexts. Is the above packet correct.

Consider for example, two terminations TermA and TermB are ADDed in a
context 22.
To subtract both terminations from that context, Can MGC send following
packet:

Transaction = 1 {
   Context = 22

      Subtract = *   ; ALL Termination Id
      }
}

In the above packet, what could '*' indicates. Whether it indicates all the
terminations
that are present in the context 22 or all the terminations in the whole
Gateway.
From the RFC, it was given that "Subtract of termination from the
NULL context is not allowed".

In the above packet, I have given ALL Termination Id to subtract TermA and
TermB.
Is that OK.

Please reply back.

Thanks & Regards,
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 Apr 10 14:34: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 OAA28786
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 14:34:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA10286;
	Wed, 10 Apr 2002 14:15:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA10247
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 14:15:13 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27951
	for <megaco@ietf.org>; Wed, 10 Apr 2002 14:15:08 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002272052@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Thu, 11 Apr 2002 00:03: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 g3AIEVU21193;
	Wed, 10 Apr 2002 23:44:31 +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, 10 Apr 2002 23:42:36 +0530
Message-Id: <003c01c1e0bb$4ba38b80$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] FW: Disabling all Events
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,
Can you reply for this doubt.
Thanks,
Sudhir

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 4:44 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: Disabling all Events


Hi,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

Thanks,
Sudhir


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


From daemon@optimus.ietf.org  Wed Apr 10 14:34: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 OAA28800
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 14:34:50 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA12088
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 14:34:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA10286;
	Wed, 10 Apr 2002 14:15:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA10247
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 14:15:13 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27951
	for <megaco@ietf.org>; Wed, 10 Apr 2002 14:15:08 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002272052@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Thu, 11 Apr 2002 00:03: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 g3AIEVU21193;
	Wed, 10 Apr 2002 23:44:31 +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, 10 Apr 2002 23:42:36 +0530
Message-Id: <003c01c1e0bb$4ba38b80$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] FW: Disabling all Events
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,
Can you reply for this doubt.
Thanks,
Sudhir

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 4:44 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: Disabling all Events


Hi,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

Thanks,
Sudhir


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



From megaco-admin@ietf.org  Wed Apr 10 14:41: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 OAA29130
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 14:41:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA10459;
	Wed, 10 Apr 2002 14:17:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA10432
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 14:17:44 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28012
	for <megaco@ietf.org>; Wed, 10 Apr 2002 14:17:39 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002272060@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Thu, 11 Apr 2002 00:05:59 +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 g3AIH5U21206;
	Wed, 10 Apr 2002 23:47:05 +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, 10 Apr 2002 23:45:10 +0530
Message-Id: <003d01c1e0bb$a7a1f5c0$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
In-Reply-To: <002401c1e084$f028dfc0$3a07020a@future.futsoft.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] RE: Deleting DigitMap from a Termination
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,
Can you please respond to this mail.
Thanks,
Sudhir


-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 5:13 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: Deleting DigitMap from a Termination


Hi,

Is MGC can delete the DigitMap that is already defined using the
following packet:

Transaction = 1 {
   Context = - {
      Modify = TermA {
         DigitMap = Dmap1 { }  ; empty value for a name
      }
   }
}

First of all, MGC can Modify DigitMap on a Termination which is in NULL
Context.

Thanks,
Sudhir


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


From daemon@optimus.ietf.org  Wed Apr 10 14:41: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 OAA29138
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 14:41:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA12339
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 14:41:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA10459;
	Wed, 10 Apr 2002 14:17:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA10432
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 14:17:44 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28012
	for <megaco@ietf.org>; Wed, 10 Apr 2002 14:17:39 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002272060@fsnt.future.futsoft.com> for <megaco@ietf.org>;
 Thu, 11 Apr 2002 00:05:59 +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 g3AIH5U21206;
	Wed, 10 Apr 2002 23:47:05 +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, 10 Apr 2002 23:45:10 +0530
Message-Id: <003d01c1e0bb$a7a1f5c0$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
In-Reply-To: <002401c1e084$f028dfc0$3a07020a@future.futsoft.com>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] RE: Deleting DigitMap from a Termination
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,
Can you please respond to this mail.
Thanks,
Sudhir


-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 5:13 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: Deleting DigitMap from a Termination


Hi,

Is MGC can delete the DigitMap that is already defined using the
following packet:

Transaction = 1 {
   Context = - {
      Modify = TermA {
         DigitMap = Dmap1 { }  ; empty value for a name
      }
   }
}

First of all, MGC can Modify DigitMap on a Termination which is in NULL
Context.

Thanks,
Sudhir


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



From megaco-admin@ietf.org  Wed Apr 10 18:53: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 SAA04701
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 18:53:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25102;
	Wed, 10 Apr 2002 18:32:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25076
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 18:32:55 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04131
	for <megaco@ietf.org>; Wed, 10 Apr 2002 18:32:50 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3AMWMZ25562
	for <megaco@ietf.org>; Wed, 10 Apr 2002 18:32:23 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63L1ABS>; Wed, 10 Apr 2002 18:32:22 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2BF@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] RE: Deleting DigitMap from a Termination
Date: Wed, 10 Apr 2002 18:32:22 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

You are correct.  See section 7.1.14.1.

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 2:15 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] RE: Deleting DigitMap from a Termination


Tom,
Can you please respond to this mail.
Thanks,
Sudhir


-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 5:13 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: Deleting DigitMap from a Termination


Hi,

Is MGC can delete the DigitMap that is already defined using the
following packet:

Transaction = 1 {
   Context = - {
      Modify = TermA {
         DigitMap = Dmap1 { }  ; empty value for a name
      }
   }
}

First of all, MGC can Modify DigitMap on a Termination which is in NULL
Context.

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 Apr 10 18:53: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 SAA04714
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 18:53:19 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA25655
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 18:53:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25102;
	Wed, 10 Apr 2002 18:32:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25076
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 18:32:55 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04131
	for <megaco@ietf.org>; Wed, 10 Apr 2002 18:32:50 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3AMWMZ25562
	for <megaco@ietf.org>; Wed, 10 Apr 2002 18:32:23 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63L1ABS>; Wed, 10 Apr 2002 18:32:22 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2BF@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] RE: Deleting DigitMap from a Termination
Date: Wed, 10 Apr 2002 18:32:22 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

You are correct.  See section 7.1.14.1.

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 2:15 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] RE: Deleting DigitMap from a Termination


Tom,
Can you please respond to this mail.
Thanks,
Sudhir


-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 5:13 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: Deleting DigitMap from a Termination


Hi,

Is MGC can delete the DigitMap that is already defined using the
following packet:

Transaction = 1 {
   Context = - {
      Modify = TermA {
         DigitMap = Dmap1 { }  ; empty value for a name
      }
   }
}

First of all, MGC can Modify DigitMap on a Termination which is in NULL
Context.

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 Apr 10 18:53: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 SAA04736
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 18:53:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA24844;
	Wed, 10 Apr 2002 18:30:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA24807
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 18:30:46 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04114
	for <megaco@ietf.org>; Wed, 10 Apr 2002 18:30:40 -0400 (EDT)
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 g3AMUCI13183
	for <megaco@ietf.org>; Wed, 10 Apr 2002 18:30:12 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63L1AA7>; Wed, 10 Apr 2002 18:30:13 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2BE@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] FW: Disabling all Events
Date: Wed, 10 Apr 2002 18:30:12 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

I'm surprised no one has brought this up before, though I have the vaguest
memory of a discussion a couple of years ago in which I favoured this
syntax.  (Whether I did or not, it looks a bit irregular to me now.)  It
certainly appears that you are right, but perhaps it is an item for an
Implementor's Guide correction in the syntax to allow the empty braces.

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 2:13 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] FW: Disabling all Events


Tom,
Can you reply for this doubt.
Thanks,
Sudhir

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 4:44 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: Disabling all Events


Hi,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

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 Apr 10 18:53: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 SAA04746
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 18:53:49 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA25689
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 18:53:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA24844;
	Wed, 10 Apr 2002 18:30:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA24807
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 18:30:46 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04114
	for <megaco@ietf.org>; Wed, 10 Apr 2002 18:30:40 -0400 (EDT)
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 g3AMUCI13183
	for <megaco@ietf.org>; Wed, 10 Apr 2002 18:30:12 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63L1AA7>; Wed, 10 Apr 2002 18:30:13 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2BE@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] FW: Disabling all Events
Date: Wed, 10 Apr 2002 18:30:12 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

I'm surprised no one has brought this up before, though I have the vaguest
memory of a discussion a couple of years ago in which I favoured this
syntax.  (Whether I did or not, it looks a bit irregular to me now.)  It
certainly appears that you are right, but perhaps it is an item for an
Implementor's Guide correction in the syntax to allow the empty braces.

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 2:13 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: [Megaco] FW: Disabling all Events


Tom,
Can you reply for this doubt.
Thanks,
Sudhir

-----Original Message-----
From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
Sent: Wednesday, April 10, 2002 4:44 PM
To: megaco@ietf.org
Cc: Sudhir (E-mail)
Subject: Disabling all Events


Hi,

Is MGC can send the following packet to disable all Events that were
previously
activated:

Transaction = 1 {
       Context = - {
           Modify = TermA {
               Events             ; just events token
        }
    }
}

Is the above packet is a valid. As far as syntax is considered, it is valid.

As far as I know, just Events token will be used by MG as a reply to
AuditValue Transaction if no Event(s) were activated.

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 Apr 10 21:31: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 VAA06666
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 21:31:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01863;
	Wed, 10 Apr 2002 21:07:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01834
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 21:07:07 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06379
	for <megaco@ietf.org>; Wed, 10 Apr 2002 21:07:01 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUDPMB01.02X; Thu,
          11 Apr 2002 09:03:47 +0800 
Message-ID: <005201c1e0f5$39d8bf80$26280b0a@huawei.com.cn>
From: "ding" <dingwh@huawei.com>
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
Cc: <megaco@ietf.org>
Subject: Fw: [Megaco] use of EventBufferDescriptor
Date: Thu, 11 Apr 2002 09:07:18 +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 VAA01835
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 Tom,

do u think I'm right or not?

thanks

Watson. Ding


----- Original Message ----- 
From: ding <dingwh@huawei.com>
To: <girirs@netlab.hcltech.com>
Cc: <megaco@ietf.org>
Sent: Wednesday, April 10, 2002 9:04 PM
Subject: Re: [Megaco] use of EventBufferDescriptor


> my understanding is that 
> 
> when EventBufferControl is LockStep mode &&
>                   EventsDescriptor is not active &&
>                        event is found in EventBufferDescriptor
> 
> the mode to process user event equal to the mode in MGCP when
> 
> endpoint is in notification state &&
>                 QuarantineHandling is "process" and "step".
> 
> do you think so?
> 
> 
> 
> ----- Original Message ----- 
> From: Giri Rajasekhar Saladi <girirs@netlab.hcltech.com>
> To: ding <dingwh@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Wednesday, April 10, 2002 6:18 PM
> Subject: Re: [Megaco] use of EventBufferDescriptor
> 
> 
> > Hi Ding,
> > My answer is inline.
> > 
> > > ding wrote:
> > > 
> > > hi,
> > > 
> > > suppose MG receives a EventBufferDescriptor and a EventDescriptor at the same
> > > time, and MG's event buffer queue(FIFO queue) is empty. now if some user event
> > 
> > We search for the event against EventBufferDescriptor only if EventBufferControl
> > is LockStep mode and EventsDescriptor is not active.
> > 
> > > is recognized in the EventBufferDescriptor(and not recognized in the
> > > EventDescriptor), should MG discard the user event or send it to the FIFO
> > > queue?
> > 
> > So, if EventBufferControl is LockStep mode &&
> >                  EventsDescriptor is not active &&
> >                       event is found in EventBufferDescriptor
> >     then
> >        send it to the FIFO queue.
> > 
> > > 
> > > I think it should be discarded, am i right?
> > > 
> > > thanks.
> > 
> > Regds.,
> > Giri
> > 
> > -- 
> > 
> > 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 Extn. 233
> > 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
> 
> _______________________________________________
> Megaco mailing list
> 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 Apr 10 21:31: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 VAA06676
	for <megaco-archive@odin.ietf.org>; Wed, 10 Apr 2002 21:31:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA02951
	for megaco-archive@odin.ietf.org; Wed, 10 Apr 2002 21:31:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01863;
	Wed, 10 Apr 2002 21:07:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01834
	for <megaco@optimus.ietf.org>; Wed, 10 Apr 2002 21:07:07 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06379
	for <megaco@ietf.org>; Wed, 10 Apr 2002 21:07:01 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUDPMB01.02X; Thu,
          11 Apr 2002 09:03:47 +0800 
Message-ID: <005201c1e0f5$39d8bf80$26280b0a@huawei.com.cn>
From: "ding" <dingwh@huawei.com>
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
Cc: <megaco@ietf.org>
Subject: Fw: [Megaco] use of EventBufferDescriptor
Date: Thu, 11 Apr 2002 09:07:18 +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 VAA01835
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 Tom,

do u think I'm right or not?

thanks

Watson. Ding


----- Original Message ----- 
From: ding <dingwh@huawei.com>
To: <girirs@netlab.hcltech.com>
Cc: <megaco@ietf.org>
Sent: Wednesday, April 10, 2002 9:04 PM
Subject: Re: [Megaco] use of EventBufferDescriptor


> my understanding is that 
> 
> when EventBufferControl is LockStep mode &&
>                   EventsDescriptor is not active &&
>                        event is found in EventBufferDescriptor
> 
> the mode to process user event equal to the mode in MGCP when
> 
> endpoint is in notification state &&
>                 QuarantineHandling is "process" and "step".
> 
> do you think so?
> 
> 
> 
> ----- Original Message ----- 
> From: Giri Rajasekhar Saladi <girirs@netlab.hcltech.com>
> To: ding <dingwh@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Wednesday, April 10, 2002 6:18 PM
> Subject: Re: [Megaco] use of EventBufferDescriptor
> 
> 
> > Hi Ding,
> > My answer is inline.
> > 
> > > ding wrote:
> > > 
> > > hi,
> > > 
> > > suppose MG receives a EventBufferDescriptor and a EventDescriptor at the same
> > > time, and MG's event buffer queue(FIFO queue) is empty. now if some user event
> > 
> > We search for the event against EventBufferDescriptor only if EventBufferControl
> > is LockStep mode and EventsDescriptor is not active.
> > 
> > > is recognized in the EventBufferDescriptor(and not recognized in the
> > > EventDescriptor), should MG discard the user event or send it to the FIFO
> > > queue?
> > 
> > So, if EventBufferControl is LockStep mode &&
> >                  EventsDescriptor is not active &&
> >                       event is found in EventBufferDescriptor
> >     then
> >        send it to the FIFO queue.
> > 
> > > 
> > > I think it should be discarded, am i right?
> > > 
> > > thanks.
> > 
> > Regds.,
> > Giri
> > 
> > -- 
> > 
> > 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 Extn. 233
> > 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
> 
> _______________________________________________
> Megaco mailing list
> 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 Apr 11 02:28: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 CAA20677
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 02:28:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA24877;
	Thu, 11 Apr 2002 01:54:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA24837
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 01:54:04 -0400 (EDT)
Received: from blaze.hcltech.com (pop.hclt-guindy.co.in [203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12090
	for <megaco@ietf.org>; Thu, 11 Apr 2002 01:54:00 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id LAA27174;
	Thu, 11 Apr 2002 11:22:34 +0530
Message-ID: <3CB4FF4D.FE92B7D@netlab.hcltech.com>
Date: Thu, 11 Apr 2002 08:43:17 +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: sudhirk@future.futsoft.com
CC: megaco@ietf.org
Subject: Re: [Megaco] Subtracting all terminations in all contexts
References: <003201c1e0a7$afc57c40$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 Sudhir,
	My answers inline.

Sudhir Kumar Appana wrote:
> 
> Hi,
> 
> >From the RFC 3015, section 7.2.3 (Subtract), it was given that
> "ALL may be used as the ContextID as well as the TerminationId in a
> Subtract, which would have the effect of deleting all contexts,
> deleting all ephemeral terminations, and returning all physical
> terminations to Null context. Subtract of termination from the
> NULL context is not allowed."
> 
> I have doubt regarding this. Can MGC send the following request packet
> to MG:
> 
> Transaction = 1 {
>    Context = * {     ; ALL Context Id
>       Subtract = *   ; ALL Termination Id
>       }
> }
> 
> I want to Subtract the corresponding ADDed Terminations from the
> corresponding created Contexts. Is the above packet correct.
> 

The above command shall subtract (delete all the Ephemeral terminations
and return all the Permanant terminations to NULL context) in all the
contexts except NULL context.

> Consider for example, two terminations TermA and TermB are ADDed in a
> context 22.
> To subtract both terminations from that context, Can MGC send following
> packet:
> 
> Transaction = 1 {
>    Context = 22
> 
>       Subtract = *   ; ALL Termination Id
>       }
> }
> 

Yes.

> In the above packet, what could '*' indicates. Whether it indicates all the
> terminations
> that are present in the context 22 or all the terminations in the whole
> Gateway.

it indicates all the terminations that are present in the context 22.

> >From the RFC, it was given that "Subtract of termination from the
> NULL context is not allowed".
> 
> In the above packet, I have given ALL Termination Id to subtract TermA and
> TermB.
> Is that OK.
> 

You have specified all terminations in the context '22'.
That's Ok.

> Please reply back.
> 
> Thanks & Regards,
> Sudhir
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

Regds.,
Giri
-- 

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 Extn. 233
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  Thu Apr 11 02: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 CAA20691
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 02:28:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA26213
	for megaco-archive@odin.ietf.org; Thu, 11 Apr 2002 02:28:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA24877;
	Thu, 11 Apr 2002 01:54:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA24837
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 01:54:04 -0400 (EDT)
Received: from blaze.hcltech.com (pop.hclt-guindy.co.in [203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12090
	for <megaco@ietf.org>; Thu, 11 Apr 2002 01:54:00 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id LAA27174;
	Thu, 11 Apr 2002 11:22:34 +0530
Message-ID: <3CB4FF4D.FE92B7D@netlab.hcltech.com>
Date: Thu, 11 Apr 2002 08:43:17 +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: sudhirk@future.futsoft.com
CC: megaco@ietf.org
Subject: Re: [Megaco] Subtracting all terminations in all contexts
References: <003201c1e0a7$afc57c40$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 Sudhir,
	My answers inline.

Sudhir Kumar Appana wrote:
> 
> Hi,
> 
> >From the RFC 3015, section 7.2.3 (Subtract), it was given that
> "ALL may be used as the ContextID as well as the TerminationId in a
> Subtract, which would have the effect of deleting all contexts,
> deleting all ephemeral terminations, and returning all physical
> terminations to Null context. Subtract of termination from the
> NULL context is not allowed."
> 
> I have doubt regarding this. Can MGC send the following request packet
> to MG:
> 
> Transaction = 1 {
>    Context = * {     ; ALL Context Id
>       Subtract = *   ; ALL Termination Id
>       }
> }
> 
> I want to Subtract the corresponding ADDed Terminations from the
> corresponding created Contexts. Is the above packet correct.
> 

The above command shall subtract (delete all the Ephemeral terminations
and return all the Permanant terminations to NULL context) in all the
contexts except NULL context.

> Consider for example, two terminations TermA and TermB are ADDed in a
> context 22.
> To subtract both terminations from that context, Can MGC send following
> packet:
> 
> Transaction = 1 {
>    Context = 22
> 
>       Subtract = *   ; ALL Termination Id
>       }
> }
> 

Yes.

> In the above packet, what could '*' indicates. Whether it indicates all the
> terminations
> that are present in the context 22 or all the terminations in the whole
> Gateway.

it indicates all the terminations that are present in the context 22.

> >From the RFC, it was given that "Subtract of termination from the
> NULL context is not allowed".
> 
> In the above packet, I have given ALL Termination Id to subtract TermA and
> TermB.
> Is that OK.
> 

You have specified all terminations in the context '22'.
That's Ok.

> Please reply back.
> 
> Thanks & Regards,
> Sudhir
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

Regds.,
Giri
-- 

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 Extn. 233
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  Thu Apr 11 03:03: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 DAA21144
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 03:03:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27085;
	Thu, 11 Apr 2002 02:39:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27054
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 02:39:22 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20828
	for <megaco@ietf.org>; Thu, 11 Apr 2002 02:39:16 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUE51J00.R8Y; Thu,
          11 Apr 2002 14:36:55 +0800 
Message-ID: <002001c1e123$c35ad760$26280b0a@huawei.com.cn>
From: "Watson Ding" <dingwh@huawei.com>
To: <girirs@netlab.hcltech.com>
Cc: <megaco@ietf.org>
References: <00a901c1e089$fe410560$26280b0a@huawei.com.cn> <3CB4116B.B375D20@netlab.hcltech.com>
Subject: Re: [Megaco] use of EventBufferDescriptor
Date: Thu, 11 Apr 2002 14:40:25 +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 CAA27055
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

when should MG set EventsDescriptor to be inactive?

after received a new EventBufferDescriptor && a new EventBufferControl  with the value LockStep 

or after send a notify command && and no new EventsDescriptor received?

----- Original Message ----- 
From: Giri Rajasekhar Saladi <girirs@netlab.hcltech.com>
To: ding <dingwh@huawei.com>
Cc: <megaco@ietf.org>
Sent: Wednesday, April 10, 2002 6:18 PM
Subject: Re: [Megaco] use of EventBufferDescriptor


> Hi Ding,
> My answer is inline.
> 
> > ding wrote:
> > 
> > hi,
> > 
> > suppose MG receives a EventBufferDescriptor and a EventDescriptor at the same
> > time, and MG's event buffer queue(FIFO queue) is empty. now if some user event
> 
> We search for the event against EventBufferDescriptor only if EventBufferControl
> is LockStep mode and EventsDescriptor is not active.
> 
> > is recognized in the EventBufferDescriptor(and not recognized in the
> > EventDescriptor), should MG discard the user event or send it to the FIFO
> > queue?
> 
> So, if EventBufferControl is LockStep mode &&
>                  EventsDescriptor is not active &&
>                       event is found in EventBufferDescriptor
>     then
>        send it to the FIFO queue.
> 
> > 
> > I think it should be discarded, am i right?
> > 
> > thanks.
> 
> Regds.,
> Giri
> 
> -- 
> 
> 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 Extn. 233
> 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

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


From daemon@optimus.ietf.org  Thu Apr 11 03:03: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 DAA21153
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 03:03:11 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA28306
	for megaco-archive@odin.ietf.org; Thu, 11 Apr 2002 03:03:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27085;
	Thu, 11 Apr 2002 02:39:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27054
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 02:39:22 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20828
	for <megaco@ietf.org>; Thu, 11 Apr 2002 02:39:16 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUE51J00.R8Y; Thu,
          11 Apr 2002 14:36:55 +0800 
Message-ID: <002001c1e123$c35ad760$26280b0a@huawei.com.cn>
From: "Watson Ding" <dingwh@huawei.com>
To: <girirs@netlab.hcltech.com>
Cc: <megaco@ietf.org>
References: <00a901c1e089$fe410560$26280b0a@huawei.com.cn> <3CB4116B.B375D20@netlab.hcltech.com>
Subject: Re: [Megaco] use of EventBufferDescriptor
Date: Thu, 11 Apr 2002 14:40:25 +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 CAA27055
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

when should MG set EventsDescriptor to be inactive?

after received a new EventBufferDescriptor && a new EventBufferControl  with the value LockStep 

or after send a notify command && and no new EventsDescriptor received?

----- Original Message ----- 
From: Giri Rajasekhar Saladi <girirs@netlab.hcltech.com>
To: ding <dingwh@huawei.com>
Cc: <megaco@ietf.org>
Sent: Wednesday, April 10, 2002 6:18 PM
Subject: Re: [Megaco] use of EventBufferDescriptor


> Hi Ding,
> My answer is inline.
> 
> > ding wrote:
> > 
> > hi,
> > 
> > suppose MG receives a EventBufferDescriptor and a EventDescriptor at the same
> > time, and MG's event buffer queue(FIFO queue) is empty. now if some user event
> 
> We search for the event against EventBufferDescriptor only if EventBufferControl
> is LockStep mode and EventsDescriptor is not active.
> 
> > is recognized in the EventBufferDescriptor(and not recognized in the
> > EventDescriptor), should MG discard the user event or send it to the FIFO
> > queue?
> 
> So, if EventBufferControl is LockStep mode &&
>                  EventsDescriptor is not active &&
>                       event is found in EventBufferDescriptor
>     then
>        send it to the FIFO queue.
> 
> > 
> > I think it should be discarded, am i right?
> > 
> > thanks.
> 
> Regds.,
> Giri
> 
> -- 
> 
> 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 Extn. 233
> 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

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



From megaco-admin@ietf.org  Thu Apr 11 03:28: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 DAA21360
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 03:28:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28350;
	Thu, 11 Apr 2002 03:03:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28319
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 03:03:20 -0400 (EDT)
Received: from blaze.hcltech.com ([61.11.73.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21142
	for <megaco@ietf.org>; Thu, 11 Apr 2002 03:03:08 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id MAA28529;
	Thu, 11 Apr 2002 12:31:22 +0530
Message-ID: <3CB5348C.4AF3B9CA@netlab.hcltech.com>
Date: Thu, 11 Apr 2002 12:30:28 +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: Watson Ding <dingwh@huawei.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] use of EventBufferDescriptor
References: <00a901c1e089$fe410560$26280b0a@huawei.com.cn> <3CB4116B.B375D20@netlab.hcltech.com> <002001c1e123$c35ad760$26280b0a@huawei.com.cn>
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 Watson,
	The latter is true, MG sets the EventsDescriptor to
Inactive, when
1) EventBufferControl is LockStep &&
2) When MG Detected an event and Notified to MGC and yet to
   receive a new EventsDescriptor.

Becomes Active when MG recieves a new EventsDescriptor from
MGC.
Regds.,
Giri

Watson Ding wrote:
> 
> when should MG set EventsDescriptor to be inactive?
> 
> after received a new EventBufferDescriptor && a new EventBufferControl  with the value LockStep
> 
> or after send a notify command && and no new EventsDescriptor received?
> 
> ----- Original Message -----
> From: Giri Rajasekhar Saladi <girirs@netlab.hcltech.com>
> To: ding <dingwh@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Wednesday, April 10, 2002 6:18 PM
> Subject: Re: [Megaco] use of EventBufferDescriptor
> 
> > Hi Ding,
> > My answer is inline.
> >
> > > ding wrote:
> > >
> > > hi,
> > >
> > > suppose MG receives a EventBufferDescriptor and a EventDescriptor at the same
> > > time, and MG's event buffer queue(FIFO queue) is empty. now if some user event
> >
> > We search for the event against EventBufferDescriptor only if EventBufferControl
> > is LockStep mode and EventsDescriptor is not active.
> >
> > > is recognized in the EventBufferDescriptor(and not recognized in the
> > > EventDescriptor), should MG discard the user event or send it to the FIFO
> > > queue?
> >
> > So, if EventBufferControl is LockStep mode &&
> >                  EventsDescriptor is not active &&
> >                       event is found in EventBufferDescriptor
> >     then
> >        send it to the FIFO queue.
> >
> > >
> > > I think it should be discarded, am i right?
> > >
> > > thanks.
> >
> > Regds.,
> > Giri
> >
> > --
> >
> > 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 Extn. 233
> > 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
> 
> _______________________________________________
> 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 Extn. 233
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  Thu Apr 11 03: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 DAA21369
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 03:28:40 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA29219
	for megaco-archive@odin.ietf.org; Thu, 11 Apr 2002 03:28:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28350;
	Thu, 11 Apr 2002 03:03:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28319
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 03:03:20 -0400 (EDT)
Received: from blaze.hcltech.com ([61.11.73.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21142
	for <megaco@ietf.org>; Thu, 11 Apr 2002 03:03:08 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id MAA28529;
	Thu, 11 Apr 2002 12:31:22 +0530
Message-ID: <3CB5348C.4AF3B9CA@netlab.hcltech.com>
Date: Thu, 11 Apr 2002 12:30:28 +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: Watson Ding <dingwh@huawei.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] use of EventBufferDescriptor
References: <00a901c1e089$fe410560$26280b0a@huawei.com.cn> <3CB4116B.B375D20@netlab.hcltech.com> <002001c1e123$c35ad760$26280b0a@huawei.com.cn>
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 Watson,
	The latter is true, MG sets the EventsDescriptor to
Inactive, when
1) EventBufferControl is LockStep &&
2) When MG Detected an event and Notified to MGC and yet to
   receive a new EventsDescriptor.

Becomes Active when MG recieves a new EventsDescriptor from
MGC.
Regds.,
Giri

Watson Ding wrote:
> 
> when should MG set EventsDescriptor to be inactive?
> 
> after received a new EventBufferDescriptor && a new EventBufferControl  with the value LockStep
> 
> or after send a notify command && and no new EventsDescriptor received?
> 
> ----- Original Message -----
> From: Giri Rajasekhar Saladi <girirs@netlab.hcltech.com>
> To: ding <dingwh@huawei.com>
> Cc: <megaco@ietf.org>
> Sent: Wednesday, April 10, 2002 6:18 PM
> Subject: Re: [Megaco] use of EventBufferDescriptor
> 
> > Hi Ding,
> > My answer is inline.
> >
> > > ding wrote:
> > >
> > > hi,
> > >
> > > suppose MG receives a EventBufferDescriptor and a EventDescriptor at the same
> > > time, and MG's event buffer queue(FIFO queue) is empty. now if some user event
> >
> > We search for the event against EventBufferDescriptor only if EventBufferControl
> > is LockStep mode and EventsDescriptor is not active.
> >
> > > is recognized in the EventBufferDescriptor(and not recognized in the
> > > EventDescriptor), should MG discard the user event or send it to the FIFO
> > > queue?
> >
> > So, if EventBufferControl is LockStep mode &&
> >                  EventsDescriptor is not active &&
> >                       event is found in EventBufferDescriptor
> >     then
> >        send it to the FIFO queue.
> >
> > >
> > > I think it should be discarded, am i right?
> > >
> > > thanks.
> >
> > Regds.,
> > Giri
> >
> > --
> >
> > 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 Extn. 233
> > 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
> 
> _______________________________________________
> 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 Extn. 233
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  Thu Apr 11 13:04: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 NAA06150
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 13:04:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24817;
	Thu, 11 Apr 2002 11:52:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24782
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 11:52:06 -0400 (EDT)
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 LAA03984
	for <megaco@ietf.org>; Thu, 11 Apr 2002 11:52:01 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3BFq2019910;
	Thu, 11 Apr 2002 11:52:03 -0400 (EDT)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA26189;
	Thu, 11 Apr 2002 11:52:45 -0400 (EDT)
Message-ID: <3CB5B12E.D31A365D@lucent.com>
Date: Thu, 11 Apr 2002 11:52:15 -0400
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: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Subject: Re: [Megaco] FW: Disabling all Events
References: <4D79C746863DD51197690002A52CDA0001E8A2BE@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------7C272BBB63EDA05E62A8A0C1"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------7C272BBB63EDA05E62A8A0C1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

This was discussed and the syntax was changed through the implementors guide to
this form rather than an empty {}.  The issue was avoiding the need for a
RequestID when no real event is being specified.  The alternative would have
been
    Events = 1234 {}
But since there would be no event to tigger a notify it seems pointless to
allocate the id.  Allowing
    Event {}
with no '=' would be too much of a deviation in form

Tom-PT Taylor wrote:

> I'm surprised no one has brought this up before, though I have the vaguest
> memory of a discussion a couple of years ago in which I favoured this
> syntax.  (Whether I did or not, it looks a bit irregular to me now.)  It
> certainly appears that you are right, but perhaps it is an item for an
> Implementor's Guide correction in the syntax to allow the empty braces.
>
> -----Original Message-----
> From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> Sent: Wednesday, April 10, 2002 2:13 PM
> To: megaco@ietf.org
> Cc: Sudhir (E-mail)
> Subject: [Megaco] FW: Disabling all Events
>
> Tom,
> Can you reply for this doubt.
> Thanks,
> Sudhir
>
> -----Original Message-----
> From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> Sent: Wednesday, April 10, 2002 4:44 PM
> To: megaco@ietf.org
> Cc: Sudhir (E-mail)
> Subject: Disabling all Events
>
> Hi,
>
> Is MGC can send the following packet to disable all Events that were
> previously
> activated:
>
> Transaction = 1 {
>        Context = - {
>            Modify = TermA {
>                Events             ; just events token
>         }
>     }
> }
>
> Is the above packet is a valid. As far as syntax is considered, it is valid.
>
> As far as I know, just Events token will be used by MG as a reply to
> AuditValue Transaction if no Event(s) were activated.
>
> 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

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------7C272BBB63EDA05E62A8A0C1
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------7C272BBB63EDA05E62A8A0C1--


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


From daemon@optimus.ietf.org  Thu Apr 11 13:04: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 NAA06162
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 13:04:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA00235
	for megaco-archive@odin.ietf.org; Thu, 11 Apr 2002 13:04:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24817;
	Thu, 11 Apr 2002 11:52:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24782
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 11:52:06 -0400 (EDT)
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 LAA03984
	for <megaco@ietf.org>; Thu, 11 Apr 2002 11:52:01 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3BFq2019910;
	Thu, 11 Apr 2002 11:52:03 -0400 (EDT)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA26189;
	Thu, 11 Apr 2002 11:52:45 -0400 (EDT)
Message-ID: <3CB5B12E.D31A365D@lucent.com>
Date: Thu, 11 Apr 2002 11:52:15 -0400
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: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'sudhirk@future.futsoft.com'" <sudhirk@future.futsoft.com>,
        megaco@ietf.org
Subject: Re: [Megaco] FW: Disabling all Events
References: <4D79C746863DD51197690002A52CDA0001E8A2BE@zcard0kc.ca.nortel.com>
Content-Type: multipart/mixed;
 boundary="------------7C272BBB63EDA05E62A8A0C1"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------7C272BBB63EDA05E62A8A0C1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

This was discussed and the syntax was changed through the implementors guide to
this form rather than an empty {}.  The issue was avoiding the need for a
RequestID when no real event is being specified.  The alternative would have
been
    Events = 1234 {}
But since there would be no event to tigger a notify it seems pointless to
allocate the id.  Allowing
    Event {}
with no '=' would be too much of a deviation in form

Tom-PT Taylor wrote:

> I'm surprised no one has brought this up before, though I have the vaguest
> memory of a discussion a couple of years ago in which I favoured this
> syntax.  (Whether I did or not, it looks a bit irregular to me now.)  It
> certainly appears that you are right, but perhaps it is an item for an
> Implementor's Guide correction in the syntax to allow the empty braces.
>
> -----Original Message-----
> From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> Sent: Wednesday, April 10, 2002 2:13 PM
> To: megaco@ietf.org
> Cc: Sudhir (E-mail)
> Subject: [Megaco] FW: Disabling all Events
>
> Tom,
> Can you reply for this doubt.
> Thanks,
> Sudhir
>
> -----Original Message-----
> From: Sudhir Kumar Appana [mailto:sudhirk@future.futsoft.com]
> Sent: Wednesday, April 10, 2002 4:44 PM
> To: megaco@ietf.org
> Cc: Sudhir (E-mail)
> Subject: Disabling all Events
>
> Hi,
>
> Is MGC can send the following packet to disable all Events that were
> previously
> activated:
>
> Transaction = 1 {
>        Context = - {
>            Modify = TermA {
>                Events             ; just events token
>         }
>     }
> }
>
> Is the above packet is a valid. As far as syntax is considered, it is valid.
>
> As far as I know, just Events token will be used by MG as a reply to
> AuditValue Transaction if no Event(s) were activated.
>
> 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

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------7C272BBB63EDA05E62A8A0C1
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------7C272BBB63EDA05E62A8A0C1--


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



From megaco-admin@ietf.org  Thu Apr 11 15:57: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 PAA12023
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 15:57:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA07473;
	Thu, 11 Apr 2002 15:20:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA07448
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 15:20:14 -0400 (EDT)
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 PAA10361
	for <megaco@ietf.org>; Thu, 11 Apr 2002 15:20:11 -0400 (EDT)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3BJJgE26552
	for <megaco@ietf.org>; Thu, 11 Apr 2002 15:19:42 -0400 (EDT)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id PAA21714; Thu, 11 Apr 2002 15:19:39 -0400 (EDT)
Cc: megaco@ietf.org
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id PAA21686; Thu, 11 Apr 2002 15:19:36 -0400 (EDT)
Message-ID: <3CB5E1C9.2CBD4EC6@bell-labs.com>
Date: Thu, 11 Apr 2002 15:19:37 -0400
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] FW: Disabling all Events
References: <4D79C746863DD51197690002A52CDA0001E8A2BE@zcard0kc.ca.nortel.com> <3CB5B12E.D31A365D@lucent.com>
Content-Type: multipart/mixed;
 boundary="------------779169E65B16F79978D2F9F8"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------779169E65B16F79978D2F9F8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Terry L Anderson wrote:
> 
> This was discussed and the syntax was changed through the implementors guide to
> this form rather than an empty {}.  The issue was avoiding the need for a
> RequestID when no real event is being specified.  The alternative would have
> been
>     Events = 1234 {}
> But since there would be no event to tigger a notify it seems pointless to
> allocate the id.  Allowing
>     Event {}
> with no '=' would be too much of a deviation in form


Terry,

This reminds me...
Last June I pointed out that the change to which you are
referring (IG 6.79) broke the ABNF in a fairly serious way.

Here's an example.  The EventsToken below could be
one of two things.

MEGACO/1 [135.114.123.123]:1234
Reply = 5000 {
  Context = 1 {
    Add = t1 {
      Events    ; this could be an empty eventsDescriptor
                ; OR an auditItem
    }
  }
}


Last October, at your suggestion, I tried to revive the
thread, but no one responded.  Below I am attaching the 
last post on the subject.

-troy
--------------779169E65B16F79978D2F9F8
Content-Type: message/rfc822
Content-Disposition: inline

Message-ID: <3BC3287B.D2E6E4E4@lucent.com>
Date: Tue, 09 Oct 2001 12:40:27 -0400
From: Troy Cauble <troy@lucent.com>
Reply-To: 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: "Rosen, Brian" <Brian.Rosen@marconi.com>,
 	Tom-PT Taylor <taylor@nortelnetworks.com>,
 	"'tla@lucent.com'" <tla@lucent.com>, MEGACO list <megaco@ietf.org>
Subject: Re: IG 6.79 "Cancelling Event Detection" breaks ABNF
References: <4FBEA8857476D311A03300204840E1CF0446551E@whq-msgusr-02.pit.comms.marconi.com> <3B20ECFC.A8C1F9BC@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Greetings,

This old thread had some fairly serious problems that were never
resolved.  I am proposing changes for the problems in the text
encoding.  There is a larger issue to the ASN.1 problems -- I
will start another thread for that.


BACKGROUND

I'm told that auditItem's use in auditReturnParameter is to
represent empty descriptors.

   auditReturnParameter = (mediaDescriptor / modemDescriptor /
                           muxDescriptor / eventsDescriptor /
                           signalsDescriptor / digitMapDescriptor /
                     observedEventsDescriptor / eventBufferDescriptor /
                           statisticsDescriptor / packagesDescriptor /
                            errorDescriptor / auditItem )

   auditItem            = ( MuxToken / ModemToken / MediaToken /
                           SignalsToken / EventBufferToken /
                           DigitMapToken / StatsToken / EventsToken /
                           ObservedEventsToken / PackagesToken )

But some of the descriptors in auditReturnParameter already have
empty forms.  This is the crux of problems #1, #2 (text) and #4 below.


PROPOSED CHANGES that fix #1, #2 (text) and #4 below

   signalsDescriptor    = SignalsToken [ LBRKT signalParm
                          *(COMMA signalParm) RBRKT ]

   auditReturnParameter = (mediaDescriptor / modemDescriptor /
                           muxDescriptor / eventsDescriptor /
                           signalsDescriptor / digitMapDescriptor /
                     observedEventsDescriptor / eventBufferDescriptor /
                           statisticsDescriptor / packagesDescriptor /
                            errorDescriptor / auditReturnItem )

   auditReturnItem      = ( MuxToken / ModemToken / MediaToken /
                           DigitMapToken / StatsToken /
                           ObservedEventsToken / PackagesToken )

   auditItem            = ( auditReturnItem / SignalsToken /
                           EventBufferToken / EventsToken )


An alternative approach would be to create empty forms for
the other 7 descriptors represented by auditItem and remove
the auditItem from auditReturnParameter.  But then those 
empty forms could be used elsewhere (ammParameter, notifyRequest) 
where they're apparantly not needed.

-troy



Troy Cauble wrote:
> 
> A summary of the problems discussed in this thread.
> 
> 1) In the text encoding, some empty descriptors have the form
>    "Signals {}" while others have "Events".
> 
> In a Termination Audit:
> 
> 2) There are two line encodings for an empty Signals descriptor
>    (text and ASN.1).
> 
> 3) There are two line encodings each for an empty Events descriptor
>    or Event Buffer descriptor (ASN.1 only).
> 
> 4) In the text encoding, EventsToken and EventBufferToken each
>    have reduce/reduce conflicts because they can represent either
>    an auditItem token or an empty descriptor in the auditReturnParameter.
> 
> -troy
> 
> 
> 
> "Rosen, Brian" wrote:
> >
> > I agree with Tom; we did a pass over the ABNF to try to make
> > all of the empty forms not have braces.  The choice was
> > completely arbitrary, and as I recall, we decided since it
> > didn't make any real difference, shorter was better.
> > If we missed one, we goofed.
> >
> > Tom, the problem here seems to be real.  As Troy says, you will get
> > a reduce conflict in a rules-based parser with this ambiguity.
> > I'm pretty sure you can ignore the problem, but it's poor design
> > practice.  You will recall all of the effort Abdallah and Nancy
> > went through to test out these kinds of things as we developed
> > the ABNF.  The IG change wasn't verified in the same way, thus
> > we have this problem.  We need to decide what to do.
> >
> > Brian
> >
> > > > Tom-PT Taylor wrote:
> > > >
> > > > I'm the one responsible for all this.  I suppose I should
> > > dig up the thread.
> > > > Anyway, the intention was definitiely to provide a way of
> > > signalling empty
> > > > descriptors.  I think we chose rather arbitrarily between
> > > the desc{} and desc
> > > > form, opting for the latter.
> > >

--------------779169E65B16F79978D2F9F8--


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


From daemon@optimus.ietf.org  Thu Apr 11 16:54: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 PAA12033
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 15:57:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA09447
	for megaco-archive@odin.ietf.org; Thu, 11 Apr 2002 15:57:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA07473;
	Thu, 11 Apr 2002 15:20:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA07448
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 15:20:14 -0400 (EDT)
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 PAA10361
	for <megaco@ietf.org>; Thu, 11 Apr 2002 15:20:11 -0400 (EDT)
Received: from wink.ho.lucent.com (h135-17-38-3.lucent.com [135.17.38.3])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3BJJgE26552
	for <megaco@ietf.org>; Thu, 11 Apr 2002 15:19:42 -0400 (EDT)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id PAA21714; Thu, 11 Apr 2002 15:19:39 -0400 (EDT)
Cc: megaco@ietf.org
Received: from bell-labs.com by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id PAA21686; Thu, 11 Apr 2002 15:19:36 -0400 (EDT)
Message-ID: <3CB5E1C9.2CBD4EC6@bell-labs.com>
Date: Thu, 11 Apr 2002 15:19:37 -0400
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] FW: Disabling all Events
References: <4D79C746863DD51197690002A52CDA0001E8A2BE@zcard0kc.ca.nortel.com> <3CB5B12E.D31A365D@lucent.com>
Content-Type: multipart/mixed;
 boundary="------------779169E65B16F79978D2F9F8"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------779169E65B16F79978D2F9F8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Terry L Anderson wrote:
> 
> This was discussed and the syntax was changed through the implementors guide to
> this form rather than an empty {}.  The issue was avoiding the need for a
> RequestID when no real event is being specified.  The alternative would have
> been
>     Events = 1234 {}
> But since there would be no event to tigger a notify it seems pointless to
> allocate the id.  Allowing
>     Event {}
> with no '=' would be too much of a deviation in form


Terry,

This reminds me...
Last June I pointed out that the change to which you are
referring (IG 6.79) broke the ABNF in a fairly serious way.

Here's an example.  The EventsToken below could be
one of two things.

MEGACO/1 [135.114.123.123]:1234
Reply = 5000 {
  Context = 1 {
    Add = t1 {
      Events    ; this could be an empty eventsDescriptor
                ; OR an auditItem
    }
  }
}


Last October, at your suggestion, I tried to revive the
thread, but no one responded.  Below I am attaching the 
last post on the subject.

-troy
--------------779169E65B16F79978D2F9F8
Content-Type: message/rfc822
Content-Disposition: inline

Message-ID: <3BC3287B.D2E6E4E4@lucent.com>
Date: Tue, 09 Oct 2001 12:40:27 -0400
From: Troy Cauble <troy@lucent.com>
Reply-To: 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: "Rosen, Brian" <Brian.Rosen@marconi.com>,
 	Tom-PT Taylor <taylor@nortelnetworks.com>,
 	"'tla@lucent.com'" <tla@lucent.com>, MEGACO list <megaco@ietf.org>
Subject: Re: IG 6.79 "Cancelling Event Detection" breaks ABNF
References: <4FBEA8857476D311A03300204840E1CF0446551E@whq-msgusr-02.pit.comms.marconi.com> <3B20ECFC.A8C1F9BC@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Greetings,

This old thread had some fairly serious problems that were never
resolved.  I am proposing changes for the problems in the text
encoding.  There is a larger issue to the ASN.1 problems -- I
will start another thread for that.


BACKGROUND

I'm told that auditItem's use in auditReturnParameter is to
represent empty descriptors.

   auditReturnParameter = (mediaDescriptor / modemDescriptor /
                           muxDescriptor / eventsDescriptor /
                           signalsDescriptor / digitMapDescriptor /
                     observedEventsDescriptor / eventBufferDescriptor /
                           statisticsDescriptor / packagesDescriptor /
                            errorDescriptor / auditItem )

   auditItem            = ( MuxToken / ModemToken / MediaToken /
                           SignalsToken / EventBufferToken /
                           DigitMapToken / StatsToken / EventsToken /
                           ObservedEventsToken / PackagesToken )

But some of the descriptors in auditReturnParameter already have
empty forms.  This is the crux of problems #1, #2 (text) and #4 below.


PROPOSED CHANGES that fix #1, #2 (text) and #4 below

   signalsDescriptor    = SignalsToken [ LBRKT signalParm
                          *(COMMA signalParm) RBRKT ]

   auditReturnParameter = (mediaDescriptor / modemDescriptor /
                           muxDescriptor / eventsDescriptor /
                           signalsDescriptor / digitMapDescriptor /
                     observedEventsDescriptor / eventBufferDescriptor /
                           statisticsDescriptor / packagesDescriptor /
                            errorDescriptor / auditReturnItem )

   auditReturnItem      = ( MuxToken / ModemToken / MediaToken /
                           DigitMapToken / StatsToken /
                           ObservedEventsToken / PackagesToken )

   auditItem            = ( auditReturnItem / SignalsToken /
                           EventBufferToken / EventsToken )


An alternative approach would be to create empty forms for
the other 7 descriptors represented by auditItem and remove
the auditItem from auditReturnParameter.  But then those 
empty forms could be used elsewhere (ammParameter, notifyRequest) 
where they're apparantly not needed.

-troy



Troy Cauble wrote:
> 
> A summary of the problems discussed in this thread.
> 
> 1) In the text encoding, some empty descriptors have the form
>    "Signals {}" while others have "Events".
> 
> In a Termination Audit:
> 
> 2) There are two line encodings for an empty Signals descriptor
>    (text and ASN.1).
> 
> 3) There are two line encodings each for an empty Events descriptor
>    or Event Buffer descriptor (ASN.1 only).
> 
> 4) In the text encoding, EventsToken and EventBufferToken each
>    have reduce/reduce conflicts because they can represent either
>    an auditItem token or an empty descriptor in the auditReturnParameter.
> 
> -troy
> 
> 
> 
> "Rosen, Brian" wrote:
> >
> > I agree with Tom; we did a pass over the ABNF to try to make
> > all of the empty forms not have braces.  The choice was
> > completely arbitrary, and as I recall, we decided since it
> > didn't make any real difference, shorter was better.
> > If we missed one, we goofed.
> >
> > Tom, the problem here seems to be real.  As Troy says, you will get
> > a reduce conflict in a rules-based parser with this ambiguity.
> > I'm pretty sure you can ignore the problem, but it's poor design
> > practice.  You will recall all of the effort Abdallah and Nancy
> > went through to test out these kinds of things as we developed
> > the ABNF.  The IG change wasn't verified in the same way, thus
> > we have this problem.  We need to decide what to do.
> >
> > Brian
> >
> > > > Tom-PT Taylor wrote:
> > > >
> > > > I'm the one responsible for all this.  I suppose I should
> > > dig up the thread.
> > > > Anyway, the intention was definitiely to provide a way of
> > > signalling empty
> > > > descriptors.  I think we chose rather arbitrarily between
> > > the desc{} and desc
> > > > form, opting for the latter.
> > >

--------------779169E65B16F79978D2F9F8--


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



From megaco-admin@ietf.org  Thu Apr 11 20: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 UAA20892
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 20:12:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA24486;
	Thu, 11 Apr 2002 19:21:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA24459
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 19:21:17 -0400 (EDT)
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 TAA19821
	for <megaco@ietf.org>; Thu, 11 Apr 2002 19:21:14 -0400 (EDT)
Message-ID: <20020411232115.42364.qmail@web12604.mail.yahoo.com>
Received: from [203.26.41.49] by web12604.mail.yahoo.com via HTTP; Thu, 11 Apr 2002 16:21:15 PDT
Date: Thu, 11 Apr 2002 16:21:15 -0700 (PDT)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] stream
Sender: megaco-admin@ietf.org
Errors-To: 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 are two questions:

1. If a MGC issues a move request, should the MGC
issue the stream inactive command first before moving
a termination or a single MOVE request does both?

2. If in a peer connection mode, both terminations are
moved out the context, should the stream still stay
the context until an explicitly delete command or
should the stream automatically deleted is there is no
terminations connected?

Thank you.
 

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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


From daemon@optimus.ietf.org  Thu Apr 11 20: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 UAA20903
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 20:12:37 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA27179
	for megaco-archive@odin.ietf.org; Thu, 11 Apr 2002 20:12:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA24486;
	Thu, 11 Apr 2002 19:21:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA24459
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 19:21:17 -0400 (EDT)
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 TAA19821
	for <megaco@ietf.org>; Thu, 11 Apr 2002 19:21:14 -0400 (EDT)
Message-ID: <20020411232115.42364.qmail@web12604.mail.yahoo.com>
Received: from [203.26.41.49] by web12604.mail.yahoo.com via HTTP; Thu, 11 Apr 2002 16:21:15 PDT
Date: Thu, 11 Apr 2002 16:21:15 -0700 (PDT)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] stream
Sender: megaco-admin@ietf.org
Errors-To: 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 are two questions:

1. If a MGC issues a move request, should the MGC
issue the stream inactive command first before moving
a termination or a single MOVE request does both?

2. If in a peer connection mode, both terminations are
moved out the context, should the stream still stay
the context until an explicitly delete command or
should the stream automatically deleted is there is no
terminations connected?

Thank you.
 

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From megaco-admin@ietf.org  Thu Apr 11 22:28: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 WAA02843
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 22:28:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01862;
	Thu, 11 Apr 2002 21:47:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01780
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 21:47:29 -0400 (EDT)
Received: from web12603.mail.yahoo.com (web12603.mail.yahoo.com [216.136.173.226])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA28353
	for <megaco@ietf.org>; Thu, 11 Apr 2002 21:47:24 -0400 (EDT)
Message-ID: <20020412014726.94803.qmail@web12603.mail.yahoo.com>
Received: from [203.26.41.49] by web12603.mail.yahoo.com via HTTP; Thu, 11 Apr 2002 18:47:26 PDT
Date: Thu, 11 Apr 2002 18:47:26 -0700 (PDT)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] stream
Sender: megaco-admin@ietf.org
Errors-To: 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,

Sorry, the previous message was pasted and posted
incompletely. Let me try again:

The spec says there are max 2 terminations in a
point-to-point connection context. In a multiplexing
termination context (such as H223), should there be
another termination for the mux in the context? 

         Context 1
    ------------------------
    | T1 ---- MUX ----- T2 |
    ------------------------

If the T1 and T2 are connected by a stream #1. When
the T1 is moved out of C1, should the stream #1 be
deleted or should the stream #1 still stay within the
C1?

If both the T1 and T2 are moved out of C1, should the
C1 be destroyed automatically or should the C1 be
waiting until the MUX termination is requested to be
deleted by the MGC?

Thank you.

At 04:21 PM 11/04/2002 -0700, you wrote:
There are two questions:

1. If a MGC issues a move request, should the MGC
issue the stream inactive command first before moving
a termination or a single MOVE request does both?

2. If in a peer connection mode, both terminations are
moved out the context, should the stream still stay
the context until an explicitly delete command or
should the stream automatically deleted is there is no
terminations connected?

Thank you.
 

__________________________________________________


__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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


From daemon@optimus.ietf.org  Thu Apr 11 22:28: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 WAA02855
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 22:28:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA03577
	for megaco-archive@odin.ietf.org; Thu, 11 Apr 2002 22:28:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01862;
	Thu, 11 Apr 2002 21:47:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01780
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 21:47:29 -0400 (EDT)
Received: from web12603.mail.yahoo.com (web12603.mail.yahoo.com [216.136.173.226])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA28353
	for <megaco@ietf.org>; Thu, 11 Apr 2002 21:47:24 -0400 (EDT)
Message-ID: <20020412014726.94803.qmail@web12603.mail.yahoo.com>
Received: from [203.26.41.49] by web12603.mail.yahoo.com via HTTP; Thu, 11 Apr 2002 18:47:26 PDT
Date: Thu, 11 Apr 2002 18:47:26 -0700 (PDT)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] stream
Sender: megaco-admin@ietf.org
Errors-To: 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,

Sorry, the previous message was pasted and posted
incompletely. Let me try again:

The spec says there are max 2 terminations in a
point-to-point connection context. In a multiplexing
termination context (such as H223), should there be
another termination for the mux in the context? 

         Context 1
    ------------------------
    | T1 ---- MUX ----- T2 |
    ------------------------

If the T1 and T2 are connected by a stream #1. When
the T1 is moved out of C1, should the stream #1 be
deleted or should the stream #1 still stay within the
C1?

If both the T1 and T2 are moved out of C1, should the
C1 be destroyed automatically or should the C1 be
waiting until the MUX termination is requested to be
deleted by the MGC?

Thank you.

At 04:21 PM 11/04/2002 -0700, you wrote:
There are two questions:

1. If a MGC issues a move request, should the MGC
issue the stream inactive command first before moving
a termination or a single MOVE request does both?

2. If in a peer connection mode, both terminations are
moved out the context, should the stream still stay
the context until an explicitly delete command or
should the stream automatically deleted is there is no
terminations connected?

Thank you.
 

__________________________________________________


__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From megaco-admin@ietf.org  Thu Apr 11 23:16: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 XAA09378
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 23:16:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04521;
	Thu, 11 Apr 2002 22:42:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04494
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 22:42:45 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05735
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:42:41 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3C2gDS09217
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:42:13 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2WJANAZN>; Thu, 11 Apr 2002 22:42:14 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2DD@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] stream
Date: Thu, 11 Apr 2002 22:42:12 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Hi.

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 11, 2002 7:21 PM
To: megaco@ietf.org
Subject: [Megaco] stream


There are two questions:

1. If a MGC issues a move request, should the MGC
issue the stream inactive command first before moving
a termination or a single MOVE request does both?

[PTT]
The MOVE itself simply moves the termination from one context to another.
It does nothing with the streams.  The MGC should include a Media Descriptor
with the necessaryu properties if something has to change.

2. If in a peer connection mode, both terminations are
moved out the context, should the stream still stay
the context until an explicitly delete command or
should the stream automatically deleted is there is no
terminations connected?

[PTT] If all terminations are moved out of a context the context is
destroyed automatically.

Thank you.
 

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.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@optimus.ietf.org  Thu Apr 11 23:16: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 XAA09392
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 23:16:01 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA05798
	for megaco-archive@odin.ietf.org; Thu, 11 Apr 2002 23:16:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04521;
	Thu, 11 Apr 2002 22:42:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04494
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 22:42:45 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05735
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:42:41 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3C2gDS09217
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:42:13 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2WJANAZN>; Thu, 11 Apr 2002 22:42:14 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2DD@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] stream
Date: Thu, 11 Apr 2002 22:42:12 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Hi.

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 11, 2002 7:21 PM
To: megaco@ietf.org
Subject: [Megaco] stream


There are two questions:

1. If a MGC issues a move request, should the MGC
issue the stream inactive command first before moving
a termination or a single MOVE request does both?

[PTT]
The MOVE itself simply moves the termination from one context to another.
It does nothing with the streams.  The MGC should include a Media Descriptor
with the necessaryu properties if something has to change.

2. If in a peer connection mode, both terminations are
moved out the context, should the stream still stay
the context until an explicitly delete command or
should the stream automatically deleted is there is no
terminations connected?

[PTT] If all terminations are moved out of a context the context is
destroyed automatically.

Thank you.
 

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.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  Thu Apr 11 23:25: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 XAA10414
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 23:25:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04806;
	Thu, 11 Apr 2002 22:55:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04775
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 22:55:51 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06923
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:55:48 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3C2tKS09499
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:55:20 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2WJANA6F>; Thu, 11 Apr 2002 22:55:21 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2DE@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] stream
Date: Thu, 11 Apr 2002 22:55:20 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Oh, well, should have read this one first :-}

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 11, 2002 9:47 PM
To: megaco@ietf.org
Subject: [Megaco] stream


Hi,

Sorry, the previous message was pasted and posted
incompletely. Let me try again:

The spec says there are max 2 terminations in a
point-to-point connection context. In a multiplexing
termination context (such as H223), should there be
another termination for the mux in the context? 

         Context 1
    ------------------------
    | T1 ---- MUX ----- T2 |
    ------------------------

[PTT]
Yes.  But multiplexing is a property of a termination, not a context.
Introducing a multiplex creates asymmetry: the termination(s) feeding into
the multiplex are hidden from the other terminations in the context.  The
"centre" of the context, where the bridging is done, lies between the MUX
and the terminations that do not feed into it (are not listed in the
Multiplex Descriptor).

If the T1 and T2 are connected by a stream #1. When
the T1 is moved out of C1, should the stream #1 be
deleted or should the stream #1 still stay within the
C1?

[PTT]
I assume you mean in the above diagram.  If you mean in general, then a
stream is present in a context until no terminations support that stream.
In the above diagram, if T1 feeds into the multiplex, then the stream it
supports is visible only to the multiplex.  It is a different stream 1 that
runs between the multiplex and the other terminations in the context.

If both the T1 and T2 are moved out of C1, should the
C1 be destroyed automatically or should the C1 be
waiting until the MUX termination is requested to be
deleted by the MGC?

[PTT]
Again assuming that T1 is the termination listed in the Multiplex
Descriptor, it would be an error to move it out before modifying the MUX
termination to remove it from the Multiplex Descriptor.  (We may need to
define a suitable error code.)  Assuming that condition is met, the context
continues to exist until the MUX termination is deleted.  The MUX
termination would be a bit strange, with no supporting terminations to
provide any media, but I think  this is the logical approach.

Thank you.

At 04:21 PM 11/04/2002 -0700, you wrote:
There are two questions:

1. If a MGC issues a move request, should the MGC
issue the stream inactive command first before moving
a termination or a single MOVE request does both?

2. If in a peer connection mode, both terminations are
moved out the context, should the stream still stay
the context until an explicitly delete command or
should the stream automatically deleted is there is no
terminations connected?

Thank you.
 

__________________________________________________


__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.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@optimus.ietf.org  Thu Apr 11 23:25: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 XAA10424
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 23:25:14 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA06049
	for megaco-archive@odin.ietf.org; Thu, 11 Apr 2002 23:25:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04806;
	Thu, 11 Apr 2002 22:55:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04775
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 22:55:51 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06923
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:55:48 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3C2tKS09499
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:55:20 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2WJANA6F>; Thu, 11 Apr 2002 22:55:21 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2DE@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Subject: RE: [Megaco] stream
Date: Thu, 11 Apr 2002 22:55:20 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Oh, well, should have read this one first :-}

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 11, 2002 9:47 PM
To: megaco@ietf.org
Subject: [Megaco] stream


Hi,

Sorry, the previous message was pasted and posted
incompletely. Let me try again:

The spec says there are max 2 terminations in a
point-to-point connection context. In a multiplexing
termination context (such as H223), should there be
another termination for the mux in the context? 

         Context 1
    ------------------------
    | T1 ---- MUX ----- T2 |
    ------------------------

[PTT]
Yes.  But multiplexing is a property of a termination, not a context.
Introducing a multiplex creates asymmetry: the termination(s) feeding into
the multiplex are hidden from the other terminations in the context.  The
"centre" of the context, where the bridging is done, lies between the MUX
and the terminations that do not feed into it (are not listed in the
Multiplex Descriptor).

If the T1 and T2 are connected by a stream #1. When
the T1 is moved out of C1, should the stream #1 be
deleted or should the stream #1 still stay within the
C1?

[PTT]
I assume you mean in the above diagram.  If you mean in general, then a
stream is present in a context until no terminations support that stream.
In the above diagram, if T1 feeds into the multiplex, then the stream it
supports is visible only to the multiplex.  It is a different stream 1 that
runs between the multiplex and the other terminations in the context.

If both the T1 and T2 are moved out of C1, should the
C1 be destroyed automatically or should the C1 be
waiting until the MUX termination is requested to be
deleted by the MGC?

[PTT]
Again assuming that T1 is the termination listed in the Multiplex
Descriptor, it would be an error to move it out before modifying the MUX
termination to remove it from the Multiplex Descriptor.  (We may need to
define a suitable error code.)  Assuming that condition is met, the context
continues to exist until the MUX termination is deleted.  The MUX
termination would be a bit strange, with no supporting terminations to
provide any media, but I think  this is the logical approach.

Thank you.

At 04:21 PM 11/04/2002 -0700, you wrote:
There are two questions:

1. If a MGC issues a move request, should the MGC
issue the stream inactive command first before moving
a termination or a single MOVE request does both?

2. If in a peer connection mode, both terminations are
moved out the context, should the stream still stay
the context until an explicitly delete command or
should the stream automatically deleted is there is no
terminations connected?

Thank you.
 

__________________________________________________


__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.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  Thu Apr 11 23:33: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 XAA11612
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 23:33:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04883;
	Thu, 11 Apr 2002 22:58:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04852
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 22:58:29 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07176
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:58:26 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3C2vwS09531
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:57:58 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2WJANA64>; Thu, 11 Apr 2002 22:57:59 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2DF@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Troy Cauble'" <troy@bell-labs.com>, Terry L Anderson <tla@lucent.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] FW: Disabling all Events
Date: Thu, 11 Apr 2002 22:57:58 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Yes, I remember now, and I'm guilty of not following through.  Brian Rosen
is the only one I remember responding.

-----Original Message-----
From: Troy Cauble [mailto:troy@bell-labs.com]
Sent: Thursday, April 11, 2002 3:20 PM
To: Terry L Anderson
Cc: megaco@ietf.org
Subject: Re: [Megaco] FW: Disabling all Events


Terry L Anderson wrote:
> 
> This was discussed and the syntax was changed through the implementors
guide to
> this form rather than an empty {}.  The issue was avoiding the need for a
> RequestID when no real event is being specified.  The alternative would
have
> been
>     Events = 1234 {}
> But since there would be no event to tigger a notify it seems pointless to
> allocate the id.  Allowing
>     Event {}
> with no '=' would be too much of a deviation in form


Terry,

This reminds me...
Last June I pointed out that the change to which you are
referring (IG 6.79) broke the ABNF in a fairly serious way.

Here's an example.  The EventsToken below could be
one of two things.

MEGACO/1 [135.114.123.123]:1234
Reply = 5000 {
  Context = 1 {
    Add = t1 {
      Events    ; this could be an empty eventsDescriptor
                ; OR an auditItem
    }
  }
}


Last October, at your suggestion, I tried to revive the
thread, but no one responded.  Below I am attaching the 
last post on the subject.

-troy

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


From daemon@optimus.ietf.org  Thu Apr 11 23:33: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 XAA11627
	for <megaco-archive@odin.ietf.org>; Thu, 11 Apr 2002 23:33:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA06752
	for megaco-archive@odin.ietf.org; Thu, 11 Apr 2002 23:33:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04883;
	Thu, 11 Apr 2002 22:58:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04852
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 22:58:29 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07176
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:58:26 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3C2vwS09531
	for <megaco@ietf.org>; Thu, 11 Apr 2002 22:57:58 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2WJANA64>; Thu, 11 Apr 2002 22:57:59 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2DF@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Troy Cauble'" <troy@bell-labs.com>, Terry L Anderson <tla@lucent.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] FW: Disabling all Events
Date: Thu, 11 Apr 2002 22:57:58 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Yes, I remember now, and I'm guilty of not following through.  Brian Rosen
is the only one I remember responding.

-----Original Message-----
From: Troy Cauble [mailto:troy@bell-labs.com]
Sent: Thursday, April 11, 2002 3:20 PM
To: Terry L Anderson
Cc: megaco@ietf.org
Subject: Re: [Megaco] FW: Disabling all Events


Terry L Anderson wrote:
> 
> This was discussed and the syntax was changed through the implementors
guide to
> this form rather than an empty {}.  The issue was avoiding the need for a
> RequestID when no real event is being specified.  The alternative would
have
> been
>     Events = 1234 {}
> But since there would be no event to tigger a notify it seems pointless to
> allocate the id.  Allowing
>     Event {}
> with no '=' would be too much of a deviation in form


Terry,

This reminds me...
Last June I pointed out that the change to which you are
referring (IG 6.79) broke the ABNF in a fairly serious way.

Here's an example.  The EventsToken below could be
one of two things.

MEGACO/1 [135.114.123.123]:1234
Reply = 5000 {
  Context = 1 {
    Add = t1 {
      Events    ; this could be an empty eventsDescriptor
                ; OR an auditItem
    }
  }
}


Last October, at your suggestion, I tried to revive the
thread, but no one responded.  Below I am attaching the 
last post on the subject.

-troy

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



From megaco-admin@ietf.org  Fri Apr 12 00:21: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 AAA17359
	for <megaco-archive@odin.ietf.org>; Fri, 12 Apr 2002 00:21:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA06861;
	Thu, 11 Apr 2002 23:34:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA06832
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 23:34:34 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11706
	for <megaco@ietf.org>; Thu, 11 Apr 2002 23:34:29 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUFR4800.959 for
          <megaco@ietf.org>; Fri, 12 Apr 2002 11:31:20 +0800 
Message-ID: <000a01c1e1d3$017b6e60$26280b0a@huawei.com.cn>
From: "Watson Ding" <dingwh@huawei.com>
To: <megaco@ietf.org>
Date: Fri, 12 Apr 2002 11:34:51 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C1E216.0F7D1CA0"
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
Subject: [Megaco] use of EPCF in MGCP
Sender: megaco-admin@ietf.org
Errors-To: 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_0007_01C1E216.0F7D1CA0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

aGksDQoNCmFueSBvbmUga25vdyB0aGUgdXNlIG9mIEVQQ0YgY29tbWFuZCBpbiBNR0NQPw0KDQp0
aGFua3MNCg0KV2F0c29uIERpbmcuDQo=

------=_NextPart_000_0007_01C1E216.0F7D1CA0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5oaSw8L0ZPTlQ+PC9ESVY+
DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5hbnkgb25lIGtub3cgdGhlIHVzZSBvZiBFUENGIGNv
bW1hbmQgaW4gTUdDUD88L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPnRoYW5rczwvRElW
Pg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+V2F0c29uIERpbmcuPC9ESVY+PC9CT0RZPjwvSFRN
TD4NCg==

------=_NextPart_000_0007_01C1E216.0F7D1CA0--


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


From daemon@optimus.ietf.org  Fri Apr 12 00:21: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 AAA17369
	for <megaco-archive@odin.ietf.org>; Fri, 12 Apr 2002 00:21:22 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA08728
	for megaco-archive@odin.ietf.org; Fri, 12 Apr 2002 00:21:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA06861;
	Thu, 11 Apr 2002 23:34:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA06832
	for <megaco@optimus.ietf.org>; Thu, 11 Apr 2002 23:34:34 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11706
	for <megaco@ietf.org>; Thu, 11 Apr 2002 23:34:29 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUFR4800.959 for
          <megaco@ietf.org>; Fri, 12 Apr 2002 11:31:20 +0800 
Message-ID: <000a01c1e1d3$017b6e60$26280b0a@huawei.com.cn>
From: "Watson Ding" <dingwh@huawei.com>
To: <megaco@ietf.org>
Date: Fri, 12 Apr 2002 11:34:51 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C1E216.0F7D1CA0"
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
Subject: [Megaco] use of EPCF in MGCP
Sender: megaco-admin@ietf.org
Errors-To: 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_0007_01C1E216.0F7D1CA0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

aGksDQoNCmFueSBvbmUga25vdyB0aGUgdXNlIG9mIEVQQ0YgY29tbWFuZCBpbiBNR0NQPw0KDQp0
aGFua3MNCg0KV2F0c29uIERpbmcuDQo=

------=_NextPart_000_0007_01C1E216.0F7D1CA0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5oaSw8L0ZPTlQ+PC9ESVY+
DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5hbnkgb25lIGtub3cgdGhlIHVzZSBvZiBFUENGIGNv
bW1hbmQgaW4gTUdDUD88L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPnRoYW5rczwvRElW
Pg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+V2F0c29uIERpbmcuPC9ESVY+PC9CT0RZPjwvSFRN
TD4NCg==

------=_NextPart_000_0007_01C1E216.0F7D1CA0--


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



From megaco-admin@ietf.org  Fri Apr 12 08:31: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 IAA15326
	for <megaco-archive@odin.ietf.org>; Fri, 12 Apr 2002 08:31:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08932;
	Fri, 12 Apr 2002 07:18:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08902
	for <megaco@optimus.ietf.org>; Fri, 12 Apr 2002 07:18:12 -0400 (EDT)
Received: from web12608.mail.yahoo.com (web12608.mail.yahoo.com [216.136.173.231])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA08155
	for <megaco@ietf.org>; Fri, 12 Apr 2002 07:18:09 -0400 (EDT)
Message-ID: <20020412111810.59944.qmail@web12608.mail.yahoo.com>
Received: from [203.26.41.49] by web12608.mail.yahoo.com via HTTP; Fri, 12 Apr 2002 04:18:10 PDT
Date: Fri, 12 Apr 2002 04:18:10 -0700 (PDT)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
Cc: Tom-PT Taylor <taylor@nortelnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] stream
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Thanks Tom.

> Yes. But multiplexing is a property of a
termination,
> not a context. Introducing a multiplex creates 
> asymmetry: the termination(s) feeding into
> the multiplex are hidden from the other terminations
> in the context. The "centre" of the context, where 
> the bridging is done, lies between the MUX
> and the terminations that do not feed into it (are 
> not listed in the Multiplex Descriptor).

Question:
(a) Does a MUX termination like other terminations
have local/remote descriptors to specify the stream
properties plus a MUX Descriptor? The MGC needs to
issue three ADD Termination requests to the context
according to the following diagram (if it is correct),
one for MUX, one for T2 and one for T1, even though
the T1 is invisible to the T2, the properties of the
T1 still need to be specified in the C1, is that
correct?

(b) If several contexts contain the MUX, all those
contexts have the same MUX Termination ID? It is a
little bit strange to me, but is it correct?

Context 1
------------------------------------------------
| --------------------------                   |
| |      MUX            |                   |
| | ------  stream 1   |                   |
| | | T1 | -----(*)------ |  s1     -------- |
| | ------                 |-----(*)---| T2 | |
| --------------------------           ------  |
-----------------------------------------------       
          

> I assume you mean in the above diagram. If you mean 
> in general, then a stream is present in a context 
> until no terminations support that stream. 

Yes, I meant that diagram. If I understand above
comment correctly, it means that the stream is a
property of the context, not the property of the
termination. Move a termination (T1) out of a context
(C1) does not move the stream properties with the
Termination although that the stream descriptor is
always specified inside of the Termination. Is that
correct?

Thank you for your patience.

At 10:55 PM 11/04/2002 -0400, you wrote:
Oh, well, should have read this one first :-}

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 11, 2002 9:47 PM
To: megaco@ietf.org
Subject: [Megaco] stream


Hi,

Sorry, the previous message was pasted and posted
incompletely. Let me try again:

The spec says there are max 2 terminations in a
point-to-point connection context. In a multiplexing
termination context (such as H223), should there be
another termination for the mux in the context? 

         Context 1
    ------------------------
    | T1 ---- MUX ----- T2 |
    ------------------------

[PTT]
Yes.  But multiplexing is a property of a termination,
not a context.
Introducing a multiplex creates asymmetry: the
termination(s) feeding into
the multiplex are hidden from the other terminations
in the context.  The
"centre" of the context, where the bridging is done,
lies between the MUX
and the terminations that do not feed into it (are not
listed in the
Multiplex Descriptor).

If the T1 and T2 are connected by a stream #1. When
the T1 is moved out of C1, should the stream #1 be
deleted or should the stream #1 still stay within the
C1?

[PTT]
I assume you mean in the above diagram.  If you mean
in general, then a
stream is present in a context until no terminations
support that stream.
In the above diagram, if T1 feeds into the multiplex,
then the stream it
supports is visible only to the multiplex.  It is a
different stream 1 that
runs between the multiplex and the other terminations
in the context.

If both the T1 and T2 are moved out of C1, should the
C1 be destroyed automatically or should the C1 be
waiting until the MUX termination is requested to be
deleted by the MGC?

[PTT]
Again assuming that T1 is the termination listed in
the Multiplex
Descriptor, it would be an error to move it out before
modifying the MUX
termination to remove it from the Multiplex
Descriptor.  (We may need to
define a suitable error code.)  Assuming that
condition is met, the context
continues to exist until the MUX termination is
deleted.  The MUX
termination would be a bit strange, with no supporting
terminations to
provide any media, but I think  this is the logical
approach.

Thank you.

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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


From daemon@optimus.ietf.org  Fri Apr 12 08:31: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 IAA15335
	for <megaco-archive@odin.ietf.org>; Fri, 12 Apr 2002 08:31:56 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA12770
	for megaco-archive@odin.ietf.org; Fri, 12 Apr 2002 08:31:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08932;
	Fri, 12 Apr 2002 07:18:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08902
	for <megaco@optimus.ietf.org>; Fri, 12 Apr 2002 07:18:12 -0400 (EDT)
Received: from web12608.mail.yahoo.com (web12608.mail.yahoo.com [216.136.173.231])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA08155
	for <megaco@ietf.org>; Fri, 12 Apr 2002 07:18:09 -0400 (EDT)
Message-ID: <20020412111810.59944.qmail@web12608.mail.yahoo.com>
Received: from [203.26.41.49] by web12608.mail.yahoo.com via HTTP; Fri, 12 Apr 2002 04:18:10 PDT
Date: Fri, 12 Apr 2002 04:18:10 -0700 (PDT)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
Cc: Tom-PT Taylor <taylor@nortelnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] stream
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Thanks Tom.

> Yes. But multiplexing is a property of a
termination,
> not a context. Introducing a multiplex creates 
> asymmetry: the termination(s) feeding into
> the multiplex are hidden from the other terminations
> in the context. The "centre" of the context, where 
> the bridging is done, lies between the MUX
> and the terminations that do not feed into it (are 
> not listed in the Multiplex Descriptor).

Question:
(a) Does a MUX termination like other terminations
have local/remote descriptors to specify the stream
properties plus a MUX Descriptor? The MGC needs to
issue three ADD Termination requests to the context
according to the following diagram (if it is correct),
one for MUX, one for T2 and one for T1, even though
the T1 is invisible to the T2, the properties of the
T1 still need to be specified in the C1, is that
correct?

(b) If several contexts contain the MUX, all those
contexts have the same MUX Termination ID? It is a
little bit strange to me, but is it correct?

Context 1
------------------------------------------------
| --------------------------                   |
| |      MUX            |                   |
| | ------  stream 1   |                   |
| | | T1 | -----(*)------ |  s1     -------- |
| | ------                 |-----(*)---| T2 | |
| --------------------------           ------  |
-----------------------------------------------       
          

> I assume you mean in the above diagram. If you mean 
> in general, then a stream is present in a context 
> until no terminations support that stream. 

Yes, I meant that diagram. If I understand above
comment correctly, it means that the stream is a
property of the context, not the property of the
termination. Move a termination (T1) out of a context
(C1) does not move the stream properties with the
Termination although that the stream descriptor is
always specified inside of the Termination. Is that
correct?

Thank you for your patience.

At 10:55 PM 11/04/2002 -0400, you wrote:
Oh, well, should have read this one first :-}

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 11, 2002 9:47 PM
To: megaco@ietf.org
Subject: [Megaco] stream


Hi,

Sorry, the previous message was pasted and posted
incompletely. Let me try again:

The spec says there are max 2 terminations in a
point-to-point connection context. In a multiplexing
termination context (such as H223), should there be
another termination for the mux in the context? 

         Context 1
    ------------------------
    | T1 ---- MUX ----- T2 |
    ------------------------

[PTT]
Yes.  But multiplexing is a property of a termination,
not a context.
Introducing a multiplex creates asymmetry: the
termination(s) feeding into
the multiplex are hidden from the other terminations
in the context.  The
"centre" of the context, where the bridging is done,
lies between the MUX
and the terminations that do not feed into it (are not
listed in the
Multiplex Descriptor).

If the T1 and T2 are connected by a stream #1. When
the T1 is moved out of C1, should the stream #1 be
deleted or should the stream #1 still stay within the
C1?

[PTT]
I assume you mean in the above diagram.  If you mean
in general, then a
stream is present in a context until no terminations
support that stream.
In the above diagram, if T1 feeds into the multiplex,
then the stream it
supports is visible only to the multiplex.  It is a
different stream 1 that
runs between the multiplex and the other terminations
in the context.

If both the T1 and T2 are moved out of C1, should the
C1 be destroyed automatically or should the C1 be
waiting until the MUX termination is requested to be
deleted by the MGC?

[PTT]
Again assuming that T1 is the termination listed in
the Multiplex
Descriptor, it would be an error to move it out before
modifying the MUX
termination to remove it from the Multiplex
Descriptor.  (We may need to
define a suitable error code.)  Assuming that
condition is met, the context
continues to exist until the MUX termination is
deleted.  The MUX
termination would be a bit strange, with no supporting
terminations to
provide any media, but I think  this is the logical
approach.

Thank you.

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From daemon@optimus.ietf.org  Fri Apr 12 10:18: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 KAA28112
	for <megaco-archive@odin.ietf.org>; Fri, 12 Apr 2002 10:18:37 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA18244
	for megaco-archive@odin.ietf.org; Fri, 12 Apr 2002 10:18:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15617;
	Fri, 12 Apr 2002 09:30:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15560
	for <megaco@optimus.ietf.org>; Fri, 12 Apr 2002 09:30:20 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20946
	for <megaco@ietf.org>; Fri, 12 Apr 2002 09:30:16 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3CDTln27391
	for <megaco@ietf.org>; Fri, 12 Apr 2002 09:29:47 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2WJANF59>; Fri, 12 Apr 2002 09:29:48 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2E6@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Date: Fri, 12 Apr 2002 09:29:45 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: stream
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Could I suggest you have a look at draft-ietf-megaco-h248v2-01.txt, section
6.2?  We considerably expanded the description of multiplexing terminations
in Geneva, and you may find the new text helpful.

One streams, have a look at section 7.1.6.  I would roughly sum up by saying
that the set of active streamIDs is a property of the context, but what
flows in each stream is a matter of the properties set at the individual
terminations.  My earlier response did not make that distinction clear.

Finally, no termination can belong to more than one context at a time.  That
includes multiplexing terminations.

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Friday, April 12, 2002 7:18 AM
To: megaco@ietf.org
Cc: Taylor, Tom-PT [CAR:B800:EXCH]
Subject: stream


Thanks Tom.

> Yes. But multiplexing is a property of a
termination,
> not a context. Introducing a multiplex creates 
> asymmetry: the termination(s) feeding into
> the multiplex are hidden from the other terminations
> in the context. The "centre" of the context, where 
> the bridging is done, lies between the MUX
> and the terminations that do not feed into it (are 
> not listed in the Multiplex Descriptor).

Question:
(a) Does a MUX termination like other terminations
have local/remote descriptors to specify the stream
properties plus a MUX Descriptor? The MGC needs to
issue three ADD Termination requests to the context
according to the following diagram (if it is correct),
one for MUX, one for T2 and one for T1, even though
the T1 is invisible to the T2, the properties of the
T1 still need to be specified in the C1, is that
correct?

(b) If several contexts contain the MUX, all those
contexts have the same MUX Termination ID? It is a
little bit strange to me, but is it correct?

Context 1
------------------------------------------------
| --------------------------                   |
| |      MUX            |                   |
| | ------  stream 1   |                   |
| | | T1 | -----(*)------ |  s1     -------- |
| | ------                 |-----(*)---| T2 | |
| --------------------------           ------  |
-----------------------------------------------       
          

> I assume you mean in the above diagram. If you mean 
> in general, then a stream is present in a context 
> until no terminations support that stream. 

Yes, I meant that diagram. If I understand above
comment correctly, it means that the stream is a
property of the context, not the property of the
termination. Move a termination (T1) out of a context
(C1) does not move the stream properties with the
Termination although that the stream descriptor is
always specified inside of the Termination. Is that
correct?

Thank you for your patience.

At 10:55 PM 11/04/2002 -0400, you wrote:
Oh, well, should have read this one first :-}

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 11, 2002 9:47 PM
To: megaco@ietf.org
Subject: [Megaco] stream


Hi,

Sorry, the previous message was pasted and posted
incompletely. Let me try again:

The spec says there are max 2 terminations in a
point-to-point connection context. In a multiplexing
termination context (such as H223), should there be
another termination for the mux in the context? 

         Context 1
    ------------------------
    | T1 ---- MUX ----- T2 |
    ------------------------

[PTT]
Yes.  But multiplexing is a property of a termination,
not a context.
Introducing a multiplex creates asymmetry: the
termination(s) feeding into
the multiplex are hidden from the other terminations
in the context.  The
"centre" of the context, where the bridging is done,
lies between the MUX
and the terminations that do not feed into it (are not
listed in the
Multiplex Descriptor).

If the T1 and T2 are connected by a stream #1. When
the T1 is moved out of C1, should the stream #1 be
deleted or should the stream #1 still stay within the
C1?

[PTT]
I assume you mean in the above diagram.  If you mean
in general, then a
stream is present in a context until no terminations
support that stream.
In the above diagram, if T1 feeds into the multiplex,
then the stream it
supports is visible only to the multiplex.  It is a
different stream 1 that
runs between the multiplex and the other terminations
in the context.

If both the T1 and T2 are moved out of C1, should the
C1 be destroyed automatically or should the C1 be
waiting until the MUX termination is requested to be
deleted by the MGC?

[PTT]
Again assuming that T1 is the termination listed in
the Multiplex
Descriptor, it would be an error to move it out before
modifying the MUX
termination to remove it from the Multiplex
Descriptor.  (We may need to
define a suitable error code.)  Assuming that
condition is met, the context
continues to exist until the MUX termination is
deleted.  The MUX
termination would be a bit strange, with no supporting
terminations to
provide any media, but I think  this is the logical
approach.

Thank you.

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From megaco-admin@ietf.org  Fri Apr 12 10:18: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 KAA28104
	for <megaco-archive@odin.ietf.org>; Fri, 12 Apr 2002 10:18:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15617;
	Fri, 12 Apr 2002 09:30:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15560
	for <megaco@optimus.ietf.org>; Fri, 12 Apr 2002 09:30:20 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20946
	for <megaco@ietf.org>; Fri, 12 Apr 2002 09:30:16 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3CDTln27391
	for <megaco@ietf.org>; Fri, 12 Apr 2002 09:29:47 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2WJANF59>; Fri, 12 Apr 2002 09:29:48 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A2E6@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Y Hu'" <yh86us@yahoo.com>, megaco@ietf.org
Date: Fri, 12 Apr 2002 09:29:45 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: stream
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Could I suggest you have a look at draft-ietf-megaco-h248v2-01.txt, section
6.2?  We considerably expanded the description of multiplexing terminations
in Geneva, and you may find the new text helpful.

One streams, have a look at section 7.1.6.  I would roughly sum up by saying
that the set of active streamIDs is a property of the context, but what
flows in each stream is a matter of the properties set at the individual
terminations.  My earlier response did not make that distinction clear.

Finally, no termination can belong to more than one context at a time.  That
includes multiplexing terminations.

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Friday, April 12, 2002 7:18 AM
To: megaco@ietf.org
Cc: Taylor, Tom-PT [CAR:B800:EXCH]
Subject: stream


Thanks Tom.

> Yes. But multiplexing is a property of a
termination,
> not a context. Introducing a multiplex creates 
> asymmetry: the termination(s) feeding into
> the multiplex are hidden from the other terminations
> in the context. The "centre" of the context, where 
> the bridging is done, lies between the MUX
> and the terminations that do not feed into it (are 
> not listed in the Multiplex Descriptor).

Question:
(a) Does a MUX termination like other terminations
have local/remote descriptors to specify the stream
properties plus a MUX Descriptor? The MGC needs to
issue three ADD Termination requests to the context
according to the following diagram (if it is correct),
one for MUX, one for T2 and one for T1, even though
the T1 is invisible to the T2, the properties of the
T1 still need to be specified in the C1, is that
correct?

(b) If several contexts contain the MUX, all those
contexts have the same MUX Termination ID? It is a
little bit strange to me, but is it correct?

Context 1
------------------------------------------------
| --------------------------                   |
| |      MUX            |                   |
| | ------  stream 1   |                   |
| | | T1 | -----(*)------ |  s1     -------- |
| | ------                 |-----(*)---| T2 | |
| --------------------------           ------  |
-----------------------------------------------       
          

> I assume you mean in the above diagram. If you mean 
> in general, then a stream is present in a context 
> until no terminations support that stream. 

Yes, I meant that diagram. If I understand above
comment correctly, it means that the stream is a
property of the context, not the property of the
termination. Move a termination (T1) out of a context
(C1) does not move the stream properties with the
Termination although that the stream descriptor is
always specified inside of the Termination. Is that
correct?

Thank you for your patience.

At 10:55 PM 11/04/2002 -0400, you wrote:
Oh, well, should have read this one first :-}

-----Original Message-----
From: Y Hu [mailto:yh86us@yahoo.com]
Sent: Thursday, April 11, 2002 9:47 PM
To: megaco@ietf.org
Subject: [Megaco] stream


Hi,

Sorry, the previous message was pasted and posted
incompletely. Let me try again:

The spec says there are max 2 terminations in a
point-to-point connection context. In a multiplexing
termination context (such as H223), should there be
another termination for the mux in the context? 

         Context 1
    ------------------------
    | T1 ---- MUX ----- T2 |
    ------------------------

[PTT]
Yes.  But multiplexing is a property of a termination,
not a context.
Introducing a multiplex creates asymmetry: the
termination(s) feeding into
the multiplex are hidden from the other terminations
in the context.  The
"centre" of the context, where the bridging is done,
lies between the MUX
and the terminations that do not feed into it (are not
listed in the
Multiplex Descriptor).

If the T1 and T2 are connected by a stream #1. When
the T1 is moved out of C1, should the stream #1 be
deleted or should the stream #1 still stay within the
C1?

[PTT]
I assume you mean in the above diagram.  If you mean
in general, then a
stream is present in a context until no terminations
support that stream.
In the above diagram, if T1 feeds into the multiplex,
then the stream it
supports is visible only to the multiplex.  It is a
different stream 1 that
runs between the multiplex and the other terminations
in the context.

If both the T1 and T2 are moved out of C1, should the
C1 be destroyed automatically or should the C1 be
waiting until the MUX termination is requested to be
deleted by the MGC?

[PTT]
Again assuming that T1 is the termination listed in
the Multiplex
Descriptor, it would be an error to move it out before
modifying the MUX
termination to remove it from the Multiplex
Descriptor.  (We may need to
define a suitable error code.)  Assuming that
condition is met, the context
continues to exist until the MUX termination is
deleted.  The MUX
termination would be a bit strange, with no supporting
terminations to
provide any media, but I think  this is the logical
approach.

Thank you.

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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


From megaco-admin@ietf.org  Fri Apr 12 11:46: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 LAA08144
	for <megaco-archive@odin.ietf.org>; Fri, 12 Apr 2002 11:46:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21496;
	Fri, 12 Apr 2002 11:14:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21465
	for <megaco@optimus.ietf.org>; Fri, 12 Apr 2002 11:14:44 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04668
	for <megaco@ietf.org>; Fri, 12 Apr 2002 11:14:39 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3CFEQT21386;
	Fri, 12 Apr 2002 11:14:26 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Watson Ding'" <dingwh@huawei.com>
Cc: <megaco@ietf.org>
Subject: RE: [Megaco] use of EPCF in MGCP
Date: Fri, 12 Apr 2002 11:14:37 -0400
Message-ID: <000d01c1e234$c2981c90$368910ac@Bala>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C1E213.3B867C90"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <000a01c1e1d3$017b6e60$26280b0a@huawei.com.cn>
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1E213.3B867C90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Please mail your MGCP questions to MGCP@LISTSERV.PULVER.COM
 
Anyways, the answer to your question - EPCF is used to configure the
endpoint with the BearerInformation (Companding - A-Law & mu-Law). Refer
to section 2.3.1 of RFC2705.
 
Thanks
Bala

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Watson Ding
Sent: Thursday, April 11, 2002 11:35 PM
To: megaco@ietf.org
Subject: [Megaco] use of EPCF in MGCP


hi,
 
any one know the use of EPCF command in MGCP?
 
thanks
 
Watson Ding.


------=_NextPart_000_000E_01C1E213.3B867C90
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D882125613-12042002><FONT face=3D"Goudy Old Style"=20
color=3D#0000ff>Please mail your MGCP questions to <A=20
href=3D"mailto:MGCP@LISTSERV.PULVER.COM">MGCP@LISTSERV.PULVER.COM</A></FO=
NT></SPAN></DIV>
<DIV><FONT face=3D"Goudy Old Style" color=3D#0000ff></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D882125613-12042002><FONT face=3D"Goudy Old Style"=20
color=3D#0000ff>Anyways, the answer to your question -&nbsp;EPCF is used =
to=20
configure the endpoint with the BearerInformation (Companding - A-Law =
&amp;=20
mu-Law). Refer to section 2.3.1 of RFC2705.</FONT></SPAN></DIV>
<DIV><FONT face=3D"Goudy Old Style" color=3D#0000ff></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3D"Goudy Old Style">Thanks</FONT></DIV>
<DIV align=3Dleft><FONT face=3D"Goudy Old Style">Bala</FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] <B>On Behalf Of=20
  </B>Watson Ding<BR><B>Sent:</B> Thursday, April 11, 2002 11:35=20
  PM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> [Megaco] use of =
EPCF in=20
  MGCP<BR><BR></FONT></DIV>
  <DIV><FONT size=3D2>hi,</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>any one know the use of EPCF command in MGCP?</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>thanks</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Watson Ding.</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000E_01C1E213.3B867C90--


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


From daemon@ns.ietf.org  Fri Apr 12 11:46: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 LAA08180
	for <megaco-archive@odin.ietf.org>; Fri, 12 Apr 2002 11:46:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA23685
	for megaco-archive@odin.ietf.org; Fri, 12 Apr 2002 11:46:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21496;
	Fri, 12 Apr 2002 11:14:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21465
	for <megaco@optimus.ietf.org>; Fri, 12 Apr 2002 11:14:44 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04668
	for <megaco@ietf.org>; Fri, 12 Apr 2002 11:14:39 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3CFEQT21386;
	Fri, 12 Apr 2002 11:14:26 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Watson Ding'" <dingwh@huawei.com>
Cc: <megaco@ietf.org>
Subject: RE: [Megaco] use of EPCF in MGCP
Date: Fri, 12 Apr 2002 11:14:37 -0400
Message-ID: <000d01c1e234$c2981c90$368910ac@Bala>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C1E213.3B867C90"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <000a01c1e1d3$017b6e60$26280b0a@huawei.com.cn>
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1E213.3B867C90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Please mail your MGCP questions to MGCP@LISTSERV.PULVER.COM
 
Anyways, the answer to your question - EPCF is used to configure the
endpoint with the BearerInformation (Companding - A-Law & mu-Law). Refer
to section 2.3.1 of RFC2705.
 
Thanks
Bala

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Watson Ding
Sent: Thursday, April 11, 2002 11:35 PM
To: megaco@ietf.org
Subject: [Megaco] use of EPCF in MGCP


hi,
 
any one know the use of EPCF command in MGCP?
 
thanks
 
Watson Ding.


------=_NextPart_000_000E_01C1E213.3B867C90
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D882125613-12042002><FONT face=3D"Goudy Old Style"=20
color=3D#0000ff>Please mail your MGCP questions to <A=20
href=3D"mailto:MGCP@LISTSERV.PULVER.COM">MGCP@LISTSERV.PULVER.COM</A></FO=
NT></SPAN></DIV>
<DIV><FONT face=3D"Goudy Old Style" color=3D#0000ff></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D882125613-12042002><FONT face=3D"Goudy Old Style"=20
color=3D#0000ff>Anyways, the answer to your question -&nbsp;EPCF is used =
to=20
configure the endpoint with the BearerInformation (Companding - A-Law =
&amp;=20
mu-Law). Refer to section 2.3.1 of RFC2705.</FONT></SPAN></DIV>
<DIV><FONT face=3D"Goudy Old Style" color=3D#0000ff></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3D"Goudy Old Style">Thanks</FONT></DIV>
<DIV align=3Dleft><FONT face=3D"Goudy Old Style">Bala</FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] <B>On Behalf Of=20
  </B>Watson Ding<BR><B>Sent:</B> Thursday, April 11, 2002 11:35=20
  PM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> [Megaco] use of =
EPCF in=20
  MGCP<BR><BR></FONT></DIV>
  <DIV><FONT size=3D2>hi,</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>any one know the use of EPCF command in MGCP?</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>thanks</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Watson Ding.</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000E_01C1E213.3B867C90--


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



From megaco-admin@ietf.org  Fri Apr 12 11:49: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 LAA08794
	for <megaco-archive@odin.ietf.org>; Fri, 12 Apr 2002 11:49:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21063;
	Fri, 12 Apr 2002 11:05:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21032
	for <megaco@optimus.ietf.org>; Fri, 12 Apr 2002 11:05:27 -0400 (EDT)
Received: from ns1.ottawa.alcatel.ca (ns1.ottawa.alcatel.ca [192.75.23.67])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03860
	for <megaco@ietf.org>; Fri, 12 Apr 2002 11:05:22 -0400 (EDT)
Received: (qmail 27011 invoked from network); 12 Apr 2002 14:51:23 -0000
Received: from portal.ottawa.alcatel.ca (HELO mx1.ca.alcatel.com) (192.75.23.76)
  by ns1.ottawa.alcatel.ca with SMTP; 12 Apr 2002 14:51:23 -0000
Received: (qmail 12111 invoked from network); 12 Apr 2002 15:07:05 -0000
Received: (ofmipd 138.120.118.71); 12 Apr 2002 15:06:43 -0000
Received: from alcatel.com ([138.120.118.114])
          by kanmail01.ca.newbridge.com (Netscape Messaging Server 3.6)
           with ESMTP id AAA6C4C for <megaco@ietf.org>;
          Fri, 12 Apr 2002 11:05:07 -0400
Date: 12 Apr 2002 11:05:06 -0400
Message-ID: <3CB6F7A2.5FA9F92C@alcatel.com>
From: "VYACHESLAV LVIN" <vyacheslav.lvin@alcatel.com>
To: "megaco@ietf.org" <megaco@ietf.org>
Organization: Alcatel Canada
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: [Megaco] Events/Signals behavior after Subtract
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 all,
is it a correct statement, that if events and/or signals are active
while MG receive Subtract request they remain active after termination
goes to Null Context?

Regards,
Slav


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


From daemon@ns.ietf.org  Fri Apr 12 11:49: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 LAA08805
	for <megaco-archive@odin.ietf.org>; Fri, 12 Apr 2002 11:49:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA23796
	for megaco-archive@odin.ietf.org; Fri, 12 Apr 2002 11:50:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21063;
	Fri, 12 Apr 2002 11:05:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21032
	for <megaco@optimus.ietf.org>; Fri, 12 Apr 2002 11:05:27 -0400 (EDT)
Received: from ns1.ottawa.alcatel.ca (ns1.ottawa.alcatel.ca [192.75.23.67])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03860
	for <megaco@ietf.org>; Fri, 12 Apr 2002 11:05:22 -0400 (EDT)
Received: (qmail 27011 invoked from network); 12 Apr 2002 14:51:23 -0000
Received: from portal.ottawa.alcatel.ca (HELO mx1.ca.alcatel.com) (192.75.23.76)
  by ns1.ottawa.alcatel.ca with SMTP; 12 Apr 2002 14:51:23 -0000
Received: (qmail 12111 invoked from network); 12 Apr 2002 15:07:05 -0000
Received: (ofmipd 138.120.118.71); 12 Apr 2002 15:06:43 -0000
Received: from alcatel.com ([138.120.118.114])
          by kanmail01.ca.newbridge.com (Netscape Messaging Server 3.6)
           with ESMTP id AAA6C4C for <megaco@ietf.org>;
          Fri, 12 Apr 2002 11:05:07 -0400
Date: 12 Apr 2002 11:05:06 -0400
Message-ID: <3CB6F7A2.5FA9F92C@alcatel.com>
From: "VYACHESLAV LVIN" <vyacheslav.lvin@alcatel.com>
To: "megaco@ietf.org" <megaco@ietf.org>
Organization: Alcatel Canada
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: [Megaco] Events/Signals behavior after Subtract
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 all,
is it a correct statement, that if events and/or signals are active
while MG receive Subtract request they remain active after termination
goes to Null Context?

Regards,
Slav


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



From megaco-admin@ietf.org  Sun Apr 14 10:37: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 KAA18386
	for <megaco-archive@odin.ietf.org>; Sun, 14 Apr 2002 10:37:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00644;
	Sun, 14 Apr 2002 10:17:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00612
	for <megaco@optimus.ietf.org>; Sun, 14 Apr 2002 10:17:50 -0400 (EDT)
Received: from hongkong.com ([202.84.12.154])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18267
	for <megaco@ietf.org>; Sun, 14 Apr 2002 10:17:42 -0400 (EDT)
Received: from hongkong.com([10.1.0.100]) by hongkong.com(JetMail 2.5.3.0)
	with SMTP id jm183cb9d4a1; Sun, 14 Apr 2002 14:11:47 -0000
Received: from loki.ietf.org([132.151.1.177]) by hongkong.com(JetMail 2.5.3.0)
	with SMTP id jm873cb4734a; Wed, 10 Apr 2002 15:46:45 -0000
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id JAA27135
	for ietf-123-outbound.03@ietf.org; Wed, 10 Apr 2002 09:35:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id IAA26463
	for <all-ietf@loki.ietf.org>; Wed, 10 Apr 2002 08:13:22 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16176;
	Wed, 10 Apr 2002 08:13:19 -0400 (EDT)
Message-Id: <200204101213.IAA16176@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: megaco@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 10 Apr 2002 08:13:19 -0400
X-Auto-Forward: nicklau@hongkong.com
 nicklau@speednet.net
Subject: [Megaco] I-D ACTION:draft-ietf-megaco-naspkg-04.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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Media Gateway Control Working Group of the IETF.

	Title		: Megaco/H.248 NAS Package
	Author(s)	: J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam
	Filename	: draft-ietf-megaco-naspkg-04.txt
	Pages		: 18
	Date		: 09-Apr-02
	
This document is intended to satisfy the requirements in section 
11.2.5 of the Megaco/H.248 requirements document.  It defines five 
packages: 
- the base NAS package contains properties and events supported by 
all NAS terminations; 
- the NAS Incoming package contains properties and events  
supported by NAS terminations involved in calls initiated by the 
circuit network; 
- the NAS Outgoing package contains properties supported by NAS 
terminations involved in calls outgoing to the circuit network; 
- the NAS Control package contains an event supported by a NAS 
Control termination, which allows the MG to indicate a request to 
initiate a data connection to a terminal served by the switched 
circuit network; 
- the NAS ROOT package contains properties supported by an MG which 
is also capable of supporting at least the NAS and NAS Incoming 
packages.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-megaco-naspkg-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020409132359.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-megaco-naspkg-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020409132359.I-D@ietf.org>

--OtherAccess--

--NextPart--



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


From daemon@optimus.ietf.org  Sun Apr 14 10:38: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 KAA18400
	for <megaco-archive@odin.ietf.org>; Sun, 14 Apr 2002 10:37:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA01378
	for megaco-archive@odin.ietf.org; Sun, 14 Apr 2002 10:38:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00644;
	Sun, 14 Apr 2002 10:17:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00612
	for <megaco@optimus.ietf.org>; Sun, 14 Apr 2002 10:17:50 -0400 (EDT)
Received: from hongkong.com ([202.84.12.154])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18267
	for <megaco@ietf.org>; Sun, 14 Apr 2002 10:17:42 -0400 (EDT)
Received: from hongkong.com([10.1.0.100]) by hongkong.com(JetMail 2.5.3.0)
	with SMTP id jm183cb9d4a1; Sun, 14 Apr 2002 14:11:47 -0000
Received: from loki.ietf.org([132.151.1.177]) by hongkong.com(JetMail 2.5.3.0)
	with SMTP id jm873cb4734a; Wed, 10 Apr 2002 15:46:45 -0000
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id JAA27135
	for ietf-123-outbound.03@ietf.org; Wed, 10 Apr 2002 09:35:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id IAA26463
	for <all-ietf@loki.ietf.org>; Wed, 10 Apr 2002 08:13:22 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16176;
	Wed, 10 Apr 2002 08:13:19 -0400 (EDT)
Message-Id: <200204101213.IAA16176@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: megaco@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 10 Apr 2002 08:13:19 -0400
X-Auto-Forward: nicklau@hongkong.com
 nicklau@speednet.net
Subject: [Megaco] I-D ACTION:draft-ietf-megaco-naspkg-04.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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Media Gateway Control Working Group of the IETF.

	Title		: Megaco/H.248 NAS Package
	Author(s)	: J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam
	Filename	: draft-ietf-megaco-naspkg-04.txt
	Pages		: 18
	Date		: 09-Apr-02
	
This document is intended to satisfy the requirements in section 
11.2.5 of the Megaco/H.248 requirements document.  It defines five 
packages: 
- the base NAS package contains properties and events supported by 
all NAS terminations; 
- the NAS Incoming package contains properties and events  
supported by NAS terminations involved in calls initiated by the 
circuit network; 
- the NAS Outgoing package contains properties supported by NAS 
terminations involved in calls outgoing to the circuit network; 
- the NAS Control package contains an event supported by a NAS 
Control termination, which allows the MG to indicate a request to 
initiate a data connection to a terminal served by the switched 
circuit network; 
- the NAS ROOT package contains properties supported by an MG which 
is also capable of supporting at least the NAS and NAS Incoming 
packages.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-megaco-naspkg-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020409132359.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-megaco-naspkg-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020409132359.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From megaco-admin@ietf.org  Mon Apr 15 02:24: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 CAA07839
	for <megaco-archive@odin.ietf.org>; Mon, 15 Apr 2002 02:24:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA15932;
	Mon, 15 Apr 2002 02:04:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA15902
	for <megaco@ns.ietf.org>; Mon, 15 Apr 2002 02:04:42 -0400 (EDT)
Received: from hanghau.pacific.net.hk (hanghau.pacific.net.hk [202.64.33.137])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03348
	for <megaco@ietf.org>; Mon, 15 Apr 2002 02:04:38 -0400 (EDT)
Received: from jade ([211.96.68.33])
        by hanghau.pacific.net.hk with SMTP
        id g3F64dO03605 for <megaco@ietf.org>; Mon, 15 Apr 2002 14:04:39 +0800 (CST)
Message-ID: <003201c1e443$6aee52f0$bfc809c0@jade>
From: "Jade Chen Yan" <jade.chen@imag.com>
To: <megaco@ietf.org>
Date: Mon, 15 Apr 2002 14:04:34 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002F_01C1E486.78EB6D50"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Subject: [Megaco] About NAT
Sender: megaco-admin@ietf.org
Errors-To: 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_002F_01C1E486.78EB6D50
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

DQoNCkhpLEFsbCwNCg0KQ2FuIHNvbWVvbmUgZ2l2ZSBtZSBzb21lIGd1aWRlcyBvbiBob3cgIG1l
Z2FjbyBwYWNrZXRzIHRyYW5zZmVyIGJlaGluZCB0aGUgZmlyZXdhbGw/U3VwcG9zZSB0aGF0IGEg
Z2F0ZXdheSBpcyBiZWhpbmQgdGhlIGZpcmV3YWxsLCBob3cgdGhlIGVuZHBvaW50cyBjb21tdW5p
Y2F0aW9uIHdpdGggdGhlIEludGVybmV0Pw0KDQoNCkJlc3QgUmVnYXJkcywNCkphZGUNCg0KDQog
DQo=

------=_NextPart_000_002F_01C1E486.78EB6D50
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4zMzE1LjI4NzAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj4mbmJzcDs8L0RJ
Vj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+SGksQWxsLDwvRk9OVD48L0RJVj4NCjxE
SVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPkNhbiBzb21lb25l
IGdpdmUgbWUgc29tZSBndWlkZXMgb24gaG93ICBtZWdhY28gDQpwYWNrZXRzIHRyYW5zZmVyIGJl
aGluZCB0aGUgZmlyZXdhbGw/U3VwcG9zZSB0aGF0IGEgZ2F0ZXdheSBpcyBiZWhpbmQgdGhlIA0K
ZmlyZXdhbGwsIGhvdyB0aGUgZW5kcG9pbnRzIGNvbW11bmljYXRpb24gd2l0aCB0aGUgSW50ZXJu
ZXQ/PC9GT05UPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1Bcmlh
bCBzaXplPTI+PEJSPkJlc3QgUmVnYXJkcyw8QlI+SmFkZTwvRk9OVD48L0RJVj4NCjxESVY+Jm5i
c3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjxCUj48L0ZPTlQ+Jm5ic3A7
PC9ESVY+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_002F_01C1E486.78EB6D50--


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


From daemon@ns.ietf.org  Mon Apr 15 02:24: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 CAA07853
	for <megaco-archive@odin.ietf.org>; Mon, 15 Apr 2002 02:24:08 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA16370
	for megaco-archive@odin.ietf.org; Mon, 15 Apr 2002 02:24:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA15932;
	Mon, 15 Apr 2002 02:04:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA15902
	for <megaco@ns.ietf.org>; Mon, 15 Apr 2002 02:04:42 -0400 (EDT)
Received: from hanghau.pacific.net.hk (hanghau.pacific.net.hk [202.64.33.137])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03348
	for <megaco@ietf.org>; Mon, 15 Apr 2002 02:04:38 -0400 (EDT)
Received: from jade ([211.96.68.33])
        by hanghau.pacific.net.hk with SMTP
        id g3F64dO03605 for <megaco@ietf.org>; Mon, 15 Apr 2002 14:04:39 +0800 (CST)
Message-ID: <003201c1e443$6aee52f0$bfc809c0@jade>
From: "Jade Chen Yan" <jade.chen@imag.com>
To: <megaco@ietf.org>
Date: Mon, 15 Apr 2002 14:04:34 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002F_01C1E486.78EB6D50"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Subject: [Megaco] About NAT
Sender: megaco-admin@ietf.org
Errors-To: 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_002F_01C1E486.78EB6D50
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

DQoNCkhpLEFsbCwNCg0KQ2FuIHNvbWVvbmUgZ2l2ZSBtZSBzb21lIGd1aWRlcyBvbiBob3cgIG1l
Z2FjbyBwYWNrZXRzIHRyYW5zZmVyIGJlaGluZCB0aGUgZmlyZXdhbGw/U3VwcG9zZSB0aGF0IGEg
Z2F0ZXdheSBpcyBiZWhpbmQgdGhlIGZpcmV3YWxsLCBob3cgdGhlIGVuZHBvaW50cyBjb21tdW5p
Y2F0aW9uIHdpdGggdGhlIEludGVybmV0Pw0KDQoNCkJlc3QgUmVnYXJkcywNCkphZGUNCg0KDQog
DQo=

------=_NextPart_000_002F_01C1E486.78EB6D50
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4zMzE1LjI4NzAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj4mbmJzcDs8L0RJ
Vj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+SGksQWxsLDwvRk9OVD48L0RJVj4NCjxE
SVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPkNhbiBzb21lb25l
IGdpdmUgbWUgc29tZSBndWlkZXMgb24gaG93ICBtZWdhY28gDQpwYWNrZXRzIHRyYW5zZmVyIGJl
aGluZCB0aGUgZmlyZXdhbGw/U3VwcG9zZSB0aGF0IGEgZ2F0ZXdheSBpcyBiZWhpbmQgdGhlIA0K
ZmlyZXdhbGwsIGhvdyB0aGUgZW5kcG9pbnRzIGNvbW11bmljYXRpb24gd2l0aCB0aGUgSW50ZXJu
ZXQ/PC9GT05UPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1Bcmlh
bCBzaXplPTI+PEJSPkJlc3QgUmVnYXJkcyw8QlI+SmFkZTwvRk9OVD48L0RJVj4NCjxESVY+Jm5i
c3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjxCUj48L0ZPTlQ+Jm5ic3A7
PC9ESVY+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_002F_01C1E486.78EB6D50--


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



From megaco-admin@ietf.org  Mon Apr 15 21:19: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 VAA10558
	for <megaco-archive@odin.ietf.org>; Mon, 15 Apr 2002 21:19:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA25608;
	Mon, 15 Apr 2002 21:01:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA25581
	for <megaco@ns.ietf.org>; Mon, 15 Apr 2002 21:01:38 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10355
	for <megaco@ietf.org>; Mon, 15 Apr 2002 21:01:35 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUMYQS00.P1Y for
          <megaco@ietf.org>; Tue, 16 Apr 2002 08:59:16 +0800 
Message-ID: <003301c1e4e2$6d6d3560$26280b0a@huawei.com.cn>
From: "Watson Ding" <dingwh@huawei.com>
To: <megaco@ietf.org>
Date: Tue, 16 Apr 2002 09:02:49 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0030_01C1E525.7B780B60"
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
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 is a multi-part message in MIME format.

------=_NextPart_000_0030_01C1E525.7B780B60
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

aGksDQoNCkluIHdoaWNoIHBhY2thZ2Ugb3IgZXh0ZW50aW9uIHBhY2thZ2UgaXMgQ2FsbGVyIE51
bWJlciBldmVudCBkZWZpbmVkPyB0aGFua3MhDQoNCldhdHNvbiBEaW5nDQoNCg==

------=_NextPart_000_0030_01C1E525.7B780B60
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5oaSw8L0ZPTlQ+PC9ESVY+
DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5JbiB3aGljaCBwYWNrYWdlIG9yIGV4dGVudGlvbiBw
YWNrYWdlIGlzIENhbGxlciBOdW1iZXIgZXZlbnQgZGVmaW5lZD8gDQp0aGFua3MhPC9ESVY+DQo8
RElWPiZuYnNwOzwvRElWPg0KPERJVj5XYXRzb24gRGluZzwvRElWPg0KPERJVj4mbmJzcDs8L0RJ
Vj48L0JPRFk+PC9IVE1MPg0K

------=_NextPart_000_0030_01C1E525.7B780B60--


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


From daemon@ns.ietf.org  Mon Apr 15 21:19: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 VAA10569
	for <megaco-archive@odin.ietf.org>; Mon, 15 Apr 2002 21:19:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA26232
	for megaco-archive@odin.ietf.org; Mon, 15 Apr 2002 21:19:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA25608;
	Mon, 15 Apr 2002 21:01:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA25581
	for <megaco@ns.ietf.org>; Mon, 15 Apr 2002 21:01:38 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10355
	for <megaco@ietf.org>; Mon, 15 Apr 2002 21:01:35 -0400 (EDT)
Received: from d12904 ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GUMYQS00.P1Y for
          <megaco@ietf.org>; Tue, 16 Apr 2002 08:59:16 +0800 
Message-ID: <003301c1e4e2$6d6d3560$26280b0a@huawei.com.cn>
From: "Watson Ding" <dingwh@huawei.com>
To: <megaco@ietf.org>
Date: Tue, 16 Apr 2002 09:02:49 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0030_01C1E525.7B780B60"
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
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 is a multi-part message in MIME format.

------=_NextPart_000_0030_01C1E525.7B780B60
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

aGksDQoNCkluIHdoaWNoIHBhY2thZ2Ugb3IgZXh0ZW50aW9uIHBhY2thZ2UgaXMgQ2FsbGVyIE51
bWJlciBldmVudCBkZWZpbmVkPyB0aGFua3MhDQoNCldhdHNvbiBEaW5nDQoNCg==

------=_NextPart_000_0030_01C1E525.7B780B60
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi
MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w
MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5oaSw8L0ZPTlQ+PC9ESVY+
DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj5JbiB3aGljaCBwYWNrYWdlIG9yIGV4dGVudGlvbiBw
YWNrYWdlIGlzIENhbGxlciBOdW1iZXIgZXZlbnQgZGVmaW5lZD8gDQp0aGFua3MhPC9ESVY+DQo8
RElWPiZuYnNwOzwvRElWPg0KPERJVj5XYXRzb24gRGluZzwvRElWPg0KPERJVj4mbmJzcDs8L0RJ
Vj48L0JPRFk+PC9IVE1MPg0K

------=_NextPart_000_0030_01C1E525.7B780B60--


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



From megaco-admin@ietf.org  Mon Apr 15 21:32: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 VAA10693
	for <megaco-archive@odin.ietf.org>; Mon, 15 Apr 2002 21:32:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA26018;
	Mon, 15 Apr 2002 21:16:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA25989
	for <megaco@ns.ietf.org>; Mon, 15 Apr 2002 21:15:57 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com (zrtps0kp.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10499
	for <megaco@ietf.org>; Mon, 15 Apr 2002 21:15:54 -0400 (EDT)
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3G1FFQ29982;
	Mon, 15 Apr 2002 21:15:15 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2T2KTVMW>; Mon, 15 Apr 2002 21:15:16 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C02DAC5AE@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: Watson Ding <dingwh@huawei.com>, megaco@ietf.org
Subject: RE: [Megaco] (no subject)
Date: Mon, 15 Apr 2002 21:15:16 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

I assume you are looking for caller ID signaling.  You can find the andisp
(analog display) package in draft-boyle-megaco-alerting-03.



Kevin

-----Original Message-----
From: Watson Ding [mailto:dingwh@huawei.com]
Sent: Monday, April 15, 2002 9:03 PM
To: megaco@ietf.org
Subject: [Megaco] (no subject)


hi,

In which package or extention package is Caller Number event defined?
thanks!

Watson Ding

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


From daemon@ns.ietf.org  Mon Apr 15 21:32: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 VAA10703
	for <megaco-archive@odin.ietf.org>; Mon, 15 Apr 2002 21:32:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA26988
	for megaco-archive@odin.ietf.org; Mon, 15 Apr 2002 21:32:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA26018;
	Mon, 15 Apr 2002 21:16:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA25989
	for <megaco@ns.ietf.org>; Mon, 15 Apr 2002 21:15:57 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com (zrtps0kp.nortelnetworks.com [47.140.192.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10499
	for <megaco@ietf.org>; Mon, 15 Apr 2002 21:15:54 -0400 (EDT)
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3G1FFQ29982;
	Mon, 15 Apr 2002 21:15:15 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2T2KTVMW>; Mon, 15 Apr 2002 21:15:16 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C02DAC5AE@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle"<kboyle@nortelnetworks.com>
To: Watson Ding <dingwh@huawei.com>, megaco@ietf.org
Subject: RE: [Megaco] (no subject)
Date: Mon, 15 Apr 2002 21:15:16 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

I assume you are looking for caller ID signaling.  You can find the andisp
(analog display) package in draft-boyle-megaco-alerting-03.



Kevin

-----Original Message-----
From: Watson Ding [mailto:dingwh@huawei.com]
Sent: Monday, April 15, 2002 9:03 PM
To: megaco@ietf.org
Subject: [Megaco] (no subject)


hi,

In which package or extention package is Caller Number event defined?
thanks!

Watson Ding

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



From megaco-admin@ietf.org  Tue Apr 16 04:14: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 EAA26242
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 04:14:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25811;
	Tue, 16 Apr 2002 03:48:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25782
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 03:48:02 -0400 (EDT)
Received: from web12608.mail.yahoo.com (web12608.mail.yahoo.com [216.136.173.231])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA25894
	for <megaco@ietf.org>; Tue, 16 Apr 2002 03:47:58 -0400 (EDT)
Message-ID: <20020416074800.49855.qmail@web12608.mail.yahoo.com>
Received: from [203.26.41.49] by web12608.mail.yahoo.com via HTTP; Tue, 16 Apr 2002 00:48:00 PDT
Date: Tue, 16 Apr 2002 00:48:00 -0700 (PDT)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] media description
Sender: megaco-admin@ietf.org
Errors-To: 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,

The spec says that a single session cannot include
more than one media description ("m="). What is the
definition of the session here? Does the
StreamDescriptor represent one single session (stream
ID) or the LocalDescriptor/RemoteDescriptor represents
one single session?

Also, the examples in the APPENDIX A (V2) have more
than one "m=" lines in the LocalDescriptor, is it
legal (regardless it is just an example)?

Thank you. 

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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


From daemon@ns.ietf.org  Tue Apr 16 05:10: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 EAA26251
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 04:14:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA27053
	for megaco-archive@odin.ietf.org; Tue, 16 Apr 2002 04:14:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25811;
	Tue, 16 Apr 2002 03:48:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25782
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 03:48:02 -0400 (EDT)
Received: from web12608.mail.yahoo.com (web12608.mail.yahoo.com [216.136.173.231])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA25894
	for <megaco@ietf.org>; Tue, 16 Apr 2002 03:47:58 -0400 (EDT)
Message-ID: <20020416074800.49855.qmail@web12608.mail.yahoo.com>
Received: from [203.26.41.49] by web12608.mail.yahoo.com via HTTP; Tue, 16 Apr 2002 00:48:00 PDT
Date: Tue, 16 Apr 2002 00:48:00 -0700 (PDT)
From: Y Hu <yh86us@yahoo.com>
To: megaco@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Megaco] media description
Sender: megaco-admin@ietf.org
Errors-To: 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,

The spec says that a single session cannot include
more than one media description ("m="). What is the
definition of the session here? Does the
StreamDescriptor represent one single session (stream
ID) or the LocalDescriptor/RemoteDescriptor represents
one single session?

Also, the examples in the APPENDIX A (V2) have more
than one "m=" lines in the LocalDescriptor, is it
legal (regardless it is just an example)?

Thank you. 

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From megaco-admin@ietf.org  Tue Apr 16 08:39: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 IAA01022
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 08:39:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA09398;
	Tue, 16 Apr 2002 08:24:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA09369
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 08:24:35 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00605
	for <megaco@ietf.org>; Tue, 16 Apr 2002 08:24:31 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3GCO2e18634
	for <megaco@ietf.org>; Tue, 16 Apr 2002 08:24:02 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2WJA3Y07>; Tue, 16 Apr 2002 08:24:02 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0002383D1F@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: Jade Chen Yan <jade.chen@imag.com>, megaco@ietf.org
Subject: RE: [Megaco] About NAT
Date: Tue, 16 Apr 2002 08:24:05 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

If you are talking about media flows, this is the sort of problem Midcom is
working on.  If you are talking about control signalling, the relationship
between the MG and MGC should be persistent enough that the administrator
can set up the necessary hole in the firewall.

-----Original Message-----
From: Jade Chen Yan [mailto:jade.chen@imag.com]
Sent: Monday, April 15, 2002 2:05 AM
To: megaco@ietf.org
Subject: [Megaco] About NAT




Hi,All,

Can someone give me some guides on how megaco packets transfer behind the
firewall?Suppose that a gateway is behind the firewall, how the endpoints
communication with the Internet?


Best Regards,
Jade


 

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


From daemon@ns.ietf.org  Tue Apr 16 08:39: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 IAA01034
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 08:39:33 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA10495
	for megaco-archive@odin.ietf.org; Tue, 16 Apr 2002 08:39:35 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA09398;
	Tue, 16 Apr 2002 08:24:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA09369
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 08:24:35 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00605
	for <megaco@ietf.org>; Tue, 16 Apr 2002 08:24:31 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3GCO2e18634
	for <megaco@ietf.org>; Tue, 16 Apr 2002 08:24:02 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2WJA3Y07>; Tue, 16 Apr 2002 08:24:02 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0002383D1F@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: Jade Chen Yan <jade.chen@imag.com>, megaco@ietf.org
Subject: RE: [Megaco] About NAT
Date: Tue, 16 Apr 2002 08:24:05 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

If you are talking about media flows, this is the sort of problem Midcom is
working on.  If you are talking about control signalling, the relationship
between the MG and MGC should be persistent enough that the administrator
can set up the necessary hole in the firewall.

-----Original Message-----
From: Jade Chen Yan [mailto:jade.chen@imag.com]
Sent: Monday, April 15, 2002 2:05 AM
To: megaco@ietf.org
Subject: [Megaco] About NAT




Hi,All,

Can someone give me some guides on how megaco packets transfer behind the
firewall?Suppose that a gateway is behind the firewall, how the endpoints
communication with the Internet?


Best Regards,
Jade


 

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



From megaco-admin@ietf.org  Tue Apr 16 09:47: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 JAA03984
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 09:47:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15144;
	Tue, 16 Apr 2002 09:33:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15121
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 09:33:06 -0400 (EDT)
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 JAA03022
	for <megaco@ietf.org>; Tue, 16 Apr 2002 09:33:02 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3GDWXA15908;
	Tue, 16 Apr 2002 09:32:33 -0400 (EDT)
Received: from lucent.com (tla.lra.lucent.com [192.11.63.211])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA17041;
	Tue, 16 Apr 2002 09:33:15 -0400 (EDT)
Message-ID: <3CBC27C0.1D013148@lucent.com>
Date: Tue, 16 Apr 2002 09:31:44 -0400
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: Y Hu <yh86us@yahoo.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] media description
References: <20020416074800.49855.qmail@web12608.mail.yahoo.com>
Content-Type: multipart/mixed;
 boundary="------------A566119B57735925DBF613C7"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------A566119B57735925DBF613C7
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

A "session" in this paragraph, refers to a session description or
instance of SDP.  In H.248 more than one session description may appear
in a single Local or Remote Descriptor - each session description begins
with "v=0".  Within each session description (block of SDP code starting
with v=0) only one m= line may appear.  Of course additional m= lines
will appear in the other session descriptions (if any) in the same Local
or Remote Descriptor and in other Stream Descriptors.

Y Hu wrote:

> Hi,
>
> The spec says that a single session cannot include
> more than one media description ("m="). What is the
> definition of the session here? Does the
> StreamDescriptor represent one single session (stream
> ID) or the LocalDescriptor/RemoteDescriptor represents
> one single session?
>
> Also, the examples in the APPENDIX A (V2) have more
> than one "m=" lines in the LocalDescriptor, is it
> legal (regardless it is just an example)?
>
> Thank you.
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Tax Center - online filing with TurboTax
> http://taxes.yahoo.com/
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------A566119B57735925DBF613C7
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------A566119B57735925DBF613C7--


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


From daemon@ns.ietf.org  Tue Apr 16 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 JAA03993
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 09:47:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA16378
	for megaco-archive@odin.ietf.org; Tue, 16 Apr 2002 09:47:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15144;
	Tue, 16 Apr 2002 09:33:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15121
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 09:33:06 -0400 (EDT)
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 JAA03022
	for <megaco@ietf.org>; Tue, 16 Apr 2002 09:33:02 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3GDWXA15908;
	Tue, 16 Apr 2002 09:32:33 -0400 (EDT)
Received: from lucent.com (tla.lra.lucent.com [192.11.63.211])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA17041;
	Tue, 16 Apr 2002 09:33:15 -0400 (EDT)
Message-ID: <3CBC27C0.1D013148@lucent.com>
Date: Tue, 16 Apr 2002 09:31:44 -0400
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: Y Hu <yh86us@yahoo.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] media description
References: <20020416074800.49855.qmail@web12608.mail.yahoo.com>
Content-Type: multipart/mixed;
 boundary="------------A566119B57735925DBF613C7"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------A566119B57735925DBF613C7
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

A "session" in this paragraph, refers to a session description or
instance of SDP.  In H.248 more than one session description may appear
in a single Local or Remote Descriptor - each session description begins
with "v=0".  Within each session description (block of SDP code starting
with v=0) only one m= line may appear.  Of course additional m= lines
will appear in the other session descriptions (if any) in the same Local
or Remote Descriptor and in other Stream Descriptors.

Y Hu wrote:

> Hi,
>
> The spec says that a single session cannot include
> more than one media description ("m="). What is the
> definition of the session here? Does the
> StreamDescriptor represent one single session (stream
> ID) or the LocalDescriptor/RemoteDescriptor represents
> one single session?
>
> Also, the examples in the APPENDIX A (V2) have more
> than one "m=" lines in the LocalDescriptor, is it
> legal (regardless it is just an example)?
>
> Thank you.
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Tax Center - online filing with TurboTax
> http://taxes.yahoo.com/
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------A566119B57735925DBF613C7
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------A566119B57735925DBF613C7--


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



From megaco-admin@ietf.org  Tue Apr 16 10:40: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 KAA06548
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:40:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18962;
	Tue, 16 Apr 2002 10:17:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18932
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 10:17:25 -0400 (EDT)
Received: from ws3-2.us4.outblaze.com (205-158-62-92.outblaze.com [205.158.62.92])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA05746
	for <megaco@ietf.org>; Tue, 16 Apr 2002 10:17:21 -0400 (EDT)
Received: (qmail 27365 invoked by uid 1001); 16 Apr 2002 14:16:50 -0000
Message-ID: <20020416141650.27364.qmail@email.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 [202.134.192.190] by ws3-2.us4.outblaze.com with http for
    harry_suede@email.com; Tue, 16 Apr 2002 22:16:50 +0800
From: "Harry Suede" <harry_suede@email.com>
To: megaco@ietf.org
Date: Tue, 16 Apr 2002 22:16:50 +0800
X-Originating-Ip: 202.134.192.190
X-Originating-Server: ws3-2.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Subject: [Megaco] ASN PDUs
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

 Are there any sample MEGACO ASN PDUs available anywhere ? I understand that there are some available at the ericsson and asn1.org sites. But I need to verify their correctness, especially the way SDP is handled [ I wonder how others are doing it]

Can anyone offer some sample PDUs ?

Regards
Harry

-- 

_______________________________________________
Sign-up for your own FREE Personalized E-mail at Email.com
http://www.email.com/?sr=signup


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


From daemon@ns.ietf.org  Tue Apr 16 10:40: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 KAA06558
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:40:52 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA20551
	for megaco-archive@odin.ietf.org; Tue, 16 Apr 2002 10:40:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18962;
	Tue, 16 Apr 2002 10:17:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18932
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 10:17:25 -0400 (EDT)
Received: from ws3-2.us4.outblaze.com (205-158-62-92.outblaze.com [205.158.62.92])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA05746
	for <megaco@ietf.org>; Tue, 16 Apr 2002 10:17:21 -0400 (EDT)
Received: (qmail 27365 invoked by uid 1001); 16 Apr 2002 14:16:50 -0000
Message-ID: <20020416141650.27364.qmail@email.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 [202.134.192.190] by ws3-2.us4.outblaze.com with http for
    harry_suede@email.com; Tue, 16 Apr 2002 22:16:50 +0800
From: "Harry Suede" <harry_suede@email.com>
To: megaco@ietf.org
Date: Tue, 16 Apr 2002 22:16:50 +0800
X-Originating-Ip: 202.134.192.190
X-Originating-Server: ws3-2.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Subject: [Megaco] ASN PDUs
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

 Are there any sample MEGACO ASN PDUs available anywhere ? I understand that there are some available at the ericsson and asn1.org sites. But I need to verify their correctness, especially the way SDP is handled [ I wonder how others are doing it]

Can anyone offer some sample PDUs ?

Regards
Harry

-- 

_______________________________________________
Sign-up for your own FREE Personalized E-mail at Email.com
http://www.email.com/?sr=signup


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



From megaco-admin@ietf.org  Tue Apr 16 15: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 PAA07711
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 15:28:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08029;
	Tue, 16 Apr 2002 15:10:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08000
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 15:10:03 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05598
	for <megaco@ietf.org>; Tue, 16 Apr 2002 15:09:59 -0400 (EDT)
Received: from Software.Mitel.COM (software [134.199.30.49]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id PAA07821
	for <megaco@ietf.org>; Tue, 16 Apr 2002 15:09:32 -0400 (EDT)
Received: from pc3027 (gx-sup26.software.mitel.com [134.199.23.103])
        by Software.Mitel.COM (V8/MAIL-HUB-2.0) with SMTP id PAA05368
	for <megaco@ietf.org>; Tue, 16 Apr 2002 15:09:31 -0400 (EDT)
Message-ID: <006f01c1e57a$4ce8caa0$6717c786@ottawa.mitel.com>
From: "Eric Cooper" <eric_cooper@Mitel.COM>
To: <megaco@ietf.org>
Date: Tue, 16 Apr 2002 15:08:12 -0400
Organization: Mitel Networks
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.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA08001
Subject: [Megaco] Default Event Detection
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 last statement of the call flow example in the spec states:

23.  The MGC now sets up both MG1 and MG2 to be ready to detect the next off-hook event. See step 1. Note that this could be the default state of a termination in the null context, and if this were the case, no message need be sent from the MGC to the MG. Once a termination returns to the null context, it goes back to the default termination values for that termination. 

My question is:  Does the protocol allow me to set the default state of a termination in the null context to include detection of off-hook events, or is that done through non-Megaco provisioning?  

Other statements in the text lead me to believe that a termination's Event descriptor returns to empty/"no value" when it enters the null context, so I guess this would be a non-Megaco provisioning activity, but I wanted to check.

Thanks,

Eric.
    


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


From daemon@ns.ietf.org  Tue Apr 16 15:28: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 PAA07721
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 15:28:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA09162
	for megaco-archive@odin.ietf.org; Tue, 16 Apr 2002 15:28:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08029;
	Tue, 16 Apr 2002 15:10:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08000
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 15:10:03 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05598
	for <megaco@ietf.org>; Tue, 16 Apr 2002 15:09:59 -0400 (EDT)
Received: from Software.Mitel.COM (software [134.199.30.49]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id PAA07821
	for <megaco@ietf.org>; Tue, 16 Apr 2002 15:09:32 -0400 (EDT)
Received: from pc3027 (gx-sup26.software.mitel.com [134.199.23.103])
        by Software.Mitel.COM (V8/MAIL-HUB-2.0) with SMTP id PAA05368
	for <megaco@ietf.org>; Tue, 16 Apr 2002 15:09:31 -0400 (EDT)
Message-ID: <006f01c1e57a$4ce8caa0$6717c786@ottawa.mitel.com>
From: "Eric Cooper" <eric_cooper@Mitel.COM>
To: <megaco@ietf.org>
Date: Tue, 16 Apr 2002 15:08:12 -0400
Organization: Mitel Networks
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.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA08001
Subject: [Megaco] Default Event Detection
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 last statement of the call flow example in the spec states:

23.  The MGC now sets up both MG1 and MG2 to be ready to detect the next off-hook event. See step 1. Note that this could be the default state of a termination in the null context, and if this were the case, no message need be sent from the MGC to the MG. Once a termination returns to the null context, it goes back to the default termination values for that termination. 

My question is:  Does the protocol allow me to set the default state of a termination in the null context to include detection of off-hook events, or is that done through non-Megaco provisioning?  

Other statements in the text lead me to believe that a termination's Event descriptor returns to empty/"no value" when it enters the null context, so I guess this would be a non-Megaco provisioning activity, but I wanted to check.

Thanks,

Eric.
    


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



From megaco-admin@ietf.org  Tue Apr 16 15: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 PAA09124
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 15:41:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA09111;
	Tue, 16 Apr 2002 15:27:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA09083
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 15:27:03 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07581
	for <megaco@ietf.org>; Tue, 16 Apr 2002 15:27:00 -0400 (EDT)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id PAA10565
	for <megaco@ietf.org>; Tue, 16 Apr 2002 15:26:31 -0400 (EDT)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2751AAVT>; Tue, 16 Apr 2002 15:26:31 -0400
Message-ID: <29B5A21C13C8D51190F900805F65B4EC506F05@rndex50.ottawa.mitel.com>
From: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 16 Apr 2002 15:26:22 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] ServiceChange for a single termination (Cold Start)
Sender: megaco-admin@ietf.org
Errors-To: 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,

	Assuming a Gateway with 2 terminations, one of them is OK and the other is Malfunctioning. How should I proceed if I want to bring just the working termination up (Cold Start)?

a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination

b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below) 

"The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"

Thanks,
Glauco

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


From daemon@ns.ietf.org  Tue Apr 16 15: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 PAA09133
	for <megaco-archive@odin.ietf.org>; Tue, 16 Apr 2002 15:41:37 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA10156
	for megaco-archive@odin.ietf.org; Tue, 16 Apr 2002 15:41:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA09111;
	Tue, 16 Apr 2002 15:27:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA09083
	for <megaco@ns.ietf.org>; Tue, 16 Apr 2002 15:27:03 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07581
	for <megaco@ietf.org>; Tue, 16 Apr 2002 15:27:00 -0400 (EDT)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id PAA10565
	for <megaco@ietf.org>; Tue, 16 Apr 2002 15:26:31 -0400 (EDT)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2751AAVT>; Tue, 16 Apr 2002 15:26:31 -0400
Message-ID: <29B5A21C13C8D51190F900805F65B4EC506F05@rndex50.ottawa.mitel.com>
From: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 16 Apr 2002 15:26:22 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] ServiceChange for a single termination (Cold Start)
Sender: megaco-admin@ietf.org
Errors-To: 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,

	Assuming a Gateway with 2 terminations, one of them is OK and the other is Malfunctioning. How should I proceed if I want to bring just the working termination up (Cold Start)?

a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination

b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below) 

"The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"

Thanks,
Glauco

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



From megaco-admin@ietf.org  Wed Apr 17 02:02: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 CAA06192
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 02:02:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA16298;
	Wed, 17 Apr 2002 01:37:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA16269
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 01:37:32 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02485
	for <megaco@ietf.org>; Wed, 17 Apr 2002 01:37:25 -0400 (EDT)
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 g3H5bO3G000276;
	Wed, 17 Apr 2002 07:37:24 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3H5bNo5006657;
	Wed, 17 Apr 2002 08:37:24 +0300 (EET DST)
Message-ID: <3CBD0A17.68E8CB58@lmf.ericsson.se>
Date: Wed, 17 Apr 2002 08:37:27 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F05@rndex50.ottawa.mitel.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,

>         Assuming a Gateway with 2 terminations, one of them is OK and the other is Malfunctioning. How should I proceed if I want to bring just the working termination up (Cold Start)?
>
> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination

I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.

Regards,

Christer Holmberg
Ericsson Finland




>
>
> b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
>
> "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
>
> Thanks,
> Glauco
>
> _______________________________________________
> Megaco mailing list
> 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 Apr 17 02:02: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 CAA06210
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 02:02:40 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA17586
	for megaco-archive@odin.ietf.org; Wed, 17 Apr 2002 02:02:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA16298;
	Wed, 17 Apr 2002 01:37:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA16269
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 01:37:32 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02485
	for <megaco@ietf.org>; Wed, 17 Apr 2002 01:37:25 -0400 (EDT)
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 g3H5bO3G000276;
	Wed, 17 Apr 2002 07:37:24 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3H5bNo5006657;
	Wed, 17 Apr 2002 08:37:24 +0300 (EET DST)
Message-ID: <3CBD0A17.68E8CB58@lmf.ericsson.se>
Date: Wed, 17 Apr 2002 08:37:27 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F05@rndex50.ottawa.mitel.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,

>         Assuming a Gateway with 2 terminations, one of them is OK and the other is Malfunctioning. How should I proceed if I want to bring just the working termination up (Cold Start)?
>
> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination

I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.

Regards,

Christer Holmberg
Ericsson Finland




>
>
> b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
>
> "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
>
> Thanks,
> Glauco
>
> _______________________________________________
> Megaco mailing list
> 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 Apr 17 04:04: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 EAA12274
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 04:04:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22572;
	Wed, 17 Apr 2002 03:46:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22549
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 03:45:58 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12044
	for <megaco@ietf.org>; Wed, 17 Apr 2002 03:45:54 -0400 (EDT)
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 g3H7jo3G004923;
	Wed, 17 Apr 2002 09:45:51 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3H7joo5015988;
	Wed, 17 Apr 2002 10:45:50 +0300 (EET DST)
Message-ID: <3CBD2831.1BC3317@lmf.ericsson.se>
Date: Wed, 17 Apr 2002 10:45:53 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Fernando Vallejo Lazaro <Fernando.Vallejo_Lazaro@alcatel.es>
CC: "Barcotti, Glauco" <Glauco_Barcotti@mitel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F05@rndex50.ottawa.mitel.com> <3CBD0A17.68E8CB58@lmf.ericsson.se> <3CBD22CF.93948686@alcatel.es>
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,

>> >         Assuming a Gateway with 2 terminations, one of them is OK
>> and the other is Malfunctioning. How should I proceed if I want to
>> bring just the working termination up (Cold Start)?
>> >
>> > a) If a ServiceChange is issued for ROOT termination MGC will
>> think that all terminations are up and, until another ServiceChange
>> is issued taking the defective Termination out of service, a call
>> could be attempted on that defective termination
>>
>> I don't agree. A ServiceChange for ROOT will indicate that the MG is
>> up, not specific terminations. You would then have to send additonal
>> ServiceChange commands, with Reason code 900, for each termination
>> you want to put in-service.
>>
>
> I don't agree. I think that when the MG issues a Service Change
> Restart the MGC must assume that all terminations are by default up
> and running. So if you have a termination out of service you should
> only send one Service Change Forced for that termination.
> Imagine a MG with 1000 terminations, if you send a Service Change
> Restart for each one you can have avalanche problems. We can suppose
> that a termination out of service is going to
> happen in much less ocassions.

You don't have to send a SeriveChange for each termination. You can use
wildcards.

One possibility could be to specify different meaning of Warm- and Cold
boot also for the MG startup. If the MGC gets a
ServiceChange/Root/Warmboot we could assume that the terminations are
"in-service", but if we get a ServiceChange/Root/Coldboot the
terminations must be put "in-service" using separate ServiceChanges.
Just some thoughts...

Regards,

Christer Holmberg
Ericsson Finland



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


From daemon@optimus.ietf.org  Wed Apr 17 04:04: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 EAA12285
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 04:04:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA23707
	for megaco-archive@odin.ietf.org; Wed, 17 Apr 2002 04:04:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22572;
	Wed, 17 Apr 2002 03:46:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22549
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 03:45:58 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12044
	for <megaco@ietf.org>; Wed, 17 Apr 2002 03:45:54 -0400 (EDT)
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 g3H7jo3G004923;
	Wed, 17 Apr 2002 09:45:51 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3H7joo5015988;
	Wed, 17 Apr 2002 10:45:50 +0300 (EET DST)
Message-ID: <3CBD2831.1BC3317@lmf.ericsson.se>
Date: Wed, 17 Apr 2002 10:45:53 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Fernando Vallejo Lazaro <Fernando.Vallejo_Lazaro@alcatel.es>
CC: "Barcotti, Glauco" <Glauco_Barcotti@mitel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F05@rndex50.ottawa.mitel.com> <3CBD0A17.68E8CB58@lmf.ericsson.se> <3CBD22CF.93948686@alcatel.es>
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,

>> >         Assuming a Gateway with 2 terminations, one of them is OK
>> and the other is Malfunctioning. How should I proceed if I want to
>> bring just the working termination up (Cold Start)?
>> >
>> > a) If a ServiceChange is issued for ROOT termination MGC will
>> think that all terminations are up and, until another ServiceChange
>> is issued taking the defective Termination out of service, a call
>> could be attempted on that defective termination
>>
>> I don't agree. A ServiceChange for ROOT will indicate that the MG is
>> up, not specific terminations. You would then have to send additonal
>> ServiceChange commands, with Reason code 900, for each termination
>> you want to put in-service.
>>
>
> I don't agree. I think that when the MG issues a Service Change
> Restart the MGC must assume that all terminations are by default up
> and running. So if you have a termination out of service you should
> only send one Service Change Forced for that termination.
> Imagine a MG with 1000 terminations, if you send a Service Change
> Restart for each one you can have avalanche problems. We can suppose
> that a termination out of service is going to
> happen in much less ocassions.

You don't have to send a SeriveChange for each termination. You can use
wildcards.

One possibility could be to specify different meaning of Warm- and Cold
boot also for the MG startup. If the MGC gets a
ServiceChange/Root/Warmboot we could assume that the terminations are
"in-service", but if we get a ServiceChange/Root/Coldboot the
terminations must be put "in-service" using separate ServiceChanges.
Just some thoughts...

Regards,

Christer Holmberg
Ericsson Finland



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



From megaco-admin@ietf.org  Wed Apr 17 10:30: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 KAA20344
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 10:30:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12134;
	Wed, 17 Apr 2002 10:11:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12106
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 10:11:13 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18913
	for <megaco@ietf.org>; Wed, 17 Apr 2002 10:11:08 -0400 (EDT)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id KAA09319;
	Wed, 17 Apr 2002 10:10:33 -0400 (EDT)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2751AF8N>; Wed, 17 Apr 2002 10:10:30 -0400
Message-ID: <29B5A21C13C8D51190F900805F65B4EC506F08@rndex50.ottawa.mitel.com>
From: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
Date: Wed, 17 Apr 2002 10:10:23 -0400
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,

>>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
>>
>> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination

>I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.

The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up? 

Thanks,
Glauco

>Regards,

>hrister Holmberg
>ricsson Finland




>
>
> b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
>
> "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
>
> Thanks,
> Glauco
>
> _______________________________________________
> Megaco mailing list
> 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 Apr 17 10:30: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 KAA20357
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 10:30:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA13669
	for megaco-archive@odin.ietf.org; Wed, 17 Apr 2002 10:30:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12134;
	Wed, 17 Apr 2002 10:11:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12106
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 10:11:13 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18913
	for <megaco@ietf.org>; Wed, 17 Apr 2002 10:11:08 -0400 (EDT)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id KAA09319;
	Wed, 17 Apr 2002 10:10:33 -0400 (EDT)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2751AF8N>; Wed, 17 Apr 2002 10:10:30 -0400
Message-ID: <29B5A21C13C8D51190F900805F65B4EC506F08@rndex50.ottawa.mitel.com>
From: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
Date: Wed, 17 Apr 2002 10:10:23 -0400
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,

>>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
>>
>> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination

>I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.

The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up? 

Thanks,
Glauco

>Regards,

>hrister Holmberg
>ricsson Finland




>
>
> b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
>
> "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
>
> Thanks,
> Glauco
>
> _______________________________________________
> Megaco mailing list
> 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 Apr 17 12:44: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 MAA26346
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 12:44:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23896;
	Wed, 17 Apr 2002 12:12:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23811
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 12:12:42 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24902
	for <megaco@ietf.org>; Wed, 17 Apr 2002 12:12:36 -0400 (EDT)
Received: from Software.Mitel.COM (software [134.199.30.49]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id MAA07380
	for <megaco@ietf.org>; Wed, 17 Apr 2002 12:08:43 -0400 (EDT)
Received: from pc3027 (gx-sup26.software.mitel.com [134.199.23.103])
        by Software.Mitel.COM (V8/MAIL-HUB-2.0) with SMTP id MAA21704
	for <megaco@ietf.org>; Wed, 17 Apr 2002 12:08:41 -0400 (EDT)
Message-ID: <00d401c1e62a$34e396f0$6717c786@ottawa.mitel.com>
From: "Eric Cooper" <eric_cooper@Mitel.COM>
To: <megaco@ietf.org>
Date: Wed, 17 Apr 2002 12:08:54 -0400
Organization: Mitel Networks
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.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA23816
Subject: [Megaco] Gain Control
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

Does the gain property in the TDM package refer to Tx, Rx, or both?

I dug through the archives and found that this was asked before, but I couldn't find the answer.

Thanks,

Eric Cooper.


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


From daemon@optimus.ietf.org  Wed Apr 17 12:44: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 MAA26357
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 12:44:18 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA28932
	for megaco-archive@odin.ietf.org; Wed, 17 Apr 2002 12:44:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23896;
	Wed, 17 Apr 2002 12:12:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23811
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 12:12:42 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24902
	for <megaco@ietf.org>; Wed, 17 Apr 2002 12:12:36 -0400 (EDT)
Received: from Software.Mitel.COM (software [134.199.30.49]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id MAA07380
	for <megaco@ietf.org>; Wed, 17 Apr 2002 12:08:43 -0400 (EDT)
Received: from pc3027 (gx-sup26.software.mitel.com [134.199.23.103])
        by Software.Mitel.COM (V8/MAIL-HUB-2.0) with SMTP id MAA21704
	for <megaco@ietf.org>; Wed, 17 Apr 2002 12:08:41 -0400 (EDT)
Message-ID: <00d401c1e62a$34e396f0$6717c786@ottawa.mitel.com>
From: "Eric Cooper" <eric_cooper@Mitel.COM>
To: <megaco@ietf.org>
Date: Wed, 17 Apr 2002 12:08:54 -0400
Organization: Mitel Networks
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.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA23816
Subject: [Megaco] Gain Control
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

Does the gain property in the TDM package refer to Tx, Rx, or both?

I dug through the archives and found that this was asked before, but I couldn't find the answer.

Thanks,

Eric Cooper.


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



From megaco-admin@ietf.org  Wed Apr 17 12:53: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 MAA26767
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 12:53:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA27847;
	Wed, 17 Apr 2002 12:32:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA21175
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 03:23:53 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11774
	for <megaco@ietf.org>; Wed, 17 Apr 2002 03:23:42 -0400 (EDT)
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 g3H7N8Y28956;
	Wed, 17 Apr 2002 09:23:08 +0200 (MEST)
Received: from alcatel.es (sevsf020 [159.23.195.20])
	by sers002.rpi.ses.alcatel.es (8.8.8+Sun/8.8.8) with ESMTP id JAA05787;
	Wed, 17 Apr 2002 09:22:52 +0200 (MET DST)
Message-ID: <3CBD22CF.93948686@alcatel.es>
Date: Wed, 17 Apr 2002 09:22:55 +0200
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: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: "Barcotti, Glauco" <Glauco_Barcotti@mitel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F05@rndex50.ottawa.mitel.com> <3CBD0A17.68E8CB58@lmf.ericsson.se>
Content-Type: multipart/alternative;
 boundary="------------18B6ED421714DBD3494697D1"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

Hi,

See my comments interleaved

Christer Holmberg wrote:

> Hi,
>
> >         Assuming a Gateway with 2 terminations, one of them is OK and the other is Malfunctioning. How should I proceed if I want to bring just the working termination up (Cold Start)?
> >
> > a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
>
> I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
>

I don't agree. I think that when the MG issues a Service Change Restart the MGC must assume that all terminations are by default up and running. So if you have a termination out of service you should only send one Service Change Forced for that
termination.
Imagine a MG with 1000 terminations, if you send a Service Change Restart for each one you can have avalanche problems. We can suppose that a termination out of service is going to
happen in much less ocassions.

Regards
Fernando


>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www1.ietf.org/mailman/listinfo/megaco
>
> _______________________________________________
> 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



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi,
<p>See my comments interleaved
<p>Christer Holmberg wrote:
<blockquote TYPE=CITE>Hi,
<p>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assuming a Gateway
with 2 terminations, one of them is OK and the other is Malfunctioning.
How should I proceed if I want to bring just the working termination up
(Cold Start)?
<br>>
<br>> a) If a ServiceChange is issued for ROOT termination MGC will think
that all terminations are up and, until another ServiceChange is issued
taking the defective Termination out of service, a call could be attempted
on that defective termination
<p>I don't agree. A ServiceChange for ROOT will indicate that the MG is
up, not specific terminations. You would then have to send additonal ServiceChange
commands, with Reason code 900, for each termination you want to put in-service.
<br>&nbsp;</blockquote>
I don't agree. I think that when the MG issues a Service Change Restart
the MGC must assume that all terminations are by default up and running.
So if you have a termination out of service you should only send one Service
Change Forced for that termination.
<br>Imagine a MG with 1000 terminations, if you send a Service Change Restart
for each one you can have avalanche problems. We can suppose that a termination
out of service is going to
<br>happen in much less ocassions.
<p>Regards
<br>Fernando
<br>&nbsp;
<blockquote TYPE=CITE>&nbsp;
<br>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<p>>
<br>>
<br>> b) If a ServiceChange is issued just for the working Termination
The ability to redirect the gateway to another MGC will be lost (See quotation
from spec below)
<br>>
<br>> "The return from ServiceChange is empty except when the Root terminationID
is used.&nbsp; In that case it includes the following parameters as required:"
<br>>
<br>> Thanks,
<br>> Glauco
<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>_______________________________________________
<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>

--------------18B6ED421714DBD3494697D1--



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


From daemon@optimus.ietf.org  Wed Apr 17 12:53: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 MAA26779
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 12:53:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA29435
	for megaco-archive@odin.ietf.org; Wed, 17 Apr 2002 12:53:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA27847;
	Wed, 17 Apr 2002 12:32:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA21175
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 03:23:53 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11774
	for <megaco@ietf.org>; Wed, 17 Apr 2002 03:23:42 -0400 (EDT)
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 g3H7N8Y28956;
	Wed, 17 Apr 2002 09:23:08 +0200 (MEST)
Received: from alcatel.es (sevsf020 [159.23.195.20])
	by sers002.rpi.ses.alcatel.es (8.8.8+Sun/8.8.8) with ESMTP id JAA05787;
	Wed, 17 Apr 2002 09:22:52 +0200 (MET DST)
Message-ID: <3CBD22CF.93948686@alcatel.es>
Date: Wed, 17 Apr 2002 09:22:55 +0200
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: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: "Barcotti, Glauco" <Glauco_Barcotti@mitel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F05@rndex50.ottawa.mitel.com> <3CBD0A17.68E8CB58@lmf.ericsson.se>
Content-Type: multipart/alternative;
 boundary="------------18B6ED421714DBD3494697D1"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

Hi,

See my comments interleaved

Christer Holmberg wrote:

> Hi,
>
> >         Assuming a Gateway with 2 terminations, one of them is OK and the other is Malfunctioning. How should I proceed if I want to bring just the working termination up (Cold Start)?
> >
> > a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
>
> I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
>

I don't agree. I think that when the MG issues a Service Change Restart the MGC must assume that all terminations are by default up and running. So if you have a termination out of service you should only send one Service Change Forced for that
termination.
Imagine a MG with 1000 terminations, if you send a Service Change Restart for each one you can have avalanche problems. We can suppose that a termination out of service is going to
happen in much less ocassions.

Regards
Fernando


>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www1.ietf.org/mailman/listinfo/megaco
>
> _______________________________________________
> 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



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi,
<p>See my comments interleaved
<p>Christer Holmberg wrote:
<blockquote TYPE=CITE>Hi,
<p>>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assuming a Gateway
with 2 terminations, one of them is OK and the other is Malfunctioning.
How should I proceed if I want to bring just the working termination up
(Cold Start)?
<br>>
<br>> a) If a ServiceChange is issued for ROOT termination MGC will think
that all terminations are up and, until another ServiceChange is issued
taking the defective Termination out of service, a call could be attempted
on that defective termination
<p>I don't agree. A ServiceChange for ROOT will indicate that the MG is
up, not specific terminations. You would then have to send additonal ServiceChange
commands, with Reason code 900, for each termination you want to put in-service.
<br>&nbsp;</blockquote>
I don't agree. I think that when the MG issues a Service Change Restart
the MGC must assume that all terminations are by default up and running.
So if you have a termination out of service you should only send one Service
Change Forced for that termination.
<br>Imagine a MG with 1000 terminations, if you send a Service Change Restart
for each one you can have avalanche problems. We can suppose that a termination
out of service is going to
<br>happen in much less ocassions.
<p>Regards
<br>Fernando
<br>&nbsp;
<blockquote TYPE=CITE>&nbsp;
<br>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<p>>
<br>>
<br>> b) If a ServiceChange is issued just for the working Termination
The ability to redirect the gateway to another MGC will be lost (See quotation
from spec below)
<br>>
<br>> "The return from ServiceChange is empty except when the Root terminationID
is used.&nbsp; In that case it includes the following parameters as required:"
<br>>
<br>> Thanks,
<br>> Glauco
<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>_______________________________________________
<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>

--------------18B6ED421714DBD3494697D1--



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



From megaco-admin@ietf.org  Wed Apr 17 13:08: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 NAA27507
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 13:08:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA29080;
	Wed, 17 Apr 2002 12:48:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA29050
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 12:48:51 -0400 (EDT)
Received: from mail1.hd.intel.com (hdfdns01.hd.intel.com [192.52.58.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26504
	for <megaco@ietf.org>; Wed, 17 Apr 2002 12:48:47 -0400 (EDT)
Received: from pysmsxvs01.py.intel.com (pysmsxvs01.py.intel.com [146.152.3.51])
	by mail1.hd.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.34 2002/04/15 17:47:41 root Exp $) with SMTP id g3HGmJW00709
	for <megaco@ietf.org>; Wed, 17 Apr 2002 16:48:19 GMT
Received: from pysmsx030.py.intel.com ([146.152.3.52])
 by pysmsxvs01.py.intel.com (NAVGW 2.5.1.16) with SMTP id M2002041712481026027
 ; Wed, 17 Apr 2002 12:48:10 -0400
Received: by pysmsx030.py.intel.com with Internet Mail Service (5.5.2653.19)
	id <HCXZCK1Y>; Wed, 17 Apr 2002 12:48:10 -0400
Message-ID: <3D90571297ABD511957400508BF29C4301B9EEFF@pysmsx101.py.intel.com>
From: "Miao, Kai" <kai.miao@intel.com>
To: "'Eric Cooper'" <eric_cooper@mitel.com>, megaco@ietf.org
Subject: RE: [Megaco] Gain Control
Date: Wed, 17 Apr 2002 12:48:04 -0400
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

Should gain control of Rx be a property of RTP rather than TDM?

Kai Miao

-----Original Message-----
From: Eric Cooper [mailto:eric_cooper@mitel.com]
Sent: Wednesday, April 17, 2002 12:09 PM
To: megaco@ietf.org
Subject: [Megaco] Gain Control


Does the gain property in the TDM package refer to Tx, Rx, or both?

I dug through the archives and found that this was asked before, but I
couldn't find the answer.

Thanks,

Eric Cooper.


_______________________________________________
Megaco mailing list
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 Apr 17 13:08: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 NAA27518
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 13:08:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA00586
	for megaco-archive@odin.ietf.org; Wed, 17 Apr 2002 13:08:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA29080;
	Wed, 17 Apr 2002 12:48:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA29050
	for <megaco@optimus.ietf.org>; Wed, 17 Apr 2002 12:48:51 -0400 (EDT)
Received: from mail1.hd.intel.com (hdfdns01.hd.intel.com [192.52.58.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26504
	for <megaco@ietf.org>; Wed, 17 Apr 2002 12:48:47 -0400 (EDT)
Received: from pysmsxvs01.py.intel.com (pysmsxvs01.py.intel.com [146.152.3.51])
	by mail1.hd.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.34 2002/04/15 17:47:41 root Exp $) with SMTP id g3HGmJW00709
	for <megaco@ietf.org>; Wed, 17 Apr 2002 16:48:19 GMT
Received: from pysmsx030.py.intel.com ([146.152.3.52])
 by pysmsxvs01.py.intel.com (NAVGW 2.5.1.16) with SMTP id M2002041712481026027
 ; Wed, 17 Apr 2002 12:48:10 -0400
Received: by pysmsx030.py.intel.com with Internet Mail Service (5.5.2653.19)
	id <HCXZCK1Y>; Wed, 17 Apr 2002 12:48:10 -0400
Message-ID: <3D90571297ABD511957400508BF29C4301B9EEFF@pysmsx101.py.intel.com>
From: "Miao, Kai" <kai.miao@intel.com>
To: "'Eric Cooper'" <eric_cooper@mitel.com>, megaco@ietf.org
Subject: RE: [Megaco] Gain Control
Date: Wed, 17 Apr 2002 12:48:04 -0400
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

Should gain control of Rx be a property of RTP rather than TDM?

Kai Miao

-----Original Message-----
From: Eric Cooper [mailto:eric_cooper@mitel.com]
Sent: Wednesday, April 17, 2002 12:09 PM
To: megaco@ietf.org
Subject: [Megaco] Gain Control


Does the gain property in the TDM package refer to Tx, Rx, or both?

I dug through the archives and found that this was asked before, but I
couldn't find the answer.

Thanks,

Eric Cooper.


_______________________________________________
Megaco mailing list
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 Apr 17 20:28: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 UAA11774
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 20:28:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA28722;
	Wed, 17 Apr 2002 20:02:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA28691
	for <megaco@ns.ietf.org>; Wed, 17 Apr 2002 20:02:02 -0400 (EDT)
Received: from cms3.etri.re.kr (cms3.etri.re.kr [129.254.16.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11468
	for <megaco@ietf.org>; Wed, 17 Apr 2002 20:01:58 -0400 (EDT)
From: hektor@etri.re.kr
Received: by cms3.etri.re.kr with Internet Mail Service (5.5.2653.19)
	id <HNZRBBFD>; Thu, 18 Apr 2002 09:01:53 +0900
Message-ID: <8470181DABD5D511B3E700D0B7A8AC4A5DA37A@cms3.etri.re.kr>
To: megaco@ietf.org
Date: Thu, 18 Apr 2002 09:01:52 +0900
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E66C.3EA82D30"
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_01C1E66C.3EA82D30
Content-Type: text/plain;
	charset="euc-kr"

hi, list

 

I have some questions about mode in localcontrol descriptor.
could you please clear my head?
see following examples(let's assume this can be happened in Trunking
gateway using IP Packet network)



                                 ctx1
                          --------------------------
pstn network --     pstn term ---  eph term         --- IP network 
                          --------------------------

 

    pstn term.          ephemeral term.
-------------------------------------------------------------------------
      recv only         recv only            ---1)
      recv only         send only           ---2)
      recv only         sendreceive        ---3)
      send only        recv only            ---4)
      send only        send only           ---5)
      send only        sendreceive        --6)
      sendreceive     recv only            --7)
      sendreceive     send only           --8)
      sendreceive     sendreceive       --9)
 

follwoing the way of undestanding is correct?

1) means
   It can receive data from LEX, but can not transfer over IP to peer MG.
   It can receive data from peer MG, but can not transfer to PSTN network.

2) means
   It can receive data from LEX, and can transfer data over IP to peer MG.
   it can receive data from peer MG, but can not transfer to PSTN network.
3) means
   It can receive data from LEX, and can transfer data over IP to peer MG.
   It can receive data from peer MG, but can not transfer to PSTN network.
4), 5), 6) means
   It can receive data from LEX,  but can not transfer data over IP to peer
MG regardless mode of  ephemeral termination.
   but in case 4) :
                         It can receive data from peer MG and also can
transfer that data to PSTN network.
   but in case 5) : 
                         It can receive data from peer MG but can not
transfer that data to PSTN network.
   but in case 6) :
                         It can receive data from peer MG and also can
transfer that data to PSTN network
7) means
   It can receive data from LEX, but can not transfer that data over IP to
peer MG.
   It can receive data from peer MG, and also can transfer that data to
PSTN network.

8) means
   It can receive data from LEX, and also can transfer that data over IP to
peer MG.
   It can receive data from peer MG, but can not transfer that data to PSTN
network
9) means
   full duplex mode.
 

thanks in advance.

------_=_NextPart_001_01C1E66C.3EA82D30
Content-Type: text/html;
	charset="euc-kr"
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=3Deuc-kr">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE></TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>hi, list</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>I have some questions about mode in localcontrol =
descriptor.</FONT>
<BR><FONT SIZE=3D2>could you please clear my head?</FONT>
<BR><FONT SIZE=3D2>see following examples(let's assume this can be =
happened in Trunking gateway using IP Packet network)</FONT>
</P>
<BR>
<BR>

<P><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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ctx1</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; --------------------------</FONT>
<BR><FONT SIZE=3D2>pstn network --&nbsp;&nbsp;&nbsp;&nbsp; pstn term =
---&nbsp; eph term&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --- =
IP network </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; --------------------------</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; pstn =
term.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ephemeral =
term.</FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------=
----------</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---1)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---2)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ---3)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---4)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---5)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --6)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
--7)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
--8)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --9)</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>follwoing the way of undestanding is correct?</FONT>
</P>

<P><FONT SIZE=3D2>1) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX, but can =
not transfer over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from peer MG, but =
can not transfer to PSTN network.</FONT>
</P>

<P><FONT SIZE=3D2>2) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX, and can =
transfer data over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; it can receive data from peer MG, but =
can not transfer to PSTN network.</FONT>
<BR><FONT SIZE=3D2>3) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX, and can =
transfer data over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from peer MG, but =
can not transfer to PSTN network.</FONT>
<BR><FONT SIZE=3D2>4), 5), 6) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX,&nbsp; but =
can not transfer data over IP to peer MG regardless mode of&nbsp; =
ephemeral termination.</FONT></P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; but in case 4) :</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; It can receive data from peer MG and also can transfer that =
data to PSTN network.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; but in case 5) : </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; It can receive data from peer MG but can not transfer that =
data to PSTN network.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; but in case 6) :</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; It can receive data from peer MG and also can transfer that =
data to PSTN network</FONT>
<BR><FONT SIZE=3D2>7) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX, but can =
not transfer that data over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from peer MG, and =
also can transfer that data to PSTN network.</FONT>
</P>

<P><FONT SIZE=3D2>8) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX, and also =
can transfer that data over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from peer MG, but =
can not transfer that data to PSTN network</FONT>
<BR><FONT SIZE=3D2>9) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; full duplex mode.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>thanks in advance.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E66C.3EA82D30--

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


From daemon@ns.ietf.org  Wed Apr 17 20:28: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 UAA11786
	for <megaco-archive@odin.ietf.org>; Wed, 17 Apr 2002 20:28:19 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA29713
	for megaco-archive@odin.ietf.org; Wed, 17 Apr 2002 20:28:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA28722;
	Wed, 17 Apr 2002 20:02:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA28691
	for <megaco@ns.ietf.org>; Wed, 17 Apr 2002 20:02:02 -0400 (EDT)
Received: from cms3.etri.re.kr (cms3.etri.re.kr [129.254.16.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11468
	for <megaco@ietf.org>; Wed, 17 Apr 2002 20:01:58 -0400 (EDT)
From: hektor@etri.re.kr
Received: by cms3.etri.re.kr with Internet Mail Service (5.5.2653.19)
	id <HNZRBBFD>; Thu, 18 Apr 2002 09:01:53 +0900
Message-ID: <8470181DABD5D511B3E700D0B7A8AC4A5DA37A@cms3.etri.re.kr>
To: megaco@ietf.org
Date: Thu, 18 Apr 2002 09:01:52 +0900
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E66C.3EA82D30"
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_01C1E66C.3EA82D30
Content-Type: text/plain;
	charset="euc-kr"

hi, list

 

I have some questions about mode in localcontrol descriptor.
could you please clear my head?
see following examples(let's assume this can be happened in Trunking
gateway using IP Packet network)



                                 ctx1
                          --------------------------
pstn network --     pstn term ---  eph term         --- IP network 
                          --------------------------

 

    pstn term.          ephemeral term.
-------------------------------------------------------------------------
      recv only         recv only            ---1)
      recv only         send only           ---2)
      recv only         sendreceive        ---3)
      send only        recv only            ---4)
      send only        send only           ---5)
      send only        sendreceive        --6)
      sendreceive     recv only            --7)
      sendreceive     send only           --8)
      sendreceive     sendreceive       --9)
 

follwoing the way of undestanding is correct?

1) means
   It can receive data from LEX, but can not transfer over IP to peer MG.
   It can receive data from peer MG, but can not transfer to PSTN network.

2) means
   It can receive data from LEX, and can transfer data over IP to peer MG.
   it can receive data from peer MG, but can not transfer to PSTN network.
3) means
   It can receive data from LEX, and can transfer data over IP to peer MG.
   It can receive data from peer MG, but can not transfer to PSTN network.
4), 5), 6) means
   It can receive data from LEX,  but can not transfer data over IP to peer
MG regardless mode of  ephemeral termination.
   but in case 4) :
                         It can receive data from peer MG and also can
transfer that data to PSTN network.
   but in case 5) : 
                         It can receive data from peer MG but can not
transfer that data to PSTN network.
   but in case 6) :
                         It can receive data from peer MG and also can
transfer that data to PSTN network
7) means
   It can receive data from LEX, but can not transfer that data over IP to
peer MG.
   It can receive data from peer MG, and also can transfer that data to
PSTN network.

8) means
   It can receive data from LEX, and also can transfer that data over IP to
peer MG.
   It can receive data from peer MG, but can not transfer that data to PSTN
network
9) means
   full duplex mode.
 

thanks in advance.

------_=_NextPart_001_01C1E66C.3EA82D30
Content-Type: text/html;
	charset="euc-kr"
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=3Deuc-kr">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE></TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>hi, list</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>I have some questions about mode in localcontrol =
descriptor.</FONT>
<BR><FONT SIZE=3D2>could you please clear my head?</FONT>
<BR><FONT SIZE=3D2>see following examples(let's assume this can be =
happened in Trunking gateway using IP Packet network)</FONT>
</P>
<BR>
<BR>

<P><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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ctx1</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; --------------------------</FONT>
<BR><FONT SIZE=3D2>pstn network --&nbsp;&nbsp;&nbsp;&nbsp; pstn term =
---&nbsp; eph term&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --- =
IP network </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; --------------------------</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; pstn =
term.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ephemeral =
term.</FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------=
----------</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---1)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---2)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ---3)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---4)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---5)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --6)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
--7)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
--8)</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --9)</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>follwoing the way of undestanding is correct?</FONT>
</P>

<P><FONT SIZE=3D2>1) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX, but can =
not transfer over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from peer MG, but =
can not transfer to PSTN network.</FONT>
</P>

<P><FONT SIZE=3D2>2) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX, and can =
transfer data over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; it can receive data from peer MG, but =
can not transfer to PSTN network.</FONT>
<BR><FONT SIZE=3D2>3) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX, and can =
transfer data over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from peer MG, but =
can not transfer to PSTN network.</FONT>
<BR><FONT SIZE=3D2>4), 5), 6) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX,&nbsp; but =
can not transfer data over IP to peer MG regardless mode of&nbsp; =
ephemeral termination.</FONT></P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; but in case 4) :</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; It can receive data from peer MG and also can transfer that =
data to PSTN network.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; but in case 5) : </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; It can receive data from peer MG but can not transfer that =
data to PSTN network.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; but in case 6) :</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; It can receive data from peer MG and also can transfer that =
data to PSTN network</FONT>
<BR><FONT SIZE=3D2>7) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX, but can =
not transfer that data over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from peer MG, and =
also can transfer that data to PSTN network.</FONT>
</P>

<P><FONT SIZE=3D2>8) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from LEX, and also =
can transfer that data over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; It can receive data from peer MG, but =
can not transfer that data to PSTN network</FONT>
<BR><FONT SIZE=3D2>9) means</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; full duplex mode.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>thanks in advance.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E66C.3EA82D30--

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



From megaco-admin@ietf.org  Thu Apr 18 02: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 CAA26693
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 02:08:50 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25868;
	Thu, 18 Apr 2002 01:53:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25842
	for <megaco@ns.ietf.org>; Thu, 18 Apr 2002 01:53:15 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18214
	for <megaco@ietf.org>; Thu, 18 Apr 2002 01:53:11 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3I5rAs7014505;
	Thu, 18 Apr 2002 07:53:11 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3I5rAo5021162;
	Thu, 18 Apr 2002 08:53:10 +0300 (EET DST)
Message-ID: <3CBE5F4B.C53A9F2@lmf.ericsson.se>
Date: Thu, 18 Apr 2002 08:53:15 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F08@rndex50.ottawa.mitel.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,

> Hi,
>
> >>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
> >>
> >> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
>
> >I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
>
> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up?

Assume my MG comes up, but for whatever reason I don't have TDM interface card X available, so those timeslots/terminations are not available. Now, to tell the MGC that there are two options:

1. I configure the MGC manually not to use those terminations.

2. The MGC will have to do Audit to find out which terminations are in servce.

Now, I don't like option 1.

And, when card X is put back into service, or I put a new card in my MG, there will have to be ServiceChanges for those terminations anyway, because I don't think we can assume the MGC to Audit the MG all the time.

Also, if I have a very big MG it may take different time before all interfaces are up. But, I still want to start using some interfaces, so I don't want to wait with the registration ServiceChange until all interfaces are up. But, again, the MGC would now have to start doing frequent Audits, to find out which interfaces are up, and
which are not, until it realizes all terminations are up.

Chapter 6.2.5 defines that the ROOT specify the whole MG, rather than specific terminations. My understanding is that it does NOT say that includes the terminations. Also, how would you define the difference between TerminationID=ROOT and TerminationID=ALL???

Also, IF ROOT would include all terminations, why am I not to send a Subtract with ContextID=ALL and TerminationID=ROOT???

Regards,

Christer Holmberg
Ericsson Finland









>
>
> Thanks,
> Glauco
>
> >Regards,
>
> >hrister Holmberg
> >ricsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing list
> > 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 Apr 18 02: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 CAA26704
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 02:08:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA26908
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 02:08:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25868;
	Thu, 18 Apr 2002 01:53:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25842
	for <megaco@ns.ietf.org>; Thu, 18 Apr 2002 01:53:15 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18214
	for <megaco@ietf.org>; Thu, 18 Apr 2002 01:53:11 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3I5rAs7014505;
	Thu, 18 Apr 2002 07:53:11 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3I5rAo5021162;
	Thu, 18 Apr 2002 08:53:10 +0300 (EET DST)
Message-ID: <3CBE5F4B.C53A9F2@lmf.ericsson.se>
Date: Thu, 18 Apr 2002 08:53:15 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F08@rndex50.ottawa.mitel.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,

> Hi,
>
> >>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
> >>
> >> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
>
> >I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
>
> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up?

Assume my MG comes up, but for whatever reason I don't have TDM interface card X available, so those timeslots/terminations are not available. Now, to tell the MGC that there are two options:

1. I configure the MGC manually not to use those terminations.

2. The MGC will have to do Audit to find out which terminations are in servce.

Now, I don't like option 1.

And, when card X is put back into service, or I put a new card in my MG, there will have to be ServiceChanges for those terminations anyway, because I don't think we can assume the MGC to Audit the MG all the time.

Also, if I have a very big MG it may take different time before all interfaces are up. But, I still want to start using some interfaces, so I don't want to wait with the registration ServiceChange until all interfaces are up. But, again, the MGC would now have to start doing frequent Audits, to find out which interfaces are up, and
which are not, until it realizes all terminations are up.

Chapter 6.2.5 defines that the ROOT specify the whole MG, rather than specific terminations. My understanding is that it does NOT say that includes the terminations. Also, how would you define the difference between TerminationID=ROOT and TerminationID=ALL???

Also, IF ROOT would include all terminations, why am I not to send a Subtract with ContextID=ALL and TerminationID=ROOT???

Regards,

Christer Holmberg
Ericsson Finland









>
>
> Thanks,
> Glauco
>
> >Regards,
>
> >hrister Holmberg
> >ricsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing list
> > 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 Apr 18 02: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 CAA27021
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 02:33:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27342;
	Thu, 18 Apr 2002 02:16:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27227
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 02:16:48 -0400 (EDT)
Received: from mailgate.sbell.com.cn (mailgate.sbell.com.cn [202.96.203.173])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26809
	for <megaco@ietf.org>; Thu, 18 Apr 2002 02:16:41 -0400 (EDT)
Received: from bellnet-mail4.sbell.com.cn (bellnet-mail4.sbell.com.cn [202.96.203.174])
	by mailgate.sbell.com.cn (8.9.2/8.9.2) with ESMTP id OAA21464;
	Thu, 18 Apr 2002 14:03:00 +0800 (CST)
Received: from bellnet-mail1.sbell.com.cn ([202.96.203.171]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 18 Apr 2002 14:14:35 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Thu, 18 Apr 2002 14:13:10 +0800
Message-ID: <C65F869D22451348A9970B1670ED366301968CCA@bellnet-mail1.sbell.com.cn>
Thread-Topic: [Megaco] ServiceChange for a single termination (Cold Start)
Thread-Index: AcHmIAyORWvh5jUZRGedgrgRyVkKGAAfzttg
From: "SRD Wang JuLin" <WangJL2@sbell.com.cn>
To: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>,
        "Christer Holmberg" <christer.holmberg@lmf.ericsson.se>
Cc: <megaco@ietf.org>
X-OriginalArrivalTime: 18 Apr 2002 06:14:35.0874 (UTC) FILETIME=[5041F420:01C1E6A0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id CAA27228
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,
Well,I send the ServiceChange for Root to Softswitch,it only send 4 modify messages  to RGW.So i can only use 4 out of the 8 phones located in RGW.
(I had provisioned 8 terminations into Softswitch

)
16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
                         4500 008e 028b 0000 3f11 63de 0a0a 007a
                         0a0a 0069 2b72 0b80 007a d67f 212f 3120
                         5b31 302e 3130 2e30 2e31 3232 5d0a 543d
                         317b 433d 2d7b 5343 3d52 4f4f 547b 5356
                         7b4d 543d 5253 2c52 453d 3930 312c 4144
                         3d31 3131 3232 2c50 463d 416e 616c 6f67
                         5f4c 696e 655f 496e 7465 726f 7065 7261
                         6269 6c69 7479 5f54 6573 745f 5072 6f66
                         696c 652f 312c 563d 317d 7d7d 7d0a
 
                          E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
                         ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
                          [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
                          1 {  C =  - {  S C  = R  O O  T {  S V
                          { M  T =  R S  , R  E =  9 0  1 ,  A D
                          = 1  1 1  2 2  , P  F =  A n  a l  o g
                          _ L  i n  e _  I n  t e  r o  p e  r a
                          b i  l i  t y  _ T  e s  t _  P r  o f
                          i l  e /  1 ,  V =  1 }  } }  }^J
16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
                         4500 005a 2bdf 0000 4011 39be 0a0a 0069
                         0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
                         5b31 302e 3130 2e30 2e31 3035 5d20 503d
                         317b 433d 2d7b 5343 3d52 4f4f 547b 5356
                         7b41 443d 3131 3132 322c 5046 3d43 4c53
                         2f31 2c56 3d31 7d7d 7d7d
 
                          E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
                         ^J^J ^@ z ^K..  + r ^@ F ^ç¸™]  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
                          1 {  C =  - {  S C  = R  O O  T {  S V
                          { A  D =  1 1  1 2  2 ,  P F  = C  L S
                          / 1  , V  = 1  } }  } }
16:46:18.325927 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
                         4500 00c0 2bf3 0000 4011 3944 0a0a 0069
                         0a0a 007a 2b72 2b72 00ac 1537 212f 3120
                         5b31 302e 3130 2e30 2e31 3035 5d20 543d
                         3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 327b 453d 3538 3938 3239 7b61
                         6c2f 6f66 7b73 7472 6963 743d 6578 6163
                         742c 454d 7b53 477b 6367 2f64 747d 2c45
                         3d33 3933 3231 377b 6464 2f63 657b 2044
                         4d3d 6469 616c 706c 616e 317d 2c61 6c2f
                         6f6e 7b73 7472 6963 743d 6578 6163 747d
                         2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
                         7472 6963 743d 6578 6163 747d 7d7d 7d7d
 
                          E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
                         ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
                          4 2  0 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  2 {  E =  5 8  9 8  2 9  { a
                          l /  o f  { s  t r  i c  t =  e x  a c
                          t ,  E M  { S  G {  c g  / d  t }  , E
                          = 3  9 3  2 1  7 {  d d  / c  e {    D
                          M =  d i  a l  p l  a n  1 }  , a  l /
                          o n  { s  t r  i c  t =  e x  a c  t }
                          , g  / s  c }  } }  , a  l /  o n  { s
                          t r  i c  t =  e x  a c  t }  } }  } }
16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
                         4500 00c0 2bf9 0000 4011 393e 0a0a 0069
                         0a0a 007a 2b72 2b72 00ac 1337 212f 3120
                         5b31 302e 3130 2e30 2e31 3035 5d20 543d
                         3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 337b 453d 3538 3938 3239 7b61
                         6c2f 6f66 7b73 7472 6963 743d 6578 6163
                         742c 454d 7b53 477b 6367 2f64 747d 2c45
                         3d33 3933 3231 377b 6464 2f63 657b 2044
                         4d3d 6469 616c 706c 616e 317d 2c61 6c2f
                         6f6e 7b73 7472 6963 743d 6578 6163 747d
                         2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
                         7472 6963 743d 6578 6163 747d 7d7d 7d7d
 
                          E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
                         ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
                          4 2  1 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  3 {  E =  5 8  9 8  2 9  { a
                          l /  o f  { s  t r  i c  t =  e x  a c
                          t ,  E M  { S  G {  c g  / d  t }  , E
                          = 3  9 3  2 1  7 {  d d  / c  e {    D
                          M =  d i  a l  p l  a n  1 }  , a  l /
                          o n  { s  t r  i c  t =  e x  a c  t }
                          , g  / s  c }  } }  , a  l /  o n  { s
                          t r  i c  t =  e x  a c  t }  } }  } }
16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
                         4500 00c0 2c01 0000 4011 3936 0a0a 0069
                         0a0a 007a 2b72 2b72 00ac 1037 212f 3120
                         5b31 302e 3130 2e30 2e31 3035 5d20 543d
                         3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 357b 453d 3538 3938 3239 7b61
                         6c2f 6f66 7b73 7472 6963 743d 6578 6163
                         742c 454d 7b53 477b 6367 2f64 747d 2c45
                         3d33 3933 3231 377b 6464 2f63 657b 2044
                         4d3d 6469 616c 706c 616e 317d 2c61 6c2f
                         6f6e 7b73 7472 6963 743d 6578 6163 747d
                         2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
                         7472 6963 743d 6578 6163 747d 7d7d 7d7d
 
                          E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
                         ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
                          4 2  2 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  5 {  E =  5 8  9 8  2 9  { a
                          l /  o f  { s  t r  i c  t =  e x  a c
                          t ,  E M  { S  G {  c g  / d  t }  , E
                          = 3  9 3  2 1  7 {  d d  / c  e {    D
                          M =  d i  a l  p l  a n  1 }  , a  l /
                          o n  { s  t r  i c  t =  e x  a c  t }
                          , g  / s  c }  } }  , a  l /  o n  { s
                          t r  i c  t =  e x  a c  t }  } }  } }
16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
                         4500 00c0 2c04 0000 4011 3933 0a0a 0069
                         0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
                         5b31 302e 3130 2e30 2e31 3035 5d20 543d
                         3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 367b 453d 3538 3938 3239 7b61
                         6c2f 6f66 7b73 7472 6963 743d 6578 6163
                         742c 454d 7b53 477b 6367 2f64 747d 2c45
                         3d33 3933 3231 377b 6464 2f63 657b 2044
                         4d3d 6469 616c 706c 616e 317d 2c61 6c2f
                         6f6e 7b73 7472 6963 743d 6578 6163 747d
                         2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
                         7472 6963 743d 6578 6163 747d 7d7d 7d7d
 
                          E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
                         ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
                          4 2  3 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  6 {  E =  5 8  9 8  2 9  { a
                          l /  o f  { s  t r  i c  t =  e x  a c
                          t ,  E M  { S  G {  c g  / d  t }  , E
                          = 3  9 3  2 1  7 {  d d  / c  e {    D
                          M =  d i  a l  p l  a n  1 }  , a  l /
                          o n  { s  t r  i c  t =  e x  a c  t }
                          , g  / s  c }  } }  , a  l /  o n  { s
                          t r  i c  t =  e x  a c  t }  } }  } }
16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
                         4500 0062 0293 0000 3f11 6402 0a0a 007a
                         0a0a 0069 2b72 2b72 004e 705a 212f 3120
                         5b31 302e 3130 2e30 2e31 3232 5d0a 503d
                         3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 327d 7d0a 503d 3432 317b 433d
                         2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
                         7d0a
 
                          E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
                         ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
                          4 2  0 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  2 }  }^J  P =  4 2  1 {  C =
                          - {  M F  = a  g w  _ j  u l  w /  3 }
                          }^J
16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
                         4500 0062 0294 0000 3f11 6401 0a0a 007a
                         0a0a 0069 2b72 2b72 004e 665a 212f 3120
                         5b31 302e 3130 2e30 2e31 3232 5d0a 503d
                         3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 357d 7d0a 503d 3432 337b 433d
                         2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
                         7d0a
 
                          E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
                         ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
                          4 2  2 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  5 }  }^J  P =  4 2  3 {  C =
                          - {  M F  = a  g w  _ j  u l  w /  6 }
                          }^J
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

best  regards
> :-)Jerry Wang
tel:(8621)58541240 ext 9615
mailto:wangjl2@sbell.com.cn
Shanghai Bell Co.LTD



-----Original Message-----
From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
Sent: Wednesday, April 17, 2002 10:10 PM
To: 'Christer Holmberg'
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)


Hi,

>>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
>>
>> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination

>I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.

The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up? 

Thanks,
Glauco

>Regards,

>hrister Holmberg
>ricsson Finland




>
>
> b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
>
> "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
>
> Thanks,
> Glauco
>
> _______________________________________________
> Megaco mailing 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 Apr 18 02: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 CAA27032
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 02:33:01 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA28374
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 02:33:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27342;
	Thu, 18 Apr 2002 02:16:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27227
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 02:16:48 -0400 (EDT)
Received: from mailgate.sbell.com.cn (mailgate.sbell.com.cn [202.96.203.173])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26809
	for <megaco@ietf.org>; Thu, 18 Apr 2002 02:16:41 -0400 (EDT)
Received: from bellnet-mail4.sbell.com.cn (bellnet-mail4.sbell.com.cn [202.96.203.174])
	by mailgate.sbell.com.cn (8.9.2/8.9.2) with ESMTP id OAA21464;
	Thu, 18 Apr 2002 14:03:00 +0800 (CST)
Received: from bellnet-mail1.sbell.com.cn ([202.96.203.171]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 18 Apr 2002 14:14:35 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Thu, 18 Apr 2002 14:13:10 +0800
Message-ID: <C65F869D22451348A9970B1670ED366301968CCA@bellnet-mail1.sbell.com.cn>
Thread-Topic: [Megaco] ServiceChange for a single termination (Cold Start)
Thread-Index: AcHmIAyORWvh5jUZRGedgrgRyVkKGAAfzttg
From: "SRD Wang JuLin" <WangJL2@sbell.com.cn>
To: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>,
        "Christer Holmberg" <christer.holmberg@lmf.ericsson.se>
Cc: <megaco@ietf.org>
X-OriginalArrivalTime: 18 Apr 2002 06:14:35.0874 (UTC) FILETIME=[5041F420:01C1E6A0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id CAA27228
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,
Well,I send the ServiceChange for Root to Softswitch,it only send 4 modify messages  to RGW.So i can only use 4 out of the 8 phones located in RGW.
(I had provisioned 8 terminations into Softswitch

)
16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
                         4500 008e 028b 0000 3f11 63de 0a0a 007a
                         0a0a 0069 2b72 0b80 007a d67f 212f 3120
                         5b31 302e 3130 2e30 2e31 3232 5d0a 543d
                         317b 433d 2d7b 5343 3d52 4f4f 547b 5356
                         7b4d 543d 5253 2c52 453d 3930 312c 4144
                         3d31 3131 3232 2c50 463d 416e 616c 6f67
                         5f4c 696e 655f 496e 7465 726f 7065 7261
                         6269 6c69 7479 5f54 6573 745f 5072 6f66
                         696c 652f 312c 563d 317d 7d7d 7d0a
 
                          E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
                         ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
                          [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
                          1 {  C =  - {  S C  = R  O O  T {  S V
                          { M  T =  R S  , R  E =  9 0  1 ,  A D
                          = 1  1 1  2 2  , P  F =  A n  a l  o g
                          _ L  i n  e _  I n  t e  r o  p e  r a
                          b i  l i  t y  _ T  e s  t _  P r  o f
                          i l  e /  1 ,  V =  1 }  } }  }^J
16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
                         4500 005a 2bdf 0000 4011 39be 0a0a 0069
                         0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
                         5b31 302e 3130 2e30 2e31 3035 5d20 503d
                         317b 433d 2d7b 5343 3d52 4f4f 547b 5356
                         7b41 443d 3131 3132 322c 5046 3d43 4c53
                         2f31 2c56 3d31 7d7d 7d7d
 
                          E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
                         ^J^J ^@ z ^K..  + r ^@ F ^ç¸™]  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
                          1 {  C =  - {  S C  = R  O O  T {  S V
                          { A  D =  1 1  1 2  2 ,  P F  = C  L S
                          / 1  , V  = 1  } }  } }
16:46:18.325927 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
                         4500 00c0 2bf3 0000 4011 3944 0a0a 0069
                         0a0a 007a 2b72 2b72 00ac 1537 212f 3120
                         5b31 302e 3130 2e30 2e31 3035 5d20 543d
                         3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 327b 453d 3538 3938 3239 7b61
                         6c2f 6f66 7b73 7472 6963 743d 6578 6163
                         742c 454d 7b53 477b 6367 2f64 747d 2c45
                         3d33 3933 3231 377b 6464 2f63 657b 2044
                         4d3d 6469 616c 706c 616e 317d 2c61 6c2f
                         6f6e 7b73 7472 6963 743d 6578 6163 747d
                         2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
                         7472 6963 743d 6578 6163 747d 7d7d 7d7d
 
                          E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
                         ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
                          4 2  0 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  2 {  E =  5 8  9 8  2 9  { a
                          l /  o f  { s  t r  i c  t =  e x  a c
                          t ,  E M  { S  G {  c g  / d  t }  , E
                          = 3  9 3  2 1  7 {  d d  / c  e {    D
                          M =  d i  a l  p l  a n  1 }  , a  l /
                          o n  { s  t r  i c  t =  e x  a c  t }
                          , g  / s  c }  } }  , a  l /  o n  { s
                          t r  i c  t =  e x  a c  t }  } }  } }
16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
                         4500 00c0 2bf9 0000 4011 393e 0a0a 0069
                         0a0a 007a 2b72 2b72 00ac 1337 212f 3120
                         5b31 302e 3130 2e30 2e31 3035 5d20 543d
                         3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 337b 453d 3538 3938 3239 7b61
                         6c2f 6f66 7b73 7472 6963 743d 6578 6163
                         742c 454d 7b53 477b 6367 2f64 747d 2c45
                         3d33 3933 3231 377b 6464 2f63 657b 2044
                         4d3d 6469 616c 706c 616e 317d 2c61 6c2f
                         6f6e 7b73 7472 6963 743d 6578 6163 747d
                         2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
                         7472 6963 743d 6578 6163 747d 7d7d 7d7d
 
                          E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
                         ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
                          4 2  1 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  3 {  E =  5 8  9 8  2 9  { a
                          l /  o f  { s  t r  i c  t =  e x  a c
                          t ,  E M  { S  G {  c g  / d  t }  , E
                          = 3  9 3  2 1  7 {  d d  / c  e {    D
                          M =  d i  a l  p l  a n  1 }  , a  l /
                          o n  { s  t r  i c  t =  e x  a c  t }
                          , g  / s  c }  } }  , a  l /  o n  { s
                          t r  i c  t =  e x  a c  t }  } }  } }
16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
                         4500 00c0 2c01 0000 4011 3936 0a0a 0069
                         0a0a 007a 2b72 2b72 00ac 1037 212f 3120
                         5b31 302e 3130 2e30 2e31 3035 5d20 543d
                         3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 357b 453d 3538 3938 3239 7b61
                         6c2f 6f66 7b73 7472 6963 743d 6578 6163
                         742c 454d 7b53 477b 6367 2f64 747d 2c45
                         3d33 3933 3231 377b 6464 2f63 657b 2044
                         4d3d 6469 616c 706c 616e 317d 2c61 6c2f
                         6f6e 7b73 7472 6963 743d 6578 6163 747d
                         2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
                         7472 6963 743d 6578 6163 747d 7d7d 7d7d
 
                          E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
                         ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
                          4 2  2 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  5 {  E =  5 8  9 8  2 9  { a
                          l /  o f  { s  t r  i c  t =  e x  a c
                          t ,  E M  { S  G {  c g  / d  t }  , E
                          = 3  9 3  2 1  7 {  d d  / c  e {    D
                          M =  d i  a l  p l  a n  1 }  , a  l /
                          o n  { s  t r  i c  t =  e x  a c  t }
                          , g  / s  c }  } }  , a  l /  o n  { s
                          t r  i c  t =  e x  a c  t }  } }  } }
16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
                         4500 00c0 2c04 0000 4011 3933 0a0a 0069
                         0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
                         5b31 302e 3130 2e30 2e31 3035 5d20 543d
                         3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 367b 453d 3538 3938 3239 7b61
                         6c2f 6f66 7b73 7472 6963 743d 6578 6163
                         742c 454d 7b53 477b 6367 2f64 747d 2c45
                         3d33 3933 3231 377b 6464 2f63 657b 2044
                         4d3d 6469 616c 706c 616e 317d 2c61 6c2f
                         6f6e 7b73 7472 6963 743d 6578 6163 747d
                         2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
                         7472 6963 743d 6578 6163 747d 7d7d 7d7d
 
                          E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
                         ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
                          4 2  3 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  6 {  E =  5 8  9 8  2 9  { a
                          l /  o f  { s  t r  i c  t =  e x  a c
                          t ,  E M  { S  G {  c g  / d  t }  , E
                          = 3  9 3  2 1  7 {  d d  / c  e {    D
                          M =  d i  a l  p l  a n  1 }  , a  l /
                          o n  { s  t r  i c  t =  e x  a c  t }
                          , g  / s  c }  } }  , a  l /  o n  { s
                          t r  i c  t =  e x  a c  t }  } }  } }
16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
                         4500 0062 0293 0000 3f11 6402 0a0a 007a
                         0a0a 0069 2b72 2b72 004e 705a 212f 3120
                         5b31 302e 3130 2e30 2e31 3232 5d0a 503d
                         3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 327d 7d0a 503d 3432 317b 433d
                         2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
                         7d0a
 
                          E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
                         ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
                          4 2  0 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  2 }  }^J  P =  4 2  1 {  C =
                          - {  M F  = a  g w  _ j  u l  w /  3 }
                          }^J
16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
                         4500 0062 0294 0000 3f11 6401 0a0a 007a
                         0a0a 0069 2b72 2b72 004e 665a 212f 3120
                         5b31 302e 3130 2e30 2e31 3232 5d0a 503d
                         3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
                         756c 772f 357d 7d0a 503d 3432 337b 433d
                         2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
                         7d0a
 
                          E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
                         ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
                          [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
                          4 2  2 {  C =  - {  M F  = a  g w  _ j
                          u l  w /  5 }  }^J  P =  4 2  3 {  C =
                          - {  M F  = a  g w  _ j  u l  w /  6 }
                          }^J
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

best  regards
> :-)Jerry Wang
tel:(8621)58541240 ext 9615
mailto:wangjl2@sbell.com.cn
Shanghai Bell Co.LTD



-----Original Message-----
From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
Sent: Wednesday, April 17, 2002 10:10 PM
To: 'Christer Holmberg'
Cc: 'megaco@ietf.org'
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)


Hi,

>>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
>>
>> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination

>I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.

The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up? 

Thanks,
Glauco

>Regards,

>hrister Holmberg
>ricsson Finland




>
>
> b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
>
> "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
>
> Thanks,
> Glauco
>
> _______________________________________________
> Megaco mailing 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 Apr 18 02:49: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 CAA27325
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 02:49:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27697;
	Thu, 18 Apr 2002 02:27:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27669
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 02:27:31 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26914
	for <megaco@ietf.org>; Thu, 18 Apr 2002 02:27:27 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3I6QZs7025585;
	Thu, 18 Apr 2002 08:26:35 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3I6QYo5023392;
	Thu, 18 Apr 2002 09:26:35 +0300 (EET DST)
Message-ID: <3CBE671F.71B73272@lmf.ericsson.se>
Date: Thu, 18 Apr 2002 09:26:39 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: SRD Wang JuLin <WangJL2@sbell.com.cn>
CC: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>, megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <C65F869D22451348A9970B1670ED366301968CCA@bellnet-mail1.sbell.com.cn>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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,

So, you want me to send a MODIFY to each of the THOUSANDS of terminations I may want to use????

And, the issue is not which termination I WANT to use (ie which I want the MGC to "enable" in the MG), but which termination I am ABLE (ie which termination has at a certain time been booted/loaded/whatevver) to use...

Regards,

Christer Holmberg
Ericsson Finland





SRD Wang JuLin wrote:

> Hi,
> Well,I send the ServiceChange for Root to Softswitch,it only send 4 modify messages  to RGW.So i can only use 4 out of the 8 phones located in RGW.
> (I had provisioned 8 terminations into Softswitch
>
> )
> 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
>                          4500 008e 028b 0000 3f11 63de 0a0a 007a
>                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b4d 543d 5253 2c52 453d 3930 312c 4144
>                          3d31 3131 3232 2c50 463d 416e 616c 6f67
>                          5f4c 696e 655f 496e 7465 726f 7065 7261
>                          6269 6c69 7479 5f54 6573 745f 5072 6f66
>                          696c 652f 312c 563d 317d 7d7d 7d0a
>
>                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
>                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { M  T =  R S  , R  E =  9 0  1 ,  A D
>                           = 1  1 1  2 2  , P  F =  A n  a l  o g
>                           _ L  i n  e _  I n  t e  r o  p e  r a
>                           b i  l i  t y  _ T  e s  t _  P r  o f
>                           i l  e /  1 ,  V =  1 }  } }  }^J
> 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
>                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
>                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b41 443d 3131 3132 322c 5046 3d43 4c53
>                          2f31 2c56 3d31 7d7d 7d7d
>
>                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
>                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸™]  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
>                           / 1  , V  = 1  } }  } }
> 16:46:18.325927 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 337b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  1 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 367b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  3 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0293 0000 3f11 6402 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327d 7d0a 503d 3432 317b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  3 }
>                           }^J
> 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0294 0000 3f11 6401 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357d 7d0a 503d 3432 337b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  6 }
>                           }^J
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> best  regards
> > :-)Jerry Wang
> tel:(8621)58541240 ext 9615
> mailto:wangjl2@sbell.com.cn
> Shanghai Bell Co.LTD
>
> -----Original Message-----
> From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> Sent: Wednesday, April 17, 2002 10:10 PM
> To: 'Christer Holmberg'
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
>
> Hi,
>
> >>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
> >>
> >> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
>
> >I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
>
> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up?
>
> Thanks,
> Glauco
>
> >Regards,
>
> >hrister Holmberg
> >ricsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing 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 Apr 18 02:49: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 CAA27338
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 02:49:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA29213
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 02:49:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27697;
	Thu, 18 Apr 2002 02:27:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA27669
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 02:27:31 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26914
	for <megaco@ietf.org>; Thu, 18 Apr 2002 02:27:27 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3I6QZs7025585;
	Thu, 18 Apr 2002 08:26:35 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3I6QYo5023392;
	Thu, 18 Apr 2002 09:26:35 +0300 (EET DST)
Message-ID: <3CBE671F.71B73272@lmf.ericsson.se>
Date: Thu, 18 Apr 2002 09:26:39 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: SRD Wang JuLin <WangJL2@sbell.com.cn>
CC: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>, megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <C65F869D22451348A9970B1670ED366301968CCA@bellnet-mail1.sbell.com.cn>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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,

So, you want me to send a MODIFY to each of the THOUSANDS of terminations I may want to use????

And, the issue is not which termination I WANT to use (ie which I want the MGC to "enable" in the MG), but which termination I am ABLE (ie which termination has at a certain time been booted/loaded/whatevver) to use...

Regards,

Christer Holmberg
Ericsson Finland





SRD Wang JuLin wrote:

> Hi,
> Well,I send the ServiceChange for Root to Softswitch,it only send 4 modify messages  to RGW.So i can only use 4 out of the 8 phones located in RGW.
> (I had provisioned 8 terminations into Softswitch
>
> )
> 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
>                          4500 008e 028b 0000 3f11 63de 0a0a 007a
>                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b4d 543d 5253 2c52 453d 3930 312c 4144
>                          3d31 3131 3232 2c50 463d 416e 616c 6f67
>                          5f4c 696e 655f 496e 7465 726f 7065 7261
>                          6269 6c69 7479 5f54 6573 745f 5072 6f66
>                          696c 652f 312c 563d 317d 7d7d 7d0a
>
>                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
>                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { M  T =  R S  , R  E =  9 0  1 ,  A D
>                           = 1  1 1  2 2  , P  F =  A n  a l  o g
>                           _ L  i n  e _  I n  t e  r o  p e  r a
>                           b i  l i  t y  _ T  e s  t _  P r  o f
>                           i l  e /  1 ,  V =  1 }  } }  }^J
> 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
>                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
>                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b41 443d 3131 3132 322c 5046 3d43 4c53
>                          2f31 2c56 3d31 7d7d 7d7d
>
>                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
>                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸™]  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
>                           / 1  , V  = 1  } }  } }
> 16:46:18.325927 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 337b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  1 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 367b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  3 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0293 0000 3f11 6402 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327d 7d0a 503d 3432 317b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  3 }
>                           }^J
> 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0294 0000 3f11 6401 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357d 7d0a 503d 3432 337b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  6 }
>                           }^J
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> best  regards
> > :-)Jerry Wang
> tel:(8621)58541240 ext 9615
> mailto:wangjl2@sbell.com.cn
> Shanghai Bell Co.LTD
>
> -----Original Message-----
> From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> Sent: Wednesday, April 17, 2002 10:10 PM
> To: 'Christer Holmberg'
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
>
> Hi,
>
> >>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
> >>
> >> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
>
> >I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
>
> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up?
>
> Thanks,
> Glauco
>
> >Regards,
>
> >hrister Holmberg
> >ricsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing 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 Apr 18 03:20: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 DAA27755
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 03:20:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00263;
	Thu, 18 Apr 2002 03:02:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00224
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 03:02:42 -0400 (EDT)
Received: from blaze.hcltech.com (pop.hclt-guindy.co.in [203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27468
	for <megaco@ietf.org>; Thu, 18 Apr 2002 03:02:37 -0400 (EDT)
Received: from venkateshpc (venkatesh.hclt-guindy.co.in [192.168.201.131])
	by blaze.hcltech.com (8.9.3/8.9.3) with SMTP id MAA12661
	for <megaco@ietf.org>; Thu, 18 Apr 2002 12:30:54 +0530
From: "Venkatesh A" <venkatesh@netlab.hcltech.com>
To: <megaco@ietf.org>
Date: Thu, 18 Apr 2002 12:34:02 +0530
Message-ID: <BCEGLBPKBLPEGJMFNDJMCEPDCKAA.venkatesh@netlab.hcltech.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.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Subject: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,

This is regarding the NOTIFICATION medGwyInvalidControllerAddress in megaco
mib.  The draft says that this notfication has to be raised whenever a
message is received from a controller that did not match any one valid
controller IP address.  Here what is meant by "invalid controller" ???  Does
it mean to say the mgc should be present in the pre provisioned list with
mg?  In case of mg running on UDP, mg is not keeping the ip address of mgc
whom it is talking to.  It simply replies to the mgc from where the request
came.  So, when / how should this NOTIFICATION be raised?

Thanks
Venkatesh


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


From daemon@optimus.ietf.org  Thu Apr 18 03:20: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 DAA27766
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 03:20:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA01798
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 03:21:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00263;
	Thu, 18 Apr 2002 03:02:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00224
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 03:02:42 -0400 (EDT)
Received: from blaze.hcltech.com (pop.hclt-guindy.co.in [203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27468
	for <megaco@ietf.org>; Thu, 18 Apr 2002 03:02:37 -0400 (EDT)
Received: from venkateshpc (venkatesh.hclt-guindy.co.in [192.168.201.131])
	by blaze.hcltech.com (8.9.3/8.9.3) with SMTP id MAA12661
	for <megaco@ietf.org>; Thu, 18 Apr 2002 12:30:54 +0530
From: "Venkatesh A" <venkatesh@netlab.hcltech.com>
To: <megaco@ietf.org>
Date: Thu, 18 Apr 2002 12:34:02 +0530
Message-ID: <BCEGLBPKBLPEGJMFNDJMCEPDCKAA.venkatesh@netlab.hcltech.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.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Subject: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,

This is regarding the NOTIFICATION medGwyInvalidControllerAddress in megaco
mib.  The draft says that this notfication has to be raised whenever a
message is received from a controller that did not match any one valid
controller IP address.  Here what is meant by "invalid controller" ???  Does
it mean to say the mgc should be present in the pre provisioned list with
mg?  In case of mg running on UDP, mg is not keeping the ip address of mgc
whom it is talking to.  It simply replies to the mgc from where the request
came.  So, when / how should this NOTIFICATION be raised?

Thanks
Venkatesh


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



From megaco-admin@ietf.org  Thu Apr 18 03:21: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 DAA27783
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 03:21:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA29562;
	Thu, 18 Apr 2002 02:56:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA29532
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 02:56:22 -0400 (EDT)
Received: from mailgate.sbell.com.cn (mailgate.sbell.com.cn [202.96.203.173])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27416
	for <megaco@ietf.org>; Thu, 18 Apr 2002 02:56:13 -0400 (EDT)
Received: from bellnet-mail4.sbell.com.cn (bellnet-mail4.sbell.com.cn [202.96.203.174])
	by mailgate.sbell.com.cn (8.9.2/8.9.2) with ESMTP id OAA27315;
	Thu, 18 Apr 2002 14:42:50 +0800 (CST)
Received: from bellnet-mail1.sbell.com.cn ([202.96.203.171]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 18 Apr 2002 14:54:35 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Thu, 18 Apr 2002 14:51:55 +0800
Message-ID: <C65F869D22451348A9970B1670ED366301968D6C@bellnet-mail1.sbell.com.cn>
Thread-Topic: [Megaco] ServiceChange for a single termination (Cold Start)
Thread-Index: AcHmoh1PD2Vg2h0bR/+dQ8o3Ql1VIAAAGNkw
From: "SRD Wang JuLin" <WangJL2@sbell.com.cn>
To: "Christer Holmberg" <christer.holmberg@lmf.ericsson.se>
Cc: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>, <megaco@ietf.org>
X-OriginalArrivalTime: 18 Apr 2002 06:54:35.0624 (UTC) FILETIME=[E69EBE80:01C1E6A5]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id CAA29533
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,
Well,I think MGC should send Modify messages (the number of it equals to the number of terminations in RGW,I only refer to Residential GW) to check the terminations's events  after MG reboot with Cold Start as a whole entity.
All terminations will start up.In case of some terminations fail to use,of course,we should send SC for definite invalid termination with restored method  to Softswtich.
Before you WANT to use a termination,you should know whether it is ABLE to use (ie.in service or out of  service).

best  regards
> :-)Jerry Wang
tel:(8621)58541240 ext 9615
mailto:wangjl2@sbell.com.cn
Shanghai Bell Co.LTD



-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Thursday, April 18, 2002 2:27 PM
To: SRD Wang JuLin
Cc: Barcotti, Glauco; megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)



Hi,

So, you want me to send a MODIFY to each of the THOUSANDS of terminations I may want to use????

And, the issue is not which termination I WANT to use (ie which I want the MGC to "enable" in the MG), but which termination I am ABLE (ie which termination has at a certain time been booted/loaded/whatevver) to use...

Regards,

Christer Holmberg
Ericsson Finland





SRD Wang JuLin wrote:

> Hi,
> Well,I send the ServiceChange for Root to Softswitch,it only send 4 modify messages  to RGW.So i can only use 4 out of the 8 phones located in RGW.
> (I had provisioned 8 terminations into Softswitch
>
> )
> 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
>                          4500 008e 028b 0000 3f11 63de 0a0a 007a
>                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b4d 543d 5253 2c52 453d 3930 312c 4144
>                          3d31 3131 3232 2c50 463d 416e 616c 6f67
>                          5f4c 696e 655f 496e 7465 726f 7065 7261
>                          6269 6c69 7479 5f54 6573 745f 5072 6f66
>                          696c 652f 312c 563d 317d 7d7d 7d0a
>
>                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
>                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { M  T =  R S  , R  E =  9 0  1 ,  A D
>                           = 1  1 1  2 2  , P  F =  A n  a l  o g
>                           _ L  i n  e _  I n  t e  r o  p e  r a
>                           b i  l i  t y  _ T  e s  t _  P r  o f
>                           i l  e /  1 ,  V =  1 }  } }  }^J
> 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
>                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
>                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b41 443d 3131 3132 322c 5046 3d43 4c53
>                          2f31 2c56 3d31 7d7d 7d7d
>
>                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
>                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
>                           / 1  , V  = 1  } }  } }
> 16:46:18.325927 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 337b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  1 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 367b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  3 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0293 0000 3f11 6402 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327d 7d0a 503d 3432 317b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  3 }
>                           }^J
> 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0294 0000 3f11 6401 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357d 7d0a 503d 3432 337b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  6 }
>                           }^J
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> best  regards
> > :-)Jerry Wang
> tel:(8621)58541240 ext 9615
> mailto:wangjl2@sbell.com.cn
> Shanghai Bell Co.LTD
>
> -----Original Message-----
> From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> Sent: Wednesday, April 17, 2002 10:10 PM
> To: 'Christer Holmberg'
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
>
> Hi,
>
> >>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
> >>
> >> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
>
> >I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
>
> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up?
>
> Thanks,
> Glauco
>
> >Regards,
>
> >hrister Holmberg
> >ricsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing 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 Apr 18 03:21: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 DAA27796
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 03:21:01 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA01812
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 03:21:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA29562;
	Thu, 18 Apr 2002 02:56:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA29532
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 02:56:22 -0400 (EDT)
Received: from mailgate.sbell.com.cn (mailgate.sbell.com.cn [202.96.203.173])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27416
	for <megaco@ietf.org>; Thu, 18 Apr 2002 02:56:13 -0400 (EDT)
Received: from bellnet-mail4.sbell.com.cn (bellnet-mail4.sbell.com.cn [202.96.203.174])
	by mailgate.sbell.com.cn (8.9.2/8.9.2) with ESMTP id OAA27315;
	Thu, 18 Apr 2002 14:42:50 +0800 (CST)
Received: from bellnet-mail1.sbell.com.cn ([202.96.203.171]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 18 Apr 2002 14:54:35 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Thu, 18 Apr 2002 14:51:55 +0800
Message-ID: <C65F869D22451348A9970B1670ED366301968D6C@bellnet-mail1.sbell.com.cn>
Thread-Topic: [Megaco] ServiceChange for a single termination (Cold Start)
Thread-Index: AcHmoh1PD2Vg2h0bR/+dQ8o3Ql1VIAAAGNkw
From: "SRD Wang JuLin" <WangJL2@sbell.com.cn>
To: "Christer Holmberg" <christer.holmberg@lmf.ericsson.se>
Cc: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>, <megaco@ietf.org>
X-OriginalArrivalTime: 18 Apr 2002 06:54:35.0624 (UTC) FILETIME=[E69EBE80:01C1E6A5]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id CAA29533
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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,
Well,I think MGC should send Modify messages (the number of it equals to the number of terminations in RGW,I only refer to Residential GW) to check the terminations's events  after MG reboot with Cold Start as a whole entity.
All terminations will start up.In case of some terminations fail to use,of course,we should send SC for definite invalid termination with restored method  to Softswtich.
Before you WANT to use a termination,you should know whether it is ABLE to use (ie.in service or out of  service).

best  regards
> :-)Jerry Wang
tel:(8621)58541240 ext 9615
mailto:wangjl2@sbell.com.cn
Shanghai Bell Co.LTD



-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Thursday, April 18, 2002 2:27 PM
To: SRD Wang JuLin
Cc: Barcotti, Glauco; megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)



Hi,

So, you want me to send a MODIFY to each of the THOUSANDS of terminations I may want to use????

And, the issue is not which termination I WANT to use (ie which I want the MGC to "enable" in the MG), but which termination I am ABLE (ie which termination has at a certain time been booted/loaded/whatevver) to use...

Regards,

Christer Holmberg
Ericsson Finland





SRD Wang JuLin wrote:

> Hi,
> Well,I send the ServiceChange for Root to Softswitch,it only send 4 modify messages  to RGW.So i can only use 4 out of the 8 phones located in RGW.
> (I had provisioned 8 terminations into Softswitch
>
> )
> 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
>                          4500 008e 028b 0000 3f11 63de 0a0a 007a
>                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b4d 543d 5253 2c52 453d 3930 312c 4144
>                          3d31 3131 3232 2c50 463d 416e 616c 6f67
>                          5f4c 696e 655f 496e 7465 726f 7065 7261
>                          6269 6c69 7479 5f54 6573 745f 5072 6f66
>                          696c 652f 312c 563d 317d 7d7d 7d0a
>
>                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
>                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { M  T =  R S  , R  E =  9 0  1 ,  A D
>                           = 1  1 1  2 2  , P  F =  A n  a l  o g
>                           _ L  i n  e _  I n  t e  r o  p e  r a
>                           b i  l i  t y  _ T  e s  t _  P r  o f
>                           i l  e /  1 ,  V =  1 }  } }  }^J
> 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
>                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
>                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b41 443d 3131 3132 322c 5046 3d43 4c53
>                          2f31 2c56 3d31 7d7d 7d7d
>
>                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
>                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
>                           / 1  , V  = 1  } }  } }
> 16:46:18.325927 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 337b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  1 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 367b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  3 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } }
> 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0293 0000 3f11 6402 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327d 7d0a 503d 3432 317b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  3 }
>                           }^J
> 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0294 0000 3f11 6401 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357d 7d0a 503d 3432 337b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  6 }
>                           }^J
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> best  regards
> > :-)Jerry Wang
> tel:(8621)58541240 ext 9615
> mailto:wangjl2@sbell.com.cn
> Shanghai Bell Co.LTD
>
> -----Original Message-----
> From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> Sent: Wednesday, April 17, 2002 10:10 PM
> To: 'Christer Holmberg'
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
>
> Hi,
>
> >>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
> >>
> >> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
>
> >I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
>
> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up?
>
> Thanks,
> Glauco
>
> >Regards,
>
> >hrister Holmberg
> >ricsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing 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 Apr 18 03: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 DAA27927
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 03:29:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00812;
	Thu, 18 Apr 2002 03:08:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00698
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 03:08:25 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27588
	for <megaco@ietf.org>; Thu, 18 Apr 2002 03:08:20 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3I78Is7014317;
	Thu, 18 Apr 2002 09:08:18 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3I78Io5026438;
	Thu, 18 Apr 2002 10:08:18 +0300 (EET DST)
Message-ID: <3CBE70E6.36159DEF@lmf.ericsson.se>
Date: Thu, 18 Apr 2002 10:08:22 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Fernando Vallejo Lazaro <Fernando.Vallejo_Lazaro@alcatel.es>
CC: "Barcotti, Glauco" <Glauco_Barcotti@mitel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F08@rndex50.ottawa.mitel.com> <3CBE5F4B.C53A9F2@lmf.ericsson.se> <3CBE6BB2.885472A5@alcatel.es>
Content-Type: multipart/alternative;
 boundary="------------03A9E12D960DBF8A7F6EB3FC"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


Hi,

>> Hi,
>>
>> > Hi,
>> >
>> > >>         Assuming a Gateway with 2 terminations, one of >them is
>> OK and the other is Malfunctioning. How should I >proceed if I want
>> to bring just the working termination >up (Cold Start)?
>> > >>
>> > >> a) If a ServiceChange is issued for ROOT termination MGC will
>> think that all terminations are up and, until another ServiceChange
>> is issued taking the defective Termination out of service, a call
>> could be attempted on that defective termination
>> >
>> > >I don't agree. A ServiceChange for ROOT will indicate that the MG
>> is up, not specific terminations. You would then have to send
>> additonal ServiceChange commands, with Reason code 900, for each
>> termination you want to put in-service.
>> >
>> > The example in the spec (Appendix A) and the
>> draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT
>> on a ServiceChange all terminations are addressed (One ServiceChange
>> ROOT is sent and the terminations are available to use). Where did
>> you find information about ServiceChange ROOT not bringing all
>> terminations up?
>>
>> Assume my MG comes up, but for whatever reason I don't have TDM
>> interface card X available, so those timeslots/terminations are not
>> available. Now, to tell the MGC that there are two options:
>>
>> 1. I configure the MGC manually not to use those terminations.
>>
>> 2. The MGC will have to do Audit to find out which terminations are
>> in servce.
>
> There is a third option:
>
>     3. Assume all terminations are up. The MG will send SVC (Forced)
> only for those termination down (the ones on the card x)

Yes, but those terminations may be up in 10 seconds, which is a very
long time in a PSTN environment, so then it would have to send a new SVC
to put them back into service...


>> Now, I don't like option 1.
>>
>> And, when card X is put back into service, or I put a new card in my
>> MG, there will have to be ServiceChanges for those terminations
>> anyway, because I don't think we can assume the MGC to Audit the MG
>> all the time.
>
>
>     The MGC does not need to audit anything it knows now what
> terminations are up (by default)

Are you sure? I may use my MGC with different MGs. Yes, the termination
naming has to be the same in both MGs, so that the MGC knows which
terminationID is associated with witch timeslot, trunk etc, but the
number of timeslots/interfaces may be different.

> and which ones down (due to the SVC(Forced) ).

Again, card X may come up within 10 seconds, card Y within 20 seconds
etc etc. How does it make all simpler by having to send SVC twice -
first to remote them, and 10 seconds later to put them back????

Regards,

Christer Holmberg
Ericsson Finland




>  If the card restores the service a SVGC (Restart) will be sent only
> for the terminations on the Card X. The process is simpler than
> sending a restart for all terminations in the system
>     on startup.
>
>>
>>
>> Also, if I have a very big MG it may take different time before all
>> interfaces are up. But, I still want to start using some interfaces,
>> so I don't want to wait with the registration ServiceChange until
>> all interfaces are up. But, again, the MGC would now have to start
>> doing frequent Audits, to find out which interfaces are up, and
>> which are not, until it realizes all terminations are up.
>>
>> Chapter 6.2.5 defines that the ROOT specify the whole MG, rather
>> than specific terminations. My understanding is that it does NOT say
>> that includes the terminations. Also, how would you define the
>> difference between TerminationID=ROOT and TerminationID=ALL???
>>
>> Also, IF ROOT would include all terminations, why am I not to send a
>> Subtract with ContextID=ALL and TerminationID=ROOT???
>>
>> Regards,
>>
>> Christer Holmberg
>> Ericsson Finland
>>
>> >
>> >
>> > Thanks,
>> > Glauco
>> >
>> > >Regards,
>> >
>> > >hrister Holmberg
>> > >ricsson Finland
>> >
>> > >
>> > >
>> > > b) If a ServiceChange is issued just for the working Termination
>> The ability to redirect the gateway to another MGC will be lost (See
>> quotation from spec below)
>> > >
>> > > "The return from ServiceChange is empty except when the Root
>> terminationID is used.  In that case it includes the following
>> parameters as required:"
>> > >
>> > > Thanks,
>> > > Glauco
>> > >
>> > > _______________________________________________
>> > > Megaco mailing list
>> > > Megaco@ietf.org
>> > > https://www1.ietf.org/mailman/listinfo/megaco
>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www1.ietf.org/mailman/listinfo/megaco
>
>
> Regards
> Fernando
>
>
>
> --
> Fernando Vallejo Lazaro
> Phone:  +34 91 330 8279
> SW  Wireline ASD-Madrid
>        ALCATEL
>
>

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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Hi,
<blockquote TYPE=CITE>
<blockquote TYPE=CITE>Hi,
<p>> Hi,
<br>>
<br>> >>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assuming a Gateway
with 2 terminations, one of >them is OK and the other is Malfunctioning.
How should I >proceed if I want to bring just the working termination >up
(Cold Start)?
<br>> >>
<br>> >> a) If a ServiceChange is issued for ROOT termination MGC will
think that all terminations are up and, until another ServiceChange is
issued taking the defective Termination out of service, a call could be
attempted on that defective termination
<br>>
<br>> >I don't agree. A ServiceChange for ROOT will indicate that the MG
is up, not specific terminations. You would then have to send additonal
ServiceChange commands, with Reason code 900, for each termination you
want to put in-service.
<br>>
<br>> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt
tell me that when I address ROOT on a ServiceChange all terminations are
addressed (One ServiceChange ROOT is sent and the terminations are available
to use). Where did you find information about ServiceChange ROOT not bringing
all terminations up?
<p>Assume my MG comes up, but for whatever reason I don't have TDM interface
card X available, so those timeslots/terminations are not available. Now,
to tell the MGC that there are two options:
<p>1. I configure the MGC manually not to use those terminations.
<p>2. The MGC will have to do Audit to find out which terminations are
in servce.</blockquote>
There is a third option:
<p>&nbsp;&nbsp;&nbsp; 3. Assume all terminations are up. The MG will send
SVC (Forced) only for those termination down (the ones on the card x)</blockquote>
Yes, but those terminations may be up in 10 seconds, which is a very long
time in a PSTN environment, so then it would have to send a new SVC to
put them back into service...
<br>&nbsp;
<blockquote TYPE=CITE>
<blockquote TYPE=CITE>Now, I don't like option 1.
<p>And, when card X is put back into service, or I put a new card in my
MG, there will have to be ServiceChanges for those terminations anyway,
because I don't think we can assume the MGC to Audit the MG all the time.</blockquote>

<p><br>&nbsp;&nbsp;&nbsp; The MGC does not need to audit anything it knows
now what terminations are up (by default)</blockquote>
Are you sure? I may use my MGC with different MGs. Yes, the termination
naming has to be the same in both MGs, so that the MGC knows which terminationID
is associated with witch timeslot, trunk etc, but the number of timeslots/interfaces
may be different.
<blockquote TYPE=CITE>and which ones down (due to the SVC(Forced) ).</blockquote>
Again, card X may come up within 10 seconds, card Y within 20 seconds etc
etc. How does it make all simpler by having to send SVC twice - first to
remote them, and 10 seconds later to put them back????
<p>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<blockquote TYPE=CITE>&nbsp;If the card restores the service a SVGC (Restart)
will be sent only for the terminations on the Card X. The process is simpler
than sending a restart for all terminations in the system
<br>&nbsp;&nbsp;&nbsp; on startup.
<blockquote TYPE=CITE>&nbsp;
<p>Also, if I have a very big MG it may take different time before all
interfaces are up. But, I still want to start using some interfaces, so
I don't want to wait with the registration ServiceChange until all interfaces
are up. But, again, the MGC would now have to start doing frequent Audits,
to find out which interfaces are up, and
<br>which are not, until it realizes all terminations are up.
<p>Chapter 6.2.5 defines that the ROOT specify the whole MG, rather than
specific terminations. My understanding is that it does NOT say that includes
the terminations. Also, how would you define the difference between TerminationID=ROOT
and TerminationID=ALL???
<p>Also, IF ROOT would include all terminations, why am I not to send a
Subtract with ContextID=ALL and TerminationID=ROOT???
<p>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<p>>
<br>>
<br>> Thanks,
<br>> Glauco
<br>>
<br>> >Regards,
<br>>
<br>> >hrister Holmberg
<br>> >ricsson Finland
<br>>
<br>> >
<br>> >
<br>> > b) If a ServiceChange is issued just for the working Termination
The ability to redirect the gateway to another MGC will be lost (See quotation
from spec below)
<br>> >
<br>> > "The return from ServiceChange is empty except when the Root terminationID
is used.&nbsp; In that case it includes the following parameters as required:"
<br>> >
<br>> > Thanks,
<br>> > Glauco
<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>_______________________________________________
<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>

<p><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;</blockquote>
</html>

--------------03A9E12D960DBF8A7F6EB3FC--


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


From daemon@optimus.ietf.org  Thu Apr 18 03: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 DAA27941
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 03:29:49 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA02405
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 03:29:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00812;
	Thu, 18 Apr 2002 03:08:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00698
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 03:08:25 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27588
	for <megaco@ietf.org>; Thu, 18 Apr 2002 03:08:20 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3I78Is7014317;
	Thu, 18 Apr 2002 09:08:18 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3I78Io5026438;
	Thu, 18 Apr 2002 10:08:18 +0300 (EET DST)
Message-ID: <3CBE70E6.36159DEF@lmf.ericsson.se>
Date: Thu, 18 Apr 2002 10:08:22 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Fernando Vallejo Lazaro <Fernando.Vallejo_Lazaro@alcatel.es>
CC: "Barcotti, Glauco" <Glauco_Barcotti@mitel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F08@rndex50.ottawa.mitel.com> <3CBE5F4B.C53A9F2@lmf.ericsson.se> <3CBE6BB2.885472A5@alcatel.es>
Content-Type: multipart/alternative;
 boundary="------------03A9E12D960DBF8A7F6EB3FC"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


Hi,

>> Hi,
>>
>> > Hi,
>> >
>> > >>         Assuming a Gateway with 2 terminations, one of >them is
>> OK and the other is Malfunctioning. How should I >proceed if I want
>> to bring just the working termination >up (Cold Start)?
>> > >>
>> > >> a) If a ServiceChange is issued for ROOT termination MGC will
>> think that all terminations are up and, until another ServiceChange
>> is issued taking the defective Termination out of service, a call
>> could be attempted on that defective termination
>> >
>> > >I don't agree. A ServiceChange for ROOT will indicate that the MG
>> is up, not specific terminations. You would then have to send
>> additonal ServiceChange commands, with Reason code 900, for each
>> termination you want to put in-service.
>> >
>> > The example in the spec (Appendix A) and the
>> draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT
>> on a ServiceChange all terminations are addressed (One ServiceChange
>> ROOT is sent and the terminations are available to use). Where did
>> you find information about ServiceChange ROOT not bringing all
>> terminations up?
>>
>> Assume my MG comes up, but for whatever reason I don't have TDM
>> interface card X available, so those timeslots/terminations are not
>> available. Now, to tell the MGC that there are two options:
>>
>> 1. I configure the MGC manually not to use those terminations.
>>
>> 2. The MGC will have to do Audit to find out which terminations are
>> in servce.
>
> There is a third option:
>
>     3. Assume all terminations are up. The MG will send SVC (Forced)
> only for those termination down (the ones on the card x)

Yes, but those terminations may be up in 10 seconds, which is a very
long time in a PSTN environment, so then it would have to send a new SVC
to put them back into service...


>> Now, I don't like option 1.
>>
>> And, when card X is put back into service, or I put a new card in my
>> MG, there will have to be ServiceChanges for those terminations
>> anyway, because I don't think we can assume the MGC to Audit the MG
>> all the time.
>
>
>     The MGC does not need to audit anything it knows now what
> terminations are up (by default)

Are you sure? I may use my MGC with different MGs. Yes, the termination
naming has to be the same in both MGs, so that the MGC knows which
terminationID is associated with witch timeslot, trunk etc, but the
number of timeslots/interfaces may be different.

> and which ones down (due to the SVC(Forced) ).

Again, card X may come up within 10 seconds, card Y within 20 seconds
etc etc. How does it make all simpler by having to send SVC twice -
first to remote them, and 10 seconds later to put them back????

Regards,

Christer Holmberg
Ericsson Finland




>  If the card restores the service a SVGC (Restart) will be sent only
> for the terminations on the Card X. The process is simpler than
> sending a restart for all terminations in the system
>     on startup.
>
>>
>>
>> Also, if I have a very big MG it may take different time before all
>> interfaces are up. But, I still want to start using some interfaces,
>> so I don't want to wait with the registration ServiceChange until
>> all interfaces are up. But, again, the MGC would now have to start
>> doing frequent Audits, to find out which interfaces are up, and
>> which are not, until it realizes all terminations are up.
>>
>> Chapter 6.2.5 defines that the ROOT specify the whole MG, rather
>> than specific terminations. My understanding is that it does NOT say
>> that includes the terminations. Also, how would you define the
>> difference between TerminationID=ROOT and TerminationID=ALL???
>>
>> Also, IF ROOT would include all terminations, why am I not to send a
>> Subtract with ContextID=ALL and TerminationID=ROOT???
>>
>> Regards,
>>
>> Christer Holmberg
>> Ericsson Finland
>>
>> >
>> >
>> > Thanks,
>> > Glauco
>> >
>> > >Regards,
>> >
>> > >hrister Holmberg
>> > >ricsson Finland
>> >
>> > >
>> > >
>> > > b) If a ServiceChange is issued just for the working Termination
>> The ability to redirect the gateway to another MGC will be lost (See
>> quotation from spec below)
>> > >
>> > > "The return from ServiceChange is empty except when the Root
>> terminationID is used.  In that case it includes the following
>> parameters as required:"
>> > >
>> > > Thanks,
>> > > Glauco
>> > >
>> > > _______________________________________________
>> > > Megaco mailing list
>> > > Megaco@ietf.org
>> > > https://www1.ietf.org/mailman/listinfo/megaco
>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www1.ietf.org/mailman/listinfo/megaco
>
>
> Regards
> Fernando
>
>
>
> --
> Fernando Vallejo Lazaro
> Phone:  +34 91 330 8279
> SW  Wireline ASD-Madrid
>        ALCATEL
>
>

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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Hi,
<blockquote TYPE=CITE>
<blockquote TYPE=CITE>Hi,
<p>> Hi,
<br>>
<br>> >>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assuming a Gateway
with 2 terminations, one of >them is OK and the other is Malfunctioning.
How should I >proceed if I want to bring just the working termination >up
(Cold Start)?
<br>> >>
<br>> >> a) If a ServiceChange is issued for ROOT termination MGC will
think that all terminations are up and, until another ServiceChange is
issued taking the defective Termination out of service, a call could be
attempted on that defective termination
<br>>
<br>> >I don't agree. A ServiceChange for ROOT will indicate that the MG
is up, not specific terminations. You would then have to send additonal
ServiceChange commands, with Reason code 900, for each termination you
want to put in-service.
<br>>
<br>> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt
tell me that when I address ROOT on a ServiceChange all terminations are
addressed (One ServiceChange ROOT is sent and the terminations are available
to use). Where did you find information about ServiceChange ROOT not bringing
all terminations up?
<p>Assume my MG comes up, but for whatever reason I don't have TDM interface
card X available, so those timeslots/terminations are not available. Now,
to tell the MGC that there are two options:
<p>1. I configure the MGC manually not to use those terminations.
<p>2. The MGC will have to do Audit to find out which terminations are
in servce.</blockquote>
There is a third option:
<p>&nbsp;&nbsp;&nbsp; 3. Assume all terminations are up. The MG will send
SVC (Forced) only for those termination down (the ones on the card x)</blockquote>
Yes, but those terminations may be up in 10 seconds, which is a very long
time in a PSTN environment, so then it would have to send a new SVC to
put them back into service...
<br>&nbsp;
<blockquote TYPE=CITE>
<blockquote TYPE=CITE>Now, I don't like option 1.
<p>And, when card X is put back into service, or I put a new card in my
MG, there will have to be ServiceChanges for those terminations anyway,
because I don't think we can assume the MGC to Audit the MG all the time.</blockquote>

<p><br>&nbsp;&nbsp;&nbsp; The MGC does not need to audit anything it knows
now what terminations are up (by default)</blockquote>
Are you sure? I may use my MGC with different MGs. Yes, the termination
naming has to be the same in both MGs, so that the MGC knows which terminationID
is associated with witch timeslot, trunk etc, but the number of timeslots/interfaces
may be different.
<blockquote TYPE=CITE>and which ones down (due to the SVC(Forced) ).</blockquote>
Again, card X may come up within 10 seconds, card Y within 20 seconds etc
etc. How does it make all simpler by having to send SVC twice - first to
remote them, and 10 seconds later to put them back????
<p>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<blockquote TYPE=CITE>&nbsp;If the card restores the service a SVGC (Restart)
will be sent only for the terminations on the Card X. The process is simpler
than sending a restart for all terminations in the system
<br>&nbsp;&nbsp;&nbsp; on startup.
<blockquote TYPE=CITE>&nbsp;
<p>Also, if I have a very big MG it may take different time before all
interfaces are up. But, I still want to start using some interfaces, so
I don't want to wait with the registration ServiceChange until all interfaces
are up. But, again, the MGC would now have to start doing frequent Audits,
to find out which interfaces are up, and
<br>which are not, until it realizes all terminations are up.
<p>Chapter 6.2.5 defines that the ROOT specify the whole MG, rather than
specific terminations. My understanding is that it does NOT say that includes
the terminations. Also, how would you define the difference between TerminationID=ROOT
and TerminationID=ALL???
<p>Also, IF ROOT would include all terminations, why am I not to send a
Subtract with ContextID=ALL and TerminationID=ROOT???
<p>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<p>>
<br>>
<br>> Thanks,
<br>> Glauco
<br>>
<br>> >Regards,
<br>>
<br>> >hrister Holmberg
<br>> >ricsson Finland
<br>>
<br>> >
<br>> >
<br>> > b) If a ServiceChange is issued just for the working Termination
The ability to redirect the gateway to another MGC will be lost (See quotation
from spec below)
<br>> >
<br>> > "The return from ServiceChange is empty except when the Root terminationID
is used.&nbsp; In that case it includes the following parameters as required:"
<br>> >
<br>> > Thanks,
<br>> > Glauco
<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>_______________________________________________
<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>

<p><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;</blockquote>
</html>

--------------03A9E12D960DBF8A7F6EB3FC--


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



From megaco-admin@ietf.org  Thu Apr 18 03:43: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 DAA28194
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 03:43:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA01695;
	Thu, 18 Apr 2002 03:19:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA01654
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 03:19:49 -0400 (EDT)
Received: from blaze.hcltech.com (pop.hclt-guindy.co.in [203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27735
	for <megaco@ietf.org>; Thu, 18 Apr 2002 03:19:44 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id MAA13001;
	Thu, 18 Apr 2002 12:47:55 +0530
Message-ID: <3CBE6A4C.C85A55A0@netlab.hcltech.com>
Date: Thu, 18 Apr 2002 12:10:12 +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: hektor@etri.re.kr
CC: megaco@ietf.org
Subject: Re: [Megaco] (no subject)
References: <8470181DABD5D511B3E700D0B7A8AC4A5DA37A@cms3.etri.re.kr>
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,
Extract from the draft draft-ietf-megaco-h248v2-00.txt.
Notice the word highlighted with ^^^^^^.

   "The allowed values for the mode property are send-only, receive-
   only, send/receive, inactive and loop-back.  "Send" and "receive"
   are with respect to the exterior of the context, so that, for
                           ^^^^^^^^
   example, a stream set to mode=sendonly does not pass received media
   into the context. The default value for the mode property is
   "Iactive"."

So the mode talks about the media entering or leaving the context at this
termination.
send-only - Media is allowed to go outside of the context at this termination
but not inside.
recv-only - Media is allowed to go inside of the context at this termination but
not outside.

See for Giri for my inline comments.

> hektor@etri.re.kr wrote:
> 
> hi, list
> 
> 
> 
> I have some questions about mode in localcontrol descriptor.
> could you please clear my head?
> see following examples(let's assume this can be happened in Trunking gateway
> using IP Packet network)
> 
>                                  ctx1
>                           --------------------------
> pstn network --     pstn term ---  eph term         --- IP network
>                           --------------------------
> 
> 
> 
>     pstn term.          ephemeral term.
> -------------------------------------------------------------------------
>       recv only         recv only            ---1)
>       recv only         send only           ---2)
>       recv only         sendreceive        ---3)
>       send only        recv only            ---4)
>       send only        send only           ---5)
>       send only        sendreceive        --6)
>       sendreceive     recv only            --7)
>       sendreceive     send only           --8)
>       sendreceive     sendreceive       --9)
> 
> 
> follwoing the way of undestanding is correct?
> 
> 1) means
>    It can receive data from LEX, but can not transfer over IP to peer MG.

[Giri] Your first part of the understanding is true.

>    It can receive data from peer MG, but can not transfer to PSTN network.
> 

[Giri] Stream Mode at pstn term = recv only, implies
       PSTN termination can only recieve media from LEX into the
       context. Nothing more than that. It doesn't say whether it
       can/can't transfer over IP to peer MG.

       And similarly the Stream Mode at eph term = recv only, implies
       EPH termination can only receive media from peer MG into the
       context. Nothing more than that. It doesn't say whether it
       can/can't transfer to PSTN network.

Hope this clears your doubt.
Thanks,
Giri
-- 

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 Extn. 233
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  Thu Apr 18 03:43: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 DAA28205
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 03:43:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA03783
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 03:43:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA01695;
	Thu, 18 Apr 2002 03:19:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA01654
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 03:19:49 -0400 (EDT)
Received: from blaze.hcltech.com (pop.hclt-guindy.co.in [203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27735
	for <megaco@ietf.org>; Thu, 18 Apr 2002 03:19:44 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id MAA13001;
	Thu, 18 Apr 2002 12:47:55 +0530
Message-ID: <3CBE6A4C.C85A55A0@netlab.hcltech.com>
Date: Thu, 18 Apr 2002 12:10:12 +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: hektor@etri.re.kr
CC: megaco@ietf.org
Subject: Re: [Megaco] (no subject)
References: <8470181DABD5D511B3E700D0B7A8AC4A5DA37A@cms3.etri.re.kr>
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,
Extract from the draft draft-ietf-megaco-h248v2-00.txt.
Notice the word highlighted with ^^^^^^.

   "The allowed values for the mode property are send-only, receive-
   only, send/receive, inactive and loop-back.  "Send" and "receive"
   are with respect to the exterior of the context, so that, for
                           ^^^^^^^^
   example, a stream set to mode=sendonly does not pass received media
   into the context. The default value for the mode property is
   "Iactive"."

So the mode talks about the media entering or leaving the context at this
termination.
send-only - Media is allowed to go outside of the context at this termination
but not inside.
recv-only - Media is allowed to go inside of the context at this termination but
not outside.

See for Giri for my inline comments.

> hektor@etri.re.kr wrote:
> 
> hi, list
> 
> 
> 
> I have some questions about mode in localcontrol descriptor.
> could you please clear my head?
> see following examples(let's assume this can be happened in Trunking gateway
> using IP Packet network)
> 
>                                  ctx1
>                           --------------------------
> pstn network --     pstn term ---  eph term         --- IP network
>                           --------------------------
> 
> 
> 
>     pstn term.          ephemeral term.
> -------------------------------------------------------------------------
>       recv only         recv only            ---1)
>       recv only         send only           ---2)
>       recv only         sendreceive        ---3)
>       send only        recv only            ---4)
>       send only        send only           ---5)
>       send only        sendreceive        --6)
>       sendreceive     recv only            --7)
>       sendreceive     send only           --8)
>       sendreceive     sendreceive       --9)
> 
> 
> follwoing the way of undestanding is correct?
> 
> 1) means
>    It can receive data from LEX, but can not transfer over IP to peer MG.

[Giri] Your first part of the understanding is true.

>    It can receive data from peer MG, but can not transfer to PSTN network.
> 

[Giri] Stream Mode at pstn term = recv only, implies
       PSTN termination can only recieve media from LEX into the
       context. Nothing more than that. It doesn't say whether it
       can/can't transfer over IP to peer MG.

       And similarly the Stream Mode at eph term = recv only, implies
       EPH termination can only receive media from peer MG into the
       context. Nothing more than that. It doesn't say whether it
       can/can't transfer to PSTN network.

Hope this clears your doubt.
Thanks,
Giri
-- 

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 Extn. 233
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  Thu Apr 18 05:39: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 FAA29968
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 05:39:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA10489;
	Thu, 18 Apr 2002 05:15:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA10460
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 05:15:01 -0400 (EDT)
Received: from cms3.etri.re.kr (cms3.etri.re.kr [129.254.16.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29581
	for <megaco@ietf.org>; Thu, 18 Apr 2002 05:14:55 -0400 (EDT)
From: hektor@etri.re.kr
Received: by cms3.etri.re.kr with Internet Mail Service (5.5.2653.19)
	id <HNZRBCL6>; Thu, 18 Apr 2002 18:14:51 +0900
Message-ID: <8470181DABD5D511B3E700D0B7A8AC4A5DA37C@cms3.etri.re.kr>
To: girirs@netlab.hcltech.com
Cc: megaco@ietf.org
Subject: re: Re: [Megaco] (no subject)
Date: Thu, 18 Apr 2002 18:14:50 +0900
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E6B9.7E33D970"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1E6B9.7E33D970
Content-Type: text/plain;
	charset="euc-kr"

hi, Giri and list.

thanks Giri.

your answer is very right. 
but I asking not asking meaning of mode in the individual termination
but the effect of pair of modes in terminations in context whichs abstract
connection.
Topology in context assummed bothway.

In other words, my question can be rewritten this way with respect to real
application.

see below,
                MGC1                     MGC2
                  |                              |
LEX1 ------- MG1 ----------------------MG2-----LEX2
         (originating)           (terminating)

when servicing 1 on 1 voice call,
if needed to open onyway connection from LEX2 to LEX1,
(only lex2 can transfer its data over IP network to lex1)
Can we specify modes in localcontrol descriptor like below?
        In MG1,                                                            
   pstn term. :  send only/sendreceive
   ephemeral term. : recv only
       In MG2,
   pstn term. : recv only
   ephemeral term. : send only


thanks in advance.


Hi, 
Extract from the draft draft-ietf-megaco-h248v2-00.txt. 
Notice the word highlighted with ^^^^^^.
   "The allowed values for the mode property are send-only, receive- 
   only, send/receive, inactive and loop-back.  "Send" and "receive" 
   are with respect to the exterior of the context, so that, for 
						   ^^^^^^^^ 
   example, a stream set to mode=sendonly does not pass received media 
   into the context. The default value for the mode property is 
   "Iactive"."
So the mode talks about the media entering or leaving the context at this 
termination. 
send-only - Media is allowed to go outside of the context at this
termination 
but not inside. 
recv-only - Media is allowed to go inside of the context at this
termination but 
not outside.
See for Giri for my inline comments.
> hektor@etri.re.kr wrote: 
> 
> hi, list 
> 
> 
> 
> I have some questions about mode in localcontrol descriptor. 
> could you please clear my head? 
> see following examples(let's assume this can be happened in Trunking
gateway 
> using IP Packet network) 
> 
>								  ctx1 
>						   -------------------------
- 
> pstn network --	 pstn term ---  eph term		 --- IP
network 
>						   -------------------------
- 
> 
> 
> 
>	 pstn term.		  ephemeral term. 
> ------------------------------------------------------------------------- 
>	   recv only		 recv only		    ---1) 
>	   recv only		 send only		   ---2) 
>	   recv only		 sendreceive	    ---3) 
>	   send only	    recv only		    ---4) 
>	   send only	    send only		   ---5) 
>	   send only	    sendreceive	    --6) 
>	   sendreceive	 recv only		    --7) 
>	   sendreceive	 send only		   --8) 
>	   sendreceive	 sendreceive	   --9) 
> 
> 
> follwoing the way of undestanding is correct? 
> 
> 1) means 
>    It can receive data from LEX, but can not transfer over IP to peer MG.
[Giri] Your first part of the understanding is true.
>    It can receive data from peer MG, but can not transfer to PSTN
network. 
> 
[Giri] Stream Mode at pstn term = recv only, implies 
	   PSTN termination can only recieve media from LEX into the 
	   context. Nothing more than that. It doesn't say whether it 
	   can/can't transfer over IP to peer MG.
	   And similarly the Stream Mode at eph term = recv only, implies 
	   EPH termination can only receive media from peer MG into the 
	   context. Nothing more than that. It doesn't say whether it 
	   can/can't transfer to PSTN network.
Hope this clears your doubt. 
Thanks, 
Giri 
-- 
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 Extn. 233 
Fax : +91 44 234 4256 
e-mail : girirs@netlab.hcltech.com <mailto:girirs@netlab.hcltech.com>

------_=_NextPart_001_01C1E6B9.7E33D970
Content-Type: text/html;
	charset="euc-kr"
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=3Deuc-kr">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>re: Re: [Megaco] (no subject)</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>hi, Giri and list.</FONT>
</P>

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

<P><FONT SIZE=3D2>your answer is very right. </FONT>
<BR><FONT SIZE=3D2>but I asking not asking meaning of mode in the =
individual termination</FONT>
<BR><FONT SIZE=3D2>but the effect of pair of modes in terminations in =
context whichs abstract connection.</FONT>
<BR><FONT SIZE=3D2>Topology in context assummed bothway.</FONT>
</P>

<P><FONT SIZE=3D2>In other words, my question can be rewritten this way =
with respect to real application.</FONT>
</P>

<P><FONT SIZE=3D2>see below,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
MGC1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MGC2</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;&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>LEX1 ------- MG1 =
----------------------MG2-----LEX2</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(originating)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; (terminating)</FONT>
</P>

<P><FONT SIZE=3D2>when servicing 1 on 1 voice call,</FONT>
<BR><FONT SIZE=3D2>if needed to open onyway connection from LEX2 to =
LEX1,</FONT>
<BR><FONT SIZE=3D2>(only lex2 can transfer its data over IP network to =
lex1)</FONT>
<BR><FONT SIZE=3D2>Can we specify modes in localcontrol descriptor like =
below?</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In =
MG1,&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;&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;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; pstn term. :&nbsp; send =
only/sendreceive</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; ephemeral term. : recv only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In MG2,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; pstn term. : recv only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; ephemeral term. : send only</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>thanks in advance.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi, </FONT>
<BR><FONT SIZE=3D2>Extract from the draft =
draft-ietf-megaco-h248v2-00.txt. </FONT>
<BR><FONT SIZE=3D2>Notice the word highlighted with ^^^^^^.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; &quot;The allowed values for the mode =
property are send-only, receive- </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; only, send/receive, inactive and =
loop-back.&nbsp; &quot;Send&quot; and &quot;receive&quot; </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; are with respect to the exterior of the =
context, so that, for </FONT>
<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;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>&nbsp;&nbsp; =
^^^^^^^^ </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; example, a stream set to =
mode=3Dsendonly does not pass received media </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; into the context. The default value for =
the mode property is </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; &quot;Iactive&quot;.&quot;</FONT>
<BR><FONT SIZE=3D2>So the mode talks about the media entering or =
leaving the context at this </FONT>
<BR><FONT SIZE=3D2>termination. </FONT>
<BR><FONT SIZE=3D2>send-only - Media is allowed to go outside of the =
context at this termination </FONT>
<BR><FONT SIZE=3D2>but not inside. </FONT>
<BR><FONT SIZE=3D2>recv-only - Media is allowed to go inside of the =
context at this termination but </FONT>
<BR><FONT SIZE=3D2>not outside.</FONT>
<BR><FONT SIZE=3D2>See for Giri for my inline comments.</FONT>
<BR><FONT SIZE=3D2>&gt; hektor@etri.re.kr wrote: </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; hi, list </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I have some questions about mode in =
localcontrol descriptor. </FONT>
<BR><FONT SIZE=3D2>&gt; could you please clear my head? </FONT>
<BR><FONT SIZE=3D2>&gt; see following examples(let's assume this can be =
happened in Trunking gateway </FONT>
<BR><FONT SIZE=3D2>&gt; using IP Packet network) </FONT>
<BR><FONT SIZE=3D2>&gt; </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; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; ctx1 </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; =
-------------------------- </FONT>
<BR><FONT SIZE=3D2>&gt; pstn network =
--&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pstn term ---&nbsp; eph =
term&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --- IP network </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; =
-------------------------- </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pstn =
term.&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; ephemeral term. =
</FONT>
<BR><FONT SIZE=3D2>&gt; =
------------------------------------------------------------------------=
- </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; recv only&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ---1) =
</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; recv only&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; ---2) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; recv only&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ---3) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; send only&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; ---4) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; send only&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; ---5) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; send only&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; sendreceive =
&nbsp;&nbsp;&nbsp; --6) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; sendreceive&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; --7) =
</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; sendreceive&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; --8) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; sendreceive&nbsp;&nbsp; sendreceive&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; --9) </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; follwoing the way of undestanding is correct? =
</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 1) means </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; It can receive data from LEX, =
but can not transfer over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>[Giri] Your first part of the understanding is =
true.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; It can receive data from peer =
MG, but can not transfer to PSTN network. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>[Giri] Stream Mode at pstn term =3D recv only, =
implies </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; PSTN termination can only recieve media from LEX =
into the </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; context. Nothing more than that. It doesn't say =
whether it </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; can/can't transfer over IP to peer MG.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; And similarly the Stream Mode at eph term =3D =
recv only, implies </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; EPH termination can only receive media from peer =
MG into the </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; context. Nothing more than that. It doesn't say =
whether it </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; can/can't transfer to PSTN network.</FONT>
<BR><FONT SIZE=3D2>Hope this clears your doubt. </FONT>
<BR><FONT SIZE=3D2>Thanks, </FONT>
<BR><FONT SIZE=3D2>Giri </FONT>
<BR><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Giri Rajasekhar Saladi </FONT>
<BR><FONT SIZE=3D2>HCL Technologies Ltd., </FONT>
<BR><FONT SIZE=3D2>51, Jawaharlal Nehru Road </FONT>
<BR><FONT SIZE=3D2>Guindy Industrial Estate, </FONT>
<BR><FONT SIZE=3D2>Ekkatuthangal, </FONT>
<BR><FONT SIZE=3D2>Chennai - 600 097.</FONT>
</P>

<P><FONT SIZE=3D2>Phone Off : +91 44 233 4174 or +91 44 233 4181 Extn. =
233 </FONT>
<BR><FONT SIZE=3D2>Fax : +91 44 234 4256 </FONT>
<BR><FONT SIZE=3D2>e-mail : girirs@netlab.hcltech.com &lt;<A =
HREF=3D"mailto:girirs@netlab.hcltech.com">mailto:girirs@netlab.hcltech.c=
om</A>&gt;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E6B9.7E33D970--

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


From daemon@optimus.ietf.org  Thu Apr 18 05:39: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 FAA29978
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 05:39:30 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA12072
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 05:39:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA10489;
	Thu, 18 Apr 2002 05:15:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA10460
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 05:15:01 -0400 (EDT)
Received: from cms3.etri.re.kr (cms3.etri.re.kr [129.254.16.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29581
	for <megaco@ietf.org>; Thu, 18 Apr 2002 05:14:55 -0400 (EDT)
From: hektor@etri.re.kr
Received: by cms3.etri.re.kr with Internet Mail Service (5.5.2653.19)
	id <HNZRBCL6>; Thu, 18 Apr 2002 18:14:51 +0900
Message-ID: <8470181DABD5D511B3E700D0B7A8AC4A5DA37C@cms3.etri.re.kr>
To: girirs@netlab.hcltech.com
Cc: megaco@ietf.org
Subject: re: Re: [Megaco] (no subject)
Date: Thu, 18 Apr 2002 18:14:50 +0900
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E6B9.7E33D970"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1E6B9.7E33D970
Content-Type: text/plain;
	charset="euc-kr"

hi, Giri and list.

thanks Giri.

your answer is very right. 
but I asking not asking meaning of mode in the individual termination
but the effect of pair of modes in terminations in context whichs abstract
connection.
Topology in context assummed bothway.

In other words, my question can be rewritten this way with respect to real
application.

see below,
                MGC1                     MGC2
                  |                              |
LEX1 ------- MG1 ----------------------MG2-----LEX2
         (originating)           (terminating)

when servicing 1 on 1 voice call,
if needed to open onyway connection from LEX2 to LEX1,
(only lex2 can transfer its data over IP network to lex1)
Can we specify modes in localcontrol descriptor like below?
        In MG1,                                                            
   pstn term. :  send only/sendreceive
   ephemeral term. : recv only
       In MG2,
   pstn term. : recv only
   ephemeral term. : send only


thanks in advance.


Hi, 
Extract from the draft draft-ietf-megaco-h248v2-00.txt. 
Notice the word highlighted with ^^^^^^.
   "The allowed values for the mode property are send-only, receive- 
   only, send/receive, inactive and loop-back.  "Send" and "receive" 
   are with respect to the exterior of the context, so that, for 
						   ^^^^^^^^ 
   example, a stream set to mode=sendonly does not pass received media 
   into the context. The default value for the mode property is 
   "Iactive"."
So the mode talks about the media entering or leaving the context at this 
termination. 
send-only - Media is allowed to go outside of the context at this
termination 
but not inside. 
recv-only - Media is allowed to go inside of the context at this
termination but 
not outside.
See for Giri for my inline comments.
> hektor@etri.re.kr wrote: 
> 
> hi, list 
> 
> 
> 
> I have some questions about mode in localcontrol descriptor. 
> could you please clear my head? 
> see following examples(let's assume this can be happened in Trunking
gateway 
> using IP Packet network) 
> 
>								  ctx1 
>						   -------------------------
- 
> pstn network --	 pstn term ---  eph term		 --- IP
network 
>						   -------------------------
- 
> 
> 
> 
>	 pstn term.		  ephemeral term. 
> ------------------------------------------------------------------------- 
>	   recv only		 recv only		    ---1) 
>	   recv only		 send only		   ---2) 
>	   recv only		 sendreceive	    ---3) 
>	   send only	    recv only		    ---4) 
>	   send only	    send only		   ---5) 
>	   send only	    sendreceive	    --6) 
>	   sendreceive	 recv only		    --7) 
>	   sendreceive	 send only		   --8) 
>	   sendreceive	 sendreceive	   --9) 
> 
> 
> follwoing the way of undestanding is correct? 
> 
> 1) means 
>    It can receive data from LEX, but can not transfer over IP to peer MG.
[Giri] Your first part of the understanding is true.
>    It can receive data from peer MG, but can not transfer to PSTN
network. 
> 
[Giri] Stream Mode at pstn term = recv only, implies 
	   PSTN termination can only recieve media from LEX into the 
	   context. Nothing more than that. It doesn't say whether it 
	   can/can't transfer over IP to peer MG.
	   And similarly the Stream Mode at eph term = recv only, implies 
	   EPH termination can only receive media from peer MG into the 
	   context. Nothing more than that. It doesn't say whether it 
	   can/can't transfer to PSTN network.
Hope this clears your doubt. 
Thanks, 
Giri 
-- 
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 Extn. 233 
Fax : +91 44 234 4256 
e-mail : girirs@netlab.hcltech.com <mailto:girirs@netlab.hcltech.com>

------_=_NextPart_001_01C1E6B9.7E33D970
Content-Type: text/html;
	charset="euc-kr"
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=3Deuc-kr">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>re: Re: [Megaco] (no subject)</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>hi, Giri and list.</FONT>
</P>

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

<P><FONT SIZE=3D2>your answer is very right. </FONT>
<BR><FONT SIZE=3D2>but I asking not asking meaning of mode in the =
individual termination</FONT>
<BR><FONT SIZE=3D2>but the effect of pair of modes in terminations in =
context whichs abstract connection.</FONT>
<BR><FONT SIZE=3D2>Topology in context assummed bothway.</FONT>
</P>

<P><FONT SIZE=3D2>In other words, my question can be rewritten this way =
with respect to real application.</FONT>
</P>

<P><FONT SIZE=3D2>see below,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; =
MGC1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MGC2</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;&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>LEX1 ------- MG1 =
----------------------MG2-----LEX2</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(originating)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; (terminating)</FONT>
</P>

<P><FONT SIZE=3D2>when servicing 1 on 1 voice call,</FONT>
<BR><FONT SIZE=3D2>if needed to open onyway connection from LEX2 to =
LEX1,</FONT>
<BR><FONT SIZE=3D2>(only lex2 can transfer its data over IP network to =
lex1)</FONT>
<BR><FONT SIZE=3D2>Can we specify modes in localcontrol descriptor like =
below?</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In =
MG1,&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;&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;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; pstn term. :&nbsp; send =
only/sendreceive</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; ephemeral term. : recv only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In MG2,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; pstn term. : recv only</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; ephemeral term. : send only</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>thanks in advance.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi, </FONT>
<BR><FONT SIZE=3D2>Extract from the draft =
draft-ietf-megaco-h248v2-00.txt. </FONT>
<BR><FONT SIZE=3D2>Notice the word highlighted with ^^^^^^.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; &quot;The allowed values for the mode =
property are send-only, receive- </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; only, send/receive, inactive and =
loop-back.&nbsp; &quot;Send&quot; and &quot;receive&quot; </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; are with respect to the exterior of the =
context, so that, for </FONT>
<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;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>&nbsp;&nbsp; =
^^^^^^^^ </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; example, a stream set to =
mode=3Dsendonly does not pass received media </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; into the context. The default value for =
the mode property is </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; &quot;Iactive&quot;.&quot;</FONT>
<BR><FONT SIZE=3D2>So the mode talks about the media entering or =
leaving the context at this </FONT>
<BR><FONT SIZE=3D2>termination. </FONT>
<BR><FONT SIZE=3D2>send-only - Media is allowed to go outside of the =
context at this termination </FONT>
<BR><FONT SIZE=3D2>but not inside. </FONT>
<BR><FONT SIZE=3D2>recv-only - Media is allowed to go inside of the =
context at this termination but </FONT>
<BR><FONT SIZE=3D2>not outside.</FONT>
<BR><FONT SIZE=3D2>See for Giri for my inline comments.</FONT>
<BR><FONT SIZE=3D2>&gt; hektor@etri.re.kr wrote: </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; hi, list </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I have some questions about mode in =
localcontrol descriptor. </FONT>
<BR><FONT SIZE=3D2>&gt; could you please clear my head? </FONT>
<BR><FONT SIZE=3D2>&gt; see following examples(let's assume this can be =
happened in Trunking gateway </FONT>
<BR><FONT SIZE=3D2>&gt; using IP Packet network) </FONT>
<BR><FONT SIZE=3D2>&gt; </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; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; ctx1 </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; =
-------------------------- </FONT>
<BR><FONT SIZE=3D2>&gt; pstn network =
--&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pstn term ---&nbsp; eph =
term&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --- IP network </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; =
-------------------------- </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pstn =
term.&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; ephemeral term. =
</FONT>
<BR><FONT SIZE=3D2>&gt; =
------------------------------------------------------------------------=
- </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; recv only&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ---1) =
</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; recv only&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; ---2) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; recv only&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sendreceive&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ---3) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; send only&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; recv =
only&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; ---4) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; send only&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; send =
only&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; ---5) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; send only&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; sendreceive =
&nbsp;&nbsp;&nbsp; --6) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; sendreceive&nbsp;&nbsp; recv =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; --7) =
</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; sendreceive&nbsp;&nbsp; send =
only&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; --8) </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; sendreceive&nbsp;&nbsp; sendreceive&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp; --9) </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; follwoing the way of undestanding is correct? =
</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 1) means </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; It can receive data from LEX, =
but can not transfer over IP to peer MG.</FONT>
<BR><FONT SIZE=3D2>[Giri] Your first part of the understanding is =
true.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; It can receive data from peer =
MG, but can not transfer to PSTN network. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>[Giri] Stream Mode at pstn term =3D recv only, =
implies </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; PSTN termination can only recieve media from LEX =
into the </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; context. Nothing more than that. It doesn't say =
whether it </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; can/can't transfer over IP to peer MG.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; And similarly the Stream Mode at eph term =3D =
recv only, implies </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; EPH termination can only receive media from peer =
MG into the </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; context. Nothing more than that. It doesn't say =
whether it </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; can/can't transfer to PSTN network.</FONT>
<BR><FONT SIZE=3D2>Hope this clears your doubt. </FONT>
<BR><FONT SIZE=3D2>Thanks, </FONT>
<BR><FONT SIZE=3D2>Giri </FONT>
<BR><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Giri Rajasekhar Saladi </FONT>
<BR><FONT SIZE=3D2>HCL Technologies Ltd., </FONT>
<BR><FONT SIZE=3D2>51, Jawaharlal Nehru Road </FONT>
<BR><FONT SIZE=3D2>Guindy Industrial Estate, </FONT>
<BR><FONT SIZE=3D2>Ekkatuthangal, </FONT>
<BR><FONT SIZE=3D2>Chennai - 600 097.</FONT>
</P>

<P><FONT SIZE=3D2>Phone Off : +91 44 233 4174 or +91 44 233 4181 Extn. =
233 </FONT>
<BR><FONT SIZE=3D2>Fax : +91 44 234 4256 </FONT>
<BR><FONT SIZE=3D2>e-mail : girirs@netlab.hcltech.com &lt;<A =
HREF=3D"mailto:girirs@netlab.hcltech.com">mailto:girirs@netlab.hcltech.c=
om</A>&gt;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E6B9.7E33D970--

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



From megaco-admin@ietf.org  Thu Apr 18 06:34: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 GAA00607
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 06:34:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA13592;
	Thu, 18 Apr 2002 06:11:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA13557
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 06:10:59 -0400 (EDT)
Received: from blaze.hcltech.com (pop.hclt-guindy.co.in [203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00386
	for <megaco@ietf.org>; Thu, 18 Apr 2002 06:10:53 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id PAA16949;
	Thu, 18 Apr 2002 15:39:13 +0530
Message-ID: <3CBE9162.A45370D4@netlab.hcltech.com>
Date: Thu, 18 Apr 2002 14:56:58 +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: hektor@etri.re.kr
CC: megaco@ietf.org
Subject: Re: [Megaco] (no subject)
References: <8470181DABD5D511B3E700D0B7A8AC4A5DA37C@cms3.etri.re.kr>
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,
	Think, we can specify. But do we need to use "send-recieve" on the pstn
termination at MG1, when we want to only send data to LEX1. Any specific reason?
Regds.,
Giri

> hektor@etri.re.kr wrote:
> 
> hi, Giri and list.
> 
> thanks Giri.
> 
> your answer is very right.
> but I asking not asking meaning of mode in the individual termination
> but the effect of pair of modes in terminations in context whichs abstract
> connection.
> Topology in context assummed bothway.
> 
> In other words, my question can be rewritten this way with respect to real
> application.
> 
> see below,
>                 MGC1                     MGC2
>                   |                              |
> LEX1 ------- MG1 ----------------------MG2-----LEX2
>          (originating)           (terminating)
> 
> when servicing 1 on 1 voice call,
> if needed to open onyway connection from LEX2 to LEX1,
> (only lex2 can transfer its data over IP network to lex1)
> Can we specify modes in localcontrol descriptor like below?
>         In MG1,
>    pstn term. :  send only/sendreceive
>    ephemeral term. : recv only
>        In MG2,
>    pstn term. : recv only
>    ephemeral term. : send only
> 
> thanks in advance.
> 
> Hi,
> Extract from the draft draft-ietf-megaco-h248v2-00.txt.
> Notice the word highlighted with ^^^^^^.
>    "The allowed values for the mode property are send-only, receive-
>    only, send/receive, inactive and loop-back.  "Send" and "receive"
>    are with respect to the exterior of the context, so that, for
>                                                    ^^^^^^^^
>    example, a stream set to mode=sendonly does not pass received media
>    into the context. The default value for the mode property is
>    "Iactive"."
> So the mode talks about the media entering or leaving the context at this
> termination.
> send-only - Media is allowed to go outside of the context at this termination
> but not inside.
> recv-only - Media is allowed to go inside of the context at this termination
> but
> not outside.
> See for Giri for my inline comments.
> > hektor@etri.re.kr wrote:
> >
> > hi, list
> >
> >
> >
> > I have some questions about mode in localcontrol descriptor.
> > could you please clear my head?
> > see following examples(let's assume this can be happened in Trunking gateway
> 
> > using IP Packet network)
> >
> >                                                                 ctx1
> >                                                  --------------------------
> > pstn network --        pstn term ---  eph term                 --- IP
> network
> >                                                  --------------------------
> >
> >
> >
> >        pstn term.               ephemeral term.
> > -------------------------------------------------------------------------
> >          recv only             recv only                  ---1)
> >          recv only             send only                 ---2)
> >          recv only             sendreceive        ---3)
> >          send only        recv only               ---4)
> >          send only        send only              ---5)
> >          send only        sendreceive     --6)
> >          sendreceive   recv only                  --7)
> >          sendreceive   send only                 --8)
> >          sendreceive   sendreceive       --9)
> >
> >
> > follwoing the way of undestanding is correct?
> >
> > 1) means
> >    It can receive data from LEX, but can not transfer over IP to peer MG.
> [Giri] Your first part of the understanding is true.
> >    It can receive data from peer MG, but can not transfer to PSTN network.
> >
> [Giri] Stream Mode at pstn term = recv only, implies
>            PSTN termination can only recieve media from LEX into the
>            context. Nothing more than that. It doesn't say whether it
>            can/can't transfer over IP to peer MG.
>            And similarly the Stream Mode at eph term = recv only, implies
>            EPH termination can only receive media from peer MG into the
>            context. Nothing more than that. It doesn't say whether it
>            can/can't transfer to PSTN network.
> Hope this clears your doubt.
> Thanks,
> Giri
> --
> 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 Extn. 233
> 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 Extn. 233
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  Thu Apr 18 06:34: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 GAA00616
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 06:34:13 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA14978
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 06:34:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA13592;
	Thu, 18 Apr 2002 06:11:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA13557
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 06:10:59 -0400 (EDT)
Received: from blaze.hcltech.com (pop.hclt-guindy.co.in [203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00386
	for <megaco@ietf.org>; Thu, 18 Apr 2002 06:10:53 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id PAA16949;
	Thu, 18 Apr 2002 15:39:13 +0530
Message-ID: <3CBE9162.A45370D4@netlab.hcltech.com>
Date: Thu, 18 Apr 2002 14:56:58 +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: hektor@etri.re.kr
CC: megaco@ietf.org
Subject: Re: [Megaco] (no subject)
References: <8470181DABD5D511B3E700D0B7A8AC4A5DA37C@cms3.etri.re.kr>
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,
	Think, we can specify. But do we need to use "send-recieve" on the pstn
termination at MG1, when we want to only send data to LEX1. Any specific reason?
Regds.,
Giri

> hektor@etri.re.kr wrote:
> 
> hi, Giri and list.
> 
> thanks Giri.
> 
> your answer is very right.
> but I asking not asking meaning of mode in the individual termination
> but the effect of pair of modes in terminations in context whichs abstract
> connection.
> Topology in context assummed bothway.
> 
> In other words, my question can be rewritten this way with respect to real
> application.
> 
> see below,
>                 MGC1                     MGC2
>                   |                              |
> LEX1 ------- MG1 ----------------------MG2-----LEX2
>          (originating)           (terminating)
> 
> when servicing 1 on 1 voice call,
> if needed to open onyway connection from LEX2 to LEX1,
> (only lex2 can transfer its data over IP network to lex1)
> Can we specify modes in localcontrol descriptor like below?
>         In MG1,
>    pstn term. :  send only/sendreceive
>    ephemeral term. : recv only
>        In MG2,
>    pstn term. : recv only
>    ephemeral term. : send only
> 
> thanks in advance.
> 
> Hi,
> Extract from the draft draft-ietf-megaco-h248v2-00.txt.
> Notice the word highlighted with ^^^^^^.
>    "The allowed values for the mode property are send-only, receive-
>    only, send/receive, inactive and loop-back.  "Send" and "receive"
>    are with respect to the exterior of the context, so that, for
>                                                    ^^^^^^^^
>    example, a stream set to mode=sendonly does not pass received media
>    into the context. The default value for the mode property is
>    "Iactive"."
> So the mode talks about the media entering or leaving the context at this
> termination.
> send-only - Media is allowed to go outside of the context at this termination
> but not inside.
> recv-only - Media is allowed to go inside of the context at this termination
> but
> not outside.
> See for Giri for my inline comments.
> > hektor@etri.re.kr wrote:
> >
> > hi, list
> >
> >
> >
> > I have some questions about mode in localcontrol descriptor.
> > could you please clear my head?
> > see following examples(let's assume this can be happened in Trunking gateway
> 
> > using IP Packet network)
> >
> >                                                                 ctx1
> >                                                  --------------------------
> > pstn network --        pstn term ---  eph term                 --- IP
> network
> >                                                  --------------------------
> >
> >
> >
> >        pstn term.               ephemeral term.
> > -------------------------------------------------------------------------
> >          recv only             recv only                  ---1)
> >          recv only             send only                 ---2)
> >          recv only             sendreceive        ---3)
> >          send only        recv only               ---4)
> >          send only        send only              ---5)
> >          send only        sendreceive     --6)
> >          sendreceive   recv only                  --7)
> >          sendreceive   send only                 --8)
> >          sendreceive   sendreceive       --9)
> >
> >
> > follwoing the way of undestanding is correct?
> >
> > 1) means
> >    It can receive data from LEX, but can not transfer over IP to peer MG.
> [Giri] Your first part of the understanding is true.
> >    It can receive data from peer MG, but can not transfer to PSTN network.
> >
> [Giri] Stream Mode at pstn term = recv only, implies
>            PSTN termination can only recieve media from LEX into the
>            context. Nothing more than that. It doesn't say whether it
>            can/can't transfer over IP to peer MG.
>            And similarly the Stream Mode at eph term = recv only, implies
>            EPH termination can only receive media from peer MG into the
>            context. Nothing more than that. It doesn't say whether it
>            can/can't transfer to PSTN network.
> Hope this clears your doubt.
> Thanks,
> Giri
> --
> 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 Extn. 233
> 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 Extn. 233
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  Thu Apr 18 10:35: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 KAA08281
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 10:35:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27805;
	Thu, 18 Apr 2002 09:58:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27695
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 09:58:27 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06299
	for <megaco@ietf.org>; Thu, 18 Apr 2002 09:58:23 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3IDvtK25224;
	Thu, 18 Apr 2002 09:57:55 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'SRD Wang JuLin'" <WangJL2@sbell.com.cn>,
        "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: "'Barcotti, Glauco'" <Glauco_Barcotti@mitel.com>, <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
Date: Thu, 18 Apr 2002 09:58:19 -0400
Message-ID: <000801c1e6e1$18dc85e0$368910ac@Bala>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <C65F869D22451348A9970B1670ED366301968D6C@bellnet-mail1.sbell.com.cn>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id JAA27696
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 agree with Christer's views.

If MG sends a ServiceChange 'ROOT', it only means that the gateway is in
or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). The
protocol is very clear on this, I think.

Given that -- SVC(ROOT) means that the gateway is up -- now there are
many ways MGC could come to know of what terminations are in service:

1. MG sends ServiceChange for all the terminations that are in service
individually (If there are large number of terminations, the MG could
use *ranges* of TerminationIds(?) to limit the number of such messages)

2. MGC could audit the MG for the list of terminations that are in
service in which case the MG returns the list of terminations that are
in service.

But clearly sending a ServiceChange('ROOT') does not mean that all the
terminations in the MG are in service. This presents lot of operational
problems as Christer pointed out.

-- Bala

__________________
Bala Pitchandi
UTStarcom Inc.


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
SRD Wang JuLin
Sent: Thursday, April 18, 2002 2:52 AM
To: Christer Holmberg
Cc: Barcotti, Glauco; megaco@ietf.org
Subject: RE: [Megaco] ServiceChange for a single termination (Cold
Start)


Hi,
Well,I think MGC should send Modify messages (the number of it equals to
the number of terminations in RGW,I only refer to Residential GW) to
check the terminations's events  after MG reboot with Cold Start as a
whole entity. All terminations will start up.In case of some
terminations fail to use,of course,we should send SC for definite
invalid termination with restored method  to Softswtich. Before you WANT
to use a termination,you should know whether it is ABLE to use (ie.in
service or out of  service).

best  regards
> :-)Jerry Wang
tel:(8621)58541240 ext 9615
mailto:wangjl2@sbell.com.cn
Shanghai Bell Co.LTD



-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Thursday, April 18, 2002 2:27 PM
To: SRD Wang JuLin
Cc: Barcotti, Glauco; megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
Start)



Hi,

So, you want me to send a MODIFY to each of the THOUSANDS of
terminations I may want to use????

And, the issue is not which termination I WANT to use (ie which I want
the MGC to "enable" in the MG), but which termination I am ABLE (ie
which termination has at a certain time been booted/loaded/whatevver) to
use...

Regards,

Christer Holmberg
Ericsson Finland





SRD Wang JuLin wrote:

> Hi,
> Well,I send the ServiceChange for Root to Softswitch,it only send 4 
> modify messages  to RGW.So i can only use 4 out of the 8 phones 
> located in RGW. (I had provisioned 8 terminations into Softswitch
>
> )
> 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
>                          4500 008e 028b 0000 3f11 63de 0a0a 007a
>                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b4d 543d 5253 2c52 453d 3930 312c 4144
>                          3d31 3131 3232 2c50 463d 416e 616c 6f67
>                          5f4c 696e 655f 496e 7465 726f 7065 7261
>                          6269 6c69 7479 5f54 6573 745f 5072 6f66
>                          696c 652f 312c 563d 317d 7d7d 7d0a
>
>                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
>                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { M  T =  R S  , R  E =  9 0  1 ,  A D
>                           = 1  1 1  2 2  , P  F =  A n  a l  o g
>                           _ L  i n  e _  I n  t e  r o  p e  r a
>                           b i  l i  t y  _ T  e s  t _  P r  o f
>                           i l  e /  1 ,  V =  1 }  } }  }^J 
> 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
>                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
>                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b41 443d 3131 3132 322c 5046 3d43 4c53
>                          2f31 2c56 3d31 7d7d 7d7d
>
>                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
>                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
>                           / 1  , V  = 1  } }  } } 16:46:18.325927 eth0

> > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } } 
> 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 337b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  1 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } } 
> 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } } 
> 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 367b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  3 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } } 
> 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0293 0000 3f11 6402 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327d 7d0a 503d 3432 317b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  3 }
>                           }^J
> 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0294 0000 3f11 6401 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357d 7d0a 503d 3432 337b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  6 }
>                           }^J
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> best  regards
> > :-)Jerry Wang
> tel:(8621)58541240 ext 9615
> mailto:wangjl2@sbell.com.cn
> Shanghai Bell Co.LTD
>
> -----Original Message-----
> From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> Sent: Wednesday, April 17, 2002 10:10 PM
> To: 'Christer Holmberg'
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] ServiceChange for a single termination (Cold 
> Start)
>
> Hi,
>
> >>         Assuming a Gateway with 2 terminations, one of >them is OK 
> >> and the other is Malfunctioning. How should I >proceed if I want to

> >> bring just the working termination >up (Cold Start)?
> >>
> >> a) If a ServiceChange is issued for ROOT termination MGC will think

> >> that all terminations are up and, until another ServiceChange is 
> >> issued taking the defective Termination out of service, a call 
> >> could be attempted on that defective termination
>
> >I don't agree. A ServiceChange for ROOT will indicate that the MG is 
> >up, not specific terminations. You would then have to send additonal 
> >ServiceChange commands, with Reason code 900, for each termination 
> >you want to put in-service.
>
> The example in the spec (Appendix A) and the 
> draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT 
> on a ServiceChange all terminations are addressed (One ServiceChange 
> ROOT is sent and the terminations are available to use). Where did you

> find information about ServiceChange ROOT not bringing all 
> terminations up?
>
> Thanks,
> Glauco
>
> >Regards,
>
> >hrister Holmberg
> >ricsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The

> > ability to redirect the gateway to another MGC will be lost (See 
> > quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root 
> > terminationID is used.  In that case it includes the following 
> > parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing 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 Apr 18 10:35: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 KAA08293
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 10:35:34 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA01018
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 10:35:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27805;
	Thu, 18 Apr 2002 09:58:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27695
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 09:58:27 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06299
	for <megaco@ietf.org>; Thu, 18 Apr 2002 09:58:23 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3IDvtK25224;
	Thu, 18 Apr 2002 09:57:55 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'SRD Wang JuLin'" <WangJL2@sbell.com.cn>,
        "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: "'Barcotti, Glauco'" <Glauco_Barcotti@mitel.com>, <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
Date: Thu, 18 Apr 2002 09:58:19 -0400
Message-ID: <000801c1e6e1$18dc85e0$368910ac@Bala>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <C65F869D22451348A9970B1670ED366301968D6C@bellnet-mail1.sbell.com.cn>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id JAA27696
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 agree with Christer's views.

If MG sends a ServiceChange 'ROOT', it only means that the gateway is in
or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). The
protocol is very clear on this, I think.

Given that -- SVC(ROOT) means that the gateway is up -- now there are
many ways MGC could come to know of what terminations are in service:

1. MG sends ServiceChange for all the terminations that are in service
individually (If there are large number of terminations, the MG could
use *ranges* of TerminationIds(?) to limit the number of such messages)

2. MGC could audit the MG for the list of terminations that are in
service in which case the MG returns the list of terminations that are
in service.

But clearly sending a ServiceChange('ROOT') does not mean that all the
terminations in the MG are in service. This presents lot of operational
problems as Christer pointed out.

-- Bala

__________________
Bala Pitchandi
UTStarcom Inc.


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
SRD Wang JuLin
Sent: Thursday, April 18, 2002 2:52 AM
To: Christer Holmberg
Cc: Barcotti, Glauco; megaco@ietf.org
Subject: RE: [Megaco] ServiceChange for a single termination (Cold
Start)


Hi,
Well,I think MGC should send Modify messages (the number of it equals to
the number of terminations in RGW,I only refer to Residential GW) to
check the terminations's events  after MG reboot with Cold Start as a
whole entity. All terminations will start up.In case of some
terminations fail to use,of course,we should send SC for definite
invalid termination with restored method  to Softswtich. Before you WANT
to use a termination,you should know whether it is ABLE to use (ie.in
service or out of  service).

best  regards
> :-)Jerry Wang
tel:(8621)58541240 ext 9615
mailto:wangjl2@sbell.com.cn
Shanghai Bell Co.LTD



-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Thursday, April 18, 2002 2:27 PM
To: SRD Wang JuLin
Cc: Barcotti, Glauco; megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
Start)



Hi,

So, you want me to send a MODIFY to each of the THOUSANDS of
terminations I may want to use????

And, the issue is not which termination I WANT to use (ie which I want
the MGC to "enable" in the MG), but which termination I am ABLE (ie
which termination has at a certain time been booted/loaded/whatevver) to
use...

Regards,

Christer Holmberg
Ericsson Finland





SRD Wang JuLin wrote:

> Hi,
> Well,I send the ServiceChange for Root to Softswitch,it only send 4 
> modify messages  to RGW.So i can only use 4 out of the 8 phones 
> located in RGW. (I had provisioned 8 terminations into Softswitch
>
> )
> 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
>                          4500 008e 028b 0000 3f11 63de 0a0a 007a
>                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b4d 543d 5253 2c52 453d 3930 312c 4144
>                          3d31 3131 3232 2c50 463d 416e 616c 6f67
>                          5f4c 696e 655f 496e 7465 726f 7065 7261
>                          6269 6c69 7479 5f54 6573 745f 5072 6f66
>                          696c 652f 312c 563d 317d 7d7d 7d0a
>
>                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
>                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { M  T =  R S  , R  E =  9 0  1 ,  A D
>                           = 1  1 1  2 2  , P  F =  A n  a l  o g
>                           _ L  i n  e _  I n  t e  r o  p e  r a
>                           b i  l i  t y  _ T  e s  t _  P r  o f
>                           i l  e /  1 ,  V =  1 }  } }  }^J 
> 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
>                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
>                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
>                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
>                          7b41 443d 3131 3132 322c 5046 3d43 4c53
>                          2f31 2c56 3d31 7d7d 7d7d
>
>                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
>                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
>                           1 {  C =  - {  S C  = R  O O  T {  S V
>                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
>                           / 1  , V  = 1  } }  } } 16:46:18.325927 eth0

> > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } } 
> 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 337b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  1 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } } 
> 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } } 
> 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
>                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
>                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
>                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
>                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 367b 453d 3538 3938 3239 7b61
>                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
>                          742c 454d 7b53 477b 6367 2f64 747d 2c45
>                          3d33 3933 3231 377b 6464 2f63 657b 2044
>                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
>                          6f6e 7b73 7472 6963 743d 6578 6163 747d
>                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
>                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
>
>                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
>                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
>                           4 2  3 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
>                           l /  o f  { s  t r  i c  t =  e x  a c
>                           t ,  E M  { S  G {  c g  / d  t }  , E
>                           = 3  9 3  2 1  7 {  d d  / c  e {    D
>                           M =  d i  a l  p l  a n  1 }  , a  l /
>                           o n  { s  t r  i c  t =  e x  a c  t }
>                           , g  / s  c }  } }  , a  l /  o n  { s
>                           t r  i c  t =  e x  a c  t }  } }  } } 
> 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0293 0000 3f11 6402 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 327d 7d0a 503d 3432 317b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  0 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  3 }
>                           }^J
> 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
>                          4500 0062 0294 0000 3f11 6401 0a0a 007a
>                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
>                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
>                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
>                          756c 772f 357d 7d0a 503d 3432 337b 433d
>                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
>                          7d0a
>
>                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
>                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
>                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
>                           4 2  2 {  C =  - {  M F  = a  g w  _ j
>                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
>                           - {  M F  = a  g w  _ j  u l  w /  6 }
>                           }^J
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> best  regards
> > :-)Jerry Wang
> tel:(8621)58541240 ext 9615
> mailto:wangjl2@sbell.com.cn
> Shanghai Bell Co.LTD
>
> -----Original Message-----
> From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> Sent: Wednesday, April 17, 2002 10:10 PM
> To: 'Christer Holmberg'
> Cc: 'megaco@ietf.org'
> Subject: RE: [Megaco] ServiceChange for a single termination (Cold 
> Start)
>
> Hi,
>
> >>         Assuming a Gateway with 2 terminations, one of >them is OK 
> >> and the other is Malfunctioning. How should I >proceed if I want to

> >> bring just the working termination >up (Cold Start)?
> >>
> >> a) If a ServiceChange is issued for ROOT termination MGC will think

> >> that all terminations are up and, until another ServiceChange is 
> >> issued taking the defective Termination out of service, a call 
> >> could be attempted on that defective termination
>
> >I don't agree. A ServiceChange for ROOT will indicate that the MG is 
> >up, not specific terminations. You would then have to send additonal 
> >ServiceChange commands, with Reason code 900, for each termination 
> >you want to put in-service.
>
> The example in the spec (Appendix A) and the 
> draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT 
> on a ServiceChange all terminations are addressed (One ServiceChange 
> ROOT is sent and the terminations are available to use). Where did you

> find information about ServiceChange ROOT not bringing all 
> terminations up?
>
> Thanks,
> Glauco
>
> >Regards,
>
> >hrister Holmberg
> >ricsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The

> > ability to redirect the gateway to another MGC will be lost (See 
> > quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root 
> > terminationID is used.  In that case it includes the following 
> > parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing 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 Apr 18 14:17: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 OAA17930
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:17:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA20360;
	Thu, 18 Apr 2002 13:58:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA20333
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 13:58:25 -0400 (EDT)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17257
	for <megaco@ietf.org>; Thu, 18 Apr 2002 13:58:21 -0400 (EDT)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AHU31107;
	Thu, 18 Apr 2002 13:57:18 -0400 (EDT)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Venkatesh A'" <venkatesh@netlab.hcltech.com>, <megaco@ietf.org>
Subject: RE: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
Date: Thu, 18 Apr 2002 13:51:07 -0400
Message-ID: <031701c1e701$9eedc250$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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <BCEGLBPKBLPEGJMFNDJMCEPDCKAA.venkatesh@netlab.hcltech.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

The MG should have a list of its primary MGC and secondary MGCs. Thus
identifying whether the request has been originated from the active
controller. Whether its TCP/UDP the MG need this information as, it has to
fall back to other MGCs in case of failure of its primary MGC.
Regards
Madhubabu Brahmanapally.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Venkatesh A
Sent: Thursday, April 18, 2002 3:04 AM
To: megaco@ietf.org
Subject: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress


Hi All,

This is regarding the NOTIFICATION medGwyInvalidControllerAddress in megaco
mib.  The draft says that this notfication has to be raised whenever a
message is received from a controller that did not match any one valid
controller IP address.  Here what is meant by "invalid controller" ???  Does
it mean to say the mgc should be present in the pre provisioned list with
mg?  In case of mg running on UDP, mg is not keeping the ip address of mgc
whom it is talking to.  It simply replies to the mgc from where the request
came.  So, when / how should this NOTIFICATION be raised?

Thanks
Venkatesh


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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


From daemon@optimus.ietf.org  Thu Apr 18 14:17: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 OAA17939
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:17:40 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA22272
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 14:17:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA20360;
	Thu, 18 Apr 2002 13:58:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA20333
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 13:58:25 -0400 (EDT)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17257
	for <megaco@ietf.org>; Thu, 18 Apr 2002 13:58:21 -0400 (EDT)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AHU31107;
	Thu, 18 Apr 2002 13:57:18 -0400 (EDT)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Venkatesh A'" <venkatesh@netlab.hcltech.com>, <megaco@ietf.org>
Subject: RE: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
Date: Thu, 18 Apr 2002 13:51:07 -0400
Message-ID: <031701c1e701$9eedc250$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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <BCEGLBPKBLPEGJMFNDJMCEPDCKAA.venkatesh@netlab.hcltech.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

The MG should have a list of its primary MGC and secondary MGCs. Thus
identifying whether the request has been originated from the active
controller. Whether its TCP/UDP the MG need this information as, it has to
fall back to other MGCs in case of failure of its primary MGC.
Regards
Madhubabu Brahmanapally.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Venkatesh A
Sent: Thursday, April 18, 2002 3:04 AM
To: megaco@ietf.org
Subject: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress


Hi All,

This is regarding the NOTIFICATION medGwyInvalidControllerAddress in megaco
mib.  The draft says that this notfication has to be raised whenever a
message is received from a controller that did not match any one valid
controller IP address.  Here what is meant by "invalid controller" ???  Does
it mean to say the mgc should be present in the pre provisioned list with
mg?  In case of mg running on UDP, mg is not keeping the ip address of mgc
whom it is talking to.  It simply replies to the mgc from where the request
came.  So, when / how should this NOTIFICATION be raised?

Thanks
Venkatesh


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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



From megaco-admin@ietf.org  Thu Apr 18 14:25: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 OAA18299
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:25:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21681;
	Thu, 18 Apr 2002 14:10:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA29459
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 02:55:09 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27411
	for <megaco@ietf.org>; Thu, 18 Apr 2002 02:55:05 -0400 (EDT)
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 g3I6sZY04365;
	Thu, 18 Apr 2002 08:54:36 +0200 (MEST)
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 IAA07342;
	Thu, 18 Apr 2002 08:54:21 +0200 (MET DST)
Message-ID: <3CBE6BB2.885472A5@alcatel.es>
Date: Thu, 18 Apr 2002 08:46:10 +0200
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: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: "Barcotti, Glauco" <Glauco_Barcotti@mitel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F08@rndex50.ottawa.mitel.com> <3CBE5F4B.C53A9F2@lmf.ericsson.se>
Content-Type: multipart/alternative;
 boundary="------------C3AE132E7CD6B16E5D45A779"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

Hi,
See comments interleaved

Christer Holmberg wrote:

> Hi,
>
> > Hi,
> >
> > >>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
> > >>
> > >> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
> >
> > >I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
> >
> > The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up?
>
> Assume my MG comes up, but for whatever reason I don't have TDM interface card X available, so those timeslots/terminations are not available. Now, to tell the MGC that there are two options:
>
> 1. I configure the MGC manually not to use those terminations.
>
> 2. The MGC will have to do Audit to find out which terminations are in servce.

There is a third option:

    3. Assume all terminations are up. The MG will send SVC (Forced) only for those termination down (the ones on the card x)


>
>
> Now, I don't like option 1.
>
> And, when card X is put back into service, or I put a new card in my MG, there will have to be ServiceChanges for those terminations anyway, because I don't think we can assume the MGC to Audit the MG all the time.

    The MGC does not need to audit anything it knows now what terminations are up (by default) and which ones down (due to the SVC(Forced) ).
    If the card restores the service a SVGC (Restart) will be sent only for the terminations on the Card X. The process is simpler than sending a restart for all terminations in the system
    on startup.

>
>
> Also, if I have a very big MG it may take different time before all interfaces are up. But, I still want to start using some interfaces, so I don't want to wait with the registration ServiceChange until all interfaces are up. But, again, the MGC would now have to start doing frequent Audits, to find out which interfaces are up, and
> which are not, until it realizes all terminations are up.
>
> Chapter 6.2.5 defines that the ROOT specify the whole MG, rather than specific terminations. My understanding is that it does NOT say that includes the terminations. Also, how would you define the difference between TerminationID=ROOT and TerminationID=ALL???
>
> Also, IF ROOT would include all terminations, why am I not to send a Subtract with ContextID=ALL and TerminationID=ROOT???
>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> >
> >
> > Thanks,
> > Glauco
> >
> > >Regards,
> >
> > >hrister Holmberg
> > >ricsson Finland
> >
> > >
> > >
> > > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> > >
> > > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> > >
> > > Thanks,
> > > Glauco
> > >
> > > _______________________________________________
> > > Megaco mailing list
> > > Megaco@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/megaco
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

Regards
Fernando



--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi,
<br>See comments interleaved
<p>Christer Holmberg wrote:
<blockquote TYPE=CITE>Hi,
<p>> Hi,
<br>>
<br>> >>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assuming a Gateway
with 2 terminations, one of >them is OK and the other is Malfunctioning.
How should I >proceed if I want to bring just the working termination >up
(Cold Start)?
<br>> >>
<br>> >> a) If a ServiceChange is issued for ROOT termination MGC will
think that all terminations are up and, until another ServiceChange is
issued taking the defective Termination out of service, a call could be
attempted on that defective termination
<br>>
<br>> >I don't agree. A ServiceChange for ROOT will indicate that the MG
is up, not specific terminations. You would then have to send additonal
ServiceChange commands, with Reason code 900, for each termination you
want to put in-service.
<br>>
<br>> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt
tell me that when I address ROOT on a ServiceChange all terminations are
addressed (One ServiceChange ROOT is sent and the terminations are available
to use). Where did you find information about ServiceChange ROOT not bringing
all terminations up?
<p>Assume my MG comes up, but for whatever reason I don't have TDM interface
card X available, so those timeslots/terminations are not available. Now,
to tell the MGC that there are two options:
<p>1. I configure the MGC manually not to use those terminations.
<p>2. The MGC will have to do Audit to find out which terminations are
in servce.</blockquote>
There is a third option:
<p>&nbsp;&nbsp;&nbsp; 3. Assume all terminations are up. The MG&nbsp;will
send SVC&nbsp;(Forced) only for those termination down (the ones on the
card x)
<br>&nbsp;
<blockquote TYPE=CITE>&nbsp;
<p>Now, I don't like option 1.
<p>And, when card X is put back into service, or I put a new card in my
MG, there will have to be ServiceChanges for those terminations anyway,
because I don't think we can assume the MGC to Audit the MG all the time.</blockquote>

<p><br>&nbsp;&nbsp;&nbsp; The MGC does not need to audit anything it knows
now what terminations are up (by default) and which ones down (due to the
SVC(Forced)&nbsp;).
<br>&nbsp;&nbsp;&nbsp; If the card restores the service a SVGC&nbsp;(Restart)
will be sent only for the terminations on the Card X. The process is simpler
than sending a restart for all terminations in the system
<br>&nbsp;&nbsp;&nbsp; on startup.
<blockquote TYPE=CITE>&nbsp;
<p>Also, if I have a very big MG it may take different time before all
interfaces are up. But, I still want to start using some interfaces, so
I don't want to wait with the registration ServiceChange until all interfaces
are up. But, again, the MGC would now have to start doing frequent Audits,
to find out which interfaces are up, and
<br>which are not, until it realizes all terminations are up.
<p>Chapter 6.2.5 defines that the ROOT specify the whole MG, rather than
specific terminations. My understanding is that it does NOT say that includes
the terminations. Also, how would you define the difference between TerminationID=ROOT
and TerminationID=ALL???
<p>Also, IF ROOT would include all terminations, why am I not to send a
Subtract with ContextID=ALL and TerminationID=ROOT???
<p>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<p>>
<br>>
<br>> Thanks,
<br>> Glauco
<br>>
<br>> >Regards,
<br>>
<br>> >hrister Holmberg
<br>> >ricsson Finland
<br>>
<br>> >
<br>> >
<br>> > b) If a ServiceChange is issued just for the working Termination
The ability to redirect the gateway to another MGC will be lost (See quotation
from spec below)
<br>> >
<br>> > "The return from ServiceChange is empty except when the Root terminationID
is used.&nbsp; In that case it includes the following parameters as required:"
<br>> >
<br>> > Thanks,
<br>> > Glauco
<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>_______________________________________________
<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>

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

--------------C3AE132E7CD6B16E5D45A779--



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


From daemon@optimus.ietf.org  Thu Apr 18 14:26: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 OAA18312
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:25:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA22776
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 14:26:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21681;
	Thu, 18 Apr 2002 14:10:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA29459
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 02:55:09 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27411
	for <megaco@ietf.org>; Thu, 18 Apr 2002 02:55:05 -0400 (EDT)
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 g3I6sZY04365;
	Thu, 18 Apr 2002 08:54:36 +0200 (MEST)
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 IAA07342;
	Thu, 18 Apr 2002 08:54:21 +0200 (MET DST)
Message-ID: <3CBE6BB2.885472A5@alcatel.es>
Date: Thu, 18 Apr 2002 08:46:10 +0200
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: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: "Barcotti, Glauco" <Glauco_Barcotti@mitel.com>,
        "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <29B5A21C13C8D51190F900805F65B4EC506F08@rndex50.ottawa.mitel.com> <3CBE5F4B.C53A9F2@lmf.ericsson.se>
Content-Type: multipart/alternative;
 boundary="------------C3AE132E7CD6B16E5D45A779"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

Hi,
See comments interleaved

Christer Holmberg wrote:

> Hi,
>
> > Hi,
> >
> > >>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
> > >>
> > >> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
> >
> > >I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
> >
> > The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up?
>
> Assume my MG comes up, but for whatever reason I don't have TDM interface card X available, so those timeslots/terminations are not available. Now, to tell the MGC that there are two options:
>
> 1. I configure the MGC manually not to use those terminations.
>
> 2. The MGC will have to do Audit to find out which terminations are in servce.

There is a third option:

    3. Assume all terminations are up. The MG will send SVC (Forced) only for those termination down (the ones on the card x)


>
>
> Now, I don't like option 1.
>
> And, when card X is put back into service, or I put a new card in my MG, there will have to be ServiceChanges for those terminations anyway, because I don't think we can assume the MGC to Audit the MG all the time.

    The MGC does not need to audit anything it knows now what terminations are up (by default) and which ones down (due to the SVC(Forced) ).
    If the card restores the service a SVGC (Restart) will be sent only for the terminations on the Card X. The process is simpler than sending a restart for all terminations in the system
    on startup.

>
>
> Also, if I have a very big MG it may take different time before all interfaces are up. But, I still want to start using some interfaces, so I don't want to wait with the registration ServiceChange until all interfaces are up. But, again, the MGC would now have to start doing frequent Audits, to find out which interfaces are up, and
> which are not, until it realizes all terminations are up.
>
> Chapter 6.2.5 defines that the ROOT specify the whole MG, rather than specific terminations. My understanding is that it does NOT say that includes the terminations. Also, how would you define the difference between TerminationID=ROOT and TerminationID=ALL???
>
> Also, IF ROOT would include all terminations, why am I not to send a Subtract with ContextID=ALL and TerminationID=ROOT???
>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> >
> >
> > Thanks,
> > Glauco
> >
> > >Regards,
> >
> > >hrister Holmberg
> > >ricsson Finland
> >
> > >
> > >
> > > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> > >
> > > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> > >
> > > Thanks,
> > > Glauco
> > >
> > > _______________________________________________
> > > Megaco mailing list
> > > Megaco@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/megaco
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

Regards
Fernando



--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi,
<br>See comments interleaved
<p>Christer Holmberg wrote:
<blockquote TYPE=CITE>Hi,
<p>> Hi,
<br>>
<br>> >>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assuming a Gateway
with 2 terminations, one of >them is OK and the other is Malfunctioning.
How should I >proceed if I want to bring just the working termination >up
(Cold Start)?
<br>> >>
<br>> >> a) If a ServiceChange is issued for ROOT termination MGC will
think that all terminations are up and, until another ServiceChange is
issued taking the defective Termination out of service, a call could be
attempted on that defective termination
<br>>
<br>> >I don't agree. A ServiceChange for ROOT will indicate that the MG
is up, not specific terminations. You would then have to send additonal
ServiceChange commands, with Reason code 900, for each termination you
want to put in-service.
<br>>
<br>> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt
tell me that when I address ROOT on a ServiceChange all terminations are
addressed (One ServiceChange ROOT is sent and the terminations are available
to use). Where did you find information about ServiceChange ROOT not bringing
all terminations up?
<p>Assume my MG comes up, but for whatever reason I don't have TDM interface
card X available, so those timeslots/terminations are not available. Now,
to tell the MGC that there are two options:
<p>1. I configure the MGC manually not to use those terminations.
<p>2. The MGC will have to do Audit to find out which terminations are
in servce.</blockquote>
There is a third option:
<p>&nbsp;&nbsp;&nbsp; 3. Assume all terminations are up. The MG&nbsp;will
send SVC&nbsp;(Forced) only for those termination down (the ones on the
card x)
<br>&nbsp;
<blockquote TYPE=CITE>&nbsp;
<p>Now, I don't like option 1.
<p>And, when card X is put back into service, or I put a new card in my
MG, there will have to be ServiceChanges for those terminations anyway,
because I don't think we can assume the MGC to Audit the MG all the time.</blockquote>

<p><br>&nbsp;&nbsp;&nbsp; The MGC does not need to audit anything it knows
now what terminations are up (by default) and which ones down (due to the
SVC(Forced)&nbsp;).
<br>&nbsp;&nbsp;&nbsp; If the card restores the service a SVGC&nbsp;(Restart)
will be sent only for the terminations on the Card X. The process is simpler
than sending a restart for all terminations in the system
<br>&nbsp;&nbsp;&nbsp; on startup.
<blockquote TYPE=CITE>&nbsp;
<p>Also, if I have a very big MG it may take different time before all
interfaces are up. But, I still want to start using some interfaces, so
I don't want to wait with the registration ServiceChange until all interfaces
are up. But, again, the MGC would now have to start doing frequent Audits,
to find out which interfaces are up, and
<br>which are not, until it realizes all terminations are up.
<p>Chapter 6.2.5 defines that the ROOT specify the whole MG, rather than
specific terminations. My understanding is that it does NOT say that includes
the terminations. Also, how would you define the difference between TerminationID=ROOT
and TerminationID=ALL???
<p>Also, IF ROOT would include all terminations, why am I not to send a
Subtract with ContextID=ALL and TerminationID=ROOT???
<p>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<p>>
<br>>
<br>> Thanks,
<br>> Glauco
<br>>
<br>> >Regards,
<br>>
<br>> >hrister Holmberg
<br>> >ricsson Finland
<br>>
<br>> >
<br>> >
<br>> > b) If a ServiceChange is issued just for the working Termination
The ability to redirect the gateway to another MGC will be lost (See quotation
from spec below)
<br>> >
<br>> > "The return from ServiceChange is empty except when the Root terminationID
is used.&nbsp; In that case it includes the following parameters as required:"
<br>> >
<br>> > Thanks,
<br>> > Glauco
<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>_______________________________________________
<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>

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

--------------C3AE132E7CD6B16E5D45A779--



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



From megaco-admin@ietf.org  Thu Apr 18 14:27: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 OAA18431
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:27:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21349;
	Thu, 18 Apr 2002 14:05:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21298
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 14:04:59 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17497
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:04:56 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3II4iK28215
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:04:44 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Subject: RE: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
Date: Thu, 18 Apr 2002 14:05:08 -0400
Message-ID: <001a01c1e703$93728a80$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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <BCEGLBPKBLPEGJMFNDJMCEPDCKAA.venkatesh@netlab.hcltech.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

The MG is provisioned with a list of Media Gateway Controllers through
"medGwyGatewayControllerTable" and if the MG receives a message from any
other MGC than the one provisioned in the
"medGwyGatewayControllerTable", it would send this NOTIFICATION (Trap -
medGwyInvalidControllerAddress) to the NMS Manager.

Thanks
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Venkatesh A
Sent: Thursday, April 18, 2002 3:04 AM
To: megaco@ietf.org
Subject: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress


Hi All,

This is regarding the NOTIFICATION medGwyInvalidControllerAddress in
megaco mib.  The draft says that this notfication has to be raised
whenever a message is received from a controller that did not match any
one valid controller IP address.  Here what is meant by "invalid
controller" ???  Does it mean to say the mgc should be present in the
pre provisioned list with mg?  In case of mg running on UDP, mg is not
keeping the ip address of mgc whom it is talking to.  It simply replies
to the mgc from where the request came.  So, when / how should this
NOTIFICATION be raised?

Thanks
Venkatesh


_______________________________________________
Megaco mailing list
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 Apr 18 14:27: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 OAA18441
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:27:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA22865
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 14:27:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21349;
	Thu, 18 Apr 2002 14:05:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21298
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 14:04:59 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17497
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:04:56 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3II4iK28215
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:04:44 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Subject: RE: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
Date: Thu, 18 Apr 2002 14:05:08 -0400
Message-ID: <001a01c1e703$93728a80$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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <BCEGLBPKBLPEGJMFNDJMCEPDCKAA.venkatesh@netlab.hcltech.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

The MG is provisioned with a list of Media Gateway Controllers through
"medGwyGatewayControllerTable" and if the MG receives a message from any
other MGC than the one provisioned in the
"medGwyGatewayControllerTable", it would send this NOTIFICATION (Trap -
medGwyInvalidControllerAddress) to the NMS Manager.

Thanks
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Venkatesh A
Sent: Thursday, April 18, 2002 3:04 AM
To: megaco@ietf.org
Subject: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress


Hi All,

This is regarding the NOTIFICATION medGwyInvalidControllerAddress in
megaco mib.  The draft says that this notfication has to be raised
whenever a message is received from a controller that did not match any
one valid controller IP address.  Here what is meant by "invalid
controller" ???  Does it mean to say the mgc should be present in the
pre provisioned list with mg?  In case of mg running on UDP, mg is not
keeping the ip address of mgc whom it is talking to.  It simply replies
to the mgc from where the request came.  So, when / how should this
NOTIFICATION be raised?

Thanks
Venkatesh


_______________________________________________
Megaco mailing list
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 Apr 18 14:29: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 OAA18501
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:29:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21597;
	Thu, 18 Apr 2002 14:09:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21544
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 14:09:32 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17599
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:09:23 -0400 (EDT)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id OAA22896;
	Thu, 18 Apr 2002 14:06:45 -0400 (EDT)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2751ARK6>; Thu, 18 Apr 2002 14:06:44 -0400
Message-ID: <29B5A21C13C8D51190F900805F65B4EC506F1C@rndex50.ottawa.mitel.com>
From: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
Date: Thu, 18 Apr 2002 14:06:44 -0400
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

Christer,

	I do understand your point.
	I have read section 6.2.5 but I have also seen the example in the Appendix A and they are contradictory.
	If the Appendix A had 2 ServiceChange messages (One ROOT and one for Termination-X) I would not be asking this question and we would be in agreement.
	There is also a Draft document (draft-hss-megaco-control-association-state-machine-00.txt) that seems to support the idea that ServiceChange-ROOT-restart will indicate that all terminations are in-service.

	Are the Appendix A and the Draft document on a need for an update? If so how do we proceed to eliminate these inconsistencies?

Glauco

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Thursday, April 18, 2002 1:53 AM
To: Barcotti, Glauco
Cc: 'megaco@ietf.org'
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
Start)



Hi,

> Hi,
>
> >>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
> >>
> >> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
>
> >I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
>
> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up?

Assume my MG comes up, but for whatever reason I don't have TDM interface card X available, so those timeslots/terminations are not available. Now, to tell the MGC that there are two options:

1. I configure the MGC manually not to use those terminations.

2. The MGC will have to do Audit to find out which terminations are in servce.

Now, I don't like option 1.

And, when card X is put back into service, or I put a new card in my MG, there will have to be ServiceChanges for those terminations anyway, because I don't think we can assume the MGC to Audit the MG all the time.
Also, if I have a very big MG it may take different time before all interfaces are up. But, I still want to start using some interfaces, so I don't want to wait with the registration ServiceChange until all interfaces are up. But, again, the MGC would now have to start doing frequent Audits, to find out which interfaces are up, and
which are not, until it realizes all terminations are up.

Chapter 6.2.5 defines that the ROOT specify the whole MG, rather than specific terminations. My understanding is that it does NOT say that includes the terminations. Also, how would you define the difference between TerminationID=ROOT and TerminationID=ALL???

Also, IF ROOT would include all terminations, why am I not to send a Subtract with ContextID=ALL and TerminationID=ROOT???

Regards,

Christer Holmberg
Ericsson Finland









>
>
> Thanks,
> Glauco
>
> >Regards,
>
> >hrister Holmberg
> >ricsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing list
> > 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 Apr 18 14:29: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 OAA18511
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:29:18 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA22960
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 14:29:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21597;
	Thu, 18 Apr 2002 14:09:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21544
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 14:09:32 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17599
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:09:23 -0400 (EDT)
Received: from rndex50.software.mitel.com (rndex50 [134.199.17.160]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id OAA22896;
	Thu, 18 Apr 2002 14:06:45 -0400 (EDT)
Received: by rndex50.ottawa.mitel.com with Internet Mail Service (5.5.2653.19)
	id <2751ARK6>; Thu, 18 Apr 2002 14:06:44 -0400
Message-ID: <29B5A21C13C8D51190F900805F65B4EC506F1C@rndex50.ottawa.mitel.com>
From: "Barcotti, Glauco" <Glauco_Barcotti@Mitel.COM>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
Date: Thu, 18 Apr 2002 14:06:44 -0400
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

Christer,

	I do understand your point.
	I have read section 6.2.5 but I have also seen the example in the Appendix A and they are contradictory.
	If the Appendix A had 2 ServiceChange messages (One ROOT and one for Termination-X) I would not be asking this question and we would be in agreement.
	There is also a Draft document (draft-hss-megaco-control-association-state-machine-00.txt) that seems to support the idea that ServiceChange-ROOT-restart will indicate that all terminations are in-service.

	Are the Appendix A and the Draft document on a need for an update? If so how do we proceed to eliminate these inconsistencies?

Glauco

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
Sent: Thursday, April 18, 2002 1:53 AM
To: Barcotti, Glauco
Cc: 'megaco@ietf.org'
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
Start)



Hi,

> Hi,
>
> >>         Assuming a Gateway with 2 terminations, one of >them is OK and the other is Malfunctioning. How should I >proceed if I want to bring just the working termination >up (Cold Start)?
> >>
> >> a) If a ServiceChange is issued for ROOT termination MGC will think that all terminations are up and, until another ServiceChange is issued taking the defective Termination out of service, a call could be attempted on that defective termination
>
> >I don't agree. A ServiceChange for ROOT will indicate that the MG is up, not specific terminations. You would then have to send additonal ServiceChange commands, with Reason code 900, for each termination you want to put in-service.
>
> The example in the spec (Appendix A) and the draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT on a ServiceChange all terminations are addressed (One ServiceChange ROOT is sent and the terminations are available to use). Where did you find information about ServiceChange ROOT not bringing all terminations up?

Assume my MG comes up, but for whatever reason I don't have TDM interface card X available, so those timeslots/terminations are not available. Now, to tell the MGC that there are two options:

1. I configure the MGC manually not to use those terminations.

2. The MGC will have to do Audit to find out which terminations are in servce.

Now, I don't like option 1.

And, when card X is put back into service, or I put a new card in my MG, there will have to be ServiceChanges for those terminations anyway, because I don't think we can assume the MGC to Audit the MG all the time.
Also, if I have a very big MG it may take different time before all interfaces are up. But, I still want to start using some interfaces, so I don't want to wait with the registration ServiceChange until all interfaces are up. But, again, the MGC would now have to start doing frequent Audits, to find out which interfaces are up, and
which are not, until it realizes all terminations are up.

Chapter 6.2.5 defines that the ROOT specify the whole MG, rather than specific terminations. My understanding is that it does NOT say that includes the terminations. Also, how would you define the difference between TerminationID=ROOT and TerminationID=ALL???

Also, IF ROOT would include all terminations, why am I not to send a Subtract with ContextID=ALL and TerminationID=ROOT???

Regards,

Christer Holmberg
Ericsson Finland









>
>
> Thanks,
> Glauco
>
> >Regards,
>
> >hrister Holmberg
> >ricsson Finland
>
> >
> >
> > b) If a ServiceChange is issued just for the working Termination The ability to redirect the gateway to another MGC will be lost (See quotation from spec below)
> >
> > "The return from ServiceChange is empty except when the Root terminationID is used.  In that case it includes the following parameters as required:"
> >
> > Thanks,
> > Glauco
> >
> > _______________________________________________
> > Megaco mailing list
> > 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 Apr 18 14:34: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 OAA18654
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:34:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21799;
	Thu, 18 Apr 2002 14:11:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14744
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 12:49:52 -0400 (EDT)
Received: from ns1.ottawa.alcatel.ca (ns1.ottawa.alcatel.ca [192.75.23.67])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14378
	for <megaco@ietf.org>; Thu, 18 Apr 2002 12:49:48 -0400 (EDT)
Received: (qmail 29845 invoked from network); 18 Apr 2002 16:35:28 -0000
Received: from portal.ottawa.alcatel.ca (HELO mx1.ca.alcatel.com) (192.75.23.76)
  by ns1.ottawa.alcatel.ca with SMTP; 18 Apr 2002 16:35:28 -0000
Received: (qmail 3018 invoked from network); 18 Apr 2002 16:51:19 -0000
Received: (ofmipd 138.120.45.50); 18 Apr 2002 16:50:57 -0000
Date: 18 Apr 2002 12:49:17 -0400
Message-ID: <3CBEF90D.1FCD87F3@alcatel.com>
From: "Ian Leighton" <Ian.Leighton@alcatel.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Multiple SDP's in Local and No Remote
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 would like to get some clarification on the expected behaviour of an
MG if the MGC sends a request which includes multiple SDP's in the Local
descriptor and does not include a Remote descriptor. For example if an
MGC sends the following information and the MG is capable of supporting
both AAL1 and AAL2 (assume ReserveGroup and ReserveValue are false);

add=$ {
      L {
        v=0
        c=ATM $ $
        m=audio - AAL2/ITU 1
        v=0
        c=ATM $ $
        m=audio - AAL1/ITU 0
      }
    }

would the reply include

1) both SDP's or
2) only its preferred transport.

My assumption is 1) based on 3015 section 7.1.8 description that the MG
chooses based on a both local and remote. Since the remote is not
currently available the MG replies with what it can support and chooses
a single SDP once the remote descriptor is provided.

Any comments or clarifications would be appreciated.

Regards
Ian Leighton





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


From daemon@optimus.ietf.org  Thu Apr 18 14:34: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 OAA18666
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:34:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA23592
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 14:34:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21799;
	Thu, 18 Apr 2002 14:11:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14744
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 12:49:52 -0400 (EDT)
Received: from ns1.ottawa.alcatel.ca (ns1.ottawa.alcatel.ca [192.75.23.67])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14378
	for <megaco@ietf.org>; Thu, 18 Apr 2002 12:49:48 -0400 (EDT)
Received: (qmail 29845 invoked from network); 18 Apr 2002 16:35:28 -0000
Received: from portal.ottawa.alcatel.ca (HELO mx1.ca.alcatel.com) (192.75.23.76)
  by ns1.ottawa.alcatel.ca with SMTP; 18 Apr 2002 16:35:28 -0000
Received: (qmail 3018 invoked from network); 18 Apr 2002 16:51:19 -0000
Received: (ofmipd 138.120.45.50); 18 Apr 2002 16:50:57 -0000
Date: 18 Apr 2002 12:49:17 -0400
Message-ID: <3CBEF90D.1FCD87F3@alcatel.com>
From: "Ian Leighton" <Ian.Leighton@alcatel.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Multiple SDP's in Local and No Remote
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 would like to get some clarification on the expected behaviour of an
MG if the MGC sends a request which includes multiple SDP's in the Local
descriptor and does not include a Remote descriptor. For example if an
MGC sends the following information and the MG is capable of supporting
both AAL1 and AAL2 (assume ReserveGroup and ReserveValue are false);

add=$ {
      L {
        v=0
        c=ATM $ $
        m=audio - AAL2/ITU 1
        v=0
        c=ATM $ $
        m=audio - AAL1/ITU 0
      }
    }

would the reply include

1) both SDP's or
2) only its preferred transport.

My assumption is 1) based on 3015 section 7.1.8 description that the MG
chooses based on a both local and remote. Since the remote is not
currently available the MG replies with what it can support and chooses
a single SDP once the remote descriptor is provided.

Any comments or clarifications would be appreciated.

Regards
Ian Leighton





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



From megaco-admin@ietf.org  Thu Apr 18 14:36: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 OAA18750
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:36:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21642;
	Thu, 18 Apr 2002 14:09:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25282
	for <megaco@ns.ietf.org>; Thu, 18 Apr 2002 01:36:00 -0400 (EDT)
Received: from epygilab.am (araler.epygilab.am [195.151.94.74])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18110
	for <megaco@ietf.org>; Thu, 18 Apr 2002 01:35:53 -0400 (EDT)
Received: (apparently) from epygilab.am ([192.168.0.156]) by epygilab.am  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 18 Apr 2002 09:35:29 +0400
Received: from epygilab.am [192.168.0.32]
	by epygilab.am [192.168.0.156]
	with SMTP (MDaemon.PRO.v5.0.1.R)
	for <megaco@ietf.org>; Thu, 18 Apr 2002 10:34:17 +0500
Message-ID: <3CBE68ED.CEAC5470@epygilab.am>
Date: Thu, 18 Apr 2002 10:34:21 +0400
From: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Megaco <megaco@ietf.org>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
X-MDRemoteIP: 192.168.0.32
X-Return-Path: Narine.Mossikyan@epygilab.am
X-MDaemon-Deliver-To: megaco@ietf.org
Content-Transfer-Encoding: 7bit
Subject: [Megaco] MGC to MGC connection standard
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 should be translated MEGACO messages into H323 or SIP  to be sent
between MGCs?
Is there any standard documentation for MGC to MGC connection and where
I can find it?
thank you very much for your help.
--------
regards
Narine Mossikyan
Epygi lab LLC





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


From daemon@optimus.ietf.org  Thu Apr 18 15:00: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 PAA19487
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:00:09 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA25227
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 15:00:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23942;
	Thu, 18 Apr 2002 14:39:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23913
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 14:39:20 -0400 (EDT)
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 OAA18814
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:39:15 -0400 (EDT)
Received: through eSafe SMTP Relay 1019111027; Thu Apr 18 21:38:42 2002
Received: by EXCHANGE with Internet Mail Service (5.5.2653.19)
	id <2WRMF7WK>; Thu, 18 Apr 2002 21:37:57 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF01B926C0@EXCHANGE>
From: Raphael Tryster <raphael@tdsoft.com>
To: madhubabu@kenetec.com, dham.prerepa@kenetec.com,
        krishna.gundamaraju@kenetec.com
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 18 Apr 2002 21:37:53 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E710.888A9100"
Subject: [Megaco] draft-ietf-megaco-callflows-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

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_01C1E710.888A9100
Content-Type: text/plain;
	charset="iso-8859-1"

I have some questions about the examples in this document relating to call
transfer:

1.	When UserB presses flash and is dialing UserC, what happens with
UserA?  It appears to me that in steps 19 through 30, nothing happens that
affects UserA, so UserA and UserB would continue to hear each other.  Is
this a real world scenario?  If not, what would happen in the real world?

2.	In the description before step 24, I think that "The physical
termination TermA is added to context 1" should be "The physical termination
TermC is added to context 3".

3.	Step 31 seems to be missing the ephemeral termination EphB, referred
to in the description preceding it.

4.	After step 31, the remote SDP of UserB and UserC point to each
other, but the remote SDP of UserA still points to UserB.  What is the
physical effect of this?

	And about call waiting:

5.	I believe the description before step 26 should refer to TermC
instead of TermB, and MG3 instead of MG2.

6.	In this example, each of the physical terminations has a single
ephemeral termination in the same context, and the MGC sends updated remote
SDP information each time UserB presses flash.  What are the considerations
for doing it this way, rather than creating in UserB's context a separate
ephemeral termination for each of its conversation partners and switching
the mode, such that at any time one is sendrecv and the others are inactive?

7.	What happens to UserA while UserB is in conversation with UserC?
UserA's remote SDP information still points to UserB.

	And some general questions:

8.	Does it ever make sense, and is it possible, to send a signal
"backwards" to a user by directing it at an ephemeral termination to which
it is connected?  For example, when UserA and UserB have EphA and EphB
pointing to each other, is it possible for an MGC to send a signal to EphA
to be sent to UserB?

9.	Under what circumstances, is any, could there be more than one
physical termination in a context?



Raphael Tryster

------_=_NextPart_001_01C1E710.888A9100
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.2653.12">
<TITLE>draft-ietf-megaco-callflows-00.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have some questions about the =
examples in this document relating to call transfer:</FONT>
</P>

<OL TYPE=3D1><LI><FONT SIZE=3D2 FACE=3D"Arial">When UserB presses flash =
and is dialing UserC, what happens with UserA?&nbsp; It appears to me =
that in steps 19 through 30, nothing happens that affects UserA, so =
UserA and UserB would continue to hear each other.&nbsp; Is this a real =
world scenario?&nbsp; If not, what would happen in the real =
world?</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">In the description before step 24, I =
think that "</FONT><FONT SIZE=3D2 FACE=3D"Arial">The physical =
termination TermA is added to context 1</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">" should be</FONT> <FONT SIZE=3D2 FACE=3D"Arial">"The =
physical terminati</FONT><FONT SIZE=3D2 FACE=3D"Arial">on TermC is =
added to context 3</FONT><FONT SIZE=3D2 FACE=3D"Arial">"</FONT><FONT =
SIZE=3D2 FACE=3D"Arial">.</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">Step 31 seems to be missing the =
ephemeral termination EphB, referred to in the description preceding =
it.</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">After step 31, the remote SDP of =
UserB and UserC point to each other, but the remote SDP of UserA still =
points to UserB.&nbsp; What is the physical effect of this?</FONT></LI>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">And about call waiting:</FONT>
</P>
<LI><FONT SIZE=3D2 FACE=3D"Arial">I believe the description before step =
26 should refer to TermC instead of TermB, and MG3 instead of =
MG2.</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">In this example, each of the physical =
terminations has a single ephemeral termination in the same context, =
and the MGC sends updated remote SDP information each time UserB =
presses flash.&nbsp; What are the considerations for doing it this way, =
rather than creating in UserB's context a separate ephemeral =
termination for each of its conversation partners and switching the =
mode, such that at any time one is sendrecv and the others are =
inactive?</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">What happens to UserA while UserB is =
in conversation with UserC?&nbsp; UserA's remote SDP information still =
points to UserB.</FONT></LI>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">And some general questions:</FONT>
</P>
<LI><FONT SIZE=3D2 FACE=3D"Arial">Does it ever make sense, and is it =
possible, to send a signal "backwards" to a user by directing it at an =
ephemeral termination to which it is connected?&nbsp; For example, when =
UserA and UserB have EphA and EphB pointing to each other, is it =
possible for an MGC to send a signal to EphA to be sent to =
UserB?</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">Under what circumstances, is any, =
could there be more than one physical termination in a =
context?</FONT></LI>
<BR>
<BR>
<BR>
</OL>
<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E710.888A9100--

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



From megaco-admin@ietf.org  Thu Apr 18 15:06: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 PAA19665
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:06:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA24520;
	Thu, 18 Apr 2002 14:46:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA24422
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 14:46:36 -0400 (EDT)
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 OAA18986
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:46:32 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3IIk4o15601
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:46:04 -0400 (EDT)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id OAA09781
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:46:46 -0400 (EDT)
Message-ID: <3CBF147D.D7A28C57@lucent.com>
Date: Thu, 18 Apr 2002 14:46:21 -0400
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@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <000801c1e6e1$18dc85e0$368910ac@Bala>
Content-Type: multipart/mixed;
 boundary="------------CD03154B7A22599D63E3735F"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------CD03154B7A22599D63E3735F
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes no
statement one way or the other) and it is apparent that there is not
agreement on what we want.  I believe that there are three possible
positions and that we should clarify this through the IG once we agree.

Possible clarifications:
ServiceChange on ROOT with method=restart (a registration):
1) implies that all physical terminations on MG are also up.  Exceptions
should be indicated by additional ServiceChanges on the down terminations
using Forced, preferrably in the same message and using wildcards where
possible.
2) implies that all physical terminations on MG are down.  Those that are up
will be indicated by additional ServiceChanges on the up terminations using
method=restart, preferrably in the same message and using wildcards were
possible.
3) has no implication whether physical terminations are up or down, but MGC
may be provisioned to know whether an MG will indicate terminations that are
up or those that are down.

I should say that I do not like #3 but am including it as a possibility.

Preference for #1 or #2 probably depend on:
1) whether most physical terminations are available almost immediately or
come up slowly and at different speeds.
2) whether MGC is provisioned with knowledge about the available physical
terminations on an MG or expects to learn about them through ServiceChanges
or Audits

Note that #1 can be implemented from #2 by adding:
    ServiceChange = *{Services{Method=Restart}}
to the action, and conversely #2 can be implemented from #1 by adding:
    ServiceChange = *{Services{Method=Forced}}

In either case exceptions (up or down) to the ALL can be indicated by
additional ServiceChange commands.

So (IMHO) it doesn't seem too critical which we choose, but we should choose
and document one.

Even though I think that most GWs probably would not register until all or
most of their physical terminations are available, I would probably prefer
#2 since I can easily indicated them all up with only one additional
ServiceChange and it seems more natural to indicate those up those that are
down.  But I can be happy with either #1 or #2.

What do folks prefer?

Balasubramanian Pitchandi wrote:

> Hi,
>
> I agree with Christer's views.
>
> If MG sends a ServiceChange 'ROOT', it only means that the gateway is in
> or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). The
> protocol is very clear on this, I think.
>
> Given that -- SVC(ROOT) means that the gateway is up -- now there are
> many ways MGC could come to know of what terminations are in service:
>
> 1. MG sends ServiceChange for all the terminations that are in service
> individually (If there are large number of terminations, the MG could
> use *ranges* of TerminationIds(?) to limit the number of such messages)
>
> 2. MGC could audit the MG for the list of terminations that are in
> service in which case the MG returns the list of terminations that are
> in service.
>
> But clearly sending a ServiceChange('ROOT') does not mean that all the
> terminations in the MG are in service. This presents lot of operational
> problems as Christer pointed out.
>
> -- Bala
>
> __________________
> Bala Pitchandi
> UTStarcom Inc.
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> SRD Wang JuLin
> Sent: Thursday, April 18, 2002 2:52 AM
> To: Christer Holmberg
> Cc: Barcotti, Glauco; megaco@ietf.org
> Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
> Hi,
> Well,I think MGC should send Modify messages (the number of it equals to
> the number of terminations in RGW,I only refer to Residential GW) to
> check the terminations's events  after MG reboot with Cold Start as a
> whole entity. All terminations will start up.In case of some
> terminations fail to use,of course,we should send SC for definite
> invalid termination with restored method  to Softswtich. Before you WANT
> to use a termination,you should know whether it is ABLE to use (ie.in
> service or out of  service).
>
> best  regards
> > :-)Jerry Wang
> tel:(8621)58541240 ext 9615
> mailto:wangjl2@sbell.com.cn
> Shanghai Bell Co.LTD
>
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Thursday, April 18, 2002 2:27 PM
> To: SRD Wang JuLin
> Cc: Barcotti, Glauco; megaco@ietf.org
> Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
> Hi,
>
> So, you want me to send a MODIFY to each of the THOUSANDS of
> terminations I may want to use????
>
> And, the issue is not which termination I WANT to use (ie which I want
> the MGC to "enable" in the MG), but which termination I am ABLE (ie
> which termination has at a certain time been booted/loaded/whatevver) to
> use...
>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> SRD Wang JuLin wrote:
>
> > Hi,
> > Well,I send the ServiceChange for Root to Softswitch,it only send 4
> > modify messages  to RGW.So i can only use 4 out of the 8 phones
> > located in RGW. (I had provisioned 8 terminations into Softswitch
> >
> > )
> > 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
> >                          4500 008e 028b 0000 3f11 63de 0a0a 007a
> >                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
> >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> >                          7b4d 543d 5253 2c52 453d 3930 312c 4144
> >                          3d31 3131 3232 2c50 463d 416e 616c 6f67
> >                          5f4c 696e 655f 496e 7465 726f 7065 7261
> >                          6269 6c69 7479 5f54 6573 745f 5072 6f66
> >                          696c 652f 312c 563d 317d 7d7d 7d0a
> >
> >                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
> >                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
> >                           1 {  C =  - {  S C  = R  O O  T {  S V
> >                           { M  T =  R S  , R  E =  9 0  1 ,  A D
> >                           = 1  1 1  2 2  , P  F =  A n  a l  o g
> >                           _ L  i n  e _  I n  t e  r o  p e  r a
> >                           b i  l i  t y  _ T  e s  t _  P r  o f
> >                           i l  e /  1 ,  V =  1 }  } }  }^J
> > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
> >                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
> >                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
> >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> >                          7b41 443d 3131 3132 322c 5046 3d43 4c53
> >                          2f31 2c56 3d31 7d7d 7d7d
> >
> >                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
> >                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
> >                           1 {  C =  - {  S C  = R  O O  T {  S V
> >                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
> >                           / 1  , V  = 1  } }  } } 16:46:18.325927 eth0
>
> > > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 327b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } }
> > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 337b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  1 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } }
> > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 357b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } }
> > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 367b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  3 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } }
> > 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> >                          4500 0062 0293 0000 3f11 6402 0a0a 007a
> >                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 327d 7d0a 503d 3432 317b 433d
> >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
> >                          7d0a
> >
> >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
> >                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
> >                           - {  M F  = a  g w  _ j  u l  w /  3 }
> >                           }^J
> > 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> >                          4500 0062 0294 0000 3f11 6401 0a0a 007a
> >                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 357d 7d0a 503d 3432 337b 433d
> >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
> >                          7d0a
> >
> >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
> >                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
> >                           - {  M F  = a  g w  _ j  u l  w /  6 }
> >                           }^J
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > best  regards
> > > :-)Jerry Wang
> > tel:(8621)58541240 ext 9615
> > mailto:wangjl2@sbell.com.cn
> > Shanghai Bell Co.LTD
> >
> > -----Original Message-----
> > From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> > Sent: Wednesday, April 17, 2002 10:10 PM
> > To: 'Christer Holmberg'
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> >
> > >>         Assuming a Gateway with 2 terminations, one of >them is OK
> > >> and the other is Malfunctioning. How should I >proceed if I want to
>
> > >> bring just the working termination >up (Cold Start)?
> > >>
> > >> a) If a ServiceChange is issued for ROOT termination MGC will think
>
> > >> that all terminations are up and, until another ServiceChange is
> > >> issued taking the defective Termination out of service, a call
> > >> could be attempted on that defective termination
> >
> > >I don't agree. A ServiceChange for ROOT will indicate that the MG is
> > >up, not specific terminations. You would then have to send additonal
> > >ServiceChange commands, with Reason code 900, for each termination
> > >you want to put in-service.
> >
> > The example in the spec (Appendix A) and the
> > draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT
> > on a ServiceChange all terminations are addressed (One ServiceChange
> > ROOT is sent and the terminations are available to use). Where did you
>
> > find information about ServiceChange ROOT not bringing all
> > terminations up?
> >
> > Thanks,
> > Glauco
> >
> > >Regards,
> >
> > >hrister Holmberg
> > >ricsson Finland
> >
> > >
> > >
> > > b) If a ServiceChange is issued just for the working Termination The
>
> > > ability to redirect the gateway to another MGC will be lost (See
> > > quotation from spec below)
> > >
> > > "The return from ServiceChange is empty except when the Root
> > > terminationID is used.  In that case it includes the following
> > > parameters as required:"
> > >
> > > Thanks,
> > > Glauco
> > >
> > > _______________________________________________
> > > Megaco mailing 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

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------CD03154B7A22599D63E3735F
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------CD03154B7A22599D63E3735F--


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


From daemon@optimus.ietf.org  Thu Apr 18 15:06: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 PAA19676
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:06:47 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA25862
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 15:06:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA24520;
	Thu, 18 Apr 2002 14:46:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA24422
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 14:46:36 -0400 (EDT)
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 OAA18986
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:46:32 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3IIk4o15601
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:46:04 -0400 (EDT)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id OAA09781
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:46:46 -0400 (EDT)
Message-ID: <3CBF147D.D7A28C57@lucent.com>
Date: Thu, 18 Apr 2002 14:46:21 -0400
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@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <000801c1e6e1$18dc85e0$368910ac@Bala>
Content-Type: multipart/mixed;
 boundary="------------CD03154B7A22599D63E3735F"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------CD03154B7A22599D63E3735F
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes no
statement one way or the other) and it is apparent that there is not
agreement on what we want.  I believe that there are three possible
positions and that we should clarify this through the IG once we agree.

Possible clarifications:
ServiceChange on ROOT with method=restart (a registration):
1) implies that all physical terminations on MG are also up.  Exceptions
should be indicated by additional ServiceChanges on the down terminations
using Forced, preferrably in the same message and using wildcards where
possible.
2) implies that all physical terminations on MG are down.  Those that are up
will be indicated by additional ServiceChanges on the up terminations using
method=restart, preferrably in the same message and using wildcards were
possible.
3) has no implication whether physical terminations are up or down, but MGC
may be provisioned to know whether an MG will indicate terminations that are
up or those that are down.

I should say that I do not like #3 but am including it as a possibility.

Preference for #1 or #2 probably depend on:
1) whether most physical terminations are available almost immediately or
come up slowly and at different speeds.
2) whether MGC is provisioned with knowledge about the available physical
terminations on an MG or expects to learn about them through ServiceChanges
or Audits

Note that #1 can be implemented from #2 by adding:
    ServiceChange = *{Services{Method=Restart}}
to the action, and conversely #2 can be implemented from #1 by adding:
    ServiceChange = *{Services{Method=Forced}}

In either case exceptions (up or down) to the ALL can be indicated by
additional ServiceChange commands.

So (IMHO) it doesn't seem too critical which we choose, but we should choose
and document one.

Even though I think that most GWs probably would not register until all or
most of their physical terminations are available, I would probably prefer
#2 since I can easily indicated them all up with only one additional
ServiceChange and it seems more natural to indicate those up those that are
down.  But I can be happy with either #1 or #2.

What do folks prefer?

Balasubramanian Pitchandi wrote:

> Hi,
>
> I agree with Christer's views.
>
> If MG sends a ServiceChange 'ROOT', it only means that the gateway is in
> or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). The
> protocol is very clear on this, I think.
>
> Given that -- SVC(ROOT) means that the gateway is up -- now there are
> many ways MGC could come to know of what terminations are in service:
>
> 1. MG sends ServiceChange for all the terminations that are in service
> individually (If there are large number of terminations, the MG could
> use *ranges* of TerminationIds(?) to limit the number of such messages)
>
> 2. MGC could audit the MG for the list of terminations that are in
> service in which case the MG returns the list of terminations that are
> in service.
>
> But clearly sending a ServiceChange('ROOT') does not mean that all the
> terminations in the MG are in service. This presents lot of operational
> problems as Christer pointed out.
>
> -- Bala
>
> __________________
> Bala Pitchandi
> UTStarcom Inc.
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> SRD Wang JuLin
> Sent: Thursday, April 18, 2002 2:52 AM
> To: Christer Holmberg
> Cc: Barcotti, Glauco; megaco@ietf.org
> Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
> Hi,
> Well,I think MGC should send Modify messages (the number of it equals to
> the number of terminations in RGW,I only refer to Residential GW) to
> check the terminations's events  after MG reboot with Cold Start as a
> whole entity. All terminations will start up.In case of some
> terminations fail to use,of course,we should send SC for definite
> invalid termination with restored method  to Softswtich. Before you WANT
> to use a termination,you should know whether it is ABLE to use (ie.in
> service or out of  service).
>
> best  regards
> > :-)Jerry Wang
> tel:(8621)58541240 ext 9615
> mailto:wangjl2@sbell.com.cn
> Shanghai Bell Co.LTD
>
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Thursday, April 18, 2002 2:27 PM
> To: SRD Wang JuLin
> Cc: Barcotti, Glauco; megaco@ietf.org
> Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
> Hi,
>
> So, you want me to send a MODIFY to each of the THOUSANDS of
> terminations I may want to use????
>
> And, the issue is not which termination I WANT to use (ie which I want
> the MGC to "enable" in the MG), but which termination I am ABLE (ie
> which termination has at a certain time been booted/loaded/whatevver) to
> use...
>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> SRD Wang JuLin wrote:
>
> > Hi,
> > Well,I send the ServiceChange for Root to Softswitch,it only send 4
> > modify messages  to RGW.So i can only use 4 out of the 8 phones
> > located in RGW. (I had provisioned 8 terminations into Softswitch
> >
> > )
> > 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
> >                          4500 008e 028b 0000 3f11 63de 0a0a 007a
> >                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
> >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> >                          7b4d 543d 5253 2c52 453d 3930 312c 4144
> >                          3d31 3131 3232 2c50 463d 416e 616c 6f67
> >                          5f4c 696e 655f 496e 7465 726f 7065 7261
> >                          6269 6c69 7479 5f54 6573 745f 5072 6f66
> >                          696c 652f 312c 563d 317d 7d7d 7d0a
> >
> >                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
> >                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
> >                           1 {  C =  - {  S C  = R  O O  T {  S V
> >                           { M  T =  R S  , R  E =  9 0  1 ,  A D
> >                           = 1  1 1  2 2  , P  F =  A n  a l  o g
> >                           _ L  i n  e _  I n  t e  r o  p e  r a
> >                           b i  l i  t y  _ T  e s  t _  P r  o f
> >                           i l  e /  1 ,  V =  1 }  } }  }^J
> > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
> >                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
> >                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
> >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> >                          7b41 443d 3131 3132 322c 5046 3d43 4c53
> >                          2f31 2c56 3d31 7d7d 7d7d
> >
> >                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
> >                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
> >                           1 {  C =  - {  S C  = R  O O  T {  S V
> >                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
> >                           / 1  , V  = 1  } }  } } 16:46:18.325927 eth0
>
> > > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 327b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } }
> > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 337b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  1 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } }
> > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 357b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } }
> > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 367b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  3 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } }
> > 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> >                          4500 0062 0293 0000 3f11 6402 0a0a 007a
> >                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 327d 7d0a 503d 3432 317b 433d
> >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
> >                          7d0a
> >
> >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
> >                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
> >                           - {  M F  = a  g w  _ j  u l  w /  3 }
> >                           }^J
> > 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> >                          4500 0062 0294 0000 3f11 6401 0a0a 007a
> >                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 357d 7d0a 503d 3432 337b 433d
> >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
> >                          7d0a
> >
> >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
> >                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
> >                           - {  M F  = a  g w  _ j  u l  w /  6 }
> >                           }^J
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > best  regards
> > > :-)Jerry Wang
> > tel:(8621)58541240 ext 9615
> > mailto:wangjl2@sbell.com.cn
> > Shanghai Bell Co.LTD
> >
> > -----Original Message-----
> > From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> > Sent: Wednesday, April 17, 2002 10:10 PM
> > To: 'Christer Holmberg'
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> >
> > >>         Assuming a Gateway with 2 terminations, one of >them is OK
> > >> and the other is Malfunctioning. How should I >proceed if I want to
>
> > >> bring just the working termination >up (Cold Start)?
> > >>
> > >> a) If a ServiceChange is issued for ROOT termination MGC will think
>
> > >> that all terminations are up and, until another ServiceChange is
> > >> issued taking the defective Termination out of service, a call
> > >> could be attempted on that defective termination
> >
> > >I don't agree. A ServiceChange for ROOT will indicate that the MG is
> > >up, not specific terminations. You would then have to send additonal
> > >ServiceChange commands, with Reason code 900, for each termination
> > >you want to put in-service.
> >
> > The example in the spec (Appendix A) and the
> > draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT
> > on a ServiceChange all terminations are addressed (One ServiceChange
> > ROOT is sent and the terminations are available to use). Where did you
>
> > find information about ServiceChange ROOT not bringing all
> > terminations up?
> >
> > Thanks,
> > Glauco
> >
> > >Regards,
> >
> > >hrister Holmberg
> > >ricsson Finland
> >
> > >
> > >
> > > b) If a ServiceChange is issued just for the working Termination The
>
> > > ability to redirect the gateway to another MGC will be lost (See
> > > quotation from spec below)
> > >
> > > "The return from ServiceChange is empty except when the Root
> > > terminationID is used.  In that case it includes the following
> > > parameters as required:"
> > >
> > > Thanks,
> > > Glauco
> > >
> > > _______________________________________________
> > > Megaco mailing 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

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------CD03154B7A22599D63E3735F
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------CD03154B7A22599D63E3735F--


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



From daemon@optimus.ietf.org  Thu Apr 18 15:25: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 OAA18758
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:36:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA23693
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 14:36:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21642;
	Thu, 18 Apr 2002 14:09:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25282
	for <megaco@ns.ietf.org>; Thu, 18 Apr 2002 01:36:00 -0400 (EDT)
Received: from epygilab.am (araler.epygilab.am [195.151.94.74])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18110
	for <megaco@ietf.org>; Thu, 18 Apr 2002 01:35:53 -0400 (EDT)
Received: (apparently) from epygilab.am ([192.168.0.156]) by epygilab.am  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Thu, 18 Apr 2002 09:35:29 +0400
Received: from epygilab.am [192.168.0.32]
	by epygilab.am [192.168.0.156]
	with SMTP (MDaemon.PRO.v5.0.1.R)
	for <megaco@ietf.org>; Thu, 18 Apr 2002 10:34:17 +0500
Message-ID: <3CBE68ED.CEAC5470@epygilab.am>
Date: Thu, 18 Apr 2002 10:34:21 +0400
From: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Megaco <megaco@ietf.org>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
X-MDRemoteIP: 192.168.0.32
X-Return-Path: Narine.Mossikyan@epygilab.am
X-MDaemon-Deliver-To: megaco@ietf.org
Content-Transfer-Encoding: 7bit
Subject: [Megaco] MGC to MGC connection standard
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 should be translated MEGACO messages into H323 or SIP  to be sent
between MGCs?
Is there any standard documentation for MGC to MGC connection and where
I can find it?
thank you very much for your help.
--------
regards
Narine Mossikyan
Epygi lab LLC





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



From megaco-admin@ietf.org  Thu Apr 18 15: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 PAA20591
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:40:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26397;
	Thu, 18 Apr 2002 15:18:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26370
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 15:18:44 -0400 (EDT)
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 PAA19928
	for <megaco@ietf.org>; Thu, 18 Apr 2002 15:18:39 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3IJITm08099;
	Thu, 18 Apr 2002 15:18:29 -0400 (EDT)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id PAA10572;
	Thu, 18 Apr 2002 15:19:11 -0400 (EDT)
Message-ID: <3CBF1C16.F336B5C5@lucent.com>
Date: Thu, 18 Apr 2002 15:18:46 -0400
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: Ian Leighton <Ian.Leighton@alcatel.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Multiple SDP's in Local and No Remote
References: <3CBEF90D.1FCD87F3@alcatel.com>
Content-Type: multipart/mixed;
 boundary="------------0680E982011BDA8C4B3E70C3"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------0680E982011BDA8C4B3E70C3
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

7.1.8 does indeed speak precisely only for the case where there are
alternatives in Remote, but I believe that the basic principle still applies
that when ReserveGroup and ReserveValue are false, no more than only
alternative are returned.  If Remote is empty, MG is not constrained in its
choice among the alternatives in Local.

Ian Leighton wrote:

> Hi All
>
> I would like to get some clarification on the expected behaviour of an
> MG if the MGC sends a request which includes multiple SDP's in the Local
> descriptor and does not include a Remote descriptor. For example if an
> MGC sends the following information and the MG is capable of supporting
> both AAL1 and AAL2 (assume ReserveGroup and ReserveValue are false);
>
> add=$ {
>       L {
>         v=0
>         c=ATM $ $
>         m=audio - AAL2/ITU 1
>         v=0
>         c=ATM $ $
>         m=audio - AAL1/ITU 0
>       }
>     }
>
> would the reply include
>
> 1) both SDP's or
> 2) only its preferred transport.
>
> My assumption is 1) based on 3015 section 7.1.8 description that the MG
> chooses based on a both local and remote. Since the remote is not
> currently available the MG replies with what it can support and chooses
> a single SDP once the remote descriptor is provided.
>
> Any comments or clarifications would be appreciated.
>
> Regards
> Ian Leighton
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------0680E982011BDA8C4B3E70C3
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------0680E982011BDA8C4B3E70C3--


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


From daemon@optimus.ietf.org  Thu Apr 18 15:40: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 PAA20613
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:40:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA27699
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 15:40:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26397;
	Thu, 18 Apr 2002 15:18:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26370
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 15:18:44 -0400 (EDT)
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 PAA19928
	for <megaco@ietf.org>; Thu, 18 Apr 2002 15:18:39 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3IJITm08099;
	Thu, 18 Apr 2002 15:18:29 -0400 (EDT)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id PAA10572;
	Thu, 18 Apr 2002 15:19:11 -0400 (EDT)
Message-ID: <3CBF1C16.F336B5C5@lucent.com>
Date: Thu, 18 Apr 2002 15:18:46 -0400
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: Ian Leighton <Ian.Leighton@alcatel.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Multiple SDP's in Local and No Remote
References: <3CBEF90D.1FCD87F3@alcatel.com>
Content-Type: multipart/mixed;
 boundary="------------0680E982011BDA8C4B3E70C3"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------0680E982011BDA8C4B3E70C3
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

7.1.8 does indeed speak precisely only for the case where there are
alternatives in Remote, but I believe that the basic principle still applies
that when ReserveGroup and ReserveValue are false, no more than only
alternative are returned.  If Remote is empty, MG is not constrained in its
choice among the alternatives in Local.

Ian Leighton wrote:

> Hi All
>
> I would like to get some clarification on the expected behaviour of an
> MG if the MGC sends a request which includes multiple SDP's in the Local
> descriptor and does not include a Remote descriptor. For example if an
> MGC sends the following information and the MG is capable of supporting
> both AAL1 and AAL2 (assume ReserveGroup and ReserveValue are false);
>
> add=$ {
>       L {
>         v=0
>         c=ATM $ $
>         m=audio - AAL2/ITU 1
>         v=0
>         c=ATM $ $
>         m=audio - AAL1/ITU 0
>       }
>     }
>
> would the reply include
>
> 1) both SDP's or
> 2) only its preferred transport.
>
> My assumption is 1) based on 3015 section 7.1.8 description that the MG
> chooses based on a both local and remote. Since the remote is not
> currently available the MG replies with what it can support and chooses
> a single SDP once the remote descriptor is provided.
>
> Any comments or clarifications would be appreciated.
>
> Regards
> Ian Leighton
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------0680E982011BDA8C4B3E70C3
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------0680E982011BDA8C4B3E70C3--


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



From megaco-admin@ietf.org  Thu Apr 18 15:47: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 PAA20885
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:47:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26651;
	Thu, 18 Apr 2002 15:27:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26620
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 15:27:15 -0400 (EDT)
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 PAA20150
	for <megaco@ietf.org>; Thu, 18 Apr 2002 15:27:10 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3IJRBm11959;
	Thu, 18 Apr 2002 15:27:11 -0400 (EDT)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id PAA10824;
	Thu, 18 Apr 2002 15:27:53 -0400 (EDT)
Message-ID: <3CBF1E20.4B7958EF@lucent.com>
Date: Thu, 18 Apr 2002 15:27:28 -0400
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: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
CC: Megaco <megaco@ietf.org>
Subject: Re: [Megaco] MGC to MGC connection standard
References: <3CBE68ED.CEAC5470@epygilab.am>
Content-Type: multipart/mixed;
 boundary="------------878DAE1D873E1C6F2846A985"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------878DAE1D873E1C6F2846A985
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Communications between MGCs is outside the scope of H.248/MEGACO and so
there is no specification for this in the H.248 documents.  Most
communications between MGCs will not be translations from H.248 but rather
carry information MGC receives from a SignalingGW (e.g, SS7).  SIP-T is one
choice for carrying such signaling between MGCs.  There is some
H.248-related information that may need to be carried between MGCs (e.g.,
SDP data such as payloads and port) and most of this has relatively obvious
expression in SIP-T, but I do not know of any formal specification, just as
there is no formal specification of how MGC works with a SignalingGW to
translate SS7 information into H.248 where appropriate.  This is up to the
MGC.

Narine_Mossikyan wrote:

> Hi All,
> How should be translated MEGACO messages into H323 or SIP  to be sent
> between MGCs?
> Is there any standard documentation for MGC to MGC connection and where
> I can find it?
> thank you very much for your help.
> --------
> regards
> Narine Mossikyan
> Epygi lab LLC
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------878DAE1D873E1C6F2846A985
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------878DAE1D873E1C6F2846A985--


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


From daemon@optimus.ietf.org  Thu Apr 18 15:47: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 PAA20897
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:47:23 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA28166
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 15:47:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26651;
	Thu, 18 Apr 2002 15:27:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26620
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 15:27:15 -0400 (EDT)
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 PAA20150
	for <megaco@ietf.org>; Thu, 18 Apr 2002 15:27:10 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3IJRBm11959;
	Thu, 18 Apr 2002 15:27:11 -0400 (EDT)
Received: from lucent.com (2g219a.ho.lucent.com [135.112.32.111])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id PAA10824;
	Thu, 18 Apr 2002 15:27:53 -0400 (EDT)
Message-ID: <3CBF1E20.4B7958EF@lucent.com>
Date: Thu, 18 Apr 2002 15:27:28 -0400
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: Narine_Mossikyan <Narine.Mossikyan@epygilab.am>
CC: Megaco <megaco@ietf.org>
Subject: Re: [Megaco] MGC to MGC connection standard
References: <3CBE68ED.CEAC5470@epygilab.am>
Content-Type: multipart/mixed;
 boundary="------------878DAE1D873E1C6F2846A985"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------878DAE1D873E1C6F2846A985
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Communications between MGCs is outside the scope of H.248/MEGACO and so
there is no specification for this in the H.248 documents.  Most
communications between MGCs will not be translations from H.248 but rather
carry information MGC receives from a SignalingGW (e.g, SS7).  SIP-T is one
choice for carrying such signaling between MGCs.  There is some
H.248-related information that may need to be carried between MGCs (e.g.,
SDP data such as payloads and port) and most of this has relatively obvious
expression in SIP-T, but I do not know of any formal specification, just as
there is no formal specification of how MGC works with a SignalingGW to
translate SS7 information into H.248 where appropriate.  This is up to the
MGC.

Narine_Mossikyan wrote:

> Hi All,
> How should be translated MEGACO messages into H323 or SIP  to be sent
> between MGCs?
> Is there any standard documentation for MGC to MGC connection and where
> I can find it?
> thank you very much for your help.
> --------
> regards
> Narine Mossikyan
> Epygi lab LLC
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------878DAE1D873E1C6F2846A985
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------878DAE1D873E1C6F2846A985--


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



From megaco-admin@ietf.org  Thu Apr 18 15:55: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 PAA19479
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:00:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23942;
	Thu, 18 Apr 2002 14:39:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23913
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 14:39:20 -0400 (EDT)
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 OAA18814
	for <megaco@ietf.org>; Thu, 18 Apr 2002 14:39:15 -0400 (EDT)
Received: through eSafe SMTP Relay 1019111027; Thu Apr 18 21:38:42 2002
Received: by EXCHANGE with Internet Mail Service (5.5.2653.19)
	id <2WRMF7WK>; Thu, 18 Apr 2002 21:37:57 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF01B926C0@EXCHANGE>
From: Raphael Tryster <raphael@tdsoft.com>
To: madhubabu@kenetec.com, dham.prerepa@kenetec.com,
        krishna.gundamaraju@kenetec.com
Cc: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Thu, 18 Apr 2002 21:37:53 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E710.888A9100"
Subject: [Megaco] draft-ietf-megaco-callflows-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

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_01C1E710.888A9100
Content-Type: text/plain;
	charset="iso-8859-1"

I have some questions about the examples in this document relating to call
transfer:

1.	When UserB presses flash and is dialing UserC, what happens with
UserA?  It appears to me that in steps 19 through 30, nothing happens that
affects UserA, so UserA and UserB would continue to hear each other.  Is
this a real world scenario?  If not, what would happen in the real world?

2.	In the description before step 24, I think that "The physical
termination TermA is added to context 1" should be "The physical termination
TermC is added to context 3".

3.	Step 31 seems to be missing the ephemeral termination EphB, referred
to in the description preceding it.

4.	After step 31, the remote SDP of UserB and UserC point to each
other, but the remote SDP of UserA still points to UserB.  What is the
physical effect of this?

	And about call waiting:

5.	I believe the description before step 26 should refer to TermC
instead of TermB, and MG3 instead of MG2.

6.	In this example, each of the physical terminations has a single
ephemeral termination in the same context, and the MGC sends updated remote
SDP information each time UserB presses flash.  What are the considerations
for doing it this way, rather than creating in UserB's context a separate
ephemeral termination for each of its conversation partners and switching
the mode, such that at any time one is sendrecv and the others are inactive?

7.	What happens to UserA while UserB is in conversation with UserC?
UserA's remote SDP information still points to UserB.

	And some general questions:

8.	Does it ever make sense, and is it possible, to send a signal
"backwards" to a user by directing it at an ephemeral termination to which
it is connected?  For example, when UserA and UserB have EphA and EphB
pointing to each other, is it possible for an MGC to send a signal to EphA
to be sent to UserB?

9.	Under what circumstances, is any, could there be more than one
physical termination in a context?



Raphael Tryster

------_=_NextPart_001_01C1E710.888A9100
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.2653.12">
<TITLE>draft-ietf-megaco-callflows-00.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have some questions about the =
examples in this document relating to call transfer:</FONT>
</P>

<OL TYPE=3D1><LI><FONT SIZE=3D2 FACE=3D"Arial">When UserB presses flash =
and is dialing UserC, what happens with UserA?&nbsp; It appears to me =
that in steps 19 through 30, nothing happens that affects UserA, so =
UserA and UserB would continue to hear each other.&nbsp; Is this a real =
world scenario?&nbsp; If not, what would happen in the real =
world?</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">In the description before step 24, I =
think that "</FONT><FONT SIZE=3D2 FACE=3D"Arial">The physical =
termination TermA is added to context 1</FONT><FONT SIZE=3D2 =
FACE=3D"Arial">" should be</FONT> <FONT SIZE=3D2 FACE=3D"Arial">"The =
physical terminati</FONT><FONT SIZE=3D2 FACE=3D"Arial">on TermC is =
added to context 3</FONT><FONT SIZE=3D2 FACE=3D"Arial">"</FONT><FONT =
SIZE=3D2 FACE=3D"Arial">.</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">Step 31 seems to be missing the =
ephemeral termination EphB, referred to in the description preceding =
it.</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">After step 31, the remote SDP of =
UserB and UserC point to each other, but the remote SDP of UserA still =
points to UserB.&nbsp; What is the physical effect of this?</FONT></LI>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">And about call waiting:</FONT>
</P>
<LI><FONT SIZE=3D2 FACE=3D"Arial">I believe the description before step =
26 should refer to TermC instead of TermB, and MG3 instead of =
MG2.</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">In this example, each of the physical =
terminations has a single ephemeral termination in the same context, =
and the MGC sends updated remote SDP information each time UserB =
presses flash.&nbsp; What are the considerations for doing it this way, =
rather than creating in UserB's context a separate ephemeral =
termination for each of its conversation partners and switching the =
mode, such that at any time one is sendrecv and the others are =
inactive?</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">What happens to UserA while UserB is =
in conversation with UserC?&nbsp; UserA's remote SDP information still =
points to UserB.</FONT></LI>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">And some general questions:</FONT>
</P>
<LI><FONT SIZE=3D2 FACE=3D"Arial">Does it ever make sense, and is it =
possible, to send a signal "backwards" to a user by directing it at an =
ephemeral termination to which it is connected?&nbsp; For example, when =
UserA and UserB have EphA and EphB pointing to each other, is it =
possible for an MGC to send a signal to EphA to be sent to =
UserB?</FONT></LI>
<BR>
<LI><FONT SIZE=3D2 FACE=3D"Arial">Under what circumstances, is any, =
could there be more than one physical termination in a =
context?</FONT></LI>
<BR>
<BR>
<BR>
</OL>
<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E710.888A9100--

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


From megaco-admin@ietf.org  Thu Apr 18 16:10: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 QAA21496
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 16:10:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28368;
	Thu, 18 Apr 2002 15:50:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28341
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 15:50:44 -0400 (EDT)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21014
	for <megaco@ietf.org>; Thu, 18 Apr 2002 15:50:39 -0400 (EDT)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AHU36364;
	Thu, 18 Apr 2002 15:50:08 -0400 (EDT)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Raphael Tryster'" <raphael@tdsoft.com>, <dham.prerepa@kenetec.com>,
        <krishna.gundamaraju@kenetec.com>
Cc: <megaco@ietf.org>
Date: Thu, 18 Apr 2002 15:43:57 -0400
Message-ID: <032601c1e711$61ef0840$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0327_01C1E6EF.DADD6840"
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 V6.00.2600.0000
Importance: Normal
In-Reply-To: <B1584457374ED211B7A90008C7242DEF01B926C0@EXCHANGE>
Subject: [Megaco] RE: draft-ietf-megaco-callflows-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

This is a multi-part message in MIME format.

------=_NextPart_000_0327_01C1E6EF.DADD6840
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

draft-ietf-megaco-callflows-00.txtHI Tryster,
Thanks for your review comments. My answers embedded [Madhubabu]
  -----Original Message-----
  From: Raphael Tryster [mailto:raphael@tdsoft.com]
  Sent: Thursday, April 18, 2002 3:38 PM
  To: madhubabu@kenetec.com; dham.prerepa@kenetec.com;
krishna.gundamaraju@kenetec.com
  Cc: 'megaco@ietf.org'
  Subject: draft-ietf-megaco-callflows-00.txt


  I have some questions about the examples in this document relating to call
transfer:

    1.. When UserB presses flash and is dialing UserC, what happens with
UserA?  It appears to me that in steps 19 through 30, nothing happens that
affects UserA, so UserA and UserB would continue to hear each other.  Is
this a real world scenario?  If not, what would happen in the real world?
    [Madhu Babu ]  One of the steps shown in the figure is missing in the
explanation. The message that makes the UserA mode to recvonly. Probably
making the mode to "inactive" will be an better idea. This will be updated.
    2.. In the description before step 24, I think that "The physical
termination TermA is added to context 1" should be "The physical termination
TermC is added to context 3".
    [Madhu Babu] That's right, needs an updation.
    3.. Step 31 seems to be missing the ephemeral termination EphB, referred
to in the description preceding it.
    [Madhu Babu Brahmanapally] The message should refer to EphB rather than
TermB.

    4.. After step 31, the remote SDP of UserB and UserC point to each
other, but the remote SDP of UserA still points to UserB.  What is the
physical effect of this?
    [Madhu Babu Brahmanapally] Making the EphA of User A inactive should
take care this scenario. Even if remote SDP is valid, if the termination
mode to "inactive" there would be no generation of packets.

    And about call waiting:

    5.. I believe the description before step 26 should refer to TermC
instead of TermB, and MG3 instead of MG2.
    [Madhu Babu Brahmanapally]  Yes, the description should refer to TermC.
    6.. In this example, each of the physical terminations has a single
ephemeral termination in the same context, and the MGC sends updated remote
SDP information each time UserB presses flash.  What are the considerations
for doing it this way, rather than creating in UserB's context a separate
ephemeral termination for each of its conversation partners and switching
the mode, such that at any time one is sendrecv and the others are inactive?
    [Madhu Babu Brahmanapally] Yes, that's another possibility. But we opted
for having a only two terminations in the context as this makes the
explanation simple.
    7.. What happens to UserA while UserB is in conversation with UserC?
UserA's remote SDP information still points to UserB.
    [Madhu Babu Brahmanapally] Even in this example, that specific message
making the EphA inactive is missing. (Even though shown in the figure).

    And some general questions:

    8.. Does it ever make sense, and is it possible, to send a signal
"backwards" to a user by directing it at an ephemeral termination to which
it is connected?  For example, when UserA and UserB have EphA and EphB
pointing to each other, is it possible for an MGC to send a signal to EphA
to be sent to UserB?
    [Madhu Babu Brahmanapally] If there is any activity on a given ephemeral
termination, the other also should have the same effect.  Considering the
example of call transfer, as pointed by you, since the ephemeral A is in
"sendrecv" mode, it should Infact hear the digits dialed by the UserB. As
TermB and EphB are in context and EphB is pointing towards EphA.

    9.. Under what circumstances, is any, could there be more than one
physical termination in a context?
    [Madhu Babu Brahmanapally]  Yes there is a possibility. If call is made
between users connected to the same Media Gateway, there can be a context
only with the physical terminations.   There is no need of other SDP
information at all. Its up to the MGC how it creates these context and add
the terminations into it.


  Raphael Tryster


  Regards
  Madhubabu







------=_NextPart_000_0327_01C1E6EF.DADD6840
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">
<TITLE>draft-ietf-megaco-callflows-00.txt</TITLE>

<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D637271319-18042002>HI=20
Tryster,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D637271319-18042002>Thanks=20
for your review comments. My answers embedded =
[Madhubabu]</SPAN></FONT></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> Raphael Tryster=20
  [mailto:raphael@tdsoft.com]<BR><B>Sent:</B> Thursday, April 18, 2002 =
3:38=20
  PM<BR><B>To:</B> madhubabu@kenetec.com; dham.prerepa@kenetec.com;=20
  krishna.gundamaraju@kenetec.com<BR><B>Cc:</B>=20
  'megaco@ietf.org'<BR><B>Subject:</B>=20
  draft-ietf-megaco-callflows-00.txt<BR><BR></FONT></DIV>
  <P><FONT face=3DArial size=3D2>I have some questions about the =
examples in this=20
  document relating to call transfer:</FONT> </P>
  <OL type=3D1>
    <LI><FONT face=3DArial size=3D2>When UserB presses flash and is =
dialing UserC,=20
    what happens with UserA?&nbsp; It appears to me that in steps 19 =
through 30,=20
    nothing happens that affects UserA, so UserA and UserB would =
continue to=20
    hear each other.&nbsp; Is this a real world scenario?&nbsp; If not, =
what=20
    would happen in the real world?</FONT> <BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    ]&nbsp;&nbsp;One of the steps shown in the figure is missing in the=20
    explanation. The message that makes the UserA mode to recvonly. =
Probably=20
    making the mode to "inactive" will be an better idea. This will be=20
    updated.</FONT></SPAN>
    <LI><FONT face=3DArial size=3D2>In the description before step 24, I =
think that=20
    "</FONT><FONT face=3DArial size=3D2>The physical termination TermA =
is added to=20
    context 1</FONT><FONT face=3DArial size=3D2>" should be</FONT> <FONT =
face=3DArial=20
    size=3D2>"The physical terminati</FONT><FONT face=3DArial =
size=3D2>on TermC is=20
    added to context 3</FONT><FONT face=3DArial size=3D2>"</FONT><FONT =
face=3DArial=20
    size=3D2>.</FONT> <BR><SPAN class=3D637271319-18042002><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>[Madhu Babu]&nbsp;That's right, needs an=20
    updation.</FONT></SPAN>
    <LI><FONT face=3DArial size=3D2>Step 31 seems to be missing the =
ephemeral=20
    termination EphB, referred to in the description preceding =
it.</FONT>=20
    <BR><SPAN class=3D637271319-18042002><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>[Madhu Babu Brahmanapally]&nbsp;The message should refer to =
EphB=20
    rather&nbsp;than TermB.&nbsp;</FONT></SPAN><BR>
    <LI><FONT face=3DArial size=3D2>After step 31, the remote SDP of =
UserB and UserC=20
    point to each other, but the remote SDP of UserA still points to=20
    UserB.&nbsp; What is the physical effect of this?</FONT> <BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    Brahmanapally]&nbsp;Making the EphA of User A inactive should take =
care this=20
    scenario. Even if remote SDP is valid, if the termination mode to =
"inactive"=20
    there would be no generation of packets.</FONT></SPAN><BR>
    <P><FONT face=3DArial size=3D2>And about call waiting:</FONT> </P>
    <LI><FONT face=3DArial size=3D2>I believe the description before =
step 26 should=20
    refer to TermC instead of TermB, and MG3 instead of MG2.</FONT> =
<BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    Brahmanapally]&nbsp; Yes, the description should refer to TermC.=20
    </FONT></SPAN><SPAN class=3D637271319-18042002>&nbsp;</SPAN>
    <LI><FONT face=3DArial size=3D2>In this example, each of the =
physical=20
    terminations has a single ephemeral termination in the same context, =
and the=20
    MGC sends updated remote SDP information each time UserB presses=20
    flash.&nbsp; What are the considerations for doing it this way, =
rather than=20
    creating in UserB's context a separate ephemeral termination for =
each of its=20
    conversation partners and switching the mode, such that at any time =
one is=20
    sendrecv and the others are inactive?</FONT> <BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    Brahmanapally]&nbsp;Yes, that's another possibility. But we opted =
for having=20
    a only two terminations in the context as this makes the explanation =
simple.=20
    </FONT></SPAN>
    <LI><FONT face=3DArial size=3D2>What happens to UserA while UserB is =
in=20
    conversation with UserC?&nbsp; UserA's remote SDP information still =
points=20
    to UserB.</FONT> <BR><SPAN class=3D637271319-18042002><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>[Madhu Babu Brahmanapally]&nbsp;Even in =
this example,=20
    that specific message making the EphA inactive is missing. (Even =
though=20
    shown in the figure). &nbsp;</FONT></SPAN><BR>
    <P><FONT face=3DArial size=3D2>And some general questions:</FONT> =
</P>
    <LI><FONT face=3DArial size=3D2>Does it ever make sense, and is it =
possible, to=20
    send a signal "backwards" to a user by directing it at an ephemeral=20
    termination to which it is connected?&nbsp; For example, when UserA =
and=20
    UserB have EphA and EphB pointing to each other, is it possible for =
an MGC=20
    to send a signal to EphA to be sent to UserB?</FONT> <BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    Brahmanapally]&nbsp;If there is any activity on a given ephemeral=20
    termination, the other also should have the same&nbsp;effect.&nbsp;=20
    Considering the example of call transfer, as pointed by you, since =
the=20
    ephemeral A is&nbsp;in "sendrecv" mode, it should Infact hear the =
digits=20
    dialed by the UserB. As TermB and EphB are in context and EphB is =
pointing=20
    towards EphA. &nbsp;</FONT></SPAN><BR>
    <LI><FONT face=3DArial size=3D2>Under what circumstances, is any, =
could there be=20
    more than one physical termination in a context?</FONT> <BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    Brahmanapally]&nbsp; Yes there is a possibility. If call is made =
between=20
    users connected to the same Media Gateway, there can be a context =
only with=20
    the physical terminations.&nbsp; &nbsp;There is no need of other SDP =

    information at all. Its up to the MGC how it creates these context =
and add=20
    the terminations into it.</FONT></SPAN><BR><BR></LI></OL>
  <P><FONT face=3DTahoma size=3D2>Raphael Tryster</FONT> <BR></P><SPAN=20
  class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></BLOCKQUOTE>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
  class=3D637271319-18042002>Regards</SPAN></FONT></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
  class=3D637271319-18042002>Madhubabu</SPAN></FONT></FONT></FONT></DIV>
  <P><SPAN class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =

  size=3D2></FONT></SPAN>&nbsp;</P>
  <P><SPAN class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =

  size=3D2></FONT></SPAN>&nbsp;</P>
  <P><SPAN =
class=3D637271319-18042002>&nbsp;</SPAN></P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0327_01C1E6EF.DADD6840--


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


From daemon@optimus.ietf.org  Thu Apr 18 16:10: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 QAA21506
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 16:10:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA29588
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 16:10:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28368;
	Thu, 18 Apr 2002 15:50:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28341
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 15:50:44 -0400 (EDT)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21014
	for <megaco@ietf.org>; Thu, 18 Apr 2002 15:50:39 -0400 (EDT)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AHU36364;
	Thu, 18 Apr 2002 15:50:08 -0400 (EDT)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Raphael Tryster'" <raphael@tdsoft.com>, <dham.prerepa@kenetec.com>,
        <krishna.gundamaraju@kenetec.com>
Cc: <megaco@ietf.org>
Date: Thu, 18 Apr 2002 15:43:57 -0400
Message-ID: <032601c1e711$61ef0840$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0327_01C1E6EF.DADD6840"
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 V6.00.2600.0000
Importance: Normal
In-Reply-To: <B1584457374ED211B7A90008C7242DEF01B926C0@EXCHANGE>
Subject: [Megaco] RE: draft-ietf-megaco-callflows-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

This is a multi-part message in MIME format.

------=_NextPart_000_0327_01C1E6EF.DADD6840
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

draft-ietf-megaco-callflows-00.txtHI Tryster,
Thanks for your review comments. My answers embedded [Madhubabu]
  -----Original Message-----
  From: Raphael Tryster [mailto:raphael@tdsoft.com]
  Sent: Thursday, April 18, 2002 3:38 PM
  To: madhubabu@kenetec.com; dham.prerepa@kenetec.com;
krishna.gundamaraju@kenetec.com
  Cc: 'megaco@ietf.org'
  Subject: draft-ietf-megaco-callflows-00.txt


  I have some questions about the examples in this document relating to call
transfer:

    1.. When UserB presses flash and is dialing UserC, what happens with
UserA?  It appears to me that in steps 19 through 30, nothing happens that
affects UserA, so UserA and UserB would continue to hear each other.  Is
this a real world scenario?  If not, what would happen in the real world?
    [Madhu Babu ]  One of the steps shown in the figure is missing in the
explanation. The message that makes the UserA mode to recvonly. Probably
making the mode to "inactive" will be an better idea. This will be updated.
    2.. In the description before step 24, I think that "The physical
termination TermA is added to context 1" should be "The physical termination
TermC is added to context 3".
    [Madhu Babu] That's right, needs an updation.
    3.. Step 31 seems to be missing the ephemeral termination EphB, referred
to in the description preceding it.
    [Madhu Babu Brahmanapally] The message should refer to EphB rather than
TermB.

    4.. After step 31, the remote SDP of UserB and UserC point to each
other, but the remote SDP of UserA still points to UserB.  What is the
physical effect of this?
    [Madhu Babu Brahmanapally] Making the EphA of User A inactive should
take care this scenario. Even if remote SDP is valid, if the termination
mode to "inactive" there would be no generation of packets.

    And about call waiting:

    5.. I believe the description before step 26 should refer to TermC
instead of TermB, and MG3 instead of MG2.
    [Madhu Babu Brahmanapally]  Yes, the description should refer to TermC.
    6.. In this example, each of the physical terminations has a single
ephemeral termination in the same context, and the MGC sends updated remote
SDP information each time UserB presses flash.  What are the considerations
for doing it this way, rather than creating in UserB's context a separate
ephemeral termination for each of its conversation partners and switching
the mode, such that at any time one is sendrecv and the others are inactive?
    [Madhu Babu Brahmanapally] Yes, that's another possibility. But we opted
for having a only two terminations in the context as this makes the
explanation simple.
    7.. What happens to UserA while UserB is in conversation with UserC?
UserA's remote SDP information still points to UserB.
    [Madhu Babu Brahmanapally] Even in this example, that specific message
making the EphA inactive is missing. (Even though shown in the figure).

    And some general questions:

    8.. Does it ever make sense, and is it possible, to send a signal
"backwards" to a user by directing it at an ephemeral termination to which
it is connected?  For example, when UserA and UserB have EphA and EphB
pointing to each other, is it possible for an MGC to send a signal to EphA
to be sent to UserB?
    [Madhu Babu Brahmanapally] If there is any activity on a given ephemeral
termination, the other also should have the same effect.  Considering the
example of call transfer, as pointed by you, since the ephemeral A is in
"sendrecv" mode, it should Infact hear the digits dialed by the UserB. As
TermB and EphB are in context and EphB is pointing towards EphA.

    9.. Under what circumstances, is any, could there be more than one
physical termination in a context?
    [Madhu Babu Brahmanapally]  Yes there is a possibility. If call is made
between users connected to the same Media Gateway, there can be a context
only with the physical terminations.   There is no need of other SDP
information at all. Its up to the MGC how it creates these context and add
the terminations into it.


  Raphael Tryster


  Regards
  Madhubabu







------=_NextPart_000_0327_01C1E6EF.DADD6840
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">
<TITLE>draft-ietf-megaco-callflows-00.txt</TITLE>

<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D637271319-18042002>HI=20
Tryster,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D637271319-18042002>Thanks=20
for your review comments. My answers embedded =
[Madhubabu]</SPAN></FONT></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> Raphael Tryster=20
  [mailto:raphael@tdsoft.com]<BR><B>Sent:</B> Thursday, April 18, 2002 =
3:38=20
  PM<BR><B>To:</B> madhubabu@kenetec.com; dham.prerepa@kenetec.com;=20
  krishna.gundamaraju@kenetec.com<BR><B>Cc:</B>=20
  'megaco@ietf.org'<BR><B>Subject:</B>=20
  draft-ietf-megaco-callflows-00.txt<BR><BR></FONT></DIV>
  <P><FONT face=3DArial size=3D2>I have some questions about the =
examples in this=20
  document relating to call transfer:</FONT> </P>
  <OL type=3D1>
    <LI><FONT face=3DArial size=3D2>When UserB presses flash and is =
dialing UserC,=20
    what happens with UserA?&nbsp; It appears to me that in steps 19 =
through 30,=20
    nothing happens that affects UserA, so UserA and UserB would =
continue to=20
    hear each other.&nbsp; Is this a real world scenario?&nbsp; If not, =
what=20
    would happen in the real world?</FONT> <BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    ]&nbsp;&nbsp;One of the steps shown in the figure is missing in the=20
    explanation. The message that makes the UserA mode to recvonly. =
Probably=20
    making the mode to "inactive" will be an better idea. This will be=20
    updated.</FONT></SPAN>
    <LI><FONT face=3DArial size=3D2>In the description before step 24, I =
think that=20
    "</FONT><FONT face=3DArial size=3D2>The physical termination TermA =
is added to=20
    context 1</FONT><FONT face=3DArial size=3D2>" should be</FONT> <FONT =
face=3DArial=20
    size=3D2>"The physical terminati</FONT><FONT face=3DArial =
size=3D2>on TermC is=20
    added to context 3</FONT><FONT face=3DArial size=3D2>"</FONT><FONT =
face=3DArial=20
    size=3D2>.</FONT> <BR><SPAN class=3D637271319-18042002><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>[Madhu Babu]&nbsp;That's right, needs an=20
    updation.</FONT></SPAN>
    <LI><FONT face=3DArial size=3D2>Step 31 seems to be missing the =
ephemeral=20
    termination EphB, referred to in the description preceding =
it.</FONT>=20
    <BR><SPAN class=3D637271319-18042002><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>[Madhu Babu Brahmanapally]&nbsp;The message should refer to =
EphB=20
    rather&nbsp;than TermB.&nbsp;</FONT></SPAN><BR>
    <LI><FONT face=3DArial size=3D2>After step 31, the remote SDP of =
UserB and UserC=20
    point to each other, but the remote SDP of UserA still points to=20
    UserB.&nbsp; What is the physical effect of this?</FONT> <BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    Brahmanapally]&nbsp;Making the EphA of User A inactive should take =
care this=20
    scenario. Even if remote SDP is valid, if the termination mode to =
"inactive"=20
    there would be no generation of packets.</FONT></SPAN><BR>
    <P><FONT face=3DArial size=3D2>And about call waiting:</FONT> </P>
    <LI><FONT face=3DArial size=3D2>I believe the description before =
step 26 should=20
    refer to TermC instead of TermB, and MG3 instead of MG2.</FONT> =
<BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    Brahmanapally]&nbsp; Yes, the description should refer to TermC.=20
    </FONT></SPAN><SPAN class=3D637271319-18042002>&nbsp;</SPAN>
    <LI><FONT face=3DArial size=3D2>In this example, each of the =
physical=20
    terminations has a single ephemeral termination in the same context, =
and the=20
    MGC sends updated remote SDP information each time UserB presses=20
    flash.&nbsp; What are the considerations for doing it this way, =
rather than=20
    creating in UserB's context a separate ephemeral termination for =
each of its=20
    conversation partners and switching the mode, such that at any time =
one is=20
    sendrecv and the others are inactive?</FONT> <BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    Brahmanapally]&nbsp;Yes, that's another possibility. But we opted =
for having=20
    a only two terminations in the context as this makes the explanation =
simple.=20
    </FONT></SPAN>
    <LI><FONT face=3DArial size=3D2>What happens to UserA while UserB is =
in=20
    conversation with UserC?&nbsp; UserA's remote SDP information still =
points=20
    to UserB.</FONT> <BR><SPAN class=3D637271319-18042002><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>[Madhu Babu Brahmanapally]&nbsp;Even in =
this example,=20
    that specific message making the EphA inactive is missing. (Even =
though=20
    shown in the figure). &nbsp;</FONT></SPAN><BR>
    <P><FONT face=3DArial size=3D2>And some general questions:</FONT> =
</P>
    <LI><FONT face=3DArial size=3D2>Does it ever make sense, and is it =
possible, to=20
    send a signal "backwards" to a user by directing it at an ephemeral=20
    termination to which it is connected?&nbsp; For example, when UserA =
and=20
    UserB have EphA and EphB pointing to each other, is it possible for =
an MGC=20
    to send a signal to EphA to be sent to UserB?</FONT> <BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    Brahmanapally]&nbsp;If there is any activity on a given ephemeral=20
    termination, the other also should have the same&nbsp;effect.&nbsp;=20
    Considering the example of call transfer, as pointed by you, since =
the=20
    ephemeral A is&nbsp;in "sendrecv" mode, it should Infact hear the =
digits=20
    dialed by the UserB. As TermB and EphB are in context and EphB is =
pointing=20
    towards EphA. &nbsp;</FONT></SPAN><BR>
    <LI><FONT face=3DArial size=3D2>Under what circumstances, is any, =
could there be=20
    more than one physical termination in a context?</FONT> <BR><SPAN=20
    class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =
size=3D2>[Madhu Babu=20
    Brahmanapally]&nbsp; Yes there is a possibility. If call is made =
between=20
    users connected to the same Media Gateway, there can be a context =
only with=20
    the physical terminations.&nbsp; &nbsp;There is no need of other SDP =

    information at all. Its up to the MGC how it creates these context =
and add=20
    the terminations into it.</FONT></SPAN><BR><BR></LI></OL>
  <P><FONT face=3DTahoma size=3D2>Raphael Tryster</FONT> <BR></P><SPAN=20
  class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></BLOCKQUOTE>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
  class=3D637271319-18042002>Regards</SPAN></FONT></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
  class=3D637271319-18042002>Madhubabu</SPAN></FONT></FONT></FONT></DIV>
  <P><SPAN class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =

  size=3D2></FONT></SPAN>&nbsp;</P>
  <P><SPAN class=3D637271319-18042002><FONT face=3DArial color=3D#0000ff =

  size=3D2></FONT></SPAN>&nbsp;</P>
  <P><SPAN =
class=3D637271319-18042002>&nbsp;</SPAN></P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0327_01C1E6EF.DADD6840--


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



From megaco-admin@ietf.org  Thu Apr 18 17:37: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 RAA23707
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 17:37:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA04279;
	Thu, 18 Apr 2002 17:18:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA04158
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 17:18:45 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23296
	for <megaco@ietf.org>; Thu, 18 Apr 2002 17:18:38 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3ILIOK00943;
	Thu, 18 Apr 2002 17:18:24 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Terry L Anderson'" <tla@lucent.com>, <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
Date: Thu, 18 Apr 2002 17:18:48 -0400
Message-ID: <002f01c1e71e$a1f41e50$368910ac@Bala>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <3CBF147D.D7A28C57@lucent.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id RAA04160
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

Please see my comments embedded as [BP] below.

Thanks
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Terry L Anderson
Sent: Thursday, April 18, 2002 2:46 PM
To: megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
Start)


I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes no
statement one way or the other) and it is apparent that there is not
agreement on what we want.  I believe that there are three possible
positions and that we should clarify this through the IG once we agree.

Possible clarifications:
ServiceChange on ROOT with method=restart (a registration):
1) implies that all physical terminations on MG are also up.  Exceptions
should be indicated by additional ServiceChanges on the down
terminations using Forced, preferrably in the same message and using
wildcards where possible.

[BP] The key here is what does *all* physical terminations represent.
Does it represent (a) all the terminations that are provisioned and are
in service (provisioned and hardware available & ready) at the time when
the MG sends the ServiceChange on ROOT (b) all the terminations that the
MG *expects* to be in service by the time it can start expecting
messages from MGC (c) all the terminations that are there in the system
irrespective of whether they come up later or sooner? 

[BP] Also this would warrant the MG to send a lot of 'forced'
ServiceChanges to bring the terminations down (up in the latter case)
particularly if the wildcarding cannot be used -- ie. when the
terminationIds are not contiguous. And it presents a potential error at
MGC, if the MG fails to send such a set of 'forced' ServiceChanges for
the terminations that are down (up in the latter case).

2) implies that all physical terminations on MG are down.  Those that
are up will be indicated by additional ServiceChanges on the up
terminations using method=restart, preferrably in the same message and
using wildcards were possible.

[BP] Same as above. What does *all* represent?

3) has no implication whether physical terminations are up or down, but
MGC may be provisioned to know whether an MG will indicate terminations
that are up or those that are down.

[BP] IMHO, this option is better because of the following reasons - (a)
It does not present any confusion about the status of the terminations
available in the MG and hence leaves it to MG/MGC to figure/inform of
the status of the terminations separately through an audit or
ServiceChange. (b) This gives flexibility to the implementors to choose
the options.

I should say that I do not like #3 but am including it as a possibility.

Preference for #1 or #2 probably depend on:
1) whether most physical terminations are available almost immediately
or come up slowly and at different speeds.
[BP] This is a larger unknown/assumption and the protocol cannot assume
anything on how soon/late the terminations can come up.

2) whether MGC is provisioned with knowledge about the available
physical terminations on an MG or expects to learn about them through
ServiceChanges or Audits
[BP] The choice should be left to the implementation and I think, the
protocol should leave it as it is.


Note that #1 can be implemented from #2 by adding:
    ServiceChange = *{Services{Method=Restart}}
to the action, and conversely #2 can be implemented from #1 by adding:
    ServiceChange = *{Services{Method=Forced}}

In either case exceptions (up or down) to the ALL can be indicated by
additional ServiceChange commands.

So (IMHO) it doesn't seem too critical which we choose, but we should
choose and document one.

Even though I think that most GWs probably would not register until all
or most of their physical terminations are available, I would probably
prefer #2 since I can easily indicated them all up with only one
additional ServiceChange and it seems more natural to indicate those up
those that are down.  But I can be happy with either #1 or #2.

[BP] Most (or many) implementations would want the gateway to just be up
so that it can be configured and then be gradually be brought up to its
full load. In that case, it would be appropriate to have the option #3
where the MG just informs the MGC of its registration and then let the
MGC know of the active terminations using the audit/ServiceChanges.

What do folks prefer?

[BP] That’s my two cents. :)




Balasubramanian Pitchandi wrote:

> Hi,
>
> I agree with Christer's views.
>
> If MG sends a ServiceChange 'ROOT', it only means that the gateway is 
> in or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). 
> The protocol is very clear on this, I think.
>
> Given that -- SVC(ROOT) means that the gateway is up -- now there are 
> many ways MGC could come to know of what terminations are in service:
>
> 1. MG sends ServiceChange for all the terminations that are in service

> individually (If there are large number of terminations, the MG could 
> use *ranges* of TerminationIds(?) to limit the number of such 
> messages)
>
> 2. MGC could audit the MG for the list of terminations that are in 
> service in which case the MG returns the list of terminations that are

> in service.
>
> But clearly sending a ServiceChange('ROOT') does not mean that all the

> terminations in the MG are in service. This presents lot of 
> operational problems as Christer pointed out.
>
> -- Bala
>
> __________________
> Bala Pitchandi
> UTStarcom Inc.
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf 
> Of SRD Wang JuLin
> Sent: Thursday, April 18, 2002 2:52 AM
> To: Christer Holmberg
> Cc: Barcotti, Glauco; megaco@ietf.org
> Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
> Hi,
> Well,I think MGC should send Modify messages (the number of it equals 
> to the number of terminations in RGW,I only refer to Residential GW) 
> to check the terminations's events  after MG reboot with Cold Start as

> a whole entity. All terminations will start up.In case of some 
> terminations fail to use,of course,we should send SC for definite 
> invalid termination with restored method  to Softswtich. Before you 
> WANT to use a termination,you should know whether it is ABLE to use 
> (ie.in service or out of  service).
>
> best  regards
> > :-)Jerry Wang
> tel:(8621)58541240 ext 9615
> mailto:wangjl2@sbell.com.cn
> Shanghai Bell Co.LTD
>
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Thursday, April 18, 2002 2:27 PM
> To: SRD Wang JuLin
> Cc: Barcotti, Glauco; megaco@ietf.org
> Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
> Hi,
>
> So, you want me to send a MODIFY to each of the THOUSANDS of 
> terminations I may want to use????
>
> And, the issue is not which termination I WANT to use (ie which I want

> the MGC to "enable" in the MG), but which termination I am ABLE (ie 
> which termination has at a certain time been booted/loaded/whatevver) 
> to use...
>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> SRD Wang JuLin wrote:
>
> > Hi,
> > Well,I send the ServiceChange for Root to Softswitch,it only send 4 
> > modify messages  to RGW.So i can only use 4 out of the 8 phones 
> > located in RGW. (I had provisioned 8 terminations into Softswitch
> >
> > )
> > 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
> >                          4500 008e 028b 0000 3f11 63de 0a0a 007a
> >                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
> >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> >                          7b4d 543d 5253 2c52 453d 3930 312c 4144
> >                          3d31 3131 3232 2c50 463d 416e 616c 6f67
> >                          5f4c 696e 655f 496e 7465 726f 7065 7261
> >                          6269 6c69 7479 5f54 6573 745f 5072 6f66
> >                          696c 652f 312c 563d 317d 7d7d 7d0a
> >
> >                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
> >                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
> >                           1 {  C =  - {  S C  = R  O O  T {  S V
> >                           { M  T =  R S  , R  E =  9 0  1 ,  A D
> >                           = 1  1 1  2 2  , P  F =  A n  a l  o g
> >                           _ L  i n  e _  I n  t e  r o  p e  r a
> >                           b i  l i  t y  _ T  e s  t _  P r  o f
> >                           i l  e /  1 ,  V =  1 }  } }  }^J 
> > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
> >                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
> >                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
> >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> >                          7b41 443d 3131 3132 322c 5046 3d43 4c53
> >                          2f31 2c56 3d31 7d7d 7d7d
> >
> >                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
> >                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
> >                           1 {  C =  - {  S C  = R  O O  T {  S V
> >                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
> >                           / 1  , V  = 1  } }  } } 16:46:18.325927 
> > eth0
>
> > > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 327b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } } 
> > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 337b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  1 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } } 
> > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 357b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } } 
> > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 367b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  3 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } } 
> > 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> >                          4500 0062 0293 0000 3f11 6402 0a0a 007a
> >                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 327d 7d0a 503d 3432 317b 433d
> >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
> >                          7d0a
> >
> >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
> >                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
> >                           - {  M F  = a  g w  _ j  u l  w /  3 }
> >                           }^J
> > 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> >                          4500 0062 0294 0000 3f11 6401 0a0a 007a
> >                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 357d 7d0a 503d 3432 337b 433d
> >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
> >                          7d0a
> >
> >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
> >                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
> >                           - {  M F  = a  g w  _ j  u l  w /  6 }
> >                           }^J
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > best  regards
> > > :-)Jerry Wang
> > tel:(8621)58541240 ext 9615
> > mailto:wangjl2@sbell.com.cn
> > Shanghai Bell Co.LTD
> >
> > -----Original Message-----
> > From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> > Sent: Wednesday, April 17, 2002 10:10 PM
> > To: 'Christer Holmberg'
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> >
> > >>         Assuming a Gateway with 2 terminations, one of >them is 
> > >> OK and the other is Malfunctioning. How should I >proceed if I 
> > >> want to
>
> > >> bring just the working termination >up (Cold Start)?
> > >>
> > >> a) If a ServiceChange is issued for ROOT termination MGC will 
> > >> think
>
> > >> that all terminations are up and, until another ServiceChange is 
> > >> issued taking the defective Termination out of service, a call 
> > >> could be attempted on that defective termination
> >
> > >I don't agree. A ServiceChange for ROOT will indicate that the MG 
> > >is up, not specific terminations. You would then have to send 
> > >additonal ServiceChange commands, with Reason code 900, for each 
> > >termination you want to put in-service.
> >
> > The example in the spec (Appendix A) and the 
> > draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT

> > on a ServiceChange all terminations are addressed (One ServiceChange

> > ROOT is sent and the terminations are available to use). Where did 
> > you
>
> > find information about ServiceChange ROOT not bringing all 
> > terminations up?
> >
> > Thanks,
> > Glauco
> >
> > >Regards,
> >
> > >hrister Holmberg
> > >ricsson Finland
> >
> > >
> > >
> > > b) If a ServiceChange is issued just for the working Termination 
> > > The
>
> > > ability to redirect the gateway to another MGC will be lost (See 
> > > quotation from spec below)
> > >
> > > "The return from ServiceChange is empty except when the Root 
> > > terminationID is used.  In that case it includes the following 
> > > parameters as required:"
> > >
> > > Thanks,
> > > Glauco
> > >
> > > _______________________________________________
> > > Megaco mailing 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

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
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  Thu Apr 18 17:37: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 RAA23721
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 17:37:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA05748
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 17:37:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA04279;
	Thu, 18 Apr 2002 17:18:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA04158
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 17:18:45 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23296
	for <megaco@ietf.org>; Thu, 18 Apr 2002 17:18:38 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3ILIOK00943;
	Thu, 18 Apr 2002 17:18:24 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Terry L Anderson'" <tla@lucent.com>, <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
Date: Thu, 18 Apr 2002 17:18:48 -0400
Message-ID: <002f01c1e71e$a1f41e50$368910ac@Bala>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <3CBF147D.D7A28C57@lucent.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id RAA04160
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

Please see my comments embedded as [BP] below.

Thanks
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Terry L Anderson
Sent: Thursday, April 18, 2002 2:46 PM
To: megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
Start)


I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes no
statement one way or the other) and it is apparent that there is not
agreement on what we want.  I believe that there are three possible
positions and that we should clarify this through the IG once we agree.

Possible clarifications:
ServiceChange on ROOT with method=restart (a registration):
1) implies that all physical terminations on MG are also up.  Exceptions
should be indicated by additional ServiceChanges on the down
terminations using Forced, preferrably in the same message and using
wildcards where possible.

[BP] The key here is what does *all* physical terminations represent.
Does it represent (a) all the terminations that are provisioned and are
in service (provisioned and hardware available & ready) at the time when
the MG sends the ServiceChange on ROOT (b) all the terminations that the
MG *expects* to be in service by the time it can start expecting
messages from MGC (c) all the terminations that are there in the system
irrespective of whether they come up later or sooner? 

[BP] Also this would warrant the MG to send a lot of 'forced'
ServiceChanges to bring the terminations down (up in the latter case)
particularly if the wildcarding cannot be used -- ie. when the
terminationIds are not contiguous. And it presents a potential error at
MGC, if the MG fails to send such a set of 'forced' ServiceChanges for
the terminations that are down (up in the latter case).

2) implies that all physical terminations on MG are down.  Those that
are up will be indicated by additional ServiceChanges on the up
terminations using method=restart, preferrably in the same message and
using wildcards were possible.

[BP] Same as above. What does *all* represent?

3) has no implication whether physical terminations are up or down, but
MGC may be provisioned to know whether an MG will indicate terminations
that are up or those that are down.

[BP] IMHO, this option is better because of the following reasons - (a)
It does not present any confusion about the status of the terminations
available in the MG and hence leaves it to MG/MGC to figure/inform of
the status of the terminations separately through an audit or
ServiceChange. (b) This gives flexibility to the implementors to choose
the options.

I should say that I do not like #3 but am including it as a possibility.

Preference for #1 or #2 probably depend on:
1) whether most physical terminations are available almost immediately
or come up slowly and at different speeds.
[BP] This is a larger unknown/assumption and the protocol cannot assume
anything on how soon/late the terminations can come up.

2) whether MGC is provisioned with knowledge about the available
physical terminations on an MG or expects to learn about them through
ServiceChanges or Audits
[BP] The choice should be left to the implementation and I think, the
protocol should leave it as it is.


Note that #1 can be implemented from #2 by adding:
    ServiceChange = *{Services{Method=Restart}}
to the action, and conversely #2 can be implemented from #1 by adding:
    ServiceChange = *{Services{Method=Forced}}

In either case exceptions (up or down) to the ALL can be indicated by
additional ServiceChange commands.

So (IMHO) it doesn't seem too critical which we choose, but we should
choose and document one.

Even though I think that most GWs probably would not register until all
or most of their physical terminations are available, I would probably
prefer #2 since I can easily indicated them all up with only one
additional ServiceChange and it seems more natural to indicate those up
those that are down.  But I can be happy with either #1 or #2.

[BP] Most (or many) implementations would want the gateway to just be up
so that it can be configured and then be gradually be brought up to its
full load. In that case, it would be appropriate to have the option #3
where the MG just informs the MGC of its registration and then let the
MGC know of the active terminations using the audit/ServiceChanges.

What do folks prefer?

[BP] That’s my two cents. :)




Balasubramanian Pitchandi wrote:

> Hi,
>
> I agree with Christer's views.
>
> If MG sends a ServiceChange 'ROOT', it only means that the gateway is 
> in or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). 
> The protocol is very clear on this, I think.
>
> Given that -- SVC(ROOT) means that the gateway is up -- now there are 
> many ways MGC could come to know of what terminations are in service:
>
> 1. MG sends ServiceChange for all the terminations that are in service

> individually (If there are large number of terminations, the MG could 
> use *ranges* of TerminationIds(?) to limit the number of such 
> messages)
>
> 2. MGC could audit the MG for the list of terminations that are in 
> service in which case the MG returns the list of terminations that are

> in service.
>
> But clearly sending a ServiceChange('ROOT') does not mean that all the

> terminations in the MG are in service. This presents lot of 
> operational problems as Christer pointed out.
>
> -- Bala
>
> __________________
> Bala Pitchandi
> UTStarcom Inc.
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf 
> Of SRD Wang JuLin
> Sent: Thursday, April 18, 2002 2:52 AM
> To: Christer Holmberg
> Cc: Barcotti, Glauco; megaco@ietf.org
> Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
> Hi,
> Well,I think MGC should send Modify messages (the number of it equals 
> to the number of terminations in RGW,I only refer to Residential GW) 
> to check the terminations's events  after MG reboot with Cold Start as

> a whole entity. All terminations will start up.In case of some 
> terminations fail to use,of course,we should send SC for definite 
> invalid termination with restored method  to Softswtich. Before you 
> WANT to use a termination,you should know whether it is ABLE to use 
> (ie.in service or out of  service).
>
> best  regards
> > :-)Jerry Wang
> tel:(8621)58541240 ext 9615
> mailto:wangjl2@sbell.com.cn
> Shanghai Bell Co.LTD
>
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Thursday, April 18, 2002 2:27 PM
> To: SRD Wang JuLin
> Cc: Barcotti, Glauco; megaco@ietf.org
> Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
> Hi,
>
> So, you want me to send a MODIFY to each of the THOUSANDS of 
> terminations I may want to use????
>
> And, the issue is not which termination I WANT to use (ie which I want

> the MGC to "enable" in the MG), but which termination I am ABLE (ie 
> which termination has at a certain time been booted/loaded/whatevver) 
> to use...
>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> SRD Wang JuLin wrote:
>
> > Hi,
> > Well,I send the ServiceChange for Root to Softswitch,it only send 4 
> > modify messages  to RGW.So i can only use 4 out of the 8 phones 
> > located in RGW. (I had provisioned 8 terminations into Softswitch
> >
> > )
> > 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
> >                          4500 008e 028b 0000 3f11 63de 0a0a 007a
> >                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
> >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> >                          7b4d 543d 5253 2c52 453d 3930 312c 4144
> >                          3d31 3131 3232 2c50 463d 416e 616c 6f67
> >                          5f4c 696e 655f 496e 7465 726f 7065 7261
> >                          6269 6c69 7479 5f54 6573 745f 5072 6f66
> >                          696c 652f 312c 563d 317d 7d7d 7d0a
> >
> >                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
> >                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
> >                           1 {  C =  - {  S C  = R  O O  T {  S V
> >                           { M  T =  R S  , R  E =  9 0  1 ,  A D
> >                           = 1  1 1  2 2  , P  F =  A n  a l  o g
> >                           _ L  i n  e _  I n  t e  r o  p e  r a
> >                           b i  l i  t y  _ T  e s  t _  P r  o f
> >                           i l  e /  1 ,  V =  1 }  } }  }^J 
> > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
> >                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
> >                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
> >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> >                          7b41 443d 3131 3132 322c 5046 3d43 4c53
> >                          2f31 2c56 3d31 7d7d 7d7d
> >
> >                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
> >                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
> >                           1 {  C =  - {  S C  = R  O O  T {  S V
> >                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
> >                           / 1  , V  = 1  } }  } } 16:46:18.325927 
> > eth0
>
> > > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 327b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } } 
> > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 337b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  1 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } } 
> > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 357b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } } 
> > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> >                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
> >                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> >                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 367b 453d 3538 3938 3239 7b61
> >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> >
> >                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
> >                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> >                           4 2  3 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
> >                           l /  o f  { s  t r  i c  t =  e x  a c
> >                           t ,  E M  { S  G {  c g  / d  t }  , E
> >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> >                           M =  d i  a l  p l  a n  1 }  , a  l /
> >                           o n  { s  t r  i c  t =  e x  a c  t }
> >                           , g  / s  c }  } }  , a  l /  o n  { s
> >                           t r  i c  t =  e x  a c  t }  } }  } } 
> > 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> >                          4500 0062 0293 0000 3f11 6402 0a0a 007a
> >                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 327d 7d0a 503d 3432 317b 433d
> >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
> >                          7d0a
> >
> >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
> >                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
> >                           - {  M F  = a  g w  _ j  u l  w /  3 }
> >                           }^J
> > 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> >                          4500 0062 0294 0000 3f11 6401 0a0a 007a
> >                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
> >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> >                          756c 772f 357d 7d0a 503d 3432 337b 433d
> >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
> >                          7d0a
> >
> >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
> >                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
> >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> >                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
> >                           - {  M F  = a  g w  _ j  u l  w /  6 }
> >                           }^J
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > best  regards
> > > :-)Jerry Wang
> > tel:(8621)58541240 ext 9615
> > mailto:wangjl2@sbell.com.cn
> > Shanghai Bell Co.LTD
> >
> > -----Original Message-----
> > From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> > Sent: Wednesday, April 17, 2002 10:10 PM
> > To: 'Christer Holmberg'
> > Cc: 'megaco@ietf.org'
> > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> >
> > >>         Assuming a Gateway with 2 terminations, one of >them is 
> > >> OK and the other is Malfunctioning. How should I >proceed if I 
> > >> want to
>
> > >> bring just the working termination >up (Cold Start)?
> > >>
> > >> a) If a ServiceChange is issued for ROOT termination MGC will 
> > >> think
>
> > >> that all terminations are up and, until another ServiceChange is 
> > >> issued taking the defective Termination out of service, a call 
> > >> could be attempted on that defective termination
> >
> > >I don't agree. A ServiceChange for ROOT will indicate that the MG 
> > >is up, not specific terminations. You would then have to send 
> > >additonal ServiceChange commands, with Reason code 900, for each 
> > >termination you want to put in-service.
> >
> > The example in the spec (Appendix A) and the 
> > draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT

> > on a ServiceChange all terminations are addressed (One ServiceChange

> > ROOT is sent and the terminations are available to use). Where did 
> > you
>
> > find information about ServiceChange ROOT not bringing all 
> > terminations up?
> >
> > Thanks,
> > Glauco
> >
> > >Regards,
> >
> > >hrister Holmberg
> > >ricsson Finland
> >
> > >
> > >
> > > b) If a ServiceChange is issued just for the working Termination 
> > > The
>
> > > ability to redirect the gateway to another MGC will be lost (See 
> > > quotation from spec below)
> > >
> > > "The return from ServiceChange is empty except when the Root 
> > > terminationID is used.  In that case it includes the following 
> > > parameters as required:"
> > >
> > > Thanks,
> > > Glauco
> > >
> > > _______________________________________________
> > > Megaco mailing 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

--

------------------------------------------------------------
Terry L Anderson              mailto:tla@lucent.com
Tel:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
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  Thu Apr 18 19:44: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 TAA25706
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 19:44:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11943;
	Thu, 18 Apr 2002 19:29:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11914
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 19:29:38 -0400 (EDT)
Received: from mtiwmhc21.worldnet.att.net (mtiwmhc21.worldnet.att.net [204.127.131.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25514
	for <megaco@ietf.org>; Thu, 18 Apr 2002 19:29:34 -0400 (EDT)
Received: from varneyhome.ieee.org ([12.84.123.144])
          by mtiwmhc21.worldnet.att.net
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020418232906.XKEN24238.mtiwmhc21.worldnet.att.net@varneyhome.ieee.org>
          for <megaco@ietf.org>; Thu, 18 Apr 2002 23:29:06 +0000
Message-Id: <4.3.2.7.2.20020418180933.00b5ec80@postoffice.worldnet.att.net>
X-Sender: a.varney@postoffice.worldnet.att.net (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 18 Apr 2002 18:29:53 -0500
To: megaco@ietf.org
From: Al Varney <varney@ieee.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
  Start)
In-Reply-To: <3CBF147D.D7A28C57@lucent.com>
References: <000801c1e6e1$18dc85e0$368910ac@Bala>
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 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
>Possible clarifications:
>ServiceChange on ROOT with method=restart (a registration):
>1) implies that all physical terminations on MG are also up.  Exceptions
>should be indicated by additional ServiceChanges on the down terminations
>using Forced, preferrably in the same message and using wildcards where
>possible.
>2) implies that all physical terminations on MG are down.  Those that are up
>will be indicated by additional ServiceChanges on the up terminations using
>method=restart, preferrably in the same message and using wildcards were
>possible.

...

>Even though I think that most GWs probably would not register until all or
>most of their physical terminations are available, I would probably prefer
>#2 since I can easily indicated them all up with only one additional
>ServiceChange and it seems more natural to indicate those up those that are
>down.  But I can be happy with either #1 or #2.

    #2 has the added (slight?) advantage that physical termination ID 
mis-matches (between MGC and MG) are identified when the MG sends 
SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC 
discovering these (non-existent) terminations 1 at a time, when connections 
are attempted.  With #1, a mis-match of this type might go undetected for 
days, until the MGC attempted to use/audit that particular termination ID.

    Terminations known only to the MGC will still go "undetected", but 
since no SVC(restart) is ever received for them, at least the MGC would not 
be trying to use them.  An audit might eventually reveal the reason for the 
OOS terminations.  (It is not unusual in "old" voice switches to have 
termination data populated without having the hardware yet in place, so a 
mis-match cannot be considered an error in all cases.)

    Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral 
interface(s) are all operational?  If it makes sense to positively assert 
SVC(restart) on physical terminations, why wouldn't it also make sense to 
indicate availability of ephemeral interfaces?  I'm thinking particularly 
of MGs with multiple ephemeral interfaces (IP, ATM, etc.).

    Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a 
big burden after MG restart.  If SVC is needed for every individual 
physical termination, then #1 becomes attractive.

Al Varney


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


From daemon@optimus.ietf.org  Thu Apr 18 19:44: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 TAA25715
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 19:44:22 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA12719
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 19:44:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11943;
	Thu, 18 Apr 2002 19:29:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11914
	for <megaco@optimus.ietf.org>; Thu, 18 Apr 2002 19:29:38 -0400 (EDT)
Received: from mtiwmhc21.worldnet.att.net (mtiwmhc21.worldnet.att.net [204.127.131.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25514
	for <megaco@ietf.org>; Thu, 18 Apr 2002 19:29:34 -0400 (EDT)
Received: from varneyhome.ieee.org ([12.84.123.144])
          by mtiwmhc21.worldnet.att.net
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020418232906.XKEN24238.mtiwmhc21.worldnet.att.net@varneyhome.ieee.org>
          for <megaco@ietf.org>; Thu, 18 Apr 2002 23:29:06 +0000
Message-Id: <4.3.2.7.2.20020418180933.00b5ec80@postoffice.worldnet.att.net>
X-Sender: a.varney@postoffice.worldnet.att.net (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 18 Apr 2002 18:29:53 -0500
To: megaco@ietf.org
From: Al Varney <varney@ieee.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
  Start)
In-Reply-To: <3CBF147D.D7A28C57@lucent.com>
References: <000801c1e6e1$18dc85e0$368910ac@Bala>
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 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
>Possible clarifications:
>ServiceChange on ROOT with method=restart (a registration):
>1) implies that all physical terminations on MG are also up.  Exceptions
>should be indicated by additional ServiceChanges on the down terminations
>using Forced, preferrably in the same message and using wildcards where
>possible.
>2) implies that all physical terminations on MG are down.  Those that are up
>will be indicated by additional ServiceChanges on the up terminations using
>method=restart, preferrably in the same message and using wildcards were
>possible.

...

>Even though I think that most GWs probably would not register until all or
>most of their physical terminations are available, I would probably prefer
>#2 since I can easily indicated them all up with only one additional
>ServiceChange and it seems more natural to indicate those up those that are
>down.  But I can be happy with either #1 or #2.

    #2 has the added (slight?) advantage that physical termination ID 
mis-matches (between MGC and MG) are identified when the MG sends 
SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC 
discovering these (non-existent) terminations 1 at a time, when connections 
are attempted.  With #1, a mis-match of this type might go undetected for 
days, until the MGC attempted to use/audit that particular termination ID.

    Terminations known only to the MGC will still go "undetected", but 
since no SVC(restart) is ever received for them, at least the MGC would not 
be trying to use them.  An audit might eventually reveal the reason for the 
OOS terminations.  (It is not unusual in "old" voice switches to have 
termination data populated without having the hardware yet in place, so a 
mis-match cannot be considered an error in all cases.)

    Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral 
interface(s) are all operational?  If it makes sense to positively assert 
SVC(restart) on physical terminations, why wouldn't it also make sense to 
indicate availability of ephemeral interfaces?  I'm thinking particularly 
of MGs with multiple ephemeral interfaces (IP, ATM, etc.).

    Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a 
big burden after MG restart.  If SVC is needed for every individual 
physical termination, then #1 becomes attractive.

Al Varney


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



From megaco-admin@ietf.org  Thu Apr 18 20:54: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 UAA26681
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 20:54:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA15404;
	Thu, 18 Apr 2002 20:32:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA15375
	for <megaco@ns.ietf.org>; Thu, 18 Apr 2002 20:32:43 -0400 (EDT)
Received: from ish7.ericsson.com.au (ish7.ericsson.com.au [203.61.155.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26458
	for <megaco@ietf.org>; Thu, 18 Apr 2002 20:32:37 -0400 (EDT)
Received: from brsf10.epa.ericsson.se (brsf10 [146.11.8.4])
	by ish7.ericsson.com.au (8.11.6+Sun/8.11.6) with ESMTP id g3J0V5017739
	for <megaco@ietf.org>; Fri, 19 Apr 2002 10:31:05 +1000 (EST)
Received: from ericsson.com.au (dhcp-239-110.epa.ericsson.se [146.11.239.110])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id KAA17478
	for <megaco@ietf.org>; Fri, 19 Apr 2002 10:32:38 +1000 (EST)
Message-ID: <3CBF65A5.9CDDAAA9@ericsson.com.au>
Date: Fri, 19 Apr 2002 10:32:37 +1000
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: [Fwd: RE: Ericsson position regarding ServiceChange for a single 
 termination? (Was: [Megaco] ServiceChange for a single termination (Cold 
 Start))]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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



G'Day Terry,

For some reason I was kicked off the Megaco mailing list seevral weeks ago so
that's why you haven't seen any input from me.

Firstly I think its clear that the Root termination addresses the gateway as a
whole not individual termination.

Secondly I think it is clear the default state of termination is "in service".

I agree that terminations which are down may be indicated via individual
servicechanges. 

I think it could be covered in the ServiceChange clarification work that we
discussed at the last SG16 meeting.

Regards, Christian

>
> -----Original Message-----
> From: Terry L Anderson [mailto:tla@lucent.com]
> Sent: Thursday, April 18, 2002 11:46 AM
> To: megaco@ietf.org
> Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
>
> I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes no
> statement one way or the other) and it is apparent that there is not
> agreement on what we want.  I believe that there are three possible
> positions and that we should clarify this through the IG once we agree.
>
> Possible clarifications:
> ServiceChange on ROOT with method=restart (a registration):
> 1) implies that all physical terminations on MG are also up.  Exceptions
> should be indicated by additional ServiceChanges on the down terminations
> using Forced, preferrably in the same message and using wildcards where
> possible.
> 2) implies that all physical terminations on MG are down.  Those
> that are up
> will be indicated by additional ServiceChanges on the up
> terminations using
> method=restart, preferrably in the same message and using wildcards were
> possible.
> 3) has no implication whether physical terminations are up or
> down, but MGC
> may be provisioned to know whether an MG will indicate
> terminations that are
> up or those that are down.
>
> I should say that I do not like #3 but am including it as a possibility.
>
> Preference for #1 or #2 probably depend on:
> 1) whether most physical terminations are available almost immediately or
> come up slowly and at different speeds.
> 2) whether MGC is provisioned with knowledge about the available physical
> terminations on an MG or expects to learn about them through
> ServiceChanges
> or Audits
>
> Note that #1 can be implemented from #2 by adding:
>     ServiceChange = *{Services{Method=Restart}}
> to the action, and conversely #2 can be implemented from #1 by adding:
>     ServiceChange = *{Services{Method=Forced}}
>
> In either case exceptions (up or down) to the ALL can be indicated by
> additional ServiceChange commands.
>
> So (IMHO) it doesn't seem too critical which we choose, but we
> should choose
> and document one.
>
> Even though I think that most GWs probably would not register until all or
> most of their physical terminations are available, I would probably prefer
> #2 since I can easily indicated them all up with only one additional
> ServiceChange and it seems more natural to indicate those up
> those that are
> down.  But I can be happy with either #1 or #2.
>
> What do folks prefer?
>
> Balasubramanian Pitchandi wrote:
>
> > Hi,
> >
> > I agree with Christer's views.
> >
> > If MG sends a ServiceChange 'ROOT', it only means that the gateway is in
> > or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). The
> > protocol is very clear on this, I think.
> >
> > Given that -- SVC(ROOT) means that the gateway is up -- now there are
> > many ways MGC could come to know of what terminations are in service:
> >
> > 1. MG sends ServiceChange for all the terminations that are in service
> > individually (If there are large number of terminations, the MG could
> > use *ranges* of TerminationIds(?) to limit the number of such messages)
> >
> > 2. MGC could audit the MG for the list of terminations that are in
> > service in which case the MG returns the list of terminations that are
> > in service.
> >
> > But clearly sending a ServiceChange('ROOT') does not mean that all the
> > terminations in the MG are in service. This presents lot of operational
> > problems as Christer pointed out.
> >
> > -- Bala
> >
> > __________________
> > Bala Pitchandi
> > UTStarcom Inc.
> >
> > -----Original Message-----
> > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> > SRD Wang JuLin
> > Sent: Thursday, April 18, 2002 2:52 AM
> > To: Christer Holmberg
> > Cc: Barcotti, Glauco; megaco@ietf.org
> > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> > Well,I think MGC should send Modify messages (the number of it equals to
> > the number of terminations in RGW,I only refer to Residential GW) to
> > check the terminations's events  after MG reboot with Cold Start as a
> > whole entity. All terminations will start up.In case of some
> > terminations fail to use,of course,we should send SC for definite
> > invalid termination with restored method  to Softswtich. Before you WANT
> > to use a termination,you should know whether it is ABLE to use (ie.in
> > service or out of  service).
> >
> > best  regards
> > > :-)Jerry Wang
> > tel:(8621)58541240 ext 9615
> > mailto:wangjl2@sbell.com.cn
> > Shanghai Bell Co.LTD
> >
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > Sent: Thursday, April 18, 2002 2:27 PM
> > To: SRD Wang JuLin
> > Cc: Barcotti, Glauco; megaco@ietf.org
> > Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> >
> > So, you want me to send a MODIFY to each of the THOUSANDS of
> > terminations I may want to use????
> >
> > And, the issue is not which termination I WANT to use (ie which I want
> > the MGC to "enable" in the MG), but which termination I am ABLE (ie
> > which termination has at a certain time been booted/loaded/whatevver) to
> > use...
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > SRD Wang JuLin wrote:
> >
> > > Hi,
> > > Well,I send the ServiceChange for Root to Softswitch,it only send 4
> > > modify messages  to RGW.So i can only use 4 out of the 8 phones
> > > located in RGW. (I had provisioned 8 terminations into Softswitch
> > >
> > > )
> > > 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
> > >                          4500 008e 028b 0000 3f11 63de 0a0a 007a
> > >                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
> > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > >                          7b4d 543d 5253 2c52 453d 3930 312c 4144
> > >                          3d31 3131 3232 2c50 463d 416e 616c 6f67
> > >                          5f4c 696e 655f 496e 7465 726f 7065 7261
> > >                          6269 6c69 7479 5f54 6573 745f 5072 6f66
> > >                          696c 652f 312c 563d 317d 7d7d 7d0a
> > >
> > >                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
> > >                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
> > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > >                           { M  T =  R S  , R  E =  9 0  1 ,  A D
> > >                           = 1  1 1  2 2  , P  F =  A n  a l  o g
> > >                           _ L  i n  e _  I n  t e  r o  p e  r a
> > >                           b i  l i  t y  _ T  e s  t _  P r  o f
> > >                           i l  e /  1 ,  V =  1 }  } }  }^J
> > > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
> > >                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
> > >                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
> > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > >                          7b41 443d 3131 3132 322c 5046 3d43 4c53
> > >                          2f31 2c56 3d31 7d7d 7d7d
> > >
> > >                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
> > >                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
> > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > >                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
> > >                           / 1  , V  = 1  } }  } } 16:46:18.325927 eth0
> >
> > > > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 327b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 337b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  1 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 357b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 367b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  3 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > >                          4500 0062 0293 0000 3f11 6402 0a0a 007a
> > >                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 327d 7d0a 503d 3432 317b 433d
> > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
> > >                          7d0a
> > >
> > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
> > >                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
> > >                           - {  M F  = a  g w  _ j  u l  w /  3 }
> > >                           }^J
> > > 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > >                          4500 0062 0294 0000 3f11 6401 0a0a 007a
> > >                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 357d 7d0a 503d 3432 337b 433d
> > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
> > >                          7d0a
> > >
> > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
> > >                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
> > >                           - {  M F  = a  g w  _ j  u l  w /  6 }
> > >                           }^J
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > best  regards
> > > > :-)Jerry Wang
> > > tel:(8621)58541240 ext 9615
> > > mailto:wangjl2@sbell.com.cn
> > > Shanghai Bell Co.LTD
> > >
> > > -----Original Message-----
> > > From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> > > Sent: Wednesday, April 17, 2002 10:10 PM
> > > To: 'Christer Holmberg'
> > > Cc: 'megaco@ietf.org'
> > > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > > Start)
> > >
> > > Hi,
> > >
> > > >>         Assuming a Gateway with 2 terminations, one of >them is OK
> > > >> and the other is Malfunctioning. How should I >proceed if I want to
> >
> > > >> bring just the working termination >up (Cold Start)?
> > > >>
> > > >> a) If a ServiceChange is issued for ROOT termination MGC will think
> >
> > > >> that all terminations are up and, until another ServiceChange is
> > > >> issued taking the defective Termination out of service, a call
> > > >> could be attempted on that defective termination
> > >
> > > >I don't agree. A ServiceChange for ROOT will indicate that the MG is
> > > >up, not specific terminations. You would then have to send additonal
> > > >ServiceChange commands, with Reason code 900, for each termination
> > > >you want to put in-service.
> > >
> > > The example in the spec (Appendix A) and the
> > > draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT
> > > on a ServiceChange all terminations are addressed (One ServiceChange
> > > ROOT is sent and the terminations are available to use). Where did you
> >
> > > find information about ServiceChange ROOT not bringing all
> > > terminations up?
> > >
> > > Thanks,
> > > Glauco
> > >
> > > >Regards,
> > >
> > > >hrister Holmberg
> > > >ricsson Finland
> > >
> > > >
> > > >
> > > > b) If a ServiceChange is issued just for the working Termination The
> >
> > > > ability to redirect the gateway to another MGC will be lost (See
> > > > quotation from spec below)
> > > >
> > > > "The return from ServiceChange is empty except when the Root
> > > > terminationID is used.  In that case it includes the following
> > > > parameters as required:"
> > > >
> > > > Thanks,
> > > > Glauco
> > > >
> > > > _______________________________________________
> > > > Megaco mailing 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
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:732.949.5628   Fax:732.949.7016
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> 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  Thu Apr 18 20:54: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 UAA26692
	for <megaco-archive@odin.ietf.org>; Thu, 18 Apr 2002 20:54:36 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA15961
	for megaco-archive@odin.ietf.org; Thu, 18 Apr 2002 20:54:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA15404;
	Thu, 18 Apr 2002 20:32:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA15375
	for <megaco@ns.ietf.org>; Thu, 18 Apr 2002 20:32:43 -0400 (EDT)
Received: from ish7.ericsson.com.au (ish7.ericsson.com.au [203.61.155.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26458
	for <megaco@ietf.org>; Thu, 18 Apr 2002 20:32:37 -0400 (EDT)
Received: from brsf10.epa.ericsson.se (brsf10 [146.11.8.4])
	by ish7.ericsson.com.au (8.11.6+Sun/8.11.6) with ESMTP id g3J0V5017739
	for <megaco@ietf.org>; Fri, 19 Apr 2002 10:31:05 +1000 (EST)
Received: from ericsson.com.au (dhcp-239-110.epa.ericsson.se [146.11.239.110])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id KAA17478
	for <megaco@ietf.org>; Fri, 19 Apr 2002 10:32:38 +1000 (EST)
Message-ID: <3CBF65A5.9CDDAAA9@ericsson.com.au>
Date: Fri, 19 Apr 2002 10:32:37 +1000
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: [Fwd: RE: Ericsson position regarding ServiceChange for a single 
 termination? (Was: [Megaco] ServiceChange for a single termination (Cold 
 Start))]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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



G'Day Terry,

For some reason I was kicked off the Megaco mailing list seevral weeks ago so
that's why you haven't seen any input from me.

Firstly I think its clear that the Root termination addresses the gateway as a
whole not individual termination.

Secondly I think it is clear the default state of termination is "in service".

I agree that terminations which are down may be indicated via individual
servicechanges. 

I think it could be covered in the ServiceChange clarification work that we
discussed at the last SG16 meeting.

Regards, Christian

>
> -----Original Message-----
> From: Terry L Anderson [mailto:tla@lucent.com]
> Sent: Thursday, April 18, 2002 11:46 AM
> To: megaco@ietf.org
> Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
>
> I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes no
> statement one way or the other) and it is apparent that there is not
> agreement on what we want.  I believe that there are three possible
> positions and that we should clarify this through the IG once we agree.
>
> Possible clarifications:
> ServiceChange on ROOT with method=restart (a registration):
> 1) implies that all physical terminations on MG are also up.  Exceptions
> should be indicated by additional ServiceChanges on the down terminations
> using Forced, preferrably in the same message and using wildcards where
> possible.
> 2) implies that all physical terminations on MG are down.  Those
> that are up
> will be indicated by additional ServiceChanges on the up
> terminations using
> method=restart, preferrably in the same message and using wildcards were
> possible.
> 3) has no implication whether physical terminations are up or
> down, but MGC
> may be provisioned to know whether an MG will indicate
> terminations that are
> up or those that are down.
>
> I should say that I do not like #3 but am including it as a possibility.
>
> Preference for #1 or #2 probably depend on:
> 1) whether most physical terminations are available almost immediately or
> come up slowly and at different speeds.
> 2) whether MGC is provisioned with knowledge about the available physical
> terminations on an MG or expects to learn about them through
> ServiceChanges
> or Audits
>
> Note that #1 can be implemented from #2 by adding:
>     ServiceChange = *{Services{Method=Restart}}
> to the action, and conversely #2 can be implemented from #1 by adding:
>     ServiceChange = *{Services{Method=Forced}}
>
> In either case exceptions (up or down) to the ALL can be indicated by
> additional ServiceChange commands.
>
> So (IMHO) it doesn't seem too critical which we choose, but we
> should choose
> and document one.
>
> Even though I think that most GWs probably would not register until all or
> most of their physical terminations are available, I would probably prefer
> #2 since I can easily indicated them all up with only one additional
> ServiceChange and it seems more natural to indicate those up
> those that are
> down.  But I can be happy with either #1 or #2.
>
> What do folks prefer?
>
> Balasubramanian Pitchandi wrote:
>
> > Hi,
> >
> > I agree with Christer's views.
> >
> > If MG sends a ServiceChange 'ROOT', it only means that the gateway is in
> > or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). The
> > protocol is very clear on this, I think.
> >
> > Given that -- SVC(ROOT) means that the gateway is up -- now there are
> > many ways MGC could come to know of what terminations are in service:
> >
> > 1. MG sends ServiceChange for all the terminations that are in service
> > individually (If there are large number of terminations, the MG could
> > use *ranges* of TerminationIds(?) to limit the number of such messages)
> >
> > 2. MGC could audit the MG for the list of terminations that are in
> > service in which case the MG returns the list of terminations that are
> > in service.
> >
> > But clearly sending a ServiceChange('ROOT') does not mean that all the
> > terminations in the MG are in service. This presents lot of operational
> > problems as Christer pointed out.
> >
> > -- Bala
> >
> > __________________
> > Bala Pitchandi
> > UTStarcom Inc.
> >
> > -----Original Message-----
> > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> > SRD Wang JuLin
> > Sent: Thursday, April 18, 2002 2:52 AM
> > To: Christer Holmberg
> > Cc: Barcotti, Glauco; megaco@ietf.org
> > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> > Well,I think MGC should send Modify messages (the number of it equals to
> > the number of terminations in RGW,I only refer to Residential GW) to
> > check the terminations's events  after MG reboot with Cold Start as a
> > whole entity. All terminations will start up.In case of some
> > terminations fail to use,of course,we should send SC for definite
> > invalid termination with restored method  to Softswtich. Before you WANT
> > to use a termination,you should know whether it is ABLE to use (ie.in
> > service or out of  service).
> >
> > best  regards
> > > :-)Jerry Wang
> > tel:(8621)58541240 ext 9615
> > mailto:wangjl2@sbell.com.cn
> > Shanghai Bell Co.LTD
> >
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > Sent: Thursday, April 18, 2002 2:27 PM
> > To: SRD Wang JuLin
> > Cc: Barcotti, Glauco; megaco@ietf.org
> > Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> >
> > So, you want me to send a MODIFY to each of the THOUSANDS of
> > terminations I may want to use????
> >
> > And, the issue is not which termination I WANT to use (ie which I want
> > the MGC to "enable" in the MG), but which termination I am ABLE (ie
> > which termination has at a certain time been booted/loaded/whatevver) to
> > use...
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > SRD Wang JuLin wrote:
> >
> > > Hi,
> > > Well,I send the ServiceChange for Root to Softswitch,it only send 4
> > > modify messages  to RGW.So i can only use 4 out of the 8 phones
> > > located in RGW. (I had provisioned 8 terminations into Softswitch
> > >
> > > )
> > > 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
> > >                          4500 008e 028b 0000 3f11 63de 0a0a 007a
> > >                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
> > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > >                          7b4d 543d 5253 2c52 453d 3930 312c 4144
> > >                          3d31 3131 3232 2c50 463d 416e 616c 6f67
> > >                          5f4c 696e 655f 496e 7465 726f 7065 7261
> > >                          6269 6c69 7479 5f54 6573 745f 5072 6f66
> > >                          696c 652f 312c 563d 317d 7d7d 7d0a
> > >
> > >                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
> > >                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
> > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > >                           { M  T =  R S  , R  E =  9 0  1 ,  A D
> > >                           = 1  1 1  2 2  , P  F =  A n  a l  o g
> > >                           _ L  i n  e _  I n  t e  r o  p e  r a
> > >                           b i  l i  t y  _ T  e s  t _  P r  o f
> > >                           i l  e /  1 ,  V =  1 }  } }  }^J
> > > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
> > >                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
> > >                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
> > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > >                          7b41 443d 3131 3132 322c 5046 3d43 4c53
> > >                          2f31 2c56 3d31 7d7d 7d7d
> > >
> > >                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
> > >                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
> > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > >                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
> > >                           / 1  , V  = 1  } }  } } 16:46:18.325927 eth0
> >
> > > > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 327b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 337b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  1 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 357b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 367b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  3 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > >                          4500 0062 0293 0000 3f11 6402 0a0a 007a
> > >                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 327d 7d0a 503d 3432 317b 433d
> > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
> > >                          7d0a
> > >
> > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
> > >                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
> > >                           - {  M F  = a  g w  _ j  u l  w /  3 }
> > >                           }^J
> > > 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > >                          4500 0062 0294 0000 3f11 6401 0a0a 007a
> > >                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 357d 7d0a 503d 3432 337b 433d
> > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
> > >                          7d0a
> > >
> > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
> > >                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
> > >                           - {  M F  = a  g w  _ j  u l  w /  6 }
> > >                           }^J
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > best  regards
> > > > :-)Jerry Wang
> > > tel:(8621)58541240 ext 9615
> > > mailto:wangjl2@sbell.com.cn
> > > Shanghai Bell Co.LTD
> > >
> > > -----Original Message-----
> > > From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> > > Sent: Wednesday, April 17, 2002 10:10 PM
> > > To: 'Christer Holmberg'
> > > Cc: 'megaco@ietf.org'
> > > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > > Start)
> > >
> > > Hi,
> > >
> > > >>         Assuming a Gateway with 2 terminations, one of >them is OK
> > > >> and the other is Malfunctioning. How should I >proceed if I want to
> >
> > > >> bring just the working termination >up (Cold Start)?
> > > >>
> > > >> a) If a ServiceChange is issued for ROOT termination MGC will think
> >
> > > >> that all terminations are up and, until another ServiceChange is
> > > >> issued taking the defective Termination out of service, a call
> > > >> could be attempted on that defective termination
> > >
> > > >I don't agree. A ServiceChange for ROOT will indicate that the MG is
> > > >up, not specific terminations. You would then have to send additonal
> > > >ServiceChange commands, with Reason code 900, for each termination
> > > >you want to put in-service.
> > >
> > > The example in the spec (Appendix A) and the
> > > draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT
> > > on a ServiceChange all terminations are addressed (One ServiceChange
> > > ROOT is sent and the terminations are available to use). Where did you
> >
> > > find information about ServiceChange ROOT not bringing all
> > > terminations up?
> > >
> > > Thanks,
> > > Glauco
> > >
> > > >Regards,
> > >
> > > >hrister Holmberg
> > > >ricsson Finland
> > >
> > > >
> > > >
> > > > b) If a ServiceChange is issued just for the working Termination The
> >
> > > > ability to redirect the gateway to another MGC will be lost (See
> > > > quotation from spec below)
> > > >
> > > > "The return from ServiceChange is empty except when the Root
> > > > terminationID is used.  In that case it includes the following
> > > > parameters as required:"
> > > >
> > > > Thanks,
> > > > Glauco
> > > >
> > > > _______________________________________________
> > > > Megaco mailing 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
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:732.949.5628   Fax:732.949.7016
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> 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  Fri Apr 19 00:38: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 AAA02063
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 00:38:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA26804;
	Fri, 19 Apr 2002 00:20:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA26773
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 00:20:47 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01701
	for <megaco@ietf.org>; Fri, 19 Apr 2002 00:20:38 -0400 (EDT)
From: vbajaj@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 g3J4L9c13081;
	Fri, 19 Apr 2002 09:51:09 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA0.001798B8 ; Fri, 19 Apr 2002 09:47:44 +0530
X-Lotus-FromDomain: HSS
To: Al Varney <varney@ieee.org>
cc: megaco@ietf.org
Message-ID: <65256BA0.00178569.00@sandesh.hss.hns.com>
Date: Fri, 19 Apr 2002 09:49:34 +0530
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
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



Al,
       The advantage you have cited below will hold true only under the
assumption
  that MG sends ServiceChange for individual terminations instead of using a
wildcard.
  Sending ServiceChange for individual terminations would be too expensive in
terms
  of network bandwidth as well as MG processing for extremely large sized
Gateways.
  I would expect that if MGC is interested in finding out configuration
inconsistencies
  with its MGs, it would do an Audit at lesiure in parallel to handling normal
calls.

 IMHO, "ServiceChange on ROOT" should indicate all terminations are up at the
MG.
 ServiceChange for Out Of Service Terminations can be sent subsequently. Total
number of messages required in this scenario would be
(1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
terminations)

Even if we go by approach #2 suggested below, the latter step (i.e. sending
ServiceChange
for Out Of Service Terminations) will anyway have to be executed.
 Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded Termination Id
to indicate that all terminations in the MG are In Service, it will need to send
 Out of Service ServiceChange for those terminations that have been configured
 but not hardware equipped. The number of messages required in this scenario
would be

(1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
ServiceChange
  for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))

The MG may of course choose not to use a wildcarded
termination signifiying all terminations on the MG and instead use multiple
ServiceChange commands each with a Termination Id (tg1/fac1/*) that siginfies a
DS0 aggregation. In this case, the number of ServiceChange commands would equal
the number of such DS0 aggregations in the MG i.e. several ServiceChange
messages
 would be needed to complete the initial MG-MGC startup sequence. The number of
 messages required in this scenario would be

(1 ServiceChange on ROOT + n ServiceChange for configured and equipped
terminations
    (Term Id = "/TG!/Fac1/*))

{Assuming most of the terminations in MG would be In Service, n could be a large
value unless
  the MG is intelligent and can optimize on the number of messages}

To summarize, IMO that number of (ServiceChange) messages required at startup
 would turn out to be larger in approach #2 than in approach #1. So, why not
choose
 a strategy that is optimal ?

Rgds,

Vikas Bajaj
NGN Group
Hughes Software Systems
(www.hssworld.com)






Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)




At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
>Possible clarifications:
>ServiceChange on ROOT with method=restart (a registration):
>1) implies that all physical terminations on MG are also up.  Exceptions
>should be indicated by additional ServiceChanges on the down terminations
>using Forced, preferrably in the same message and using wildcards where
>possible.
>2) implies that all physical terminations on MG are down.  Those that are up
>will be indicated by additional ServiceChanges on the up terminations using
>method=restart, preferrably in the same message and using wildcards were
>possible.

...

>Even though I think that most GWs probably would not register until all or
>most of their physical terminations are available, I would probably prefer
>#2 since I can easily indicated them all up with only one additional
>ServiceChange and it seems more natural to indicate those up those that are
>down.  But I can be happy with either #1 or #2.

    #2 has the added (slight?) advantage that physical termination ID
mis-matches (between MGC and MG) are identified when the MG sends
SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
discovering these (non-existent) terminations 1 at a time, when connections
are attempted.  With #1, a mis-match of this type might go undetected for
days, until the MGC attempted to use/audit that particular termination ID.

    Terminations known only to the MGC will still go "undetected", but
since no SVC(restart) is ever received for them, at least the MGC would not
be trying to use them.  An audit might eventually reveal the reason for the
OOS terminations.  (It is not unusual in "old" voice switches to have
termination data populated without having the hardware yet in place, so a
mis-match cannot be considered an error in all cases.)

    Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
interface(s) are all operational?  If it makes sense to positively assert
SVC(restart) on physical terminations, why wouldn't it also make sense to
indicate availability of ephemeral interfaces?  I'm thinking particularly
of MGs with multiple ephemeral interfaces (IP, ATM, etc.).

    Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
big burden after MG restart.  If SVC is needed for every individual
physical termination, then #1 becomes attractive.

Al Varney


_______________________________________________
Megaco mailing list
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 Apr 19 00:38: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 AAA02074
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 00:38:11 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA27945
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 00:38:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA26804;
	Fri, 19 Apr 2002 00:20:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA26773
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 00:20:47 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01701
	for <megaco@ietf.org>; Fri, 19 Apr 2002 00:20:38 -0400 (EDT)
From: vbajaj@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 g3J4L9c13081;
	Fri, 19 Apr 2002 09:51:09 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA0.001798B8 ; Fri, 19 Apr 2002 09:47:44 +0530
X-Lotus-FromDomain: HSS
To: Al Varney <varney@ieee.org>
cc: megaco@ietf.org
Message-ID: <65256BA0.00178569.00@sandesh.hss.hns.com>
Date: Fri, 19 Apr 2002 09:49:34 +0530
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
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



Al,
       The advantage you have cited below will hold true only under the
assumption
  that MG sends ServiceChange for individual terminations instead of using a
wildcard.
  Sending ServiceChange for individual terminations would be too expensive in
terms
  of network bandwidth as well as MG processing for extremely large sized
Gateways.
  I would expect that if MGC is interested in finding out configuration
inconsistencies
  with its MGs, it would do an Audit at lesiure in parallel to handling normal
calls.

 IMHO, "ServiceChange on ROOT" should indicate all terminations are up at the
MG.
 ServiceChange for Out Of Service Terminations can be sent subsequently. Total
number of messages required in this scenario would be
(1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
terminations)

Even if we go by approach #2 suggested below, the latter step (i.e. sending
ServiceChange
for Out Of Service Terminations) will anyway have to be executed.
 Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded Termination Id
to indicate that all terminations in the MG are In Service, it will need to send
 Out of Service ServiceChange for those terminations that have been configured
 but not hardware equipped. The number of messages required in this scenario
would be

(1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
ServiceChange
  for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))

The MG may of course choose not to use a wildcarded
termination signifiying all terminations on the MG and instead use multiple
ServiceChange commands each with a Termination Id (tg1/fac1/*) that siginfies a
DS0 aggregation. In this case, the number of ServiceChange commands would equal
the number of such DS0 aggregations in the MG i.e. several ServiceChange
messages
 would be needed to complete the initial MG-MGC startup sequence. The number of
 messages required in this scenario would be

(1 ServiceChange on ROOT + n ServiceChange for configured and equipped
terminations
    (Term Id = "/TG!/Fac1/*))

{Assuming most of the terminations in MG would be In Service, n could be a large
value unless
  the MG is intelligent and can optimize on the number of messages}

To summarize, IMO that number of (ServiceChange) messages required at startup
 would turn out to be larger in approach #2 than in approach #1. So, why not
choose
 a strategy that is optimal ?

Rgds,

Vikas Bajaj
NGN Group
Hughes Software Systems
(www.hssworld.com)






Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM

To:   megaco@ietf.org
cc:    (bcc: Vikas Bajaj/HSS)

Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)




At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
>Possible clarifications:
>ServiceChange on ROOT with method=restart (a registration):
>1) implies that all physical terminations on MG are also up.  Exceptions
>should be indicated by additional ServiceChanges on the down terminations
>using Forced, preferrably in the same message and using wildcards where
>possible.
>2) implies that all physical terminations on MG are down.  Those that are up
>will be indicated by additional ServiceChanges on the up terminations using
>method=restart, preferrably in the same message and using wildcards were
>possible.

...

>Even though I think that most GWs probably would not register until all or
>most of their physical terminations are available, I would probably prefer
>#2 since I can easily indicated them all up with only one additional
>ServiceChange and it seems more natural to indicate those up those that are
>down.  But I can be happy with either #1 or #2.

    #2 has the added (slight?) advantage that physical termination ID
mis-matches (between MGC and MG) are identified when the MG sends
SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
discovering these (non-existent) terminations 1 at a time, when connections
are attempted.  With #1, a mis-match of this type might go undetected for
days, until the MGC attempted to use/audit that particular termination ID.

    Terminations known only to the MGC will still go "undetected", but
since no SVC(restart) is ever received for them, at least the MGC would not
be trying to use them.  An audit might eventually reveal the reason for the
OOS terminations.  (It is not unusual in "old" voice switches to have
termination data populated without having the hardware yet in place, so a
mis-match cannot be considered an error in all cases.)

    Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
interface(s) are all operational?  If it makes sense to positively assert
SVC(restart) on physical terminations, why wouldn't it also make sense to
indicate availability of ephemeral interfaces?  I'm thinking particularly
of MGs with multiple ephemeral interfaces (IP, ATM, etc.).

    Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
big burden after MG restart.  If SVC is needed for every individual
physical termination, then #1 becomes attractive.

Al Varney


_______________________________________________
Megaco mailing list
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 Apr 19 01:01: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 BAA02289
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 01:01:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28128;
	Fri, 19 Apr 2002 00:40:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28028
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 00:40:31 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02099
	for <megaco@ietf.org>; Fri, 19 Apr 2002 00:40:30 -0400 (EDT)
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 g3J4eE3G010405;
	Fri, 19 Apr 2002 06:40:14 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3J4eDo5003139;
	Fri, 19 Apr 2002 07:40:13 +0300 (EET DST)
Message-ID: <3CBF9FB3.9208F958@lmf.ericsson.se>
Date: Fri, 19 Apr 2002 07:40:20 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <000801c1e6e1$18dc85e0$368910ac@Bala> <3CBF147D.D7A28C57@lucent.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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,

Opton 1) vs 2) is what we have been discussing in this thread so far, and I
would prefear option 2).

I don't think option 3) - it would just be a compromise, since we couldn't agree
on something else :)

Regards,

Christer Holmberg
Ericsson Finland




Terry L Anderson wrote:

> I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes no
> statement one way or the other) and it is apparent that there is not
> agreement on what we want.  I believe that there are three possible
> positions and that we should clarify this through the IG once we agree.
>
> Possible clarifications:
> ServiceChange on ROOT with method=restart (a registration):
> 1) implies that all physical terminations on MG are also up.  Exceptions
> should be indicated by additional ServiceChanges on the down terminations
> using Forced, preferrably in the same message and using wildcards where
> possible.
> 2) implies that all physical terminations on MG are down.  Those that are up
> will be indicated by additional ServiceChanges on the up terminations using
> method=restart, preferrably in the same message and using wildcards were
> possible.
> 3) has no implication whether physical terminations are up or down, but MGC
> may be provisioned to know whether an MG will indicate terminations that are
> up or those that are down.
>
> I should say that I do not like #3 but am including it as a possibility.
>
> Preference for #1 or #2 probably depend on:
> 1) whether most physical terminations are available almost immediately or
> come up slowly and at different speeds.
> 2) whether MGC is provisioned with knowledge about the available physical
> terminations on an MG or expects to learn about them through ServiceChanges
> or Audits
>
> Note that #1 can be implemented from #2 by adding:
>     ServiceChange = *{Services{Method=Restart}}
> to the action, and conversely #2 can be implemented from #1 by adding:
>     ServiceChange = *{Services{Method=Forced}}
>
> In either case exceptions (up or down) to the ALL can be indicated by
> additional ServiceChange commands.
>
> So (IMHO) it doesn't seem too critical which we choose, but we should choose
> and document one.
>
> Even though I think that most GWs probably would not register until all or
> most of their physical terminations are available, I would probably prefer
> #2 since I can easily indicated them all up with only one additional
> ServiceChange and it seems more natural to indicate those up those that are
> down.  But I can be happy with either #1 or #2.
>
> What do folks prefer?
>
> Balasubramanian Pitchandi wrote:
>
> > Hi,
> >
> > I agree with Christer's views.
> >
> > If MG sends a ServiceChange 'ROOT', it only means that the gateway is in
> > or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). The
> > protocol is very clear on this, I think.
> >
> > Given that -- SVC(ROOT) means that the gateway is up -- now there are
> > many ways MGC could come to know of what terminations are in service:
> >
> > 1. MG sends ServiceChange for all the terminations that are in service
> > individually (If there are large number of terminations, the MG could
> > use *ranges* of TerminationIds(?) to limit the number of such messages)
> >
> > 2. MGC could audit the MG for the list of terminations that are in
> > service in which case the MG returns the list of terminations that are
> > in service.
> >
> > But clearly sending a ServiceChange('ROOT') does not mean that all the
> > terminations in the MG are in service. This presents lot of operational
> > problems as Christer pointed out.
> >
> > -- Bala
> >
> > __________________
> > Bala Pitchandi
> > UTStarcom Inc.
> >
> > -----Original Message-----
> > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> > SRD Wang JuLin
> > Sent: Thursday, April 18, 2002 2:52 AM
> > To: Christer Holmberg
> > Cc: Barcotti, Glauco; megaco@ietf.org
> > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> > Well,I think MGC should send Modify messages (the number of it equals to
> > the number of terminations in RGW,I only refer to Residential GW) to
> > check the terminations's events  after MG reboot with Cold Start as a
> > whole entity. All terminations will start up.In case of some
> > terminations fail to use,of course,we should send SC for definite
> > invalid termination with restored method  to Softswtich. Before you WANT
> > to use a termination,you should know whether it is ABLE to use (ie.in
> > service or out of  service).
> >
> > best  regards
> > > :-)Jerry Wang
> > tel:(8621)58541240 ext 9615
> > mailto:wangjl2@sbell.com.cn
> > Shanghai Bell Co.LTD
> >
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > Sent: Thursday, April 18, 2002 2:27 PM
> > To: SRD Wang JuLin
> > Cc: Barcotti, Glauco; megaco@ietf.org
> > Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> >
> > So, you want me to send a MODIFY to each of the THOUSANDS of
> > terminations I may want to use????
> >
> > And, the issue is not which termination I WANT to use (ie which I want
> > the MGC to "enable" in the MG), but which termination I am ABLE (ie
> > which termination has at a certain time been booted/loaded/whatevver) to
> > use...
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > SRD Wang JuLin wrote:
> >
> > > Hi,
> > > Well,I send the ServiceChange for Root to Softswitch,it only send 4
> > > modify messages  to RGW.So i can only use 4 out of the 8 phones
> > > located in RGW. (I had provisioned 8 terminations into Softswitch
> > >
> > > )
> > > 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
> > >                          4500 008e 028b 0000 3f11 63de 0a0a 007a
> > >                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
> > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > >                          7b4d 543d 5253 2c52 453d 3930 312c 4144
> > >                          3d31 3131 3232 2c50 463d 416e 616c 6f67
> > >                          5f4c 696e 655f 496e 7465 726f 7065 7261
> > >                          6269 6c69 7479 5f54 6573 745f 5072 6f66
> > >                          696c 652f 312c 563d 317d 7d7d 7d0a
> > >
> > >                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
> > >                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
> > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > >                           { M  T =  R S  , R  E =  9 0  1 ,  A D
> > >                           = 1  1 1  2 2  , P  F =  A n  a l  o g
> > >                           _ L  i n  e _  I n  t e  r o  p e  r a
> > >                           b i  l i  t y  _ T  e s  t _  P r  o f
> > >                           i l  e /  1 ,  V =  1 }  } }  }^J
> > > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
> > >                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
> > >                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
> > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > >                          7b41 443d 3131 3132 322c 5046 3d43 4c53
> > >                          2f31 2c56 3d31 7d7d 7d7d
> > >
> > >                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
> > >                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
> > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > >                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
> > >                           / 1  , V  = 1  } }  } } 16:46:18.325927 eth0
> >
> > > > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 327b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 337b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  1 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 357b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 367b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  3 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > >                          4500 0062 0293 0000 3f11 6402 0a0a 007a
> > >                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 327d 7d0a 503d 3432 317b 433d
> > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
> > >                          7d0a
> > >
> > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
> > >                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
> > >                           - {  M F  = a  g w  _ j  u l  w /  3 }
> > >                           }^J
> > > 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > >                          4500 0062 0294 0000 3f11 6401 0a0a 007a
> > >                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 357d 7d0a 503d 3432 337b 433d
> > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
> > >                          7d0a
> > >
> > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
> > >                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
> > >                           - {  M F  = a  g w  _ j  u l  w /  6 }
> > >                           }^J
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > best  regards
> > > > :-)Jerry Wang
> > > tel:(8621)58541240 ext 9615
> > > mailto:wangjl2@sbell.com.cn
> > > Shanghai Bell Co.LTD
> > >
> > > -----Original Message-----
> > > From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> > > Sent: Wednesday, April 17, 2002 10:10 PM
> > > To: 'Christer Holmberg'
> > > Cc: 'megaco@ietf.org'
> > > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > > Start)
> > >
> > > Hi,
> > >
> > > >>         Assuming a Gateway with 2 terminations, one of >them is OK
> > > >> and the other is Malfunctioning. How should I >proceed if I want to
> >
> > > >> bring just the working termination >up (Cold Start)?
> > > >>
> > > >> a) If a ServiceChange is issued for ROOT termination MGC will think
> >
> > > >> that all terminations are up and, until another ServiceChange is
> > > >> issued taking the defective Termination out of service, a call
> > > >> could be attempted on that defective termination
> > >
> > > >I don't agree. A ServiceChange for ROOT will indicate that the MG is
> > > >up, not specific terminations. You would then have to send additonal
> > > >ServiceChange commands, with Reason code 900, for each termination
> > > >you want to put in-service.
> > >
> > > The example in the spec (Appendix A) and the
> > > draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT
> > > on a ServiceChange all terminations are addressed (One ServiceChange
> > > ROOT is sent and the terminations are available to use). Where did you
> >
> > > find information about ServiceChange ROOT not bringing all
> > > terminations up?
> > >
> > > Thanks,
> > > Glauco
> > >
> > > >Regards,
> > >
> > > >hrister Holmberg
> > > >ricsson Finland
> > >
> > > >
> > > >
> > > > b) If a ServiceChange is issued just for the working Termination The
> >
> > > > ability to redirect the gateway to another MGC will be lost (See
> > > > quotation from spec below)
> > > >
> > > > "The return from ServiceChange is empty except when the Root
> > > > terminationID is used.  In that case it includes the following
> > > > parameters as required:"
> > > >
> > > > Thanks,
> > > > Glauco
> > > >
> > > > _______________________________________________
> > > > Megaco mailing 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
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:732.949.5628   Fax:732.949.7016
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> 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  Fri Apr 19 01:01: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 BAA02303
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 01:01:34 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA29401
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 01:01:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28128;
	Fri, 19 Apr 2002 00:40:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28028
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 00:40:31 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02099
	for <megaco@ietf.org>; Fri, 19 Apr 2002 00:40:30 -0400 (EDT)
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 g3J4eE3G010405;
	Fri, 19 Apr 2002 06:40:14 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3J4eDo5003139;
	Fri, 19 Apr 2002 07:40:13 +0300 (EET DST)
Message-ID: <3CBF9FB3.9208F958@lmf.ericsson.se>
Date: Fri, 19 Apr 2002 07:40:20 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Terry L Anderson <tla@lucent.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <000801c1e6e1$18dc85e0$368910ac@Bala> <3CBF147D.D7A28C57@lucent.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
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,

Opton 1) vs 2) is what we have been discussing in this thread so far, and I
would prefear option 2).

I don't think option 3) - it would just be a compromise, since we couldn't agree
on something else :)

Regards,

Christer Holmberg
Ericsson Finland




Terry L Anderson wrote:

> I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes no
> statement one way or the other) and it is apparent that there is not
> agreement on what we want.  I believe that there are three possible
> positions and that we should clarify this through the IG once we agree.
>
> Possible clarifications:
> ServiceChange on ROOT with method=restart (a registration):
> 1) implies that all physical terminations on MG are also up.  Exceptions
> should be indicated by additional ServiceChanges on the down terminations
> using Forced, preferrably in the same message and using wildcards where
> possible.
> 2) implies that all physical terminations on MG are down.  Those that are up
> will be indicated by additional ServiceChanges on the up terminations using
> method=restart, preferrably in the same message and using wildcards were
> possible.
> 3) has no implication whether physical terminations are up or down, but MGC
> may be provisioned to know whether an MG will indicate terminations that are
> up or those that are down.
>
> I should say that I do not like #3 but am including it as a possibility.
>
> Preference for #1 or #2 probably depend on:
> 1) whether most physical terminations are available almost immediately or
> come up slowly and at different speeds.
> 2) whether MGC is provisioned with knowledge about the available physical
> terminations on an MG or expects to learn about them through ServiceChanges
> or Audits
>
> Note that #1 can be implemented from #2 by adding:
>     ServiceChange = *{Services{Method=Restart}}
> to the action, and conversely #2 can be implemented from #1 by adding:
>     ServiceChange = *{Services{Method=Forced}}
>
> In either case exceptions (up or down) to the ALL can be indicated by
> additional ServiceChange commands.
>
> So (IMHO) it doesn't seem too critical which we choose, but we should choose
> and document one.
>
> Even though I think that most GWs probably would not register until all or
> most of their physical terminations are available, I would probably prefer
> #2 since I can easily indicated them all up with only one additional
> ServiceChange and it seems more natural to indicate those up those that are
> down.  But I can be happy with either #1 or #2.
>
> What do folks prefer?
>
> Balasubramanian Pitchandi wrote:
>
> > Hi,
> >
> > I agree with Christer's views.
> >
> > If MG sends a ServiceChange 'ROOT', it only means that the gateway is in
> > or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). The
> > protocol is very clear on this, I think.
> >
> > Given that -- SVC(ROOT) means that the gateway is up -- now there are
> > many ways MGC could come to know of what terminations are in service:
> >
> > 1. MG sends ServiceChange for all the terminations that are in service
> > individually (If there are large number of terminations, the MG could
> > use *ranges* of TerminationIds(?) to limit the number of such messages)
> >
> > 2. MGC could audit the MG for the list of terminations that are in
> > service in which case the MG returns the list of terminations that are
> > in service.
> >
> > But clearly sending a ServiceChange('ROOT') does not mean that all the
> > terminations in the MG are in service. This presents lot of operational
> > problems as Christer pointed out.
> >
> > -- Bala
> >
> > __________________
> > Bala Pitchandi
> > UTStarcom Inc.
> >
> > -----Original Message-----
> > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> > SRD Wang JuLin
> > Sent: Thursday, April 18, 2002 2:52 AM
> > To: Christer Holmberg
> > Cc: Barcotti, Glauco; megaco@ietf.org
> > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> > Well,I think MGC should send Modify messages (the number of it equals to
> > the number of terminations in RGW,I only refer to Residential GW) to
> > check the terminations's events  after MG reboot with Cold Start as a
> > whole entity. All terminations will start up.In case of some
> > terminations fail to use,of course,we should send SC for definite
> > invalid termination with restored method  to Softswtich. Before you WANT
> > to use a termination,you should know whether it is ABLE to use (ie.in
> > service or out of  service).
> >
> > best  regards
> > > :-)Jerry Wang
> > tel:(8621)58541240 ext 9615
> > mailto:wangjl2@sbell.com.cn
> > Shanghai Bell Co.LTD
> >
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > Sent: Thursday, April 18, 2002 2:27 PM
> > To: SRD Wang JuLin
> > Cc: Barcotti, Glauco; megaco@ietf.org
> > Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> > Hi,
> >
> > So, you want me to send a MODIFY to each of the THOUSANDS of
> > terminations I may want to use????
> >
> > And, the issue is not which termination I WANT to use (ie which I want
> > the MGC to "enable" in the MG), but which termination I am ABLE (ie
> > which termination has at a certain time been booted/loaded/whatevver) to
> > use...
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> > SRD Wang JuLin wrote:
> >
> > > Hi,
> > > Well,I send the ServiceChange for Root to Softswitch,it only send 4
> > > modify messages  to RGW.So i can only use 4 out of the 8 phones
> > > located in RGW. (I had provisioned 8 terminations into Softswitch
> > >
> > > )
> > > 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
> > >                          4500 008e 028b 0000 3f11 63de 0a0a 007a
> > >                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
> > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > >                          7b4d 543d 5253 2c52 453d 3930 312c 4144
> > >                          3d31 3131 3232 2c50 463d 416e 616c 6f67
> > >                          5f4c 696e 655f 496e 7465 726f 7065 7261
> > >                          6269 6c69 7479 5f54 6573 745f 5072 6f66
> > >                          696c 652f 312c 563d 317d 7d7d 7d0a
> > >
> > >                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
> > >                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
> > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > >                           { M  T =  R S  , R  E =  9 0  1 ,  A D
> > >                           = 1  1 1  2 2  , P  F =  A n  a l  o g
> > >                           _ L  i n  e _  I n  t e  r o  p e  r a
> > >                           b i  l i  t y  _ T  e s  t _  P r  o f
> > >                           i l  e /  1 ,  V =  1 }  } }  }^J
> > > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
> > >                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
> > >                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
> > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > >                          7b41 443d 3131 3132 322c 5046 3d43 4c53
> > >                          2f31 2c56 3d31 7d7d 7d7d
> > >
> > >                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
> > >                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
> > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > >                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
> > >                           / 1  , V  = 1  } }  } } 16:46:18.325927 eth0
> >
> > > > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 327b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 337b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  1 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 357b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > >                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
> > >                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > >                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 367b 453d 3538 3938 3239 7b61
> > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > >
> > >                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
> > >                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > >                           4 2  3 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
> > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > >                          4500 0062 0293 0000 3f11 6402 0a0a 007a
> > >                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 327d 7d0a 503d 3432 317b 433d
> > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
> > >                          7d0a
> > >
> > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
> > >                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
> > >                           - {  M F  = a  g w  _ j  u l  w /  3 }
> > >                           }^J
> > > 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > >                          4500 0062 0294 0000 3f11 6401 0a0a 007a
> > >                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
> > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > >                          756c 772f 357d 7d0a 503d 3432 337b 433d
> > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
> > >                          7d0a
> > >
> > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
> > >                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
> > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > >                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
> > >                           - {  M F  = a  g w  _ j  u l  w /  6 }
> > >                           }^J
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > best  regards
> > > > :-)Jerry Wang
> > > tel:(8621)58541240 ext 9615
> > > mailto:wangjl2@sbell.com.cn
> > > Shanghai Bell Co.LTD
> > >
> > > -----Original Message-----
> > > From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> > > Sent: Wednesday, April 17, 2002 10:10 PM
> > > To: 'Christer Holmberg'
> > > Cc: 'megaco@ietf.org'
> > > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > > Start)
> > >
> > > Hi,
> > >
> > > >>         Assuming a Gateway with 2 terminations, one of >them is OK
> > > >> and the other is Malfunctioning. How should I >proceed if I want to
> >
> > > >> bring just the working termination >up (Cold Start)?
> > > >>
> > > >> a) If a ServiceChange is issued for ROOT termination MGC will think
> >
> > > >> that all terminations are up and, until another ServiceChange is
> > > >> issued taking the defective Termination out of service, a call
> > > >> could be attempted on that defective termination
> > >
> > > >I don't agree. A ServiceChange for ROOT will indicate that the MG is
> > > >up, not specific terminations. You would then have to send additonal
> > > >ServiceChange commands, with Reason code 900, for each termination
> > > >you want to put in-service.
> > >
> > > The example in the spec (Appendix A) and the
> > > draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT
> > > on a ServiceChange all terminations are addressed (One ServiceChange
> > > ROOT is sent and the terminations are available to use). Where did you
> >
> > > find information about ServiceChange ROOT not bringing all
> > > terminations up?
> > >
> > > Thanks,
> > > Glauco
> > >
> > > >Regards,
> > >
> > > >hrister Holmberg
> > > >ricsson Finland
> > >
> > > >
> > > >
> > > > b) If a ServiceChange is issued just for the working Termination The
> >
> > > > ability to redirect the gateway to another MGC will be lost (See
> > > > quotation from spec below)
> > > >
> > > > "The return from ServiceChange is empty except when the Root
> > > > terminationID is used.  In that case it includes the following
> > > > parameters as required:"
> > > >
> > > > Thanks,
> > > > Glauco
> > > >
> > > > _______________________________________________
> > > > Megaco mailing 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
>
> --
>
> ------------------------------------------------------------
> Terry L Anderson              mailto:tla@lucent.com
> Tel:732.949.5628   Fax:732.949.7016
> Lucent Technologies/INS/Voice Over IP Access Networks
> Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> 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  Fri Apr 19 01:17: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 BAA02449
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 01:17:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28612;
	Fri, 19 Apr 2002 00:55:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28582
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 00:55:07 -0400 (EDT)
Received: from ish7.ericsson.com.au (ish7.ericsson.com.au [203.61.155.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02227
	for <megaco@ietf.org>; Fri, 19 Apr 2002 00:55:05 -0400 (EDT)
Received: from brsf10.epa.ericsson.se (brsf10 [146.11.8.4])
	by ish7.ericsson.com.au (8.11.6+Sun/8.11.6) with ESMTP id g3J4rT011175;
	Fri, 19 Apr 2002 14:53:29 +1000 (EST)
Received: from ericsson.com.au (dhcp-239-110.epa.ericsson.se [146.11.239.110])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA07924;
	Fri, 19 Apr 2002 14:55:04 +1000 (EST)
Message-ID: <3CBFA31E.D0FB8548@ericsson.com.au>
Date: Fri, 19 Apr 2002 14:54:54 +1000
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: vbajaj@hss.hns.com
CC: Al Varney <varney@ieee.org>, megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <65256BA0.00178569.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 Vikas,

I believe you are getting what you asked for. The default state of all
terminaton is "inservice". 
If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can assume
that:
o as the MG is running and
o a MG contains terminations and 
o the termination's natural state is "inservice" 
therefore the individual terminations are running also.

Regards, Christian

vbajaj@hss.hns.com wrote:
> 
> Al,
>        The advantage you have cited below will hold true only under the
> assumption
>   that MG sends ServiceChange for individual terminations instead of using a
> wildcard.
>   Sending ServiceChange for individual terminations would be too expensive in
> terms
>   of network bandwidth as well as MG processing for extremely large sized
> Gateways.
>   I would expect that if MGC is interested in finding out configuration
> inconsistencies
>   with its MGs, it would do an Audit at lesiure in parallel to handling normal
> calls.
> 
>  IMHO, "ServiceChange on ROOT" should indicate all terminations are up at the
> MG.
>  ServiceChange for Out Of Service Terminations can be sent subsequently. Total
> number of messages required in this scenario would be
> (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
> terminations)
> 
> Even if we go by approach #2 suggested below, the latter step (i.e. sending
> ServiceChange
> for Out Of Service Terminations) will anyway have to be executed.
>  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded Termination Id
> to indicate that all terminations in the MG are In Service, it will need to send
>  Out of Service ServiceChange for those terminations that have been configured
>  but not hardware equipped. The number of messages required in this scenario
> would be
> 
> (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> ServiceChange
>   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
> 
> The MG may of course choose not to use a wildcarded
> termination signifiying all terminations on the MG and instead use multiple
> ServiceChange commands each with a Termination Id (tg1/fac1/*) that siginfies a
> DS0 aggregation. In this case, the number of ServiceChange commands would equal
> the number of such DS0 aggregations in the MG i.e. several ServiceChange
> messages
>  would be needed to complete the initial MG-MGC startup sequence. The number of
>  messages required in this scenario would be
> 
> (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
> terminations
>     (Term Id = "/TG!/Fac1/*))
> 
> {Assuming most of the terminations in MG would be In Service, n could be a large
> value unless
>   the MG is intelligent and can optimize on the number of messages}
> 
> To summarize, IMO that number of (ServiceChange) messages required at startup
>  would turn out to be larger in approach #2 than in approach #1. So, why not
> choose
>  a strategy that is optimal ?
> 
> Rgds,
> 
> Vikas Bajaj
> NGN Group
> Hughes Software Systems
> (www.hssworld.com)
> 
> Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> 
> To:   megaco@ietf.org
> cc:    (bcc: Vikas Bajaj/HSS)
> 
> Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)
> 
> At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> >Possible clarifications:
> >ServiceChange on ROOT with method=restart (a registration):
> >1) implies that all physical terminations on MG are also up.  Exceptions
> >should be indicated by additional ServiceChanges on the down terminations
> >using Forced, preferrably in the same message and using wildcards where
> >possible.
> >2) implies that all physical terminations on MG are down.  Those that are up
> >will be indicated by additional ServiceChanges on the up terminations using
> >method=restart, preferrably in the same message and using wildcards were
> >possible.
> 
> ...
> 
> >Even though I think that most GWs probably would not register until all or
> >most of their physical terminations are available, I would probably prefer
> >#2 since I can easily indicated them all up with only one additional
> >ServiceChange and it seems more natural to indicate those up those that are
> >down.  But I can be happy with either #1 or #2.
> 
>     #2 has the added (slight?) advantage that physical termination ID
> mis-matches (between MGC and MG) are identified when the MG sends
> SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
> discovering these (non-existent) terminations 1 at a time, when connections
> are attempted.  With #1, a mis-match of this type might go undetected for
> days, until the MGC attempted to use/audit that particular termination ID.
> 
>     Terminations known only to the MGC will still go "undetected", but
> since no SVC(restart) is ever received for them, at least the MGC would not
> be trying to use them.  An audit might eventually reveal the reason for the
> OOS terminations.  (It is not unusual in "old" voice switches to have
> termination data populated without having the hardware yet in place, so a
> mis-match cannot be considered an error in all cases.)
> 
>     Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> interface(s) are all operational?  If it makes sense to positively assert
> SVC(restart) on physical terminations, why wouldn't it also make sense to
> indicate availability of ephemeral interfaces?  I'm thinking particularly
> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> 
>     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
> big burden after MG restart.  If SVC is needed for every individual
> physical termination, then #1 becomes attractive.
> 
> Al Varney
> 
> _______________________________________________
> Megaco mailing 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 Apr 19 01: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 BAA02463
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 01:17:32 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA08364
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 01:17:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28612;
	Fri, 19 Apr 2002 00:55:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28582
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 00:55:07 -0400 (EDT)
Received: from ish7.ericsson.com.au (ish7.ericsson.com.au [203.61.155.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02227
	for <megaco@ietf.org>; Fri, 19 Apr 2002 00:55:05 -0400 (EDT)
Received: from brsf10.epa.ericsson.se (brsf10 [146.11.8.4])
	by ish7.ericsson.com.au (8.11.6+Sun/8.11.6) with ESMTP id g3J4rT011175;
	Fri, 19 Apr 2002 14:53:29 +1000 (EST)
Received: from ericsson.com.au (dhcp-239-110.epa.ericsson.se [146.11.239.110])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id OAA07924;
	Fri, 19 Apr 2002 14:55:04 +1000 (EST)
Message-ID: <3CBFA31E.D0FB8548@ericsson.com.au>
Date: Fri, 19 Apr 2002 14:54:54 +1000
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: vbajaj@hss.hns.com
CC: Al Varney <varney@ieee.org>, megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <65256BA0.00178569.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 Vikas,

I believe you are getting what you asked for. The default state of all
terminaton is "inservice". 
If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can assume
that:
o as the MG is running and
o a MG contains terminations and 
o the termination's natural state is "inservice" 
therefore the individual terminations are running also.

Regards, Christian

vbajaj@hss.hns.com wrote:
> 
> Al,
>        The advantage you have cited below will hold true only under the
> assumption
>   that MG sends ServiceChange for individual terminations instead of using a
> wildcard.
>   Sending ServiceChange for individual terminations would be too expensive in
> terms
>   of network bandwidth as well as MG processing for extremely large sized
> Gateways.
>   I would expect that if MGC is interested in finding out configuration
> inconsistencies
>   with its MGs, it would do an Audit at lesiure in parallel to handling normal
> calls.
> 
>  IMHO, "ServiceChange on ROOT" should indicate all terminations are up at the
> MG.
>  ServiceChange for Out Of Service Terminations can be sent subsequently. Total
> number of messages required in this scenario would be
> (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
> terminations)
> 
> Even if we go by approach #2 suggested below, the latter step (i.e. sending
> ServiceChange
> for Out Of Service Terminations) will anyway have to be executed.
>  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded Termination Id
> to indicate that all terminations in the MG are In Service, it will need to send
>  Out of Service ServiceChange for those terminations that have been configured
>  but not hardware equipped. The number of messages required in this scenario
> would be
> 
> (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> ServiceChange
>   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
> 
> The MG may of course choose not to use a wildcarded
> termination signifiying all terminations on the MG and instead use multiple
> ServiceChange commands each with a Termination Id (tg1/fac1/*) that siginfies a
> DS0 aggregation. In this case, the number of ServiceChange commands would equal
> the number of such DS0 aggregations in the MG i.e. several ServiceChange
> messages
>  would be needed to complete the initial MG-MGC startup sequence. The number of
>  messages required in this scenario would be
> 
> (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
> terminations
>     (Term Id = "/TG!/Fac1/*))
> 
> {Assuming most of the terminations in MG would be In Service, n could be a large
> value unless
>   the MG is intelligent and can optimize on the number of messages}
> 
> To summarize, IMO that number of (ServiceChange) messages required at startup
>  would turn out to be larger in approach #2 than in approach #1. So, why not
> choose
>  a strategy that is optimal ?
> 
> Rgds,
> 
> Vikas Bajaj
> NGN Group
> Hughes Software Systems
> (www.hssworld.com)
> 
> Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> 
> To:   megaco@ietf.org
> cc:    (bcc: Vikas Bajaj/HSS)
> 
> Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)
> 
> At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> >Possible clarifications:
> >ServiceChange on ROOT with method=restart (a registration):
> >1) implies that all physical terminations on MG are also up.  Exceptions
> >should be indicated by additional ServiceChanges on the down terminations
> >using Forced, preferrably in the same message and using wildcards where
> >possible.
> >2) implies that all physical terminations on MG are down.  Those that are up
> >will be indicated by additional ServiceChanges on the up terminations using
> >method=restart, preferrably in the same message and using wildcards were
> >possible.
> 
> ...
> 
> >Even though I think that most GWs probably would not register until all or
> >most of their physical terminations are available, I would probably prefer
> >#2 since I can easily indicated them all up with only one additional
> >ServiceChange and it seems more natural to indicate those up those that are
> >down.  But I can be happy with either #1 or #2.
> 
>     #2 has the added (slight?) advantage that physical termination ID
> mis-matches (between MGC and MG) are identified when the MG sends
> SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
> discovering these (non-existent) terminations 1 at a time, when connections
> are attempted.  With #1, a mis-match of this type might go undetected for
> days, until the MGC attempted to use/audit that particular termination ID.
> 
>     Terminations known only to the MGC will still go "undetected", but
> since no SVC(restart) is ever received for them, at least the MGC would not
> be trying to use them.  An audit might eventually reveal the reason for the
> OOS terminations.  (It is not unusual in "old" voice switches to have
> termination data populated without having the hardware yet in place, so a
> mis-match cannot be considered an error in all cases.)
> 
>     Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> interface(s) are all operational?  If it makes sense to positively assert
> SVC(restart) on physical terminations, why wouldn't it also make sense to
> indicate availability of ephemeral interfaces?  I'm thinking particularly
> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> 
>     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
> big burden after MG restart.  If SVC is needed for every individual
> physical termination, then #1 becomes attractive.
> 
> Al Varney
> 
> _______________________________________________
> Megaco mailing 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 Apr 19 03:37: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 DAA12574
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 03:37:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18688;
	Fri, 19 Apr 2002 03:19:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18644
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 03:19:39 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12361
	for <megaco@ietf.org>; Fri, 19 Apr 2002 03:19:37 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3J7JOs7015509;
	Fri, 19 Apr 2002 09:19:24 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3J7JOo5012856;
	Fri, 19 Apr 2002 10:19:24 +0300 (EET DST)
Message-ID: <3CBFC502.D111C101@lmf.ericsson.se>
Date: Fri, 19 Apr 2002 10:19:30 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: vbajaj@hss.hns.com, Al Varney <varney@ieee.org>, megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <65256BA0.00178569.00@sandesh.hss.hns.com> <3CBFA31E.D0FB8548@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,

Ok, so assuming that ROOT is enough to indicate that all Terminations are
"in-service", what error code shall the MG use if the MGC tries to use a termination
which still isn't ready to be used (but WILL be in eg 10 seconds)? 503? 521?

Regards,

Christer Holmberg
Ericsson Finland





Christian Groves wrote:

> G'Day Vikas,
>
> I believe you are getting what you asked for. The default state of all
> terminaton is "inservice".
> If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can assume
> that:
> o as the MG is running and
> o a MG contains terminations and
> o the termination's natural state is "inservice"
> therefore the individual terminations are running also.
>
> Regards, Christian
>
> vbajaj@hss.hns.com wrote:
> >
> > Al,
> >        The advantage you have cited below will hold true only under the
> > assumption
> >   that MG sends ServiceChange for individual terminations instead of using a
> > wildcard.
> >   Sending ServiceChange for individual terminations would be too expensive in
> > terms
> >   of network bandwidth as well as MG processing for extremely large sized
> > Gateways.
> >   I would expect that if MGC is interested in finding out configuration
> > inconsistencies
> >   with its MGs, it would do an Audit at lesiure in parallel to handling normal
> > calls.
> >
> >  IMHO, "ServiceChange on ROOT" should indicate all terminations are up at the
> > MG.
> >  ServiceChange for Out Of Service Terminations can be sent subsequently. Total
> > number of messages required in this scenario would be
> > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
> > terminations)
> >
> > Even if we go by approach #2 suggested below, the latter step (i.e. sending
> > ServiceChange
> > for Out Of Service Terminations) will anyway have to be executed.
> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded Termination Id
> > to indicate that all terminations in the MG are In Service, it will need to send
> >  Out of Service ServiceChange for those terminations that have been configured
> >  but not hardware equipped. The number of messages required in this scenario
> > would be
> >
> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> > ServiceChange
> >   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
> >
> > The MG may of course choose not to use a wildcarded
> > termination signifiying all terminations on the MG and instead use multiple
> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that siginfies a
> > DS0 aggregation. In this case, the number of ServiceChange commands would equal
> > the number of such DS0 aggregations in the MG i.e. several ServiceChange
> > messages
> >  would be needed to complete the initial MG-MGC startup sequence. The number of
> >  messages required in this scenario would be
> >
> > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
> > terminations
> >     (Term Id = "/TG!/Fac1/*))
> >
> > {Assuming most of the terminations in MG would be In Service, n could be a large
> > value unless
> >   the MG is intelligent and can optimize on the number of messages}
> >
> > To summarize, IMO that number of (ServiceChange) messages required at startup
> >  would turn out to be larger in approach #2 than in approach #1. So, why not
> > choose
> >  a strategy that is optimal ?
> >
> > Rgds,
> >
> > Vikas Bajaj
> > NGN Group
> > Hughes Software Systems
> > (www.hssworld.com)
> >
> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> >
> > To:   megaco@ietf.org
> > cc:    (bcc: Vikas Bajaj/HSS)
> >
> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)
> >
> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> > >Possible clarifications:
> > >ServiceChange on ROOT with method=restart (a registration):
> > >1) implies that all physical terminations on MG are also up.  Exceptions
> > >should be indicated by additional ServiceChanges on the down terminations
> > >using Forced, preferrably in the same message and using wildcards where
> > >possible.
> > >2) implies that all physical terminations on MG are down.  Those that are up
> > >will be indicated by additional ServiceChanges on the up terminations using
> > >method=restart, preferrably in the same message and using wildcards were
> > >possible.
> >
> > ...
> >
> > >Even though I think that most GWs probably would not register until all or
> > >most of their physical terminations are available, I would probably prefer
> > >#2 since I can easily indicated them all up with only one additional
> > >ServiceChange and it seems more natural to indicate those up those that are
> > >down.  But I can be happy with either #1 or #2.
> >
> >     #2 has the added (slight?) advantage that physical termination ID
> > mis-matches (between MGC and MG) are identified when the MG sends
> > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
> > discovering these (non-existent) terminations 1 at a time, when connections
> > are attempted.  With #1, a mis-match of this type might go undetected for
> > days, until the MGC attempted to use/audit that particular termination ID.
> >
> >     Terminations known only to the MGC will still go "undetected", but
> > since no SVC(restart) is ever received for them, at least the MGC would not
> > be trying to use them.  An audit might eventually reveal the reason for the
> > OOS terminations.  (It is not unusual in "old" voice switches to have
> > termination data populated without having the hardware yet in place, so a
> > mis-match cannot be considered an error in all cases.)
> >
> >     Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> > interface(s) are all operational?  If it makes sense to positively assert
> > SVC(restart) on physical terminations, why wouldn't it also make sense to
> > indicate availability of ephemeral interfaces?  I'm thinking particularly
> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> >
> >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
> > big burden after MG restart.  If SVC is needed for every individual
> > physical termination, then #1 becomes attractive.
> >
> > Al Varney
> >
> > _______________________________________________
> > Megaco mailing 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 Apr 19 03:37: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 DAA12585
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 03:37:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA19805
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 03:37:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18688;
	Fri, 19 Apr 2002 03:19:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18644
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 03:19:39 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12361
	for <megaco@ietf.org>; Fri, 19 Apr 2002 03:19:37 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3J7JOs7015509;
	Fri, 19 Apr 2002 09:19:24 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3J7JOo5012856;
	Fri, 19 Apr 2002 10:19:24 +0300 (EET DST)
Message-ID: <3CBFC502.D111C101@lmf.ericsson.se>
Date: Fri, 19 Apr 2002 10:19:30 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@ericsson.com.au>
CC: vbajaj@hss.hns.com, Al Varney <varney@ieee.org>, megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <65256BA0.00178569.00@sandesh.hss.hns.com> <3CBFA31E.D0FB8548@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,

Ok, so assuming that ROOT is enough to indicate that all Terminations are
"in-service", what error code shall the MG use if the MGC tries to use a termination
which still isn't ready to be used (but WILL be in eg 10 seconds)? 503? 521?

Regards,

Christer Holmberg
Ericsson Finland





Christian Groves wrote:

> G'Day Vikas,
>
> I believe you are getting what you asked for. The default state of all
> terminaton is "inservice".
> If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can assume
> that:
> o as the MG is running and
> o a MG contains terminations and
> o the termination's natural state is "inservice"
> therefore the individual terminations are running also.
>
> Regards, Christian
>
> vbajaj@hss.hns.com wrote:
> >
> > Al,
> >        The advantage you have cited below will hold true only under the
> > assumption
> >   that MG sends ServiceChange for individual terminations instead of using a
> > wildcard.
> >   Sending ServiceChange for individual terminations would be too expensive in
> > terms
> >   of network bandwidth as well as MG processing for extremely large sized
> > Gateways.
> >   I would expect that if MGC is interested in finding out configuration
> > inconsistencies
> >   with its MGs, it would do an Audit at lesiure in parallel to handling normal
> > calls.
> >
> >  IMHO, "ServiceChange on ROOT" should indicate all terminations are up at the
> > MG.
> >  ServiceChange for Out Of Service Terminations can be sent subsequently. Total
> > number of messages required in this scenario would be
> > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
> > terminations)
> >
> > Even if we go by approach #2 suggested below, the latter step (i.e. sending
> > ServiceChange
> > for Out Of Service Terminations) will anyway have to be executed.
> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded Termination Id
> > to indicate that all terminations in the MG are In Service, it will need to send
> >  Out of Service ServiceChange for those terminations that have been configured
> >  but not hardware equipped. The number of messages required in this scenario
> > would be
> >
> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> > ServiceChange
> >   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
> >
> > The MG may of course choose not to use a wildcarded
> > termination signifiying all terminations on the MG and instead use multiple
> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that siginfies a
> > DS0 aggregation. In this case, the number of ServiceChange commands would equal
> > the number of such DS0 aggregations in the MG i.e. several ServiceChange
> > messages
> >  would be needed to complete the initial MG-MGC startup sequence. The number of
> >  messages required in this scenario would be
> >
> > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
> > terminations
> >     (Term Id = "/TG!/Fac1/*))
> >
> > {Assuming most of the terminations in MG would be In Service, n could be a large
> > value unless
> >   the MG is intelligent and can optimize on the number of messages}
> >
> > To summarize, IMO that number of (ServiceChange) messages required at startup
> >  would turn out to be larger in approach #2 than in approach #1. So, why not
> > choose
> >  a strategy that is optimal ?
> >
> > Rgds,
> >
> > Vikas Bajaj
> > NGN Group
> > Hughes Software Systems
> > (www.hssworld.com)
> >
> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> >
> > To:   megaco@ietf.org
> > cc:    (bcc: Vikas Bajaj/HSS)
> >
> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)
> >
> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> > >Possible clarifications:
> > >ServiceChange on ROOT with method=restart (a registration):
> > >1) implies that all physical terminations on MG are also up.  Exceptions
> > >should be indicated by additional ServiceChanges on the down terminations
> > >using Forced, preferrably in the same message and using wildcards where
> > >possible.
> > >2) implies that all physical terminations on MG are down.  Those that are up
> > >will be indicated by additional ServiceChanges on the up terminations using
> > >method=restart, preferrably in the same message and using wildcards were
> > >possible.
> >
> > ...
> >
> > >Even though I think that most GWs probably would not register until all or
> > >most of their physical terminations are available, I would probably prefer
> > >#2 since I can easily indicated them all up with only one additional
> > >ServiceChange and it seems more natural to indicate those up those that are
> > >down.  But I can be happy with either #1 or #2.
> >
> >     #2 has the added (slight?) advantage that physical termination ID
> > mis-matches (between MGC and MG) are identified when the MG sends
> > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
> > discovering these (non-existent) terminations 1 at a time, when connections
> > are attempted.  With #1, a mis-match of this type might go undetected for
> > days, until the MGC attempted to use/audit that particular termination ID.
> >
> >     Terminations known only to the MGC will still go "undetected", but
> > since no SVC(restart) is ever received for them, at least the MGC would not
> > be trying to use them.  An audit might eventually reveal the reason for the
> > OOS terminations.  (It is not unusual in "old" voice switches to have
> > termination data populated without having the hardware yet in place, so a
> > mis-match cannot be considered an error in all cases.)
> >
> >     Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> > interface(s) are all operational?  If it makes sense to positively assert
> > SVC(restart) on physical terminations, why wouldn't it also make sense to
> > indicate availability of ephemeral interfaces?  I'm thinking particularly
> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> >
> >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
> > big burden after MG restart.  If SVC is needed for every individual
> > physical termination, then #1 becomes attractive.
> >
> > Al Varney
> >
> > _______________________________________________
> > Megaco mailing 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 Apr 19 05:24: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 FAA14265
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 05:24:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24481;
	Fri, 19 Apr 2002 04:59:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24456
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 04:59:36 -0400 (EDT)
Received: from blaze.hcltech.com ([203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13911
	for <megaco@ietf.org>; Fri, 19 Apr 2002 04:59:32 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id OAA07744;
	Fri, 19 Apr 2002 14:27:32 +0530
Message-ID: <3CBFDB9B.A0EBA6FC@netlab.hcltech.com>
Date: Fri, 19 Apr 2002 14:25:55 +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: Balasubramanian Pitchandi <bs@utstar.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
References: <001a01c1e703$93728a80$368910ac@Bala>
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 Bala/All,
	Are the list of provisioned MGCs and the list of active
MGCs same? I thought that the controller table corresponds to the
list of provisioned MGCs of all virtual MGs. And at any given point
of time, one(atmost) MGC of this list shall be active per virtual
MG. Such one active MGC per every virtual MG form the list of
active MGCs. Is my understanding correct?
Thanks & Regds.,
Giri
Balasubramanian Pitchandi wrote:
> 
> The MG is provisioned with a list of Media Gateway Controllers through
> "medGwyGatewayControllerTable" and if the MG receives a message from any
> other MGC than the one provisioned in the
> "medGwyGatewayControllerTable", it would send this NOTIFICATION (Trap -
> medGwyInvalidControllerAddress) to the NMS Manager.
> 
> Thanks
> Bala
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> Venkatesh A
> Sent: Thursday, April 18, 2002 3:04 AM
> To: megaco@ietf.org
> Subject: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
> 
> Hi All,
> 
> This is regarding the NOTIFICATION medGwyInvalidControllerAddress in
> megaco mib.  The draft says that this notfication has to be raised
> whenever a message is received from a controller that did not match any
> one valid controller IP address.  Here what is meant by "invalid
> controller" ???  Does it mean to say the mgc should be present in the
> pre provisioned list with mg?  In case of mg running on UDP, mg is not
> keeping the ip address of mgc whom it is talking to.  It simply replies
> to the mgc from where the request came.  So, when / how should this
> NOTIFICATION be raised?
> 
> Thanks
> Venkatesh
> 
> _______________________________________________
> Megaco mailing 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 Apr 19 05:24: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 FAA14276
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 05:24:15 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA25802
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 05:24:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24481;
	Fri, 19 Apr 2002 04:59:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA24456
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 04:59:36 -0400 (EDT)
Received: from blaze.hcltech.com ([203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13911
	for <megaco@ietf.org>; Fri, 19 Apr 2002 04:59:32 -0400 (EDT)
Received: from netlab.hcltech.com (giri.hclt-guindy.co.in [192.168.201.199])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id OAA07744;
	Fri, 19 Apr 2002 14:27:32 +0530
Message-ID: <3CBFDB9B.A0EBA6FC@netlab.hcltech.com>
Date: Fri, 19 Apr 2002 14:25:55 +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: Balasubramanian Pitchandi <bs@utstar.com>
CC: megaco@ietf.org
Subject: Re: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
References: <001a01c1e703$93728a80$368910ac@Bala>
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 Bala/All,
	Are the list of provisioned MGCs and the list of active
MGCs same? I thought that the controller table corresponds to the
list of provisioned MGCs of all virtual MGs. And at any given point
of time, one(atmost) MGC of this list shall be active per virtual
MG. Such one active MGC per every virtual MG form the list of
active MGCs. Is my understanding correct?
Thanks & Regds.,
Giri
Balasubramanian Pitchandi wrote:
> 
> The MG is provisioned with a list of Media Gateway Controllers through
> "medGwyGatewayControllerTable" and if the MG receives a message from any
> other MGC than the one provisioned in the
> "medGwyGatewayControllerTable", it would send this NOTIFICATION (Trap -
> medGwyInvalidControllerAddress) to the NMS Manager.
> 
> Thanks
> Bala
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> Venkatesh A
> Sent: Thursday, April 18, 2002 3:04 AM
> To: megaco@ietf.org
> Subject: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
> 
> Hi All,
> 
> This is regarding the NOTIFICATION medGwyInvalidControllerAddress in
> megaco mib.  The draft says that this notfication has to be raised
> whenever a message is received from a controller that did not match any
> one valid controller IP address.  Here what is meant by "invalid
> controller" ???  Does it mean to say the mgc should be present in the
> pre provisioned list with mg?  In case of mg running on UDP, mg is not
> keeping the ip address of mgc whom it is talking to.  It simply replies
> to the mgc from where the request came.  So, when / how should this
> NOTIFICATION be raised?
> 
> Thanks
> Venkatesh
> 
> _______________________________________________
> Megaco mailing 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 Apr 19 06:48: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 GAA15466
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 06:48:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00086;
	Fri, 19 Apr 2002 06:27:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00060
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 06:27:55 -0400 (EDT)
Received: from cms3.etri.re.kr (cms3.etri.re.kr [129.254.16.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15305
	for <megaco@ietf.org>; Fri, 19 Apr 2002 06:27:53 -0400 (EDT)
From: hektor@etri.re.kr
Received: by cms3.etri.re.kr with Internet Mail Service (5.5.2653.19)
	id <HNZRBFAP>; Fri, 19 Apr 2002 19:27:45 +0900
Message-ID: <8470181DABD5D511B3E700D0B7A8AC4A5DA384@cms3.etri.re.kr>
To: megaco@ietf.org
Date: Fri, 19 Apr 2002 19:27:38 +0900
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E78C.D3F34DE0"
Subject: [Megaco] doubt about "failover" because of MG 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

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_01C1E78C.D3F34DE0
Content-Type: text/plain;
	charset="euc-kr"

hi, list.

Can "failover" only be applied when redundant MGs used?
what redundant MGs implies that two(or more) MGs have same states(about
active contexts, terminations and so on).
Is that correct? 
Could please teach me what "redundant" exactly means?

In other words, if MG fails and there no MG which is running as standby
having same states as failed one
(even though there could be other MGs),
Shall the failed MG send ServiceChange command with graceful/forced?
If MG fails and there is a MG which is running as standby having same
states as failed one,
Eventaully, this time Can we use "failover"?

Anyway, another question arises.
In RFC 3015, 11.4 Failure of an MG reads
"If a MG fails.... ..... ......
[
Allowing the MGC to send duplicate messages to both MGs accomodates pairs
of MGs that are capable of redundant failover of one of the MGs. Only the
Working MG shall accept or reject transactions. 
]
...
...."

                    ---------------------
                          MGC
                    ---------------------
                      |  <-----------|-------------------  1) 
                      |               |                              1), 2)
MGC send same messages, MG1 and MG2 do something  
                      |               |<------------------ 2)
but only MG1 replies?
             ---------------        ---------------
              MG1(active)       MG2(standby)
             ---------------        -----------------

Above paragraph means that redundant MGs configuration is assisted by MGC
which duplicates messages.
Is that correct?
Should MGC support duplicating messages for this kind of configuration?

Do redundant MGs have same mIds?
Does not MGC send message to failed one until recovering completed?

Duplicating message makes me puzzled. 
Is it not better leave all redundancy mechanism to MG sides?

Last question)
If ,as a result of failover, now MG2 becomes active one and a little bit
later MG1 recovers from error,
Which MG issues ServiceChange with "restart"? MG1 or MG2?

Anyway, what is the effect of "restart"? 
Does "restarted MG" seem to be initial state which means there's no context?

thanks in advance.

------_=_NextPart_001_01C1E78C.D3F34DE0
Content-Type: text/html;
	charset="euc-kr"
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=3Deuc-kr">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>doubt about &quot;failover&quot; because of MG failure?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>hi, list.</FONT>
</P>

<P><FONT SIZE=3D2>Can &quot;failover&quot; only be applied when =
redundant MGs used?</FONT>
<BR><FONT SIZE=3D2>what redundant MGs implies that two(or more) MGs =
have same states(about active contexts, terminations and so on).</FONT>
<BR><FONT SIZE=3D2>Is that correct? </FONT>
<BR><FONT SIZE=3D2>Could please teach me what &quot;redundant&quot; =
exactly means?</FONT>
</P>

<P><FONT SIZE=3D2>In other words, if MG fails and there no MG which is =
running as standby having same states as failed one</FONT>
<BR><FONT SIZE=3D2>(even though there could be other MGs),</FONT>
<BR><FONT SIZE=3D2>Shall the failed MG send ServiceChange command with =
graceful/forced?</FONT>
<BR><FONT SIZE=3D2>If MG fails and there is a MG which is running as =
standby having same states as failed one,</FONT>
<BR><FONT SIZE=3D2>Eventaully, this time Can we use =
&quot;failover&quot;?</FONT>
</P>

<P><FONT SIZE=3D2>Anyway, another question arises.</FONT>
<BR><FONT SIZE=3D2>In RFC 3015, 11.4 Failure of an MG reads</FONT>
<BR><FONT SIZE=3D2>&quot;If a MG fails.... ..... ......</FONT>
<BR><FONT SIZE=3D2>[</FONT>
<BR><FONT SIZE=3D2>Allowing the MGC to send duplicate messages to both =
MGs accomodates pairs of MGs that are capable of redundant failover of =
one of the MGs. Only the Working MG shall accept or reject =
transactions. </FONT></P>

<P><FONT SIZE=3D2>]</FONT>
<BR><FONT SIZE=3D2>...</FONT>
<BR><FONT SIZE=3D2>....&quot;</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---------------------</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; MGC</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; =
---------------------</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; =
&lt;-----------|-------------------&nbsp; 1) </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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1), 2) MGC send same messages, MG1 and =
MG2 do something&nbsp; </FONT></P>

<P><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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; |&lt;------------------ =
2)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; but only MG1 replies?</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; =
---------------</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; MG1(active)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MG2(standby)</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; =
-----------------</FONT>
</P>

<P><FONT SIZE=3D2>Above paragraph means that redundant MGs =
configuration is assisted by MGC which duplicates messages.</FONT>
<BR><FONT SIZE=3D2>Is that correct?</FONT>
<BR><FONT SIZE=3D2>Should MGC support duplicating messages for this =
kind of configuration?</FONT>
</P>

<P><FONT SIZE=3D2>Do redundant MGs have same mIds?</FONT>
<BR><FONT SIZE=3D2>Does not MGC send message to failed one until =
recovering completed?</FONT>
</P>

<P><FONT SIZE=3D2>Duplicating message makes me puzzled. </FONT>
<BR><FONT SIZE=3D2>Is it not better leave all redundancy mechanism to =
MG sides?</FONT>
</P>

<P><FONT SIZE=3D2>Last question)</FONT>
<BR><FONT SIZE=3D2>If ,as a result of failover, now MG2 becomes active =
one and a little bit later MG1 recovers from error,</FONT>
<BR><FONT SIZE=3D2>Which MG issues ServiceChange with =
&quot;restart&quot;? MG1 or MG2?</FONT>
</P>

<P><FONT SIZE=3D2>Anyway, what is the effect of &quot;restart&quot;? =
</FONT>
<BR><FONT SIZE=3D2>Does &quot;restarted MG&quot; seem to be initial =
state which means there's no context?</FONT>
</P>

<P><FONT SIZE=3D2>thanks in advance.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E78C.D3F34DE0--

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


From daemon@ns.ietf.org  Fri Apr 19 06:48: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 GAA15480
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 06:48:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA01062
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 06:48:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00086;
	Fri, 19 Apr 2002 06:27:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00060
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 06:27:55 -0400 (EDT)
Received: from cms3.etri.re.kr (cms3.etri.re.kr [129.254.16.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15305
	for <megaco@ietf.org>; Fri, 19 Apr 2002 06:27:53 -0400 (EDT)
From: hektor@etri.re.kr
Received: by cms3.etri.re.kr with Internet Mail Service (5.5.2653.19)
	id <HNZRBFAP>; Fri, 19 Apr 2002 19:27:45 +0900
Message-ID: <8470181DABD5D511B3E700D0B7A8AC4A5DA384@cms3.etri.re.kr>
To: megaco@ietf.org
Date: Fri, 19 Apr 2002 19:27:38 +0900
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E78C.D3F34DE0"
Subject: [Megaco] doubt about "failover" because of MG 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

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_01C1E78C.D3F34DE0
Content-Type: text/plain;
	charset="euc-kr"

hi, list.

Can "failover" only be applied when redundant MGs used?
what redundant MGs implies that two(or more) MGs have same states(about
active contexts, terminations and so on).
Is that correct? 
Could please teach me what "redundant" exactly means?

In other words, if MG fails and there no MG which is running as standby
having same states as failed one
(even though there could be other MGs),
Shall the failed MG send ServiceChange command with graceful/forced?
If MG fails and there is a MG which is running as standby having same
states as failed one,
Eventaully, this time Can we use "failover"?

Anyway, another question arises.
In RFC 3015, 11.4 Failure of an MG reads
"If a MG fails.... ..... ......
[
Allowing the MGC to send duplicate messages to both MGs accomodates pairs
of MGs that are capable of redundant failover of one of the MGs. Only the
Working MG shall accept or reject transactions. 
]
...
...."

                    ---------------------
                          MGC
                    ---------------------
                      |  <-----------|-------------------  1) 
                      |               |                              1), 2)
MGC send same messages, MG1 and MG2 do something  
                      |               |<------------------ 2)
but only MG1 replies?
             ---------------        ---------------
              MG1(active)       MG2(standby)
             ---------------        -----------------

Above paragraph means that redundant MGs configuration is assisted by MGC
which duplicates messages.
Is that correct?
Should MGC support duplicating messages for this kind of configuration?

Do redundant MGs have same mIds?
Does not MGC send message to failed one until recovering completed?

Duplicating message makes me puzzled. 
Is it not better leave all redundancy mechanism to MG sides?

Last question)
If ,as a result of failover, now MG2 becomes active one and a little bit
later MG1 recovers from error,
Which MG issues ServiceChange with "restart"? MG1 or MG2?

Anyway, what is the effect of "restart"? 
Does "restarted MG" seem to be initial state which means there's no context?

thanks in advance.

------_=_NextPart_001_01C1E78C.D3F34DE0
Content-Type: text/html;
	charset="euc-kr"
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=3Deuc-kr">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>doubt about &quot;failover&quot; because of MG failure?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>hi, list.</FONT>
</P>

<P><FONT SIZE=3D2>Can &quot;failover&quot; only be applied when =
redundant MGs used?</FONT>
<BR><FONT SIZE=3D2>what redundant MGs implies that two(or more) MGs =
have same states(about active contexts, terminations and so on).</FONT>
<BR><FONT SIZE=3D2>Is that correct? </FONT>
<BR><FONT SIZE=3D2>Could please teach me what &quot;redundant&quot; =
exactly means?</FONT>
</P>

<P><FONT SIZE=3D2>In other words, if MG fails and there no MG which is =
running as standby having same states as failed one</FONT>
<BR><FONT SIZE=3D2>(even though there could be other MGs),</FONT>
<BR><FONT SIZE=3D2>Shall the failed MG send ServiceChange command with =
graceful/forced?</FONT>
<BR><FONT SIZE=3D2>If MG fails and there is a MG which is running as =
standby having same states as failed one,</FONT>
<BR><FONT SIZE=3D2>Eventaully, this time Can we use =
&quot;failover&quot;?</FONT>
</P>

<P><FONT SIZE=3D2>Anyway, another question arises.</FONT>
<BR><FONT SIZE=3D2>In RFC 3015, 11.4 Failure of an MG reads</FONT>
<BR><FONT SIZE=3D2>&quot;If a MG fails.... ..... ......</FONT>
<BR><FONT SIZE=3D2>[</FONT>
<BR><FONT SIZE=3D2>Allowing the MGC to send duplicate messages to both =
MGs accomodates pairs of MGs that are capable of redundant failover of =
one of the MGs. Only the Working MG shall accept or reject =
transactions. </FONT></P>

<P><FONT SIZE=3D2>]</FONT>
<BR><FONT SIZE=3D2>...</FONT>
<BR><FONT SIZE=3D2>....&quot;</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---------------------</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; MGC</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; =
---------------------</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; =
&lt;-----------|-------------------&nbsp; 1) </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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1), 2) MGC send same messages, MG1 and =
MG2 do something&nbsp; </FONT></P>

<P><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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; |&lt;------------------ =
2)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; but only MG1 replies?</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; =
---------------</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; MG1(active)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MG2(standby)</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; =
-----------------</FONT>
</P>

<P><FONT SIZE=3D2>Above paragraph means that redundant MGs =
configuration is assisted by MGC which duplicates messages.</FONT>
<BR><FONT SIZE=3D2>Is that correct?</FONT>
<BR><FONT SIZE=3D2>Should MGC support duplicating messages for this =
kind of configuration?</FONT>
</P>

<P><FONT SIZE=3D2>Do redundant MGs have same mIds?</FONT>
<BR><FONT SIZE=3D2>Does not MGC send message to failed one until =
recovering completed?</FONT>
</P>

<P><FONT SIZE=3D2>Duplicating message makes me puzzled. </FONT>
<BR><FONT SIZE=3D2>Is it not better leave all redundancy mechanism to =
MG sides?</FONT>
</P>

<P><FONT SIZE=3D2>Last question)</FONT>
<BR><FONT SIZE=3D2>If ,as a result of failover, now MG2 becomes active =
one and a little bit later MG1 recovers from error,</FONT>
<BR><FONT SIZE=3D2>Which MG issues ServiceChange with =
&quot;restart&quot;? MG1 or MG2?</FONT>
</P>

<P><FONT SIZE=3D2>Anyway, what is the effect of &quot;restart&quot;? =
</FONT>
<BR><FONT SIZE=3D2>Does &quot;restarted MG&quot; seem to be initial =
state which means there's no context?</FONT>
</P>

<P><FONT SIZE=3D2>thanks in advance.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E78C.D3F34DE0--

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



From megaco-admin@ietf.org  Fri Apr 19 09:46: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 JAA19779
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 09:46:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08453;
	Fri, 19 Apr 2002 09:20:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08356
	for <megaco@optimus.ietf.org>; Fri, 19 Apr 2002 09:20:26 -0400 (EDT)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19017
	for <megaco@ietf.org>; Fri, 19 Apr 2002 09:20:18 -0400 (EDT)
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 g3JDJox01431
	for <megaco@ietf.org>; Fri, 19 Apr 2002 08:19:50 -0500 (CDT)
Received: from cls7ws1.ssd.usa.alcatel.com (cls7ws1.ssd.usa.alcatel.com [143.209.236.42])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g3JDJWO01295
	for <megaco@ietf.org>; Fri, 19 Apr 2002 08:19:32 -0500 (CDT)
Received: from alcatel.com (localhost [127.0.0.1])
	by cls7ws1.ssd.usa.alcatel.com (8.9.3+Sun/8.9.1) with ESMTP id IAA03688
	for <megaco@ietf.org>; Fri, 19 Apr 2002 08:19:28 -0500 (CDT)
Message-ID: <3CC01960.5E4A4BAC@alcatel.com>
Date: Fri, 19 Apr 2002 08:19:28 -0500
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] ServiceChange for a single termination (Cold Start)
References: <65256BA0.00178569.00@sandesh.hss.hns.com> <3CBFA31E.D0FB8548@ericsson.com.au> <3CBFC502.D111C101@lmf.ericsson.se>
Content-Type: multipart/alternative;
 boundary="------------2E77CC1D7B3FAF367CA87102"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


Per Annex L, 503 and 521 are not used anymore.

Error Code # : 502 Name: Not ready.
Definition: The command directed to a termination was not executed because of the
service state of the termination.



Christer Holmberg wrote:

> Hi,
>
> Ok, so assuming that ROOT is enough to indicate that all Terminations are
> "in-service", what error code shall the MG use if the MGC tries to use a termination
> which still isn't ready to be used (but WILL be in eg 10 seconds)? 503? 521?
>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> Christian Groves wrote:
>
> > G'Day Vikas,
> >
> > I believe you are getting what you asked for. The default state of all
> > terminaton is "inservice".
> > If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can assume
> > that:
> > o as the MG is running and
> > o a MG contains terminations and
> > o the termination's natural state is "inservice"
> > therefore the individual terminations are running also.
> >
> > Regards, Christian
> >
> > vbajaj@hss.hns.com wrote:
> > >
> > > Al,
> > >        The advantage you have cited below will hold true only under the
> > > assumption
> > >   that MG sends ServiceChange for individual terminations instead of using a
> > > wildcard.
> > >   Sending ServiceChange for individual terminations would be too expensive in
> > > terms
> > >   of network bandwidth as well as MG processing for extremely large sized
> > > Gateways.
> > >   I would expect that if MGC is interested in finding out configuration
> > > inconsistencies
> > >   with its MGs, it would do an Audit at lesiure in parallel to handling normal
> > > calls.
> > >
> > >  IMHO, "ServiceChange on ROOT" should indicate all terminations are up at the
> > > MG.
> > >  ServiceChange for Out Of Service Terminations can be sent subsequently. Total
> > > number of messages required in this scenario would be
> > > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
> > > terminations)
> > >
> > > Even if we go by approach #2 suggested below, the latter step (i.e. sending
> > > ServiceChange
> > > for Out Of Service Terminations) will anyway have to be executed.
> > >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded Termination Id
> > > to indicate that all terminations in the MG are In Service, it will need to send
> > >  Out of Service ServiceChange for those terminations that have been configured
> > >  but not hardware equipped. The number of messages required in this scenario
> > > would be
> > >
> > > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> > > ServiceChange
> > >   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
> > >
> > > The MG may of course choose not to use a wildcarded
> > > termination signifiying all terminations on the MG and instead use multiple
> > > ServiceChange commands each with a Termination Id (tg1/fac1/*) that siginfies a
> > > DS0 aggregation. In this case, the number of ServiceChange commands would equal
> > > the number of such DS0 aggregations in the MG i.e. several ServiceChange
> > > messages
> > >  would be needed to complete the initial MG-MGC startup sequence. The number of
> > >  messages required in this scenario would be
> > >
> > > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
> > > terminations
> > >     (Term Id = "/TG!/Fac1/*))
> > >
> > > {Assuming most of the terminations in MG would be In Service, n could be a large
> > > value unless
> > >   the MG is intelligent and can optimize on the number of messages}
> > >
> > > To summarize, IMO that number of (ServiceChange) messages required at startup
> > >  would turn out to be larger in approach #2 than in approach #1. So, why not
> > > choose
> > >  a strategy that is optimal ?
> > >
> > > Rgds,
> > >
> > > Vikas Bajaj
> > > NGN Group
> > > Hughes Software Systems
> > > (www.hssworld.com)
> > >
> > > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> > >
> > > To:   megaco@ietf.org
> > > cc:    (bcc: Vikas Bajaj/HSS)
> > >
> > > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)
> > >
> > > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> > > >Possible clarifications:
> > > >ServiceChange on ROOT with method=restart (a registration):
> > > >1) implies that all physical terminations on MG are also up.  Exceptions
> > > >should be indicated by additional ServiceChanges on the down terminations
> > > >using Forced, preferrably in the same message and using wildcards where
> > > >possible.
> > > >2) implies that all physical terminations on MG are down.  Those that are up
> > > >will be indicated by additional ServiceChanges on the up terminations using
> > > >method=restart, preferrably in the same message and using wildcards were
> > > >possible.
> > >
> > > ...
> > >
> > > >Even though I think that most GWs probably would not register until all or
> > > >most of their physical terminations are available, I would probably prefer
> > > >#2 since I can easily indicated them all up with only one additional
> > > >ServiceChange and it seems more natural to indicate those up those that are
> > > >down.  But I can be happy with either #1 or #2.
> > >
> > >     #2 has the added (slight?) advantage that physical termination ID
> > > mis-matches (between MGC and MG) are identified when the MG sends
> > > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
> > > discovering these (non-existent) terminations 1 at a time, when connections
> > > are attempted.  With #1, a mis-match of this type might go undetected for
> > > days, until the MGC attempted to use/audit that particular termination ID.
> > >
> > >     Terminations known only to the MGC will still go "undetected", but
> > > since no SVC(restart) is ever received for them, at least the MGC would not
> > > be trying to use them.  An audit might eventually reveal the reason for the
> > > OOS terminations.  (It is not unusual in "old" voice switches to have
> > > termination data populated without having the hardware yet in place, so a
> > > mis-match cannot be considered an error in all cases.)
> > >
> > >     Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> > > interface(s) are all operational?  If it makes sense to positively assert
> > > SVC(restart) on physical terminations, why wouldn't it also make sense to
> > > indicate availability of ephemeral interfaces?  I'm thinking particularly
> > > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> > >
> > >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
> > > big burden after MG restart.  If SVC is needed for every individual
> > > physical termination, then #1 becomes attractive.
> > >
> > > Al Varney
> > >
> > > _______________________________________________
> > > Megaco mailing 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

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



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Per Annex L, 503 and 521 are not used anymore.
<p>Error Code # : 502 Name: Not ready.
<br>Definition: The command directed to a termination was not executed
because of the service state of the termination.
<br>&nbsp;
<br>&nbsp;
<p>Christer Holmberg wrote:
<blockquote TYPE=CITE>Hi,
<p>Ok, so assuming that ROOT is enough to indicate that all Terminations
are
<br>"in-service", what error code shall the MG use if the MGC tries to
use a termination
<br>which still isn't ready to be used (but WILL be in eg 10 seconds)?
503? 521?
<p>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<p>Christian Groves wrote:
<p>> G'Day Vikas,
<br>>
<br>> I believe you are getting what you asked for. The default state of
all
<br>> terminaton is "inservice".
<br>> If the MG cold starts and sends ServiceChange on "ROOT" then the
MGC can assume
<br>> that:
<br>> o as the MG is running and
<br>> o a MG contains terminations and
<br>> o the termination's natural state is "inservice"
<br>> therefore the individual terminations are running also.
<br>>
<br>> Regards, Christian
<br>>
<br>> vbajaj@hss.hns.com wrote:
<br>> >
<br>> > Al,
<br>> >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The advantage you have
cited below will hold true only under the
<br>> > assumption
<br>> >&nbsp;&nbsp; that MG sends ServiceChange for individual terminations
instead of using a
<br>> > wildcard.
<br>> >&nbsp;&nbsp; Sending ServiceChange for individual terminations would
be too expensive in
<br>> > terms
<br>> >&nbsp;&nbsp; of network bandwidth as well as MG processing for extremely
large sized
<br>> > Gateways.
<br>> >&nbsp;&nbsp; I would expect that if MGC is interested in finding
out configuration
<br>> > inconsistencies
<br>> >&nbsp;&nbsp; with its MGs, it would do an Audit at lesiure in parallel
to handling normal
<br>> > calls.
<br>> >
<br>> >&nbsp; IMHO, "ServiceChange on ROOT" should indicate all terminations
are up at the
<br>> > MG.
<br>> >&nbsp; ServiceChange for Out Of Service Terminations can be sent
subsequently. Total
<br>> > number of messages required in this scenario would be
<br>> > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
<br>> > terminations)
<br>> >
<br>> > Even if we go by approach #2 suggested below, the latter step (i.e.
sending
<br>> > ServiceChange
<br>> > for Out Of Service Terminations) will anyway have to be executed.
<br>> >&nbsp; Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded
Termination Id
<br>> > to indicate that all terminations in the MG are In Service, it
will need to send
<br>> >&nbsp; Out of Service ServiceChange for those terminations that
have been configured
<br>> >&nbsp; but not hardware equipped. The number of messages required
in this scenario
<br>> > would be
<br>> >
<br>> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id
"*"+ n
<br>> > ServiceChange
<br>> >&nbsp;&nbsp; for configured but unequipped terminations (Term Id
= "/TG!/Fac1/*))
<br>> >
<br>> > The MG may of course choose not to use a wildcarded
<br>> > termination signifiying all terminations on the MG and instead
use multiple
<br>> > ServiceChange commands each with a Termination Id (tg1/fac1/*)
that siginfies a
<br>> > DS0 aggregation. In this case, the number of ServiceChange commands
would equal
<br>> > the number of such DS0 aggregations in the MG i.e. several ServiceChange
<br>> > messages
<br>> >&nbsp; would be needed to complete the initial MG-MGC startup sequence.
The number of
<br>> >&nbsp; messages required in this scenario would be
<br>> >
<br>> > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
<br>> > terminations
<br>> >&nbsp;&nbsp;&nbsp;&nbsp; (Term Id = "/TG!/Fac1/*))
<br>> >
<br>> > {Assuming most of the terminations in MG would be In Service, n
could be a large
<br>> > value unless
<br>> >&nbsp;&nbsp; the MG is intelligent and can optimize on the number
of messages}
<br>> >
<br>> > To summarize, IMO that number of (ServiceChange) messages required
at startup
<br>> >&nbsp; would turn out to be larger in approach #2 than in approach
#1. So, why not
<br>> > choose
<br>> >&nbsp; a strategy that is optimal ?
<br>> >
<br>> > Rgds,
<br>> >
<br>> > Vikas Bajaj
<br>> > NGN Group
<br>> > Hughes Software Systems
<br>> > (www.hssworld.com)
<br>> >
<br>> > Al Varney &lt;varney@ieee.org> on 04/19/2002 04:59:53 AM
<br>> >
<br>> > To:&nbsp;&nbsp; megaco@ietf.org
<br>> > cc:&nbsp;&nbsp;&nbsp; (bcc: Vikas Bajaj/HSS)
<br>> >
<br>> > Subject:&nbsp; Re: [Megaco] ServiceChange for a single termination
(Cold&nbsp; Start)
<br>> >
<br>> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
<br>> > >Possible clarifications:
<br>> > >ServiceChange on ROOT with method=restart (a registration):
<br>> > >1) implies that all physical terminations on MG are also up.&nbsp;
Exceptions
<br>> > >should be indicated by additional ServiceChanges on the down terminations
<br>> > >using Forced, preferrably in the same message and using wildcards
where
<br>> > >possible.
<br>> > >2) implies that all physical terminations on MG are down.&nbsp;
Those that are up
<br>> > >will be indicated by additional ServiceChanges on the up terminations
using
<br>> > >method=restart, preferrably in the same message and using wildcards
were
<br>> > >possible.
<br>> >
<br>> > ...
<br>> >
<br>> > >Even though I think that most GWs probably would not register
until all or
<br>> > >most of their physical terminations are available, I would probably
prefer
<br>> > >#2 since I can easily indicated them all up with only one additional
<br>> > >ServiceChange and it seems more natural to indicate those up those
that are
<br>> > >down.&nbsp; But I can be happy with either #1 or #2.
<br>> >
<br>> >&nbsp;&nbsp;&nbsp;&nbsp; #2 has the added (slight?) advantage that
physical termination ID
<br>> > mis-matches (between MGC and MG) are identified when the MG sends
<br>> > SVC(restart) on a termination ID unknown to the MGC.&nbsp; #1 relies
on MGC
<br>> > discovering these (non-existent) terminations 1 at a time, when
connections
<br>> > are attempted.&nbsp; With #1, a mis-match of this type might go
undetected for
<br>> > days, until the MGC attempted to use/audit that particular termination
ID.
<br>> >
<br>> >&nbsp;&nbsp;&nbsp;&nbsp; Terminations known only to the MGC will
still go "undetected", but
<br>> > since no SVC(restart) is ever received for them, at least the MGC
would not
<br>> > be trying to use them.&nbsp; An audit might eventually reveal the
reason for the
<br>> > OOS terminations.&nbsp; (It is not unusual in "old" voice switches
to have
<br>> > termination data populated without having the hardware yet in place,
so a
<br>> > mis-match cannot be considered an error in all cases.)
<br>> >
<br>> >&nbsp;&nbsp;&nbsp;&nbsp; Is there an assumption that MG SVC(ROOT,restart)
implies the ephemeral
<br>> > interface(s) are all operational?&nbsp; If it makes sense to positively
assert
<br>> > SVC(restart) on physical terminations, why wouldn't it also make
sense to
<br>> > indicate availability of ephemeral interfaces?&nbsp; I'm thinking
particularly
<br>> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
<br>> >
<br>> >&nbsp;&nbsp;&nbsp;&nbsp; Assuming a reasonable SVC mechanism with
"ranges" exists, #2 is not a
<br>> > big burden after MG restart.&nbsp; If SVC is needed for every individual
<br>> > physical termination, then #1 becomes attractive.
<br>> >
<br>> > Al Varney
<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>
<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>_______________________________________________
<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>

--------------2E77CC1D7B3FAF367CA87102--


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


From daemon@ns.ietf.org  Fri Apr 19 09:46: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 JAA19797
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 09:46:49 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA10237
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 09:46:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08453;
	Fri, 19 Apr 2002 09:20:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08356
	for <megaco@optimus.ietf.org>; Fri, 19 Apr 2002 09:20:26 -0400 (EDT)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19017
	for <megaco@ietf.org>; Fri, 19 Apr 2002 09:20:18 -0400 (EDT)
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 g3JDJox01431
	for <megaco@ietf.org>; Fri, 19 Apr 2002 08:19:50 -0500 (CDT)
Received: from cls7ws1.ssd.usa.alcatel.com (cls7ws1.ssd.usa.alcatel.com [143.209.236.42])
	by ssd.usa.alcatel.com (8.11.1/8.11.1) with ESMTP id g3JDJWO01295
	for <megaco@ietf.org>; Fri, 19 Apr 2002 08:19:32 -0500 (CDT)
Received: from alcatel.com (localhost [127.0.0.1])
	by cls7ws1.ssd.usa.alcatel.com (8.9.3+Sun/8.9.1) with ESMTP id IAA03688
	for <megaco@ietf.org>; Fri, 19 Apr 2002 08:19:28 -0500 (CDT)
Message-ID: <3CC01960.5E4A4BAC@alcatel.com>
Date: Fri, 19 Apr 2002 08:19:28 -0500
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] ServiceChange for a single termination (Cold Start)
References: <65256BA0.00178569.00@sandesh.hss.hns.com> <3CBFA31E.D0FB8548@ericsson.com.au> <3CBFC502.D111C101@lmf.ericsson.se>
Content-Type: multipart/alternative;
 boundary="------------2E77CC1D7B3FAF367CA87102"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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


Per Annex L, 503 and 521 are not used anymore.

Error Code # : 502 Name: Not ready.
Definition: The command directed to a termination was not executed because of the
service state of the termination.



Christer Holmberg wrote:

> Hi,
>
> Ok, so assuming that ROOT is enough to indicate that all Terminations are
> "in-service", what error code shall the MG use if the MGC tries to use a termination
> which still isn't ready to be used (but WILL be in eg 10 seconds)? 503? 521?
>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> Christian Groves wrote:
>
> > G'Day Vikas,
> >
> > I believe you are getting what you asked for. The default state of all
> > terminaton is "inservice".
> > If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can assume
> > that:
> > o as the MG is running and
> > o a MG contains terminations and
> > o the termination's natural state is "inservice"
> > therefore the individual terminations are running also.
> >
> > Regards, Christian
> >
> > vbajaj@hss.hns.com wrote:
> > >
> > > Al,
> > >        The advantage you have cited below will hold true only under the
> > > assumption
> > >   that MG sends ServiceChange for individual terminations instead of using a
> > > wildcard.
> > >   Sending ServiceChange for individual terminations would be too expensive in
> > > terms
> > >   of network bandwidth as well as MG processing for extremely large sized
> > > Gateways.
> > >   I would expect that if MGC is interested in finding out configuration
> > > inconsistencies
> > >   with its MGs, it would do an Audit at lesiure in parallel to handling normal
> > > calls.
> > >
> > >  IMHO, "ServiceChange on ROOT" should indicate all terminations are up at the
> > > MG.
> > >  ServiceChange for Out Of Service Terminations can be sent subsequently. Total
> > > number of messages required in this scenario would be
> > > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
> > > terminations)
> > >
> > > Even if we go by approach #2 suggested below, the latter step (i.e. sending
> > > ServiceChange
> > > for Out Of Service Terminations) will anyway have to be executed.
> > >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded Termination Id
> > > to indicate that all terminations in the MG are In Service, it will need to send
> > >  Out of Service ServiceChange for those terminations that have been configured
> > >  but not hardware equipped. The number of messages required in this scenario
> > > would be
> > >
> > > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> > > ServiceChange
> > >   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
> > >
> > > The MG may of course choose not to use a wildcarded
> > > termination signifiying all terminations on the MG and instead use multiple
> > > ServiceChange commands each with a Termination Id (tg1/fac1/*) that siginfies a
> > > DS0 aggregation. In this case, the number of ServiceChange commands would equal
> > > the number of such DS0 aggregations in the MG i.e. several ServiceChange
> > > messages
> > >  would be needed to complete the initial MG-MGC startup sequence. The number of
> > >  messages required in this scenario would be
> > >
> > > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
> > > terminations
> > >     (Term Id = "/TG!/Fac1/*))
> > >
> > > {Assuming most of the terminations in MG would be In Service, n could be a large
> > > value unless
> > >   the MG is intelligent and can optimize on the number of messages}
> > >
> > > To summarize, IMO that number of (ServiceChange) messages required at startup
> > >  would turn out to be larger in approach #2 than in approach #1. So, why not
> > > choose
> > >  a strategy that is optimal ?
> > >
> > > Rgds,
> > >
> > > Vikas Bajaj
> > > NGN Group
> > > Hughes Software Systems
> > > (www.hssworld.com)
> > >
> > > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> > >
> > > To:   megaco@ietf.org
> > > cc:    (bcc: Vikas Bajaj/HSS)
> > >
> > > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)
> > >
> > > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> > > >Possible clarifications:
> > > >ServiceChange on ROOT with method=restart (a registration):
> > > >1) implies that all physical terminations on MG are also up.  Exceptions
> > > >should be indicated by additional ServiceChanges on the down terminations
> > > >using Forced, preferrably in the same message and using wildcards where
> > > >possible.
> > > >2) implies that all physical terminations on MG are down.  Those that are up
> > > >will be indicated by additional ServiceChanges on the up terminations using
> > > >method=restart, preferrably in the same message and using wildcards were
> > > >possible.
> > >
> > > ...
> > >
> > > >Even though I think that most GWs probably would not register until all or
> > > >most of their physical terminations are available, I would probably prefer
> > > >#2 since I can easily indicated them all up with only one additional
> > > >ServiceChange and it seems more natural to indicate those up those that are
> > > >down.  But I can be happy with either #1 or #2.
> > >
> > >     #2 has the added (slight?) advantage that physical termination ID
> > > mis-matches (between MGC and MG) are identified when the MG sends
> > > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
> > > discovering these (non-existent) terminations 1 at a time, when connections
> > > are attempted.  With #1, a mis-match of this type might go undetected for
> > > days, until the MGC attempted to use/audit that particular termination ID.
> > >
> > >     Terminations known only to the MGC will still go "undetected", but
> > > since no SVC(restart) is ever received for them, at least the MGC would not
> > > be trying to use them.  An audit might eventually reveal the reason for the
> > > OOS terminations.  (It is not unusual in "old" voice switches to have
> > > termination data populated without having the hardware yet in place, so a
> > > mis-match cannot be considered an error in all cases.)
> > >
> > >     Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> > > interface(s) are all operational?  If it makes sense to positively assert
> > > SVC(restart) on physical terminations, why wouldn't it also make sense to
> > > indicate availability of ephemeral interfaces?  I'm thinking particularly
> > > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> > >
> > >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
> > > big burden after MG restart.  If SVC is needed for every individual
> > > physical termination, then #1 becomes attractive.
> > >
> > > Al Varney
> > >
> > > _______________________________________________
> > > Megaco mailing 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

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



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Per Annex L, 503 and 521 are not used anymore.
<p>Error Code # : 502 Name: Not ready.
<br>Definition: The command directed to a termination was not executed
because of the service state of the termination.
<br>&nbsp;
<br>&nbsp;
<p>Christer Holmberg wrote:
<blockquote TYPE=CITE>Hi,
<p>Ok, so assuming that ROOT is enough to indicate that all Terminations
are
<br>"in-service", what error code shall the MG use if the MGC tries to
use a termination
<br>which still isn't ready to be used (but WILL be in eg 10 seconds)?
503? 521?
<p>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<p>Christian Groves wrote:
<p>> G'Day Vikas,
<br>>
<br>> I believe you are getting what you asked for. The default state of
all
<br>> terminaton is "inservice".
<br>> If the MG cold starts and sends ServiceChange on "ROOT" then the
MGC can assume
<br>> that:
<br>> o as the MG is running and
<br>> o a MG contains terminations and
<br>> o the termination's natural state is "inservice"
<br>> therefore the individual terminations are running also.
<br>>
<br>> Regards, Christian
<br>>
<br>> vbajaj@hss.hns.com wrote:
<br>> >
<br>> > Al,
<br>> >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The advantage you have
cited below will hold true only under the
<br>> > assumption
<br>> >&nbsp;&nbsp; that MG sends ServiceChange for individual terminations
instead of using a
<br>> > wildcard.
<br>> >&nbsp;&nbsp; Sending ServiceChange for individual terminations would
be too expensive in
<br>> > terms
<br>> >&nbsp;&nbsp; of network bandwidth as well as MG processing for extremely
large sized
<br>> > Gateways.
<br>> >&nbsp;&nbsp; I would expect that if MGC is interested in finding
out configuration
<br>> > inconsistencies
<br>> >&nbsp;&nbsp; with its MGs, it would do an Audit at lesiure in parallel
to handling normal
<br>> > calls.
<br>> >
<br>> >&nbsp; IMHO, "ServiceChange on ROOT" should indicate all terminations
are up at the
<br>> > MG.
<br>> >&nbsp; ServiceChange for Out Of Service Terminations can be sent
subsequently. Total
<br>> > number of messages required in this scenario would be
<br>> > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
<br>> > terminations)
<br>> >
<br>> > Even if we go by approach #2 suggested below, the latter step (i.e.
sending
<br>> > ServiceChange
<br>> > for Out Of Service Terminations) will anyway have to be executed.
<br>> >&nbsp; Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded
Termination Id
<br>> > to indicate that all terminations in the MG are In Service, it
will need to send
<br>> >&nbsp; Out of Service ServiceChange for those terminations that
have been configured
<br>> >&nbsp; but not hardware equipped. The number of messages required
in this scenario
<br>> > would be
<br>> >
<br>> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id
"*"+ n
<br>> > ServiceChange
<br>> >&nbsp;&nbsp; for configured but unequipped terminations (Term Id
= "/TG!/Fac1/*))
<br>> >
<br>> > The MG may of course choose not to use a wildcarded
<br>> > termination signifiying all terminations on the MG and instead
use multiple
<br>> > ServiceChange commands each with a Termination Id (tg1/fac1/*)
that siginfies a
<br>> > DS0 aggregation. In this case, the number of ServiceChange commands
would equal
<br>> > the number of such DS0 aggregations in the MG i.e. several ServiceChange
<br>> > messages
<br>> >&nbsp; would be needed to complete the initial MG-MGC startup sequence.
The number of
<br>> >&nbsp; messages required in this scenario would be
<br>> >
<br>> > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
<br>> > terminations
<br>> >&nbsp;&nbsp;&nbsp;&nbsp; (Term Id = "/TG!/Fac1/*))
<br>> >
<br>> > {Assuming most of the terminations in MG would be In Service, n
could be a large
<br>> > value unless
<br>> >&nbsp;&nbsp; the MG is intelligent and can optimize on the number
of messages}
<br>> >
<br>> > To summarize, IMO that number of (ServiceChange) messages required
at startup
<br>> >&nbsp; would turn out to be larger in approach #2 than in approach
#1. So, why not
<br>> > choose
<br>> >&nbsp; a strategy that is optimal ?
<br>> >
<br>> > Rgds,
<br>> >
<br>> > Vikas Bajaj
<br>> > NGN Group
<br>> > Hughes Software Systems
<br>> > (www.hssworld.com)
<br>> >
<br>> > Al Varney &lt;varney@ieee.org> on 04/19/2002 04:59:53 AM
<br>> >
<br>> > To:&nbsp;&nbsp; megaco@ietf.org
<br>> > cc:&nbsp;&nbsp;&nbsp; (bcc: Vikas Bajaj/HSS)
<br>> >
<br>> > Subject:&nbsp; Re: [Megaco] ServiceChange for a single termination
(Cold&nbsp; Start)
<br>> >
<br>> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
<br>> > >Possible clarifications:
<br>> > >ServiceChange on ROOT with method=restart (a registration):
<br>> > >1) implies that all physical terminations on MG are also up.&nbsp;
Exceptions
<br>> > >should be indicated by additional ServiceChanges on the down terminations
<br>> > >using Forced, preferrably in the same message and using wildcards
where
<br>> > >possible.
<br>> > >2) implies that all physical terminations on MG are down.&nbsp;
Those that are up
<br>> > >will be indicated by additional ServiceChanges on the up terminations
using
<br>> > >method=restart, preferrably in the same message and using wildcards
were
<br>> > >possible.
<br>> >
<br>> > ...
<br>> >
<br>> > >Even though I think that most GWs probably would not register
until all or
<br>> > >most of their physical terminations are available, I would probably
prefer
<br>> > >#2 since I can easily indicated them all up with only one additional
<br>> > >ServiceChange and it seems more natural to indicate those up those
that are
<br>> > >down.&nbsp; But I can be happy with either #1 or #2.
<br>> >
<br>> >&nbsp;&nbsp;&nbsp;&nbsp; #2 has the added (slight?) advantage that
physical termination ID
<br>> > mis-matches (between MGC and MG) are identified when the MG sends
<br>> > SVC(restart) on a termination ID unknown to the MGC.&nbsp; #1 relies
on MGC
<br>> > discovering these (non-existent) terminations 1 at a time, when
connections
<br>> > are attempted.&nbsp; With #1, a mis-match of this type might go
undetected for
<br>> > days, until the MGC attempted to use/audit that particular termination
ID.
<br>> >
<br>> >&nbsp;&nbsp;&nbsp;&nbsp; Terminations known only to the MGC will
still go "undetected", but
<br>> > since no SVC(restart) is ever received for them, at least the MGC
would not
<br>> > be trying to use them.&nbsp; An audit might eventually reveal the
reason for the
<br>> > OOS terminations.&nbsp; (It is not unusual in "old" voice switches
to have
<br>> > termination data populated without having the hardware yet in place,
so a
<br>> > mis-match cannot be considered an error in all cases.)
<br>> >
<br>> >&nbsp;&nbsp;&nbsp;&nbsp; Is there an assumption that MG SVC(ROOT,restart)
implies the ephemeral
<br>> > interface(s) are all operational?&nbsp; If it makes sense to positively
assert
<br>> > SVC(restart) on physical terminations, why wouldn't it also make
sense to
<br>> > indicate availability of ephemeral interfaces?&nbsp; I'm thinking
particularly
<br>> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
<br>> >
<br>> >&nbsp;&nbsp;&nbsp;&nbsp; Assuming a reasonable SVC mechanism with
"ranges" exists, #2 is not a
<br>> > big burden after MG restart.&nbsp; If SVC is needed for every individual
<br>> > physical termination, then #1 becomes attractive.
<br>> >
<br>> > Al Varney
<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>
<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>_______________________________________________
<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>

--------------2E77CC1D7B3FAF367CA87102--


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



From megaco-admin@ietf.org  Fri Apr 19 11:46: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 LAA24393
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 11:46:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18448;
	Fri, 19 Apr 2002 11:22:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18417
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 11:22:42 -0400 (EDT)
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 LAA23413
	for <megaco@ietf.org>; Fri, 19 Apr 2002 11:22:39 -0400 (EDT)
Received: from varneyhome.ieee.org ([12.84.123.150])
          by mtiwmhc22.worldnet.att.net
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020419152210.CSAP28991.mtiwmhc22.worldnet.att.net@varneyhome.ieee.org>;
          Fri, 19 Apr 2002 15:22:10 +0000
Message-Id: <4.3.2.7.2.20020419094935.00b64100@postoffice.worldnet.att.net>
X-Sender: a.varney@postoffice.worldnet.att.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 19 Apr 2002 10:22:04 -0500
To: vbajaj@hss.hns.com
From: Al Varney <varney@ieee.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
  Start)
Cc: megaco@ietf.org
In-Reply-To: <65256BA0.00178569.00@sandesh.hss.hns.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:49 AM 4/19/02 +0530, vbajaj@hss.hns.com wrote:
>Al,
>        The advantage you have cited below will hold true only under the
>assumption
>   that MG sends ServiceChange for individual terminations instead of using a
>wildcard.

    I have no preference for #1 vs. #2.  I was just pointing out a 
potential advantage of #2.  I was assuming ServiceChange with "ranges" 
identifying only in-service terminations would be used, never a "*" 
wildcard.  If the protocol adopted #2, "*" would obviously loose the 
explicit termination verification at the MGC.

>   I would expect that if MGC is interested in finding out configuration
>inconsistencies
>   with its MGs, it would do an Audit at lesiure in parallel to handling 
> normal
>calls.

    It may happen that a "normal call" could encounter an unusable 
termination prior to the leisurely audit.  Since an MGC has to be prepared 
to handle this case anyway, using approach #1 is certainly simpler for both 
MGC and MG.  But will it meet requirements of applications?

>To summarize, IMO that number of (ServiceChange) messages required at startup
>  would turn out to be larger in approach #2 than in approach #1. So, why not
>choose a strategy that is optimal ?

    I agree, the goal is an optimal strategy.  If service provider 
performance requirements heavily penalize connection attempts to OOS 
terminations, then approach #2 is optimal because it allows the MGC to 
start using known-in-service terminations as soon as possible, while 
avoiding failing attempts.  With approach #1, such performance requirements 
would force an MGC to audit terminations before attempting to use them -- 
less optimal than #2, right?

    If the performance requirements are heavily weighted toward reducing 
"down-time" after an MG restart (ignoring how many initial connections 
might fail), then approach #1 is obviously optimal.

    An unfortunate side-effect of doing only protocol development, rather 
than services development, is that we don't know the requirements of the 
service providers.  An optimal strategy for the protocol may be non-optimal 
for the application.

Al Varney


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


From daemon@ns.ietf.org  Fri Apr 19 11:46: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 LAA24404
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 11:46:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA20270
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 11:46:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18448;
	Fri, 19 Apr 2002 11:22:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18417
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 11:22:42 -0400 (EDT)
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 LAA23413
	for <megaco@ietf.org>; Fri, 19 Apr 2002 11:22:39 -0400 (EDT)
Received: from varneyhome.ieee.org ([12.84.123.150])
          by mtiwmhc22.worldnet.att.net
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020419152210.CSAP28991.mtiwmhc22.worldnet.att.net@varneyhome.ieee.org>;
          Fri, 19 Apr 2002 15:22:10 +0000
Message-Id: <4.3.2.7.2.20020419094935.00b64100@postoffice.worldnet.att.net>
X-Sender: a.varney@postoffice.worldnet.att.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 19 Apr 2002 10:22:04 -0500
To: vbajaj@hss.hns.com
From: Al Varney <varney@ieee.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
  Start)
Cc: megaco@ietf.org
In-Reply-To: <65256BA0.00178569.00@sandesh.hss.hns.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:49 AM 4/19/02 +0530, vbajaj@hss.hns.com wrote:
>Al,
>        The advantage you have cited below will hold true only under the
>assumption
>   that MG sends ServiceChange for individual terminations instead of using a
>wildcard.

    I have no preference for #1 vs. #2.  I was just pointing out a 
potential advantage of #2.  I was assuming ServiceChange with "ranges" 
identifying only in-service terminations would be used, never a "*" 
wildcard.  If the protocol adopted #2, "*" would obviously loose the 
explicit termination verification at the MGC.

>   I would expect that if MGC is interested in finding out configuration
>inconsistencies
>   with its MGs, it would do an Audit at lesiure in parallel to handling 
> normal
>calls.

    It may happen that a "normal call" could encounter an unusable 
termination prior to the leisurely audit.  Since an MGC has to be prepared 
to handle this case anyway, using approach #1 is certainly simpler for both 
MGC and MG.  But will it meet requirements of applications?

>To summarize, IMO that number of (ServiceChange) messages required at startup
>  would turn out to be larger in approach #2 than in approach #1. So, why not
>choose a strategy that is optimal ?

    I agree, the goal is an optimal strategy.  If service provider 
performance requirements heavily penalize connection attempts to OOS 
terminations, then approach #2 is optimal because it allows the MGC to 
start using known-in-service terminations as soon as possible, while 
avoiding failing attempts.  With approach #1, such performance requirements 
would force an MGC to audit terminations before attempting to use them -- 
less optimal than #2, right?

    If the performance requirements are heavily weighted toward reducing 
"down-time" after an MG restart (ignoring how many initial connections 
might fail), then approach #1 is obviously optimal.

    An unfortunate side-effect of doing only protocol development, rather 
than services development, is that we don't know the requirements of the 
service providers.  An optimal strategy for the protocol may be non-optimal 
for the application.

Al Varney


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



From megaco-admin@ietf.org  Fri Apr 19 11:51: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 LAA24673
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 11:51:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17970;
	Fri, 19 Apr 2002 11:17:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18786
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 03:23:42 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12426
	for <megaco@ietf.org>; Fri, 19 Apr 2002 03:23:35 -0400 (EDT)
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 g3J7N3Y11483;
	Fri, 19 Apr 2002 09:23:03 +0200 (MEST)
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 JAA20531;
	Fri, 19 Apr 2002 09:22:50 +0200 (MET DST)
Message-ID: <3CBFC3DD.F3DBA052@alcatel.es>
Date: Fri, 19 Apr 2002 09:14:37 +0200
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: Christer Holmberg <christer.holmberg@lmf.ericsson.se>,
        Megaco <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <000801c1e6e1$18dc85e0$368910ac@Bala> <3CBF147D.D7A28C57@lucent.com> <3CBF9FB3.9208F958@lmf.ericsson.se>
Content-Type: multipart/alternative;
 boundary="------------68BD87654B52B6166157A630"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


--------------68BD87654B52B6166157A630
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,

As you have said in previous emails the pstn gateways from
the old point of view of switching may have different boards
with different terminations. And the may start up in a lapse of
seconds...
IMO I would wait for all to restart before sending a SVC (Restart).
In the best case no more messages will be sent, we can suppose
tha a faulty termination is not the normal case.
Another thing is that we may not be able to use wildcards... this
implies a message per termination.
I would prefer option 1)


Fernando Vallejo
Alcatel Spain

Christer Holmberg wrote:

> Hi,
>
> Opton 1) vs 2) is what we have been discussing in this thread so far, and I
> would prefear option 2).
>
> I don't think option 3) - it would just be a compromise, since we couldn't agree
> on something else :)
>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> Terry L Anderson wrote:
>
> > I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes no
> > statement one way or the other) and it is apparent that there is not
> > agreement on what we want.  I believe that there are three possible
> > positions and that we should clarify this through the IG once we agree.
> >
> > Possible clarifications:
> > ServiceChange on ROOT with method=restart (a registration):
> > 1) implies that all physical terminations on MG are also up.  Exceptions
> > should be indicated by additional ServiceChanges on the down terminations
> > using Forced, preferrably in the same message and using wildcards where
> > possible.
> > 2) implies that all physical terminations on MG are down.  Those that are up
> > will be indicated by additional ServiceChanges on the up terminations using
> > method=restart, preferrably in the same message and using wildcards were
> > possible.
> > 3) has no implication whether physical terminations are up or down, but MGC
> > may be provisioned to know whether an MG will indicate terminations that are
> > up or those that are down.
> >
> > I should say that I do not like #3 but am including it as a possibility.
> >
> > Preference for #1 or #2 probably depend on:
> > 1) whether most physical terminations are available almost immediately or
> > come up slowly and at different speeds.
> > 2) whether MGC is provisioned with knowledge about the available physical
> > terminations on an MG or expects to learn about them through ServiceChanges
> > or Audits
> >
> > Note that #1 can be implemented from #2 by adding:
> >     ServiceChange = *{Services{Method=Restart}}
> > to the action, and conversely #2 can be implemented from #1 by adding:
> >     ServiceChange = *{Services{Method=Forced}}
> >
> > In either case exceptions (up or down) to the ALL can be indicated by
> > additional ServiceChange commands.
> >
> > So (IMHO) it doesn't seem too critical which we choose, but we should choose
> > and document one.
> >
> > Even though I think that most GWs probably would not register until all or
> > most of their physical terminations are available, I would probably prefer
> > #2 since I can easily indicated them all up with only one additional
> > ServiceChange and it seems more natural to indicate those up those that are
> > down.  But I can be happy with either #1 or #2.
> >
> > What do folks prefer?
> >
> > Balasubramanian Pitchandi wrote:
> >
> > > Hi,
> > >
> > > I agree with Christer's views.
> > >
> > > If MG sends a ServiceChange 'ROOT', it only means that the gateway is in
> > > or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). The
> > > protocol is very clear on this, I think.
> > >
> > > Given that -- SVC(ROOT) means that the gateway is up -- now there are
> > > many ways MGC could come to know of what terminations are in service:
> > >
> > > 1. MG sends ServiceChange for all the terminations that are in service
> > > individually (If there are large number of terminations, the MG could
> > > use *ranges* of TerminationIds(?) to limit the number of such messages)
> > >
> > > 2. MGC could audit the MG for the list of terminations that are in
> > > service in which case the MG returns the list of terminations that are
> > > in service.
> > >
> > > But clearly sending a ServiceChange('ROOT') does not mean that all the
> > > terminations in the MG are in service. This presents lot of operational
> > > problems as Christer pointed out.
> > >
> > > -- Bala
> > >
> > > __________________
> > > Bala Pitchandi
> > > UTStarcom Inc.
> > >
> > > -----Original Message-----
> > > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> > > SRD Wang JuLin
> > > Sent: Thursday, April 18, 2002 2:52 AM
> > > To: Christer Holmberg
> > > Cc: Barcotti, Glauco; megaco@ietf.org
> > > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > > Start)
> > >
> > > Hi,
> > > Well,I think MGC should send Modify messages (the number of it equals to
> > > the number of terminations in RGW,I only refer to Residential GW) to
> > > check the terminations's events  after MG reboot with Cold Start as a
> > > whole entity. All terminations will start up.In case of some
> > > terminations fail to use,of course,we should send SC for definite
> > > invalid termination with restored method  to Softswtich. Before you WANT
> > > to use a termination,you should know whether it is ABLE to use (ie.in
> > > service or out of  service).
> > >
> > > best  regards
> > > > :-)Jerry Wang
> > > tel:(8621)58541240 ext 9615
> > > mailto:wangjl2@sbell.com.cn
> > > Shanghai Bell Co.LTD
> > >
> > > -----Original Message-----
> > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > Sent: Thursday, April 18, 2002 2:27 PM
> > > To: SRD Wang JuLin
> > > Cc: Barcotti, Glauco; megaco@ietf.org
> > > Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> > > Start)
> > >
> > > Hi,
> > >
> > > So, you want me to send a MODIFY to each of the THOUSANDS of
> > > terminations I may want to use????
> > >
> > > And, the issue is not which termination I WANT to use (ie which I want
> > > the MGC to "enable" in the MG), but which termination I am ABLE (ie
> > > which termination has at a certain time been booted/loaded/whatevver) to
> > > use...
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > SRD Wang JuLin wrote:
> > >
> > > > Hi,
> > > > Well,I send the ServiceChange for Root to Softswitch,it only send 4
> > > > modify messages  to RGW.So i can only use 4 out of the 8 phones
> > > > located in RGW. (I had provisioned 8 terminations into Softswitch
> > > >
> > > > )
> > > > 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
> > > >                          4500 008e 028b 0000 3f11 63de 0a0a 007a
> > > >                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
> > > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > > >                          7b4d 543d 5253 2c52 453d 3930 312c 4144
> > > >                          3d31 3131 3232 2c50 463d 416e 616c 6f67
> > > >                          5f4c 696e 655f 496e 7465 726f 7065 7261
> > > >                          6269 6c69 7479 5f54 6573 745f 5072 6f66
> > > >                          696c 652f 312c 563d 317d 7d7d 7d0a
> > > >
> > > >                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
> > > >                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
> > > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > > >                           { M  T =  R S  , R  E =  9 0  1 ,  A D
> > > >                           = 1  1 1  2 2  , P  F =  A n  a l  o g
> > > >                           _ L  i n  e _  I n  t e  r o  p e  r a
> > > >                           b i  l i  t y  _ T  e s  t _  P r  o f
> > > >                           i l  e /  1 ,  V =  1 }  } }  }^J
> > > > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
> > > >                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
> > > >                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
> > > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > > >                          7b41 443d 3131 3132 322c 5046 3d43 4c53
> > > >                          2f31 2c56 3d31 7d7d 7d7d
> > > >
> > > >                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
> > > >                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
> > > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > > >                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
> > > >                           / 1  , V  = 1  } }  } } 16:46:18.325927 eth0
> > >
> > > > > coco2.11122 > 10.10.0.122.11122: udp 164
> > > >                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
> > > >                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 327b 453d 3538 3938 3239 7b61
> > > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > > >
> > > >                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
> > > >                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
> > > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > > >                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
> > > >                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > > >                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 337b 453d 3538 3938 3239 7b61
> > > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > > >
> > > >                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
> > > >                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > > >                           4 2  1 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
> > > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > > >                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
> > > >                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 357b 453d 3538 3938 3239 7b61
> > > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > > >
> > > >                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
> > > >                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
> > > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > > >                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
> > > >                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > > >                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 367b 453d 3538 3938 3239 7b61
> > > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > > >
> > > >                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
> > > >                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > > >                           4 2  3 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
> > > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > > 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > > >                          4500 0062 0293 0000 3f11 6402 0a0a 007a
> > > >                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 327d 7d0a 503d 3432 317b 433d
> > > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
> > > >                          7d0a
> > > >
> > > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
> > > >                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
> > > >                           - {  M F  = a  g w  _ j  u l  w /  3 }
> > > >                           }^J
> > > > 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > > >                          4500 0062 0294 0000 3f11 6401 0a0a 007a
> > > >                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 357d 7d0a 503d 3432 337b 433d
> > > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
> > > >                          7d0a
> > > >
> > > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
> > > >                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
> > > >                           - {  M F  = a  g w  _ j  u l  w /  6 }
> > > >                           }^J
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > best  regards
> > > > > :-)Jerry Wang
> > > > tel:(8621)58541240 ext 9615
> > > > mailto:wangjl2@sbell.com.cn
> > > > Shanghai Bell Co.LTD
> > > >
> > > > -----Original Message-----
> > > > From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> > > > Sent: Wednesday, April 17, 2002 10:10 PM
> > > > To: 'Christer Holmberg'
> > > > Cc: 'megaco@ietf.org'
> > > > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > > > Start)
> > > >
> > > > Hi,
> > > >
> > > > >>         Assuming a Gateway with 2 terminations, one of >them is OK
> > > > >> and the other is Malfunctioning. How should I >proceed if I want to
> > >
> > > > >> bring just the working termination >up (Cold Start)?
> > > > >>
> > > > >> a) If a ServiceChange is issued for ROOT termination MGC will think
> > >
> > > > >> that all terminations are up and, until another ServiceChange is
> > > > >> issued taking the defective Termination out of service, a call
> > > > >> could be attempted on that defective termination
> > > >
> > > > >I don't agree. A ServiceChange for ROOT will indicate that the MG is
> > > > >up, not specific terminations. You would then have to send additonal
> > > > >ServiceChange commands, with Reason code 900, for each termination
> > > > >you want to put in-service.
> > > >
> > > > The example in the spec (Appendix A) and the
> > > > draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT
> > > > on a ServiceChange all terminations are addressed (One ServiceChange
> > > > ROOT is sent and the terminations are available to use). Where did you
> > >
> > > > find information about ServiceChange ROOT not bringing all
> > > > terminations up?
> > > >
> > > > Thanks,
> > > > Glauco
> > > >
> > > > >Regards,
> > > >
> > > > >hrister Holmberg
> > > > >ricsson Finland
> > > >
> > > > >
> > > > >
> > > > > b) If a ServiceChange is issued just for the working Termination The
> > >
> > > > > ability to redirect the gateway to another MGC will be lost (See
> > > > > quotation from spec below)
> > > > >
> > > > > "The return from ServiceChange is empty except when the Root
> > > > > terminationID is used.  In that case it includes the following
> > > > > parameters as required:"
> > > > >
> > > > > Thanks,
> > > > > Glauco
> > > > >
> > > > > _______________________________________________
> > > > > Megaco mailing 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
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson             mailto:tla@lucent.com
> > Tel:732.949.5628   Fax:732.949.7016
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > 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

--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi,
<p>As you have said in previous emails the pstn gateways from
<br>the old point of view of switching may have different boards
<br>with different terminations. And the may start up in a lapse of
<br>seconds...
<br>IMO I would wait for all to restart before sending a SVC&nbsp;(Restart).
<br>In the best case no more messages will be sent, we can suppose
<br>tha a faulty termination is not the normal case.
<br>Another thing is that we may not be able to use wildcards... this
<br>implies a message per termination.
<br>I would prefer option 1)
<br>&nbsp;
<p>Fernando Vallejo
<br>Alcatel Spain
<p>Christer Holmberg wrote:
<blockquote TYPE=CITE>Hi,
<p>Opton 1) vs 2) is what we have been discussing in this thread so far,
and I
<br>would prefear option 2).
<p>I don't think option 3) - it would just be a compromise, since we couldn't
agree
<br>on something else :)
<p>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<p>Terry L Anderson wrote:
<p>> I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes
no
<br>> statement one way or the other) and it is apparent that there is
not
<br>> agreement on what we want.&nbsp; I believe that there are three possible
<br>> positions and that we should clarify this through the IG once we
agree.
<br>>
<br>> Possible clarifications:
<br>> ServiceChange on ROOT with method=restart (a registration):
<br>> 1) implies that all physical terminations on MG are also up.&nbsp;
Exceptions
<br>> should be indicated by additional ServiceChanges on the down terminations
<br>> using Forced, preferrably in the same message and using wildcards
where
<br>> possible.
<br>> 2) implies that all physical terminations on MG are down.&nbsp; Those
that are up
<br>> will be indicated by additional ServiceChanges on the up terminations
using
<br>> method=restart, preferrably in the same message and using wildcards
were
<br>> possible.
<br>> 3) has no implication whether physical terminations are up or down,
but MGC
<br>> may be provisioned to know whether an MG will indicate terminations
that are
<br>> up or those that are down.
<br>>
<br>> I should say that I do not like #3 but am including it as a possibility.
<br>>
<br>> Preference for #1 or #2 probably depend on:
<br>> 1) whether most physical terminations are available almost immediately
or
<br>> come up slowly and at different speeds.
<br>> 2) whether MGC is provisioned with knowledge about the available
physical
<br>> terminations on an MG or expects to learn about them through ServiceChanges
<br>> or Audits
<br>>
<br>> Note that #1 can be implemented from #2 by adding:
<br>>&nbsp;&nbsp;&nbsp;&nbsp; ServiceChange = *{Services{Method=Restart}}
<br>> to the action, and conversely #2 can be implemented from #1 by adding:
<br>>&nbsp;&nbsp;&nbsp;&nbsp; ServiceChange = *{Services{Method=Forced}}
<br>>
<br>> In either case exceptions (up or down) to the ALL can be indicated
by
<br>> additional ServiceChange commands.
<br>>
<br>> So (IMHO) it doesn't seem too critical which we choose, but we should
choose
<br>> and document one.
<br>>
<br>> Even though I think that most GWs probably would not register until
all or
<br>> most of their physical terminations are available, I would probably
prefer
<br>> #2 since I can easily indicated them all up with only one additional
<br>> ServiceChange and it seems more natural to indicate those up those
that are
<br>> down.&nbsp; But I can be happy with either #1 or #2.
<br>>
<br>> What do folks prefer?
<br>>
<br>> Balasubramanian Pitchandi wrote:
<br>>
<br>> > Hi,
<br>> >
<br>> > I agree with Christer's views.
<br>> >
<br>> > If MG sends a ServiceChange 'ROOT', it only means that the gateway
is in
<br>> > or out of service (Refer to Section 6.2.5 &amp; 7.2.8 of the RFC3015).
The
<br>> > protocol is very clear on this, I think.
<br>> >
<br>> > Given that -- SVC(ROOT) means that the gateway is up -- now there
are
<br>> > many ways MGC could come to know of what terminations are in service:
<br>> >
<br>> > 1. MG sends ServiceChange for all the terminations that are in
service
<br>> > individually (If there are large number of terminations, the MG
could
<br>> > use *ranges* of TerminationIds(?) to limit the number of such messages)
<br>> >
<br>> > 2. MGC could audit the MG for the list of terminations that are
in
<br>> > service in which case the MG returns the list of terminations that
are
<br>> > in service.
<br>> >
<br>> > But clearly sending a ServiceChange('ROOT') does not mean that
all the
<br>> > terminations in the MG are in service. This presents lot of operational
<br>> > problems as Christer pointed out.
<br>> >
<br>> > -- Bala
<br>> >
<br>> > __________________
<br>> > Bala Pitchandi
<br>> > UTStarcom Inc.
<br>> >
<br>> > -----Original Message-----
<br>> > From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]
On Behalf Of
<br>> > SRD Wang JuLin
<br>> > Sent: Thursday, April 18, 2002 2:52 AM
<br>> > To: Christer Holmberg
<br>> > Cc: Barcotti, Glauco; megaco@ietf.org
<br>> > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
<br>> > Start)
<br>> >
<br>> > Hi,
<br>> > Well,I think MGC should send Modify messages (the number of it
equals to
<br>> > the number of terminations in RGW,I only refer to Residential GW)
to
<br>> > check the terminations's events&nbsp; after MG reboot with Cold
Start as a
<br>> > whole entity. All terminations will start up.In case of some
<br>> > terminations fail to use,of course,we should send SC for definite
<br>> > invalid termination with restored method&nbsp; to Softswtich. Before
you WANT
<br>> > to use a termination,you should know whether it is ABLE to use
(ie.in
<br>> > service or out of&nbsp; service).
<br>> >
<br>> > best&nbsp; regards
<br>> > > :-)Jerry Wang
<br>> > tel:(8621)58541240 ext 9615
<br>> > <a href="mailto:wangjl2@sbell.com.cn">mailto:wangjl2@sbell.com.cn</a>
<br>> > Shanghai Bell Co.LTD
<br>> >
<br>> > -----Original Message-----
<br>> > From: Christer Holmberg [<a href="mailto:christer.holmberg@lmf.ericsson.se">mailto:christer.holmberg@lmf.ericsson.se</a>]
<br>> > Sent: Thursday, April 18, 2002 2:27 PM
<br>> > To: SRD Wang JuLin
<br>> > Cc: Barcotti, Glauco; megaco@ietf.org
<br>> > Subject: Re: [Megaco] ServiceChange for a single termination (Cold
<br>> > Start)
<br>> >
<br>> > Hi,
<br>> >
<br>> > So, you want me to send a MODIFY to each of the THOUSANDS of
<br>> > terminations I may want to use????
<br>> >
<br>> > And, the issue is not which termination I WANT to use (ie which
I want
<br>> > the MGC to "enable" in the MG), but which termination I am ABLE
(ie
<br>> > which termination has at a certain time been booted/loaded/whatevver)
to
<br>> > use...
<br>> >
<br>> > Regards,
<br>> >
<br>> > Christer Holmberg
<br>> > Ericsson Finland
<br>> >
<br>> > SRD Wang JuLin wrote:
<br>> >
<br>> > > Hi,
<br>> > > Well,I send the ServiceChange for Root to Softswitch,it only
send 4
<br>> > > modify messages&nbsp; to RGW.So i can only use 4 out of the 8
phones
<br>> > > located in RGW. (I had provisioned 8 terminations into Softswitch
<br>> > >
<br>> > > )
<br>> > > 16:46:17.873046 eth0 &lt; 10.10.0.122.11122 > coco2.2944: udp
114
<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;
4500 008e 028b 0000 3f11 63de 0a0a 007a
<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;
0a0a 0069 2b72 0b80 007a d67f 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3232 5d0a 543d
<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;
317b 433d 2d7b 5343 3d52 4f4f 547b 5356
<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;
7b4d 543d 5253 2c52 453d 3930 312c 4144
<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;
3d31 3131 3232 2c50 463d 416e 616c 6f67
<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;
5f4c 696e 655f 496e 7465 726f 7065 7261
<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;
6269 6c69 7479 5f54 6573 745f 5072 6f66
<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;
696c 652f 312c 563d 317d 7d7d 7d0a
<br>> > >
<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;
E^@ ^@.. ^B.. ^@^@&nbsp; ?^Q&nbsp; c.. ^J^J ^@ z
<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;
^J^J ^@ i&nbsp; + r ^K.. ^@ z ..^? ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 2 2&nbsp; ]^J&nbsp; T
=
<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;
1 {&nbsp; C =&nbsp; - {&nbsp; S C&nbsp; = R&nbsp; O O&nbsp; T {&nbsp; S
V
<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;
{ M&nbsp; T =&nbsp; R S&nbsp; , R&nbsp; E =&nbsp; 9 0&nbsp; 1 ,&nbsp; A
D
<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;
= 1&nbsp; 1 1&nbsp; 2 2&nbsp; , P&nbsp; F =&nbsp; A n&nbsp; a l&nbsp; o
g
<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;
_ L&nbsp; i n&nbsp; e _&nbsp; I n&nbsp; t e&nbsp; r o&nbsp; p e&nbsp; r
a
<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;
b i&nbsp; l i&nbsp; t y&nbsp; _ T&nbsp; e s&nbsp; t _&nbsp; P r&nbsp; o
f
<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;
i l&nbsp; e /&nbsp; 1 ,&nbsp; V =&nbsp; 1 }&nbsp; } }&nbsp; }^J
<br>> > > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
<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;
4500 005a 2bdf 0000 4011 39be 0a0a 0069
<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;
0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3035 5d20 503d
<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;
317b 433d 2d7b 5343 3d52 4f4f 547b 5356
<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;
7b41 443d 3131 3132 322c 5046 3d43 4c53
<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;
2f31 2c56 3d31 7d7d 7d7d
<br>> > >
<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;
E^@ ^@ Z&nbsp; +.. ^@^@&nbsp; @^Q&nbsp; 9.. ^J^J ^@ i
<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;
^J^J ^@ z ^K..&nbsp; + r ^@ F ^&ccedil;&cedil;(tm)]&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 0 5&nbsp; ]&nbsp;&nbsp;&nbsp;
P =
<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;
1 {&nbsp; C =&nbsp; - {&nbsp; S C&nbsp; = R&nbsp; O O&nbsp; T {&nbsp; S
V
<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;
{ A&nbsp; D =&nbsp; 1 1&nbsp; 1 2&nbsp; 2 ,&nbsp; P F&nbsp; = C&nbsp; L
S
<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;
/ 1&nbsp; , V&nbsp; = 1&nbsp; } }&nbsp; } } 16:46:18.325927 eth0
<br>> >
<br>> > > > coco2.11122 > 10.10.0.122.11122: udp 164
<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;
4500 00c0 2bf3 0000 4011 3944 0a0a 0069
<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;
0a0a 007a 2b72 2b72 00ac 1537 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3035 5d20 543d
<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;
3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 327b 453d 3538 3938 3239 7b61
<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;
6c2f 6f66 7b73 7472 6963 743d 6578 6163
<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;
742c 454d 7b53 477b 6367 2f64 747d 2c45
<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;
3d33 3933 3231 377b 6464 2f63 657b 2044
<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;
4d3d 6469 616c 706c 616e 317d 2c61 6c2f
<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;
6f6e 7b73 7472 6963 743d 6578 6163 747d
<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;
2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
<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;
7472 6963 743d 6578 6163 747d 7d7d 7d7d
<br>> > >
<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;
E^@ ^@..&nbsp; +.. ^@^@&nbsp; @^Q&nbsp; 9 D ^J^J ^@ i
<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;
^J^J ^@ z&nbsp; + r&nbsp; + r ^@.. ^U 7&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 0 5&nbsp; ]&nbsp;&nbsp;&nbsp;
T =
<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;
4 2&nbsp; 0 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 2 {&nbsp; E =&nbsp; 5 8&nbsp; 9 8&nbsp; 2 9&nbsp; {
a
<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;
l /&nbsp; o f&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a
c
<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;
t ,&nbsp; E M&nbsp; { S&nbsp; G {&nbsp; c g&nbsp; / d&nbsp; t }&nbsp; ,
E
<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;
= 3&nbsp; 9 3&nbsp; 2 1&nbsp; 7 {&nbsp; d d&nbsp; / c&nbsp; e {&nbsp;&nbsp;&nbsp;
D
<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;
M =&nbsp; d i&nbsp; a l&nbsp; p l&nbsp; a n&nbsp; 1 }&nbsp; , a&nbsp; l
/
<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;
o n&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t
}
<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;
, g&nbsp; / s&nbsp; c }&nbsp; } }&nbsp; , a&nbsp; l /&nbsp; o n&nbsp; {
s
<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;
t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t }&nbsp; } }&nbsp; }
}
<br>> > > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
<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;
4500 00c0 2bf9 0000 4011 393e 0a0a 0069
<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;
0a0a 007a 2b72 2b72 00ac 1337 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3035 5d20 543d
<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;
3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 337b 453d 3538 3938 3239 7b61
<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;
6c2f 6f66 7b73 7472 6963 743d 6578 6163
<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;
742c 454d 7b53 477b 6367 2f64 747d 2c45
<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;
3d33 3933 3231 377b 6464 2f63 657b 2044
<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;
4d3d 6469 616c 706c 616e 317d 2c61 6c2f
<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;
6f6e 7b73 7472 6963 743d 6578 6163 747d
<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;
2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
<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;
7472 6963 743d 6578 6163 747d 7d7d 7d7d
<br>> > >
<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;
E^@ ^@..&nbsp; +.. ^@^@&nbsp; @^Q&nbsp; 9 > ^J^J ^@ i
<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;
^J^J ^@ z&nbsp; + r&nbsp; + r ^@.. ^S 7&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 0 5&nbsp; ]&nbsp;&nbsp;&nbsp;
T =
<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;
4 2&nbsp; 1 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 3 {&nbsp; E =&nbsp; 5 8&nbsp; 9 8&nbsp; 2 9&nbsp; {
a
<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;
l /&nbsp; o f&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a
c
<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;
t ,&nbsp; E M&nbsp; { S&nbsp; G {&nbsp; c g&nbsp; / d&nbsp; t }&nbsp; ,
E
<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;
= 3&nbsp; 9 3&nbsp; 2 1&nbsp; 7 {&nbsp; d d&nbsp; / c&nbsp; e {&nbsp;&nbsp;&nbsp;
D
<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;
M =&nbsp; d i&nbsp; a l&nbsp; p l&nbsp; a n&nbsp; 1 }&nbsp; , a&nbsp; l
/
<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;
o n&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t
}
<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;
, g&nbsp; / s&nbsp; c }&nbsp; } }&nbsp; , a&nbsp; l /&nbsp; o n&nbsp; {
s
<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;
t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t }&nbsp; } }&nbsp; }
}
<br>> > > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
<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;
4500 00c0 2c01 0000 4011 3936 0a0a 0069
<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;
0a0a 007a 2b72 2b72 00ac 1037 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3035 5d20 543d
<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;
3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 357b 453d 3538 3938 3239 7b61
<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;
6c2f 6f66 7b73 7472 6963 743d 6578 6163
<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;
742c 454d 7b53 477b 6367 2f64 747d 2c45
<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;
3d33 3933 3231 377b 6464 2f63 657b 2044
<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;
4d3d 6469 616c 706c 616e 317d 2c61 6c2f
<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;
6f6e 7b73 7472 6963 743d 6578 6163 747d
<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;
2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
<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;
7472 6963 743d 6578 6163 747d 7d7d 7d7d
<br>> > >
<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;
E^@ ^@..&nbsp; ,^A ^@^@&nbsp; @^Q&nbsp; 9 6 ^J^J ^@ i
<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;
^J^J ^@ z&nbsp; + r&nbsp; + r ^@.. ^P 7&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 0 5&nbsp; ]&nbsp;&nbsp;&nbsp;
T =
<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;
4 2&nbsp; 2 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 5 {&nbsp; E =&nbsp; 5 8&nbsp; 9 8&nbsp; 2 9&nbsp; {
a
<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;
l /&nbsp; o f&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a
c
<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;
t ,&nbsp; E M&nbsp; { S&nbsp; G {&nbsp; c g&nbsp; / d&nbsp; t }&nbsp; ,
E
<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;
= 3&nbsp; 9 3&nbsp; 2 1&nbsp; 7 {&nbsp; d d&nbsp; / c&nbsp; e {&nbsp;&nbsp;&nbsp;
D
<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;
M =&nbsp; d i&nbsp; a l&nbsp; p l&nbsp; a n&nbsp; 1 }&nbsp; , a&nbsp; l
/
<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;
o n&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t
}
<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;
, g&nbsp; / s&nbsp; c }&nbsp; } }&nbsp; , a&nbsp; l /&nbsp; o n&nbsp; {
s
<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;
t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t }&nbsp; } }&nbsp; }
}
<br>> > > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
<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;
4500 00c0 2c04 0000 4011 3933 0a0a 0069
<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;
0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3035 5d20 543d
<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;
3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 367b 453d 3538 3938 3239 7b61
<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;
6c2f 6f66 7b73 7472 6963 743d 6578 6163
<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;
742c 454d 7b53 477b 6367 2f64 747d 2c45
<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;
3d33 3933 3231 377b 6464 2f63 657b 2044
<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;
4d3d 6469 616c 706c 616e 317d 2c61 6c2f
<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;
6f6e 7b73 7472 6963 743d 6578 6163 747d
<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;
2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
<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;
7472 6963 743d 6578 6163 747d 7d7d 7d7d
<br>> > >
<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;
E^@ ^@..&nbsp; ,^D ^@^@&nbsp; @^Q&nbsp; 9 3 ^J^J ^@ i
<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;
^J^J ^@ z&nbsp; + r&nbsp; + r ^@.. ^N 7&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 0 5&nbsp; ]&nbsp;&nbsp;&nbsp;
T =
<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;
4 2&nbsp; 3 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 6 {&nbsp; E =&nbsp; 5 8&nbsp; 9 8&nbsp; 2 9&nbsp; {
a
<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;
l /&nbsp; o f&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a
c
<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;
t ,&nbsp; E M&nbsp; { S&nbsp; G {&nbsp; c g&nbsp; / d&nbsp; t }&nbsp; ,
E
<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;
= 3&nbsp; 9 3&nbsp; 2 1&nbsp; 7 {&nbsp; d d&nbsp; / c&nbsp; e {&nbsp;&nbsp;&nbsp;
D
<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;
M =&nbsp; d i&nbsp; a l&nbsp; p l&nbsp; a n&nbsp; 1 }&nbsp; , a&nbsp; l
/
<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;
o n&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t
}
<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;
, g&nbsp; / s&nbsp; c }&nbsp; } }&nbsp; , a&nbsp; l /&nbsp; o n&nbsp; {
s
<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;
t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t }&nbsp; } }&nbsp; }
}
<br>> > > 16:46:18.405818 eth0 &lt; 10.10.0.122.11122 > coco2.11122: udp
70
<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;
4500 0062 0293 0000 3f11 6402 0a0a 007a
<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;
0a0a 0069 2b72 2b72 004e 705a 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3232 5d0a 503d
<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;
3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 327d 7d0a 503d 3432 317b 433d
<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;
2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
<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;
7d0a
<br>> > >
<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;
E^@ ^@ b ^B.. ^@^@&nbsp; ?^Q&nbsp; d^B ^J^J ^@ z
<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;
^J^J ^@ i&nbsp; + r&nbsp; + r ^@ N&nbsp; p Z&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 2 2&nbsp; ]^J&nbsp; P
=
<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;
4 2&nbsp; 0 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 2 }&nbsp; }^J&nbsp; P =&nbsp; 4 2&nbsp; 1 {&nbsp; C
=
<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; M F&nbsp; = a&nbsp; g w&nbsp; _ j&nbsp; u l&nbsp; w /&nbsp; 3
}
<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;
}^J
<br>> > > 16:46:18.506842 eth0 &lt; 10.10.0.122.11122 > coco2.11122: udp
70
<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;
4500 0062 0294 0000 3f11 6401 0a0a 007a
<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;
0a0a 0069 2b72 2b72 004e 665a 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3232 5d0a 503d
<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;
3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 357d 7d0a 503d 3432 337b 433d
<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;
2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
<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;
7d0a
<br>> > >
<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;
E^@ ^@ b ^B.. ^@^@&nbsp; ?^Q&nbsp; d^A ^J^J ^@ z
<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;
^J^J ^@ i&nbsp; + r&nbsp; + r ^@ N&nbsp; f Z&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 2 2&nbsp; ]^J&nbsp; P
=
<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;
4 2&nbsp; 2 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 5 }&nbsp; }^J&nbsp; P =&nbsp; 4 2&nbsp; 3 {&nbsp; C
=
<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; M F&nbsp; = a&nbsp; g w&nbsp; _ j&nbsp; u l&nbsp; w /&nbsp; 6
}
<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;
}^J
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > > best&nbsp; regards
<br>> > > > :-)Jerry Wang
<br>> > > tel:(8621)58541240 ext 9615
<br>> > > <a href="mailto:wangjl2@sbell.com.cn">mailto:wangjl2@sbell.com.cn</a>
<br>> > > Shanghai Bell Co.LTD
<br>> > >
<br>> > > -----Original Message-----
<br>> > > From: Barcotti, Glauco [<a href="mailto:Glauco_Barcotti@Mitel.COM">mailto:Glauco_Barcotti@Mitel.COM</a>]
<br>> > > Sent: Wednesday, April 17, 2002 10:10 PM
<br>> > > To: 'Christer Holmberg'
<br>> > > Cc: 'megaco@ietf.org'
<br>> > > Subject: RE: [Megaco] ServiceChange for a single termination
(Cold
<br>> > > Start)
<br>> > >
<br>> > > Hi,
<br>> > >
<br>> > > >>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assuming a
Gateway with 2 terminations, one of >them is OK
<br>> > > >> and the other is Malfunctioning. How should I >proceed if
I want to
<br>> >
<br>> > > >> bring just the working termination >up (Cold Start)?
<br>> > > >>
<br>> > > >> a) If a ServiceChange is issued for ROOT termination MGC will
think
<br>> >
<br>> > > >> that all terminations are up and, until another ServiceChange
is
<br>> > > >> issued taking the defective Termination out of service, a
call
<br>> > > >> could be attempted on that defective termination
<br>> > >
<br>> > > >I don't agree. A ServiceChange for ROOT will indicate that the
MG is
<br>> > > >up, not specific terminations. You would then have to send additonal
<br>> > > >ServiceChange commands, with Reason code 900, for each termination
<br>> > > >you want to put in-service.
<br>> > >
<br>> > > The example in the spec (Appendix A) and the
<br>> > > draft-madhu-megaco-callflows-00.txt tell me that when I address
ROOT
<br>> > > on a ServiceChange all terminations are addressed (One ServiceChange
<br>> > > ROOT is sent and the terminations are available to use). Where
did you
<br>> >
<br>> > > find information about ServiceChange ROOT not bringing all
<br>> > > terminations up?
<br>> > >
<br>> > > Thanks,
<br>> > > Glauco
<br>> > >
<br>> > > >Regards,
<br>> > >
<br>> > > >hrister Holmberg
<br>> > > >ricsson Finland
<br>> > >
<br>> > > >
<br>> > > >
<br>> > > > b) If a ServiceChange is issued just for the working Termination
The
<br>> >
<br>> > > > ability to redirect the gateway to another MGC will be lost
(See
<br>> > > > quotation from spec below)
<br>> > > >
<br>> > > > "The return from ServiceChange is empty except when the Root
<br>> > > > terminationID is used.&nbsp; In that case it includes the following
<br>> > > > parameters as required:"
<br>> > > >
<br>> > > > Thanks,
<br>> > > > Glauco
<br>> > > >
<br>> > > > _______________________________________________
<br>> > > > Megaco mailing list
<br>> > > > Megaco@ietf.org <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>
<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>
<br>>
<br>> --
<br>>
<br>> ------------------------------------------------------------
<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:732.949.5628&nbsp;&nbsp; Fax:732.949.7016
<br>> Lucent Technologies/INS/Voice Over IP Access Networks
<br>> Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
<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>
<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>

--------------68BD87654B52B6166157A630--



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


From daemon@ns.ietf.org  Fri Apr 19 11:51: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 LAA24686
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 11:51:34 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA20762
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 11:51:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17970;
	Fri, 19 Apr 2002 11:17:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18786
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 03:23:42 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12426
	for <megaco@ietf.org>; Fri, 19 Apr 2002 03:23:35 -0400 (EDT)
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 g3J7N3Y11483;
	Fri, 19 Apr 2002 09:23:03 +0200 (MEST)
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 JAA20531;
	Fri, 19 Apr 2002 09:22:50 +0200 (MET DST)
Message-ID: <3CBFC3DD.F3DBA052@alcatel.es>
Date: Fri, 19 Apr 2002 09:14:37 +0200
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: Christer Holmberg <christer.holmberg@lmf.ericsson.se>,
        Megaco <megaco@ietf.org>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <000801c1e6e1$18dc85e0$368910ac@Bala> <3CBF147D.D7A28C57@lucent.com> <3CBF9FB3.9208F958@lmf.ericsson.se>
Content-Type: multipart/alternative;
 boundary="------------68BD87654B52B6166157A630"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


--------------68BD87654B52B6166157A630
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,

As you have said in previous emails the pstn gateways from
the old point of view of switching may have different boards
with different terminations. And the may start up in a lapse of
seconds...
IMO I would wait for all to restart before sending a SVC (Restart).
In the best case no more messages will be sent, we can suppose
tha a faulty termination is not the normal case.
Another thing is that we may not be able to use wildcards... this
implies a message per termination.
I would prefer option 1)


Fernando Vallejo
Alcatel Spain

Christer Holmberg wrote:

> Hi,
>
> Opton 1) vs 2) is what we have been discussing in this thread so far, and I
> would prefear option 2).
>
> I don't think option 3) - it would just be a compromise, since we couldn't agree
> on something else :)
>
> Regards,
>
> Christer Holmberg
> Ericsson Finland
>
> Terry L Anderson wrote:
>
> > I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes no
> > statement one way or the other) and it is apparent that there is not
> > agreement on what we want.  I believe that there are three possible
> > positions and that we should clarify this through the IG once we agree.
> >
> > Possible clarifications:
> > ServiceChange on ROOT with method=restart (a registration):
> > 1) implies that all physical terminations on MG are also up.  Exceptions
> > should be indicated by additional ServiceChanges on the down terminations
> > using Forced, preferrably in the same message and using wildcards where
> > possible.
> > 2) implies that all physical terminations on MG are down.  Those that are up
> > will be indicated by additional ServiceChanges on the up terminations using
> > method=restart, preferrably in the same message and using wildcards were
> > possible.
> > 3) has no implication whether physical terminations are up or down, but MGC
> > may be provisioned to know whether an MG will indicate terminations that are
> > up or those that are down.
> >
> > I should say that I do not like #3 but am including it as a possibility.
> >
> > Preference for #1 or #2 probably depend on:
> > 1) whether most physical terminations are available almost immediately or
> > come up slowly and at different speeds.
> > 2) whether MGC is provisioned with knowledge about the available physical
> > terminations on an MG or expects to learn about them through ServiceChanges
> > or Audits
> >
> > Note that #1 can be implemented from #2 by adding:
> >     ServiceChange = *{Services{Method=Restart}}
> > to the action, and conversely #2 can be implemented from #1 by adding:
> >     ServiceChange = *{Services{Method=Forced}}
> >
> > In either case exceptions (up or down) to the ALL can be indicated by
> > additional ServiceChange commands.
> >
> > So (IMHO) it doesn't seem too critical which we choose, but we should choose
> > and document one.
> >
> > Even though I think that most GWs probably would not register until all or
> > most of their physical terminations are available, I would probably prefer
> > #2 since I can easily indicated them all up with only one additional
> > ServiceChange and it seems more natural to indicate those up those that are
> > down.  But I can be happy with either #1 or #2.
> >
> > What do folks prefer?
> >
> > Balasubramanian Pitchandi wrote:
> >
> > > Hi,
> > >
> > > I agree with Christer's views.
> > >
> > > If MG sends a ServiceChange 'ROOT', it only means that the gateway is in
> > > or out of service (Refer to Section 6.2.5 & 7.2.8 of the RFC3015). The
> > > protocol is very clear on this, I think.
> > >
> > > Given that -- SVC(ROOT) means that the gateway is up -- now there are
> > > many ways MGC could come to know of what terminations are in service:
> > >
> > > 1. MG sends ServiceChange for all the terminations that are in service
> > > individually (If there are large number of terminations, the MG could
> > > use *ranges* of TerminationIds(?) to limit the number of such messages)
> > >
> > > 2. MGC could audit the MG for the list of terminations that are in
> > > service in which case the MG returns the list of terminations that are
> > > in service.
> > >
> > > But clearly sending a ServiceChange('ROOT') does not mean that all the
> > > terminations in the MG are in service. This presents lot of operational
> > > problems as Christer pointed out.
> > >
> > > -- Bala
> > >
> > > __________________
> > > Bala Pitchandi
> > > UTStarcom Inc.
> > >
> > > -----Original Message-----
> > > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> > > SRD Wang JuLin
> > > Sent: Thursday, April 18, 2002 2:52 AM
> > > To: Christer Holmberg
> > > Cc: Barcotti, Glauco; megaco@ietf.org
> > > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > > Start)
> > >
> > > Hi,
> > > Well,I think MGC should send Modify messages (the number of it equals to
> > > the number of terminations in RGW,I only refer to Residential GW) to
> > > check the terminations's events  after MG reboot with Cold Start as a
> > > whole entity. All terminations will start up.In case of some
> > > terminations fail to use,of course,we should send SC for definite
> > > invalid termination with restored method  to Softswtich. Before you WANT
> > > to use a termination,you should know whether it is ABLE to use (ie.in
> > > service or out of  service).
> > >
> > > best  regards
> > > > :-)Jerry Wang
> > > tel:(8621)58541240 ext 9615
> > > mailto:wangjl2@sbell.com.cn
> > > Shanghai Bell Co.LTD
> > >
> > > -----Original Message-----
> > > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > > Sent: Thursday, April 18, 2002 2:27 PM
> > > To: SRD Wang JuLin
> > > Cc: Barcotti, Glauco; megaco@ietf.org
> > > Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> > > Start)
> > >
> > > Hi,
> > >
> > > So, you want me to send a MODIFY to each of the THOUSANDS of
> > > terminations I may want to use????
> > >
> > > And, the issue is not which termination I WANT to use (ie which I want
> > > the MGC to "enable" in the MG), but which termination I am ABLE (ie
> > > which termination has at a certain time been booted/loaded/whatevver) to
> > > use...
> > >
> > > Regards,
> > >
> > > Christer Holmberg
> > > Ericsson Finland
> > >
> > > SRD Wang JuLin wrote:
> > >
> > > > Hi,
> > > > Well,I send the ServiceChange for Root to Softswitch,it only send 4
> > > > modify messages  to RGW.So i can only use 4 out of the 8 phones
> > > > located in RGW. (I had provisioned 8 terminations into Softswitch
> > > >
> > > > )
> > > > 16:46:17.873046 eth0 < 10.10.0.122.11122 > coco2.2944: udp 114
> > > >                          4500 008e 028b 0000 3f11 63de 0a0a 007a
> > > >                          0a0a 0069 2b72 0b80 007a d67f 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 543d
> > > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > > >                          7b4d 543d 5253 2c52 453d 3930 312c 4144
> > > >                          3d31 3131 3232 2c50 463d 416e 616c 6f67
> > > >                          5f4c 696e 655f 496e 7465 726f 7065 7261
> > > >                          6269 6c69 7479 5f54 6573 745f 5072 6f66
> > > >                          696c 652f 312c 563d 317d 7d7d 7d0a
> > > >
> > > >                           E^@ ^@.. ^B.. ^@^@  ?^Q  c.. ^J^J ^@ z
> > > >                          ^J^J ^@ i  + r ^K.. ^@ z ..^? ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  T =
> > > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > > >                           { M  T =  R S  , R  E =  9 0  1 ,  A D
> > > >                           = 1  1 1  2 2  , P  F =  A n  a l  o g
> > > >                           _ L  i n  e _  I n  t e  r o  p e  r a
> > > >                           b i  l i  t y  _ T  e s  t _  P r  o f
> > > >                           i l  e /  1 ,  V =  1 }  } }  }^J
> > > > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
> > > >                          4500 005a 2bdf 0000 4011 39be 0a0a 0069
> > > >                          0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3035 5d20 503d
> > > >                          317b 433d 2d7b 5343 3d52 4f4f 547b 5356
> > > >                          7b41 443d 3131 3132 322c 5046 3d43 4c53
> > > >                          2f31 2c56 3d31 7d7d 7d7d
> > > >
> > > >                           E^@ ^@ Z  +.. ^@^@  @^Q  9.. ^J^J ^@ i
> > > >                          ^J^J ^@ z ^K..  + r ^@ F ^ç¸(tm)]  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    P =
> > > >                           1 {  C =  - {  S C  = R  O O  T {  S V
> > > >                           { A  D =  1 1  1 2  2 ,  P F  = C  L S
> > > >                           / 1  , V  = 1  } }  } } 16:46:18.325927 eth0
> > >
> > > > > coco2.11122 > 10.10.0.122.11122: udp 164
> > > >                          4500 00c0 2bf3 0000 4011 3944 0a0a 0069
> > > >                          0a0a 007a 2b72 2b72 00ac 1537 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 327b 453d 3538 3938 3239 7b61
> > > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > > >
> > > >                           E^@ ^@..  +.. ^@^@  @^Q  9 D ^J^J ^@ i
> > > >                          ^J^J ^@ z  + r  + r ^@.. ^U 7  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  2 {  E =  5 8  9 8  2 9  { a
> > > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > > >                          4500 00c0 2bf9 0000 4011 393e 0a0a 0069
> > > >                          0a0a 007a 2b72 2b72 00ac 1337 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > > >                          3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 337b 453d 3538 3938 3239 7b61
> > > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > > >
> > > >                           E^@ ^@..  +.. ^@^@  @^Q  9 > ^J^J ^@ i
> > > >                          ^J^J ^@ z  + r  + r ^@.. ^S 7  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > > >                           4 2  1 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  3 {  E =  5 8  9 8  2 9  { a
> > > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > > >                          4500 00c0 2c01 0000 4011 3936 0a0a 0069
> > > >                          0a0a 007a 2b72 2b72 00ac 1037 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 357b 453d 3538 3938 3239 7b61
> > > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > > >
> > > >                           E^@ ^@..  ,^A ^@^@  @^Q  9 6 ^J^J ^@ i
> > > >                          ^J^J ^@ z  + r  + r ^@.. ^P 7  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  5 {  E =  5 8  9 8  2 9  { a
> > > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
> > > >                          4500 00c0 2c04 0000 4011 3933 0a0a 0069
> > > >                          0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3035 5d20 543d
> > > >                          3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 367b 453d 3538 3938 3239 7b61
> > > >                          6c2f 6f66 7b73 7472 6963 743d 6578 6163
> > > >                          742c 454d 7b53 477b 6367 2f64 747d 2c45
> > > >                          3d33 3933 3231 377b 6464 2f63 657b 2044
> > > >                          4d3d 6469 616c 706c 616e 317d 2c61 6c2f
> > > >                          6f6e 7b73 7472 6963 743d 6578 6163 747d
> > > >                          2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
> > > >                          7472 6963 743d 6578 6163 747d 7d7d 7d7d
> > > >
> > > >                           E^@ ^@..  ,^D ^@^@  @^Q  9 3 ^J^J ^@ i
> > > >                          ^J^J ^@ z  + r  + r ^@.. ^N 7  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  0 5  ]    T =
> > > >                           4 2  3 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  6 {  E =  5 8  9 8  2 9  { a
> > > >                           l /  o f  { s  t r  i c  t =  e x  a c
> > > >                           t ,  E M  { S  G {  c g  / d  t }  , E
> > > >                           = 3  9 3  2 1  7 {  d d  / c  e {    D
> > > >                           M =  d i  a l  p l  a n  1 }  , a  l /
> > > >                           o n  { s  t r  i c  t =  e x  a c  t }
> > > >                           , g  / s  c }  } }  , a  l /  o n  { s
> > > >                           t r  i c  t =  e x  a c  t }  } }  } }
> > > > 16:46:18.405818 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > > >                          4500 0062 0293 0000 3f11 6402 0a0a 007a
> > > >                          0a0a 0069 2b72 2b72 004e 705a 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > > >                          3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 327d 7d0a 503d 3432 317b 433d
> > > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
> > > >                          7d0a
> > > >
> > > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^B ^J^J ^@ z
> > > >                          ^J^J ^@ i  + r  + r ^@ N  p Z  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > > >                           4 2  0 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  2 }  }^J  P =  4 2  1 {  C =
> > > >                           - {  M F  = a  g w  _ j  u l  w /  3 }
> > > >                           }^J
> > > > 16:46:18.506842 eth0 < 10.10.0.122.11122 > coco2.11122: udp 70
> > > >                          4500 0062 0294 0000 3f11 6401 0a0a 007a
> > > >                          0a0a 0069 2b72 2b72 004e 665a 212f 3120
> > > >                          5b31 302e 3130 2e30 2e31 3232 5d0a 503d
> > > >                          3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
> > > >                          756c 772f 357d 7d0a 503d 3432 337b 433d
> > > >                          2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
> > > >                          7d0a
> > > >
> > > >                           E^@ ^@ b ^B.. ^@^@  ?^Q  d^A ^J^J ^@ z
> > > >                          ^J^J ^@ i  + r  + r ^@ N  f Z  ! /  1
> > > >                           [ 1  0 .  1 0  . 0  . 1  2 2  ]^J  P =
> > > >                           4 2  2 {  C =  - {  M F  = a  g w  _ j
> > > >                           u l  w /  5 }  }^J  P =  4 2  3 {  C =
> > > >                           - {  M F  = a  g w  _ j  u l  w /  6 }
> > > >                           }^J
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > best  regards
> > > > > :-)Jerry Wang
> > > > tel:(8621)58541240 ext 9615
> > > > mailto:wangjl2@sbell.com.cn
> > > > Shanghai Bell Co.LTD
> > > >
> > > > -----Original Message-----
> > > > From: Barcotti, Glauco [mailto:Glauco_Barcotti@Mitel.COM]
> > > > Sent: Wednesday, April 17, 2002 10:10 PM
> > > > To: 'Christer Holmberg'
> > > > Cc: 'megaco@ietf.org'
> > > > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
> > > > Start)
> > > >
> > > > Hi,
> > > >
> > > > >>         Assuming a Gateway with 2 terminations, one of >them is OK
> > > > >> and the other is Malfunctioning. How should I >proceed if I want to
> > >
> > > > >> bring just the working termination >up (Cold Start)?
> > > > >>
> > > > >> a) If a ServiceChange is issued for ROOT termination MGC will think
> > >
> > > > >> that all terminations are up and, until another ServiceChange is
> > > > >> issued taking the defective Termination out of service, a call
> > > > >> could be attempted on that defective termination
> > > >
> > > > >I don't agree. A ServiceChange for ROOT will indicate that the MG is
> > > > >up, not specific terminations. You would then have to send additonal
> > > > >ServiceChange commands, with Reason code 900, for each termination
> > > > >you want to put in-service.
> > > >
> > > > The example in the spec (Appendix A) and the
> > > > draft-madhu-megaco-callflows-00.txt tell me that when I address ROOT
> > > > on a ServiceChange all terminations are addressed (One ServiceChange
> > > > ROOT is sent and the terminations are available to use). Where did you
> > >
> > > > find information about ServiceChange ROOT not bringing all
> > > > terminations up?
> > > >
> > > > Thanks,
> > > > Glauco
> > > >
> > > > >Regards,
> > > >
> > > > >hrister Holmberg
> > > > >ricsson Finland
> > > >
> > > > >
> > > > >
> > > > > b) If a ServiceChange is issued just for the working Termination The
> > >
> > > > > ability to redirect the gateway to another MGC will be lost (See
> > > > > quotation from spec below)
> > > > >
> > > > > "The return from ServiceChange is empty except when the Root
> > > > > terminationID is used.  In that case it includes the following
> > > > > parameters as required:"
> > > > >
> > > > > Thanks,
> > > > > Glauco
> > > > >
> > > > > _______________________________________________
> > > > > Megaco mailing 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
> >
> > --
> >
> > ------------------------------------------------------------
> > Terry L Anderson             mailto:tla@lucent.com
> > Tel:732.949.5628   Fax:732.949.7016
> > Lucent Technologies/INS/Voice Over IP Access Networks
> > Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > 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

--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi,
<p>As you have said in previous emails the pstn gateways from
<br>the old point of view of switching may have different boards
<br>with different terminations. And the may start up in a lapse of
<br>seconds...
<br>IMO I would wait for all to restart before sending a SVC&nbsp;(Restart).
<br>In the best case no more messages will be sent, we can suppose
<br>tha a faulty termination is not the normal case.
<br>Another thing is that we may not be able to use wildcards... this
<br>implies a message per termination.
<br>I would prefer option 1)
<br>&nbsp;
<p>Fernando Vallejo
<br>Alcatel Spain
<p>Christer Holmberg wrote:
<blockquote TYPE=CITE>Hi,
<p>Opton 1) vs 2) is what we have been discussing in this thread so far,
and I
<br>would prefear option 2).
<p>I don't think option 3) - it would just be a compromise, since we couldn't
agree
<br>on something else :)
<p>Regards,
<p>Christer Holmberg
<br>Ericsson Finland
<p>Terry L Anderson wrote:
<p>> I cannot agree that 6.2.5 and/or 7.2.8 is clear on this (it makes
no
<br>> statement one way or the other) and it is apparent that there is
not
<br>> agreement on what we want.&nbsp; I believe that there are three possible
<br>> positions and that we should clarify this through the IG once we
agree.
<br>>
<br>> Possible clarifications:
<br>> ServiceChange on ROOT with method=restart (a registration):
<br>> 1) implies that all physical terminations on MG are also up.&nbsp;
Exceptions
<br>> should be indicated by additional ServiceChanges on the down terminations
<br>> using Forced, preferrably in the same message and using wildcards
where
<br>> possible.
<br>> 2) implies that all physical terminations on MG are down.&nbsp; Those
that are up
<br>> will be indicated by additional ServiceChanges on the up terminations
using
<br>> method=restart, preferrably in the same message and using wildcards
were
<br>> possible.
<br>> 3) has no implication whether physical terminations are up or down,
but MGC
<br>> may be provisioned to know whether an MG will indicate terminations
that are
<br>> up or those that are down.
<br>>
<br>> I should say that I do not like #3 but am including it as a possibility.
<br>>
<br>> Preference for #1 or #2 probably depend on:
<br>> 1) whether most physical terminations are available almost immediately
or
<br>> come up slowly and at different speeds.
<br>> 2) whether MGC is provisioned with knowledge about the available
physical
<br>> terminations on an MG or expects to learn about them through ServiceChanges
<br>> or Audits
<br>>
<br>> Note that #1 can be implemented from #2 by adding:
<br>>&nbsp;&nbsp;&nbsp;&nbsp; ServiceChange = *{Services{Method=Restart}}
<br>> to the action, and conversely #2 can be implemented from #1 by adding:
<br>>&nbsp;&nbsp;&nbsp;&nbsp; ServiceChange = *{Services{Method=Forced}}
<br>>
<br>> In either case exceptions (up or down) to the ALL can be indicated
by
<br>> additional ServiceChange commands.
<br>>
<br>> So (IMHO) it doesn't seem too critical which we choose, but we should
choose
<br>> and document one.
<br>>
<br>> Even though I think that most GWs probably would not register until
all or
<br>> most of their physical terminations are available, I would probably
prefer
<br>> #2 since I can easily indicated them all up with only one additional
<br>> ServiceChange and it seems more natural to indicate those up those
that are
<br>> down.&nbsp; But I can be happy with either #1 or #2.
<br>>
<br>> What do folks prefer?
<br>>
<br>> Balasubramanian Pitchandi wrote:
<br>>
<br>> > Hi,
<br>> >
<br>> > I agree with Christer's views.
<br>> >
<br>> > If MG sends a ServiceChange 'ROOT', it only means that the gateway
is in
<br>> > or out of service (Refer to Section 6.2.5 &amp; 7.2.8 of the RFC3015).
The
<br>> > protocol is very clear on this, I think.
<br>> >
<br>> > Given that -- SVC(ROOT) means that the gateway is up -- now there
are
<br>> > many ways MGC could come to know of what terminations are in service:
<br>> >
<br>> > 1. MG sends ServiceChange for all the terminations that are in
service
<br>> > individually (If there are large number of terminations, the MG
could
<br>> > use *ranges* of TerminationIds(?) to limit the number of such messages)
<br>> >
<br>> > 2. MGC could audit the MG for the list of terminations that are
in
<br>> > service in which case the MG returns the list of terminations that
are
<br>> > in service.
<br>> >
<br>> > But clearly sending a ServiceChange('ROOT') does not mean that
all the
<br>> > terminations in the MG are in service. This presents lot of operational
<br>> > problems as Christer pointed out.
<br>> >
<br>> > -- Bala
<br>> >
<br>> > __________________
<br>> > Bala Pitchandi
<br>> > UTStarcom Inc.
<br>> >
<br>> > -----Original Message-----
<br>> > From: megaco-admin@ietf.org [<a href="mailto:megaco-admin@ietf.org">mailto:megaco-admin@ietf.org</a>]
On Behalf Of
<br>> > SRD Wang JuLin
<br>> > Sent: Thursday, April 18, 2002 2:52 AM
<br>> > To: Christer Holmberg
<br>> > Cc: Barcotti, Glauco; megaco@ietf.org
<br>> > Subject: RE: [Megaco] ServiceChange for a single termination (Cold
<br>> > Start)
<br>> >
<br>> > Hi,
<br>> > Well,I think MGC should send Modify messages (the number of it
equals to
<br>> > the number of terminations in RGW,I only refer to Residential GW)
to
<br>> > check the terminations's events&nbsp; after MG reboot with Cold
Start as a
<br>> > whole entity. All terminations will start up.In case of some
<br>> > terminations fail to use,of course,we should send SC for definite
<br>> > invalid termination with restored method&nbsp; to Softswtich. Before
you WANT
<br>> > to use a termination,you should know whether it is ABLE to use
(ie.in
<br>> > service or out of&nbsp; service).
<br>> >
<br>> > best&nbsp; regards
<br>> > > :-)Jerry Wang
<br>> > tel:(8621)58541240 ext 9615
<br>> > <a href="mailto:wangjl2@sbell.com.cn">mailto:wangjl2@sbell.com.cn</a>
<br>> > Shanghai Bell Co.LTD
<br>> >
<br>> > -----Original Message-----
<br>> > From: Christer Holmberg [<a href="mailto:christer.holmberg@lmf.ericsson.se">mailto:christer.holmberg@lmf.ericsson.se</a>]
<br>> > Sent: Thursday, April 18, 2002 2:27 PM
<br>> > To: SRD Wang JuLin
<br>> > Cc: Barcotti, Glauco; megaco@ietf.org
<br>> > Subject: Re: [Megaco] ServiceChange for a single termination (Cold
<br>> > Start)
<br>> >
<br>> > Hi,
<br>> >
<br>> > So, you want me to send a MODIFY to each of the THOUSANDS of
<br>> > terminations I may want to use????
<br>> >
<br>> > And, the issue is not which termination I WANT to use (ie which
I want
<br>> > the MGC to "enable" in the MG), but which termination I am ABLE
(ie
<br>> > which termination has at a certain time been booted/loaded/whatevver)
to
<br>> > use...
<br>> >
<br>> > Regards,
<br>> >
<br>> > Christer Holmberg
<br>> > Ericsson Finland
<br>> >
<br>> > SRD Wang JuLin wrote:
<br>> >
<br>> > > Hi,
<br>> > > Well,I send the ServiceChange for Root to Softswitch,it only
send 4
<br>> > > modify messages&nbsp; to RGW.So i can only use 4 out of the 8
phones
<br>> > > located in RGW. (I had provisioned 8 terminations into Softswitch
<br>> > >
<br>> > > )
<br>> > > 16:46:17.873046 eth0 &lt; 10.10.0.122.11122 > coco2.2944: udp
114
<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;
4500 008e 028b 0000 3f11 63de 0a0a 007a
<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;
0a0a 0069 2b72 0b80 007a d67f 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3232 5d0a 543d
<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;
317b 433d 2d7b 5343 3d52 4f4f 547b 5356
<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;
7b4d 543d 5253 2c52 453d 3930 312c 4144
<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;
3d31 3131 3232 2c50 463d 416e 616c 6f67
<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;
5f4c 696e 655f 496e 7465 726f 7065 7261
<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;
6269 6c69 7479 5f54 6573 745f 5072 6f66
<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;
696c 652f 312c 563d 317d 7d7d 7d0a
<br>> > >
<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;
E^@ ^@.. ^B.. ^@^@&nbsp; ?^Q&nbsp; c.. ^J^J ^@ z
<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;
^J^J ^@ i&nbsp; + r ^K.. ^@ z ..^? ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 2 2&nbsp; ]^J&nbsp; T
=
<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;
1 {&nbsp; C =&nbsp; - {&nbsp; S C&nbsp; = R&nbsp; O O&nbsp; T {&nbsp; S
V
<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;
{ M&nbsp; T =&nbsp; R S&nbsp; , R&nbsp; E =&nbsp; 9 0&nbsp; 1 ,&nbsp; A
D
<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;
= 1&nbsp; 1 1&nbsp; 2 2&nbsp; , P&nbsp; F =&nbsp; A n&nbsp; a l&nbsp; o
g
<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;
_ L&nbsp; i n&nbsp; e _&nbsp; I n&nbsp; t e&nbsp; r o&nbsp; p e&nbsp; r
a
<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;
b i&nbsp; l i&nbsp; t y&nbsp; _ T&nbsp; e s&nbsp; t _&nbsp; P r&nbsp; o
f
<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;
i l&nbsp; e /&nbsp; 1 ,&nbsp; V =&nbsp; 1 }&nbsp; } }&nbsp; }^J
<br>> > > 16:46:17.874841 eth0 > coco2.2944 > 10.10.0.122.11122: udp 62
<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;
4500 005a 2bdf 0000 4011 39be 0a0a 0069
<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;
0a0a 007a 0b80 2b72 0046 7f1d 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3035 5d20 503d
<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;
317b 433d 2d7b 5343 3d52 4f4f 547b 5356
<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;
7b41 443d 3131 3132 322c 5046 3d43 4c53
<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;
2f31 2c56 3d31 7d7d 7d7d
<br>> > >
<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;
E^@ ^@ Z&nbsp; +.. ^@^@&nbsp; @^Q&nbsp; 9.. ^J^J ^@ i
<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;
^J^J ^@ z ^K..&nbsp; + r ^@ F ^&ccedil;&cedil;(tm)]&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 0 5&nbsp; ]&nbsp;&nbsp;&nbsp;
P =
<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;
1 {&nbsp; C =&nbsp; - {&nbsp; S C&nbsp; = R&nbsp; O O&nbsp; T {&nbsp; S
V
<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;
{ A&nbsp; D =&nbsp; 1 1&nbsp; 1 2&nbsp; 2 ,&nbsp; P F&nbsp; = C&nbsp; L
S
<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;
/ 1&nbsp; , V&nbsp; = 1&nbsp; } }&nbsp; } } 16:46:18.325927 eth0
<br>> >
<br>> > > > coco2.11122 > 10.10.0.122.11122: udp 164
<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;
4500 00c0 2bf3 0000 4011 3944 0a0a 0069
<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;
0a0a 007a 2b72 2b72 00ac 1537 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3035 5d20 543d
<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;
3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 327b 453d 3538 3938 3239 7b61
<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;
6c2f 6f66 7b73 7472 6963 743d 6578 6163
<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;
742c 454d 7b53 477b 6367 2f64 747d 2c45
<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;
3d33 3933 3231 377b 6464 2f63 657b 2044
<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;
4d3d 6469 616c 706c 616e 317d 2c61 6c2f
<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;
6f6e 7b73 7472 6963 743d 6578 6163 747d
<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;
2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
<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;
7472 6963 743d 6578 6163 747d 7d7d 7d7d
<br>> > >
<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;
E^@ ^@..&nbsp; +.. ^@^@&nbsp; @^Q&nbsp; 9 D ^J^J ^@ i
<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;
^J^J ^@ z&nbsp; + r&nbsp; + r ^@.. ^U 7&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 0 5&nbsp; ]&nbsp;&nbsp;&nbsp;
T =
<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;
4 2&nbsp; 0 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 2 {&nbsp; E =&nbsp; 5 8&nbsp; 9 8&nbsp; 2 9&nbsp; {
a
<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;
l /&nbsp; o f&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a
c
<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;
t ,&nbsp; E M&nbsp; { S&nbsp; G {&nbsp; c g&nbsp; / d&nbsp; t }&nbsp; ,
E
<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;
= 3&nbsp; 9 3&nbsp; 2 1&nbsp; 7 {&nbsp; d d&nbsp; / c&nbsp; e {&nbsp;&nbsp;&nbsp;
D
<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;
M =&nbsp; d i&nbsp; a l&nbsp; p l&nbsp; a n&nbsp; 1 }&nbsp; , a&nbsp; l
/
<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;
o n&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t
}
<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;
, g&nbsp; / s&nbsp; c }&nbsp; } }&nbsp; , a&nbsp; l /&nbsp; o n&nbsp; {
s
<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;
t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t }&nbsp; } }&nbsp; }
}
<br>> > > 16:46:18.329845 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
<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;
4500 00c0 2bf9 0000 4011 393e 0a0a 0069
<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;
0a0a 007a 2b72 2b72 00ac 1337 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3035 5d20 543d
<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;
3432 317b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 337b 453d 3538 3938 3239 7b61
<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;
6c2f 6f66 7b73 7472 6963 743d 6578 6163
<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;
742c 454d 7b53 477b 6367 2f64 747d 2c45
<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;
3d33 3933 3231 377b 6464 2f63 657b 2044
<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;
4d3d 6469 616c 706c 616e 317d 2c61 6c2f
<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;
6f6e 7b73 7472 6963 743d 6578 6163 747d
<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;
2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
<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;
7472 6963 743d 6578 6163 747d 7d7d 7d7d
<br>> > >
<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;
E^@ ^@..&nbsp; +.. ^@^@&nbsp; @^Q&nbsp; 9 > ^J^J ^@ i
<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;
^J^J ^@ z&nbsp; + r&nbsp; + r ^@.. ^S 7&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 0 5&nbsp; ]&nbsp;&nbsp;&nbsp;
T =
<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;
4 2&nbsp; 1 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 3 {&nbsp; E =&nbsp; 5 8&nbsp; 9 8&nbsp; 2 9&nbsp; {
a
<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;
l /&nbsp; o f&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a
c
<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;
t ,&nbsp; E M&nbsp; { S&nbsp; G {&nbsp; c g&nbsp; / d&nbsp; t }&nbsp; ,
E
<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;
= 3&nbsp; 9 3&nbsp; 2 1&nbsp; 7 {&nbsp; d d&nbsp; / c&nbsp; e {&nbsp;&nbsp;&nbsp;
D
<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;
M =&nbsp; d i&nbsp; a l&nbsp; p l&nbsp; a n&nbsp; 1 }&nbsp; , a&nbsp; l
/
<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;
o n&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t
}
<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;
, g&nbsp; / s&nbsp; c }&nbsp; } }&nbsp; , a&nbsp; l /&nbsp; o n&nbsp; {
s
<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;
t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t }&nbsp; } }&nbsp; }
}
<br>> > > 16:46:18.333869 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
<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;
4500 00c0 2c01 0000 4011 3936 0a0a 0069
<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;
0a0a 007a 2b72 2b72 00ac 1037 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3035 5d20 543d
<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;
3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 357b 453d 3538 3938 3239 7b61
<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;
6c2f 6f66 7b73 7472 6963 743d 6578 6163
<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;
742c 454d 7b53 477b 6367 2f64 747d 2c45
<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;
3d33 3933 3231 377b 6464 2f63 657b 2044
<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;
4d3d 6469 616c 706c 616e 317d 2c61 6c2f
<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;
6f6e 7b73 7472 6963 743d 6578 6163 747d
<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;
2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
<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;
7472 6963 743d 6578 6163 747d 7d7d 7d7d
<br>> > >
<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;
E^@ ^@..&nbsp; ,^A ^@^@&nbsp; @^Q&nbsp; 9 6 ^J^J ^@ i
<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;
^J^J ^@ z&nbsp; + r&nbsp; + r ^@.. ^P 7&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 0 5&nbsp; ]&nbsp;&nbsp;&nbsp;
T =
<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;
4 2&nbsp; 2 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 5 {&nbsp; E =&nbsp; 5 8&nbsp; 9 8&nbsp; 2 9&nbsp; {
a
<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;
l /&nbsp; o f&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a
c
<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;
t ,&nbsp; E M&nbsp; { S&nbsp; G {&nbsp; c g&nbsp; / d&nbsp; t }&nbsp; ,
E
<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;
= 3&nbsp; 9 3&nbsp; 2 1&nbsp; 7 {&nbsp; d d&nbsp; / c&nbsp; e {&nbsp;&nbsp;&nbsp;
D
<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;
M =&nbsp; d i&nbsp; a l&nbsp; p l&nbsp; a n&nbsp; 1 }&nbsp; , a&nbsp; l
/
<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;
o n&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t
}
<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;
, g&nbsp; / s&nbsp; c }&nbsp; } }&nbsp; , a&nbsp; l /&nbsp; o n&nbsp; {
s
<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;
t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t }&nbsp; } }&nbsp; }
}
<br>> > > 16:46:18.336658 eth0 > coco2.11122 > 10.10.0.122.11122: udp 164
<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;
4500 00c0 2c04 0000 4011 3933 0a0a 0069
<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;
0a0a 007a 2b72 2b72 00ac 0e37 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3035 5d20 543d
<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;
3432 337b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 367b 453d 3538 3938 3239 7b61
<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;
6c2f 6f66 7b73 7472 6963 743d 6578 6163
<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;
742c 454d 7b53 477b 6367 2f64 747d 2c45
<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;
3d33 3933 3231 377b 6464 2f63 657b 2044
<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;
4d3d 6469 616c 706c 616e 317d 2c61 6c2f
<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;
6f6e 7b73 7472 6963 743d 6578 6163 747d
<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;
2c67 2f73 637d 7d7d 2c61 6c2f 6f6e 7b73
<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;
7472 6963 743d 6578 6163 747d 7d7d 7d7d
<br>> > >
<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;
E^@ ^@..&nbsp; ,^D ^@^@&nbsp; @^Q&nbsp; 9 3 ^J^J ^@ i
<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;
^J^J ^@ z&nbsp; + r&nbsp; + r ^@.. ^N 7&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 0 5&nbsp; ]&nbsp;&nbsp;&nbsp;
T =
<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;
4 2&nbsp; 3 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 6 {&nbsp; E =&nbsp; 5 8&nbsp; 9 8&nbsp; 2 9&nbsp; {
a
<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;
l /&nbsp; o f&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a
c
<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;
t ,&nbsp; E M&nbsp; { S&nbsp; G {&nbsp; c g&nbsp; / d&nbsp; t }&nbsp; ,
E
<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;
= 3&nbsp; 9 3&nbsp; 2 1&nbsp; 7 {&nbsp; d d&nbsp; / c&nbsp; e {&nbsp;&nbsp;&nbsp;
D
<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;
M =&nbsp; d i&nbsp; a l&nbsp; p l&nbsp; a n&nbsp; 1 }&nbsp; , a&nbsp; l
/
<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;
o n&nbsp; { s&nbsp; t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t
}
<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;
, g&nbsp; / s&nbsp; c }&nbsp; } }&nbsp; , a&nbsp; l /&nbsp; o n&nbsp; {
s
<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;
t r&nbsp; i c&nbsp; t =&nbsp; e x&nbsp; a c&nbsp; t }&nbsp; } }&nbsp; }
}
<br>> > > 16:46:18.405818 eth0 &lt; 10.10.0.122.11122 > coco2.11122: udp
70
<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;
4500 0062 0293 0000 3f11 6402 0a0a 007a
<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;
0a0a 0069 2b72 2b72 004e 705a 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3232 5d0a 503d
<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;
3432 307b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 327d 7d0a 503d 3432 317b 433d
<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;
2d7b 4d46 3d61 6777 5f6a 756c 772f 337d
<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;
7d0a
<br>> > >
<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;
E^@ ^@ b ^B.. ^@^@&nbsp; ?^Q&nbsp; d^B ^J^J ^@ z
<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;
^J^J ^@ i&nbsp; + r&nbsp; + r ^@ N&nbsp; p Z&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 2 2&nbsp; ]^J&nbsp; P
=
<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;
4 2&nbsp; 0 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 2 }&nbsp; }^J&nbsp; P =&nbsp; 4 2&nbsp; 1 {&nbsp; C
=
<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; M F&nbsp; = a&nbsp; g w&nbsp; _ j&nbsp; u l&nbsp; w /&nbsp; 3
}
<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;
}^J
<br>> > > 16:46:18.506842 eth0 &lt; 10.10.0.122.11122 > coco2.11122: udp
70
<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;
4500 0062 0294 0000 3f11 6401 0a0a 007a
<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;
0a0a 0069 2b72 2b72 004e 665a 212f 3120
<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;
5b31 302e 3130 2e30 2e31 3232 5d0a 503d
<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;
3432 327b 433d 2d7b 4d46 3d61 6777 5f6a
<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;
756c 772f 357d 7d0a 503d 3432 337b 433d
<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;
2d7b 4d46 3d61 6777 5f6a 756c 772f 367d
<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;
7d0a
<br>> > >
<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;
E^@ ^@ b ^B.. ^@^@&nbsp; ?^Q&nbsp; d^A ^J^J ^@ z
<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;
^J^J ^@ i&nbsp; + r&nbsp; + r ^@ N&nbsp; f Z&nbsp; ! /&nbsp; 1
<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;
[ 1&nbsp; 0 .&nbsp; 1 0&nbsp; . 0&nbsp; . 1&nbsp; 2 2&nbsp; ]^J&nbsp; P
=
<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;
4 2&nbsp; 2 {&nbsp; C =&nbsp; - {&nbsp; M F&nbsp; = a&nbsp; g w&nbsp; _
j
<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;
u l&nbsp; w /&nbsp; 5 }&nbsp; }^J&nbsp; P =&nbsp; 4 2&nbsp; 3 {&nbsp; C
=
<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; M F&nbsp; = a&nbsp; g w&nbsp; _ j&nbsp; u l&nbsp; w /&nbsp; 6
}
<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;
}^J
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > >
<br>> > > best&nbsp; regards
<br>> > > > :-)Jerry Wang
<br>> > > tel:(8621)58541240 ext 9615
<br>> > > <a href="mailto:wangjl2@sbell.com.cn">mailto:wangjl2@sbell.com.cn</a>
<br>> > > Shanghai Bell Co.LTD
<br>> > >
<br>> > > -----Original Message-----
<br>> > > From: Barcotti, Glauco [<a href="mailto:Glauco_Barcotti@Mitel.COM">mailto:Glauco_Barcotti@Mitel.COM</a>]
<br>> > > Sent: Wednesday, April 17, 2002 10:10 PM
<br>> > > To: 'Christer Holmberg'
<br>> > > Cc: 'megaco@ietf.org'
<br>> > > Subject: RE: [Megaco] ServiceChange for a single termination
(Cold
<br>> > > Start)
<br>> > >
<br>> > > Hi,
<br>> > >
<br>> > > >>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Assuming a
Gateway with 2 terminations, one of >them is OK
<br>> > > >> and the other is Malfunctioning. How should I >proceed if
I want to
<br>> >
<br>> > > >> bring just the working termination >up (Cold Start)?
<br>> > > >>
<br>> > > >> a) If a ServiceChange is issued for ROOT termination MGC will
think
<br>> >
<br>> > > >> that all terminations are up and, until another ServiceChange
is
<br>> > > >> issued taking the defective Termination out of service, a
call
<br>> > > >> could be attempted on that defective termination
<br>> > >
<br>> > > >I don't agree. A ServiceChange for ROOT will indicate that the
MG is
<br>> > > >up, not specific terminations. You would then have to send additonal
<br>> > > >ServiceChange commands, with Reason code 900, for each termination
<br>> > > >you want to put in-service.
<br>> > >
<br>> > > The example in the spec (Appendix A) and the
<br>> > > draft-madhu-megaco-callflows-00.txt tell me that when I address
ROOT
<br>> > > on a ServiceChange all terminations are addressed (One ServiceChange
<br>> > > ROOT is sent and the terminations are available to use). Where
did you
<br>> >
<br>> > > find information about ServiceChange ROOT not bringing all
<br>> > > terminations up?
<br>> > >
<br>> > > Thanks,
<br>> > > Glauco
<br>> > >
<br>> > > >Regards,
<br>> > >
<br>> > > >hrister Holmberg
<br>> > > >ricsson Finland
<br>> > >
<br>> > > >
<br>> > > >
<br>> > > > b) If a ServiceChange is issued just for the working Termination
The
<br>> >
<br>> > > > ability to redirect the gateway to another MGC will be lost
(See
<br>> > > > quotation from spec below)
<br>> > > >
<br>> > > > "The return from ServiceChange is empty except when the Root
<br>> > > > terminationID is used.&nbsp; In that case it includes the following
<br>> > > > parameters as required:"
<br>> > > >
<br>> > > > Thanks,
<br>> > > > Glauco
<br>> > > >
<br>> > > > _______________________________________________
<br>> > > > Megaco mailing list
<br>> > > > Megaco@ietf.org <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>
<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>
<br>>
<br>> --
<br>>
<br>> ------------------------------------------------------------
<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:732.949.5628&nbsp;&nbsp; Fax:732.949.7016
<br>> Lucent Technologies/INS/Voice Over IP Access Networks
<br>> Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
<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>
<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>

--------------68BD87654B52B6166157A630--



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



From megaco-admin@ietf.org  Fri Apr 19 12:15: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 MAA27044
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 12:15:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20742;
	Fri, 19 Apr 2002 11:51:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20716
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 11:51:23 -0400 (EDT)
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 LAA24669
	for <megaco@ietf.org>; Fri, 19 Apr 2002 11:51:20 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3JFopL14914;
	Fri, 19 Apr 2002 11:50:51 -0400 (EDT)
Received: from lucent.com (tla.lra.lucent.com [192.11.62.234])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA26689;
	Fri, 19 Apr 2002 11:51:31 -0400 (EDT)
Message-ID: <3CC03C05.6E10F89A@lucent.com>
Date: Fri, 19 Apr 2002 11:47:18 -0400
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: vbajaj@hss.hns.com, Al Varney <varney@ieee.org>, megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <65256BA0.00178569.00@sandesh.hss.hns.com> <3CBFA31E.D0FB8548@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------71A0DFBC6CA159359A947382"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------71A0DFBC6CA159359A947382
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Christian
Good point.  I missed the relevance of the ServiceState property in 7.1.5.  There is
states that "in service" is default.  While Service State is not defined to be
precisely the same as ServiceChange forced and restart (maybe it should be for a
termination), I agree that this default indicates the intention defaulting to
inservice.  Thus I think that my assumption #1 is the more consistent.  I still think
that the link between ServiceState and ServiceChange for a termination is ambiguous
enough that it would be helpful to restate the assumption in 7.2.8.

I propose we add the following to 7.2.8 at the end of the current Restart entry:

"When applied to ROOT, this specifies that the Media Gateway as a whole will be in
service and includes all its physical terminations which will be in their default
state ("in service").  Exceptions can be indicated by additional ServiceChange
commands."

As Vikas points out, most uses of wildcard ALL assumes that MGC knows the range of
valid terminationIDs for the GW.  Packages have been proposed (but not yet approved)
for MGC to discover this range if it is not known from provisioning.  Sending
individual (non-wildcard) ServiceChange for every distinct physical termination would
be legal but impractical for most large MGs.

Al Varney asked:

>  Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> interface(s) are all operational?  If it makes sense to positively assert
> SVC(restart) on physical terminations, why wouldn't it also make sense to
> indicate availability of ephemeral interfaces?  I'm thinking particularly
> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>

There has been previous discussions about the applicability of ServiceChange for
ephemerals.  While there is nothing stating that one could not use ServiceChange to
take an ephemeral out of service, but since it would then be subtracted from any
context it was in, it would cease to exist and so could never be "restarted".  Clearly
serviceChange cannot be used to indicate whether an ephemeral Add will succeed or not
(availability of any underlying network or gateway resources).  I think that the
assumption is that if a GW is in service then any ephemeral Add can be attempted.
Failure of an underlying network can be indicated using nt/netfail, but since events
are only set on terminations, one must Add an ephemeral before such an event can be
used.

I think we currently have no good way to announce that the MG is in service but one or
more classes of ephemerals are unavailable.  I think that a specific error to indicate
this after an Add attempt might be sufficient (I don't believe that there is a good
one now).


Christian Groves wrote:

> G'Day Vikas,
>
> I believe you are getting what you asked for. The default state of all
> terminaton is "inservice".
> If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can assume
> that:
> o as the MG is running and
> o a MG contains terminations and
> o the termination's natural state is "inservice"
> therefore the individual terminations are running also.
>
> Regards, Christian
>
> vbajaj@hss.hns.com wrote:
> >
> > Al,
> >        The advantage you have cited below will hold true only under the
> > assumption
> >   that MG sends ServiceChange for individual terminations instead of using a
> > wildcard.
> >   Sending ServiceChange for individual terminations would be too expensive in
> > terms
> >   of network bandwidth as well as MG processing for extremely large sized
> > Gateways.
> >   I would expect that if MGC is interested in finding out configuration
> > inconsistencies
> >   with its MGs, it would do an Audit at lesiure in parallel to handling normal
> > calls.
> >
> >  IMHO, "ServiceChange on ROOT" should indicate all terminations are up at the
> > MG.
> >  ServiceChange for Out Of Service Terminations can be sent subsequently. Total
> > number of messages required in this scenario would be
> > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
> > terminations)
> >
> > Even if we go by approach #2 suggested below, the latter step (i.e. sending
> > ServiceChange
> > for Out Of Service Terminations) will anyway have to be executed.
> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded Termination Id
> > to indicate that all terminations in the MG are In Service, it will need to send
> >  Out of Service ServiceChange for those terminations that have been configured
> >  but not hardware equipped. The number of messages required in this scenario
> > would be
> >
> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> > ServiceChange
> >   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
> >
> > The MG may of course choose not to use a wildcarded
> > termination signifiying all terminations on the MG and instead use multiple
> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that siginfies a
> > DS0 aggregation. In this case, the number of ServiceChange commands would equal
> > the number of such DS0 aggregations in the MG i.e. several ServiceChange
> > messages
> >  would be needed to complete the initial MG-MGC startup sequence. The number of
> >  messages required in this scenario would be
> >
> > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
> > terminations
> >     (Term Id = "/TG!/Fac1/*))
> >
> > {Assuming most of the terminations in MG would be In Service, n could be a large
> > value unless
> >   the MG is intelligent and can optimize on the number of messages}
> >
> > To summarize, IMO that number of (ServiceChange) messages required at startup
> >  would turn out to be larger in approach #2 than in approach #1. So, why not
> > choose
> >  a strategy that is optimal ?
> >
> > Rgds,
> >
> > Vikas Bajaj
> > NGN Group
> > Hughes Software Systems
> > (www.hssworld.com)
> >
> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> >
> > To:   megaco@ietf.org
> > cc:    (bcc: Vikas Bajaj/HSS)
> >
> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)
> >
> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> > >Possible clarifications:
> > >ServiceChange on ROOT with method=restart (a registration):
> > >1) implies that all physical terminations on MG are also up.  Exceptions
> > >should be indicated by additional ServiceChanges on the down terminations
> > >using Forced, preferrably in the same message and using wildcards where
> > >possible.
> > >2) implies that all physical terminations on MG are down.  Those that are up
> > >will be indicated by additional ServiceChanges on the up terminations using
> > >method=restart, preferrably in the same message and using wildcards were
> > >possible.
> >
> > ...
> >
> > >Even though I think that most GWs probably would not register until all or
> > >most of their physical terminations are available, I would probably prefer
> > >#2 since I can easily indicated them all up with only one additional
> > >ServiceChange and it seems more natural to indicate those up those that are
> > >down.  But I can be happy with either #1 or #2.
> >
> >     #2 has the added (slight?) advantage that physical termination ID
> > mis-matches (between MGC and MG) are identified when the MG sends
> > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
> > discovering these (non-existent) terminations 1 at a time, when connections
> > are attempted.  With #1, a mis-match of this type might go undetected for
> > days, until the MGC attempted to use/audit that particular termination ID.
> >
> >     Terminations known only to the MGC will still go "undetected", but
> > since no SVC(restart) is ever received for them, at least the MGC would not
> > be trying to use them.  An audit might eventually reveal the reason for the
> > OOS terminations.  (It is not unusual in "old" voice switches to have
> > termination data populated without having the hardware yet in place, so a
> > mis-match cannot be considered an error in all cases.)
> >
> >     Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> > interface(s) are all operational?  If it makes sense to positively assert
> > SVC(restart) on physical terminations, why wouldn't it also make sense to
> > indicate availability of ephemeral interfaces?  I'm thinking particularly
> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> >
> >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
> > big burden after MG restart.  If SVC is needed for every individual
> > physical termination, then #1 becomes attractive.
> >
> > Al Varney
> >
> > _______________________________________________
> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------71A0DFBC6CA159359A947382
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------71A0DFBC6CA159359A947382--


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


From daemon@ns.ietf.org  Fri Apr 19 12:15: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 MAA27053
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 12:15:48 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA23267
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 12:15:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20742;
	Fri, 19 Apr 2002 11:51:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20716
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 11:51:23 -0400 (EDT)
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 LAA24669
	for <megaco@ietf.org>; Fri, 19 Apr 2002 11:51:20 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3JFopL14914;
	Fri, 19 Apr 2002 11:50:51 -0400 (EDT)
Received: from lucent.com (tla.lra.lucent.com [192.11.62.234])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id LAA26689;
	Fri, 19 Apr 2002 11:51:31 -0400 (EDT)
Message-ID: <3CC03C05.6E10F89A@lucent.com>
Date: Fri, 19 Apr 2002 11:47:18 -0400
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: vbajaj@hss.hns.com, Al Varney <varney@ieee.org>, megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
References: <65256BA0.00178569.00@sandesh.hss.hns.com> <3CBFA31E.D0FB8548@ericsson.com.au>
Content-Type: multipart/mixed;
 boundary="------------71A0DFBC6CA159359A947382"
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------71A0DFBC6CA159359A947382
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Christian
Good point.  I missed the relevance of the ServiceState property in 7.1.5.  There is
states that "in service" is default.  While Service State is not defined to be
precisely the same as ServiceChange forced and restart (maybe it should be for a
termination), I agree that this default indicates the intention defaulting to
inservice.  Thus I think that my assumption #1 is the more consistent.  I still think
that the link between ServiceState and ServiceChange for a termination is ambiguous
enough that it would be helpful to restate the assumption in 7.2.8.

I propose we add the following to 7.2.8 at the end of the current Restart entry:

"When applied to ROOT, this specifies that the Media Gateway as a whole will be in
service and includes all its physical terminations which will be in their default
state ("in service").  Exceptions can be indicated by additional ServiceChange
commands."

As Vikas points out, most uses of wildcard ALL assumes that MGC knows the range of
valid terminationIDs for the GW.  Packages have been proposed (but not yet approved)
for MGC to discover this range if it is not known from provisioning.  Sending
individual (non-wildcard) ServiceChange for every distinct physical termination would
be legal but impractical for most large MGs.

Al Varney asked:

>  Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> interface(s) are all operational?  If it makes sense to positively assert
> SVC(restart) on physical terminations, why wouldn't it also make sense to
> indicate availability of ephemeral interfaces?  I'm thinking particularly
> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>

There has been previous discussions about the applicability of ServiceChange for
ephemerals.  While there is nothing stating that one could not use ServiceChange to
take an ephemeral out of service, but since it would then be subtracted from any
context it was in, it would cease to exist and so could never be "restarted".  Clearly
serviceChange cannot be used to indicate whether an ephemeral Add will succeed or not
(availability of any underlying network or gateway resources).  I think that the
assumption is that if a GW is in service then any ephemeral Add can be attempted.
Failure of an underlying network can be indicated using nt/netfail, but since events
are only set on terminations, one must Add an ephemeral before such an event can be
used.

I think we currently have no good way to announce that the MG is in service but one or
more classes of ephemerals are unavailable.  I think that a specific error to indicate
this after an Add attempt might be sufficient (I don't believe that there is a good
one now).


Christian Groves wrote:

> G'Day Vikas,
>
> I believe you are getting what you asked for. The default state of all
> terminaton is "inservice".
> If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can assume
> that:
> o as the MG is running and
> o a MG contains terminations and
> o the termination's natural state is "inservice"
> therefore the individual terminations are running also.
>
> Regards, Christian
>
> vbajaj@hss.hns.com wrote:
> >
> > Al,
> >        The advantage you have cited below will hold true only under the
> > assumption
> >   that MG sends ServiceChange for individual terminations instead of using a
> > wildcard.
> >   Sending ServiceChange for individual terminations would be too expensive in
> > terms
> >   of network bandwidth as well as MG processing for extremely large sized
> > Gateways.
> >   I would expect that if MGC is interested in finding out configuration
> > inconsistencies
> >   with its MGs, it would do an Audit at lesiure in parallel to handling normal
> > calls.
> >
> >  IMHO, "ServiceChange on ROOT" should indicate all terminations are up at the
> > MG.
> >  ServiceChange for Out Of Service Terminations can be sent subsequently. Total
> > number of messages required in this scenario would be
> > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
> > terminations)
> >
> > Even if we go by approach #2 suggested below, the latter step (i.e. sending
> > ServiceChange
> > for Out Of Service Terminations) will anyway have to be executed.
> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded Termination Id
> > to indicate that all terminations in the MG are In Service, it will need to send
> >  Out of Service ServiceChange for those terminations that have been configured
> >  but not hardware equipped. The number of messages required in this scenario
> > would be
> >
> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> > ServiceChange
> >   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
> >
> > The MG may of course choose not to use a wildcarded
> > termination signifiying all terminations on the MG and instead use multiple
> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that siginfies a
> > DS0 aggregation. In this case, the number of ServiceChange commands would equal
> > the number of such DS0 aggregations in the MG i.e. several ServiceChange
> > messages
> >  would be needed to complete the initial MG-MGC startup sequence. The number of
> >  messages required in this scenario would be
> >
> > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
> > terminations
> >     (Term Id = "/TG!/Fac1/*))
> >
> > {Assuming most of the terminations in MG would be In Service, n could be a large
> > value unless
> >   the MG is intelligent and can optimize on the number of messages}
> >
> > To summarize, IMO that number of (ServiceChange) messages required at startup
> >  would turn out to be larger in approach #2 than in approach #1. So, why not
> > choose
> >  a strategy that is optimal ?
> >
> > Rgds,
> >
> > Vikas Bajaj
> > NGN Group
> > Hughes Software Systems
> > (www.hssworld.com)
> >
> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> >
> > To:   megaco@ietf.org
> > cc:    (bcc: Vikas Bajaj/HSS)
> >
> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)
> >
> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> > >Possible clarifications:
> > >ServiceChange on ROOT with method=restart (a registration):
> > >1) implies that all physical terminations on MG are also up.  Exceptions
> > >should be indicated by additional ServiceChanges on the down terminations
> > >using Forced, preferrably in the same message and using wildcards where
> > >possible.
> > >2) implies that all physical terminations on MG are down.  Those that are up
> > >will be indicated by additional ServiceChanges on the up terminations using
> > >method=restart, preferrably in the same message and using wildcards were
> > >possible.
> >
> > ...
> >
> > >Even though I think that most GWs probably would not register until all or
> > >most of their physical terminations are available, I would probably prefer
> > >#2 since I can easily indicated them all up with only one additional
> > >ServiceChange and it seems more natural to indicate those up those that are
> > >down.  But I can be happy with either #1 or #2.
> >
> >     #2 has the added (slight?) advantage that physical termination ID
> > mis-matches (between MGC and MG) are identified when the MG sends
> > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
> > discovering these (non-existent) terminations 1 at a time, when connections
> > are attempted.  With #1, a mis-match of this type might go undetected for
> > days, until the MGC attempted to use/audit that particular termination ID.
> >
> >     Terminations known only to the MGC will still go "undetected", but
> > since no SVC(restart) is ever received for them, at least the MGC would not
> > be trying to use them.  An audit might eventually reveal the reason for the
> > OOS terminations.  (It is not unusual in "old" voice switches to have
> > termination data populated without having the hardware yet in place, so a
> > mis-match cannot be considered an error in all cases.)
> >
> >     Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> > interface(s) are all operational?  If it makes sense to positively assert
> > SVC(restart) on physical terminations, why wouldn't it also make sense to
> > indicate availability of ephemeral interfaces?  I'm thinking particularly
> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> >
> >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
> > big burden after MG restart.  If SVC is needed for every individual
> > physical termination, then #1 becomes attractive.
> >
> > Al Varney
> >
> > _______________________________________________
> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla


--------------71A0DFBC6CA159359A947382
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------71A0DFBC6CA159359A947382--


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



From megaco-admin@ietf.org  Fri Apr 19 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 MAA02440
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 12:49:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23962;
	Fri, 19 Apr 2002 12:29:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23931
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 12:29:05 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29092
	for <megaco@ietf.org>; Fri, 19 Apr 2002 12:29:01 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3JGLGK01325;
	Fri, 19 Apr 2002 12:21:16 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Terry L Anderson'" <tla@lucent.com>,
        "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: <vbajaj@hss.hns.com>, "'Al Varney'" <varney@ieee.org>, <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
Date: Fri, 19 Apr 2002 12:21:42 -0400
Message-ID: <002a01c1e7be$4affb8c0$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.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <3CC03C05.6E10F89A@lucent.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

This proposal sounds good. But to make it absolutely unambiguous you
could specify:

"When applied to ROOT, this specifies that the Media Gateway as a whole
will be in service and includes all its physical terminations which will
be in their default Service State ("in service").  Exceptions can be
indicated by additional ServiceChange commands."
^^^^^^^

-- Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Terry L Anderson
Sent: Friday, April 19, 2002 11:47 AM
To: Christian Groves
Cc: vbajaj@hss.hns.com; Al Varney; megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
Start)


Christian
Good point.  I missed the relevance of the ServiceState property in
7.1.5.  There is states that "in service" is default.  While Service
State is not defined to be precisely the same as ServiceChange forced
and restart (maybe it should be for a termination), I agree that this
default indicates the intention defaulting to inservice.  Thus I think
that my assumption #1 is the more consistent.  I still think that the
link between ServiceState and ServiceChange for a termination is
ambiguous enough that it would be helpful to restate the assumption in
7.2.8.

I propose we add the following to 7.2.8 at the end of the current
Restart entry:

"When applied to ROOT, this specifies that the Media Gateway as a whole
will be in service and includes all its physical terminations which will
be in their default state ("in service").  Exceptions can be indicated
by additional ServiceChange commands."

As Vikas points out, most uses of wildcard ALL assumes that MGC knows
the range of valid terminationIDs for the GW.  Packages have been
proposed (but not yet approved) for MGC to discover this range if it is
not known from provisioning.  Sending individual (non-wildcard)
ServiceChange for every distinct physical termination would be legal but
impractical for most large MGs.

Al Varney asked:

>  Is there an assumption that MG SVC(ROOT,restart) implies the 
> ephemeral
> interface(s) are all operational?  If it makes sense to positively
assert
> SVC(restart) on physical terminations, why wouldn't it also make sense
to
> indicate availability of ephemeral interfaces?  I'm thinking
particularly
> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>

There has been previous discussions about the applicability of
ServiceChange for ephemerals.  While there is nothing stating that one
could not use ServiceChange to take an ephemeral out of service, but
since it would then be subtracted from any context it was in, it would
cease to exist and so could never be "restarted".  Clearly serviceChange
cannot be used to indicate whether an ephemeral Add will succeed or not
(availability of any underlying network or gateway resources).  I think
that the assumption is that if a GW is in service then any ephemeral Add
can be attempted. Failure of an underlying network can be indicated
using nt/netfail, but since events are only set on terminations, one
must Add an ephemeral before such an event can be used.

I think we currently have no good way to announce that the MG is in
service but one or more classes of ephemerals are unavailable.  I think
that a specific error to indicate this after an Add attempt might be
sufficient (I don't believe that there is a good one now).


Christian Groves wrote:

> G'Day Vikas,
>
> I believe you are getting what you asked for. The default state of all

> terminaton is "inservice". If the MG cold starts and sends 
> ServiceChange on "ROOT" then the MGC can assume
> that:
> o as the MG is running and
> o a MG contains terminations and
> o the termination's natural state is "inservice"
> therefore the individual terminations are running also.
>
> Regards, Christian
>
> vbajaj@hss.hns.com wrote:
> >
> > Al,
> >        The advantage you have cited below will hold true only under 
> > the assumption
> >   that MG sends ServiceChange for individual terminations instead of

> > using a wildcard.
> >   Sending ServiceChange for individual terminations would be too 
> > expensive in terms
> >   of network bandwidth as well as MG processing for extremely large 
> > sized Gateways.
> >   I would expect that if MGC is interested in finding out 
> > configuration inconsistencies
> >   with its MGs, it would do an Audit at lesiure in parallel to 
> > handling normal calls.
> >
> >  IMHO, "ServiceChange on ROOT" should indicate all terminations are 
> > up at the MG.  ServiceChange for Out Of Service Terminations can be 
> > sent subsequently. Total number of messages required in this 
> > scenario would be (1 ServiceChange on ROOT + x ServiceChange for 
> > configured but unequipped
> > terminations)
> >
> > Even if we go by approach #2 suggested below, the latter step (i.e. 
> > sending ServiceChange for Out Of Service Terminations) will anyway 
> > have to be executed.  Subsequent to a ServiceChange on ROOT, if MG 
> > uses Wildcarded Termination Id to indicate that all terminations in 
> > the MG are In Service, it will need to send  Out of Service 
> > ServiceChange for those terminations that have been configured  but 
> > not hardware equipped. The number of messages required in this 
> > scenario would be
> >
> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ 
> > n ServiceChange
> >   for configured but unequipped terminations (Term Id = 
> > "/TG!/Fac1/*))
> >
> > The MG may of course choose not to use a wildcarded termination 
> > signifiying all terminations on the MG and instead use multiple 
> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that 
> > siginfies a DS0 aggregation. In this case, the number of 
> > ServiceChange commands would equal the number of such DS0 
> > aggregations in the MG i.e. several ServiceChange messages  would be

> > needed to complete the initial MG-MGC startup sequence. The number 
> > of  messages required in this scenario would be
> >
> > (1 ServiceChange on ROOT + n ServiceChange for configured and 
> > equipped terminations
> >     (Term Id = "/TG!/Fac1/*))
> >
> > {Assuming most of the terminations in MG would be In Service, n 
> > could be a large value unless
> >   the MG is intelligent and can optimize on the number of messages}
> >
> > To summarize, IMO that number of (ServiceChange) messages required 
> > at startup  would turn out to be larger in approach #2 than in 
> > approach #1. So, why not choose  a strategy that is optimal ?
> >
> > Rgds,
> >
> > Vikas Bajaj
> > NGN Group
> > Hughes Software Systems
> > (www.hssworld.com)
> >
> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> >
> > To:   megaco@ietf.org
> > cc:    (bcc: Vikas Bajaj/HSS)
> >
> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold

> > Start)
> >
> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> > >Possible clarifications:
> > >ServiceChange on ROOT with method=restart (a registration):
> > >1) implies that all physical terminations on MG are also up.  
> > >Exceptions should be indicated by additional ServiceChanges on the 
> > >down terminations using Forced, preferrably in the same message and

> > >using wildcards where possible.
> > >2) implies that all physical terminations on MG are down.  Those 
> > >that are up will be indicated by additional ServiceChanges on the 
> > >up terminations using method=restart, preferrably in the same 
> > >message and using wildcards were possible.
> >
> > ...
> >
> > >Even though I think that most GWs probably would not register until

> > >all or most of their physical terminations are available, I would 
> > >probably prefer #2 since I can easily indicated them all up with 
> > >only one additional ServiceChange and it seems more natural to 
> > >indicate those up those that are down.  But I can be happy with 
> > >either #1 or #2.
> >
> >     #2 has the added (slight?) advantage that physical termination 
> > ID mis-matches (between MGC and MG) are identified when the MG sends
> > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on 
> > MGC discovering these (non-existent) terminations 1 at a time, when 
> > connections are attempted.  With #1, a mis-match of this type might 
> > go undetected for days, until the MGC attempted to use/audit that 
> > particular termination ID.
> >
> >     Terminations known only to the MGC will still go "undetected", 
> > but since no SVC(restart) is ever received for them, at least the 
> > MGC would not be trying to use them.  An audit might eventually 
> > reveal the reason for the OOS terminations.  (It is not unusual in 
> > "old" voice switches to have termination data populated without 
> > having the hardware yet in place, so a mis-match cannot be 
> > considered an error in all cases.)
> >
> >     Is there an assumption that MG SVC(ROOT,restart) implies the 
> > ephemeral
> > interface(s) are all operational?  If it makes sense to positively
assert
> > SVC(restart) on physical terminations, why wouldn't it also make
sense to
> > indicate availability of ephemeral interfaces?  I'm thinking
particularly
> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> >
> >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is 
> > not a big burden after MG restart.  If SVC is needed for every 
> > individual physical termination, then #1 becomes attractive.
> >
> > Al Varney
> >
> > _______________________________________________
> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
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  Fri Apr 19 12: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 MAA02450
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 12:49:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA25313
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 12:49:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23962;
	Fri, 19 Apr 2002 12:29:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23931
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 12:29:05 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29092
	for <megaco@ietf.org>; Fri, 19 Apr 2002 12:29:01 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3JGLGK01325;
	Fri, 19 Apr 2002 12:21:16 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Terry L Anderson'" <tla@lucent.com>,
        "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: <vbajaj@hss.hns.com>, "'Al Varney'" <varney@ieee.org>, <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold Start)
Date: Fri, 19 Apr 2002 12:21:42 -0400
Message-ID: <002a01c1e7be$4affb8c0$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.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <3CC03C05.6E10F89A@lucent.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

This proposal sounds good. But to make it absolutely unambiguous you
could specify:

"When applied to ROOT, this specifies that the Media Gateway as a whole
will be in service and includes all its physical terminations which will
be in their default Service State ("in service").  Exceptions can be
indicated by additional ServiceChange commands."
^^^^^^^

-- Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Terry L Anderson
Sent: Friday, April 19, 2002 11:47 AM
To: Christian Groves
Cc: vbajaj@hss.hns.com; Al Varney; megaco@ietf.org
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
Start)


Christian
Good point.  I missed the relevance of the ServiceState property in
7.1.5.  There is states that "in service" is default.  While Service
State is not defined to be precisely the same as ServiceChange forced
and restart (maybe it should be for a termination), I agree that this
default indicates the intention defaulting to inservice.  Thus I think
that my assumption #1 is the more consistent.  I still think that the
link between ServiceState and ServiceChange for a termination is
ambiguous enough that it would be helpful to restate the assumption in
7.2.8.

I propose we add the following to 7.2.8 at the end of the current
Restart entry:

"When applied to ROOT, this specifies that the Media Gateway as a whole
will be in service and includes all its physical terminations which will
be in their default state ("in service").  Exceptions can be indicated
by additional ServiceChange commands."

As Vikas points out, most uses of wildcard ALL assumes that MGC knows
the range of valid terminationIDs for the GW.  Packages have been
proposed (but not yet approved) for MGC to discover this range if it is
not known from provisioning.  Sending individual (non-wildcard)
ServiceChange for every distinct physical termination would be legal but
impractical for most large MGs.

Al Varney asked:

>  Is there an assumption that MG SVC(ROOT,restart) implies the 
> ephemeral
> interface(s) are all operational?  If it makes sense to positively
assert
> SVC(restart) on physical terminations, why wouldn't it also make sense
to
> indicate availability of ephemeral interfaces?  I'm thinking
particularly
> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>

There has been previous discussions about the applicability of
ServiceChange for ephemerals.  While there is nothing stating that one
could not use ServiceChange to take an ephemeral out of service, but
since it would then be subtracted from any context it was in, it would
cease to exist and so could never be "restarted".  Clearly serviceChange
cannot be used to indicate whether an ephemeral Add will succeed or not
(availability of any underlying network or gateway resources).  I think
that the assumption is that if a GW is in service then any ephemeral Add
can be attempted. Failure of an underlying network can be indicated
using nt/netfail, but since events are only set on terminations, one
must Add an ephemeral before such an event can be used.

I think we currently have no good way to announce that the MG is in
service but one or more classes of ephemerals are unavailable.  I think
that a specific error to indicate this after an Add attempt might be
sufficient (I don't believe that there is a good one now).


Christian Groves wrote:

> G'Day Vikas,
>
> I believe you are getting what you asked for. The default state of all

> terminaton is "inservice". If the MG cold starts and sends 
> ServiceChange on "ROOT" then the MGC can assume
> that:
> o as the MG is running and
> o a MG contains terminations and
> o the termination's natural state is "inservice"
> therefore the individual terminations are running also.
>
> Regards, Christian
>
> vbajaj@hss.hns.com wrote:
> >
> > Al,
> >        The advantage you have cited below will hold true only under 
> > the assumption
> >   that MG sends ServiceChange for individual terminations instead of

> > using a wildcard.
> >   Sending ServiceChange for individual terminations would be too 
> > expensive in terms
> >   of network bandwidth as well as MG processing for extremely large 
> > sized Gateways.
> >   I would expect that if MGC is interested in finding out 
> > configuration inconsistencies
> >   with its MGs, it would do an Audit at lesiure in parallel to 
> > handling normal calls.
> >
> >  IMHO, "ServiceChange on ROOT" should indicate all terminations are 
> > up at the MG.  ServiceChange for Out Of Service Terminations can be 
> > sent subsequently. Total number of messages required in this 
> > scenario would be (1 ServiceChange on ROOT + x ServiceChange for 
> > configured but unequipped
> > terminations)
> >
> > Even if we go by approach #2 suggested below, the latter step (i.e. 
> > sending ServiceChange for Out Of Service Terminations) will anyway 
> > have to be executed.  Subsequent to a ServiceChange on ROOT, if MG 
> > uses Wildcarded Termination Id to indicate that all terminations in 
> > the MG are In Service, it will need to send  Out of Service 
> > ServiceChange for those terminations that have been configured  but 
> > not hardware equipped. The number of messages required in this 
> > scenario would be
> >
> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ 
> > n ServiceChange
> >   for configured but unequipped terminations (Term Id = 
> > "/TG!/Fac1/*))
> >
> > The MG may of course choose not to use a wildcarded termination 
> > signifiying all terminations on the MG and instead use multiple 
> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that 
> > siginfies a DS0 aggregation. In this case, the number of 
> > ServiceChange commands would equal the number of such DS0 
> > aggregations in the MG i.e. several ServiceChange messages  would be

> > needed to complete the initial MG-MGC startup sequence. The number 
> > of  messages required in this scenario would be
> >
> > (1 ServiceChange on ROOT + n ServiceChange for configured and 
> > equipped terminations
> >     (Term Id = "/TG!/Fac1/*))
> >
> > {Assuming most of the terminations in MG would be In Service, n 
> > could be a large value unless
> >   the MG is intelligent and can optimize on the number of messages}
> >
> > To summarize, IMO that number of (ServiceChange) messages required 
> > at startup  would turn out to be larger in approach #2 than in 
> > approach #1. So, why not choose  a strategy that is optimal ?
> >
> > Rgds,
> >
> > Vikas Bajaj
> > NGN Group
> > Hughes Software Systems
> > (www.hssworld.com)
> >
> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> >
> > To:   megaco@ietf.org
> > cc:    (bcc: Vikas Bajaj/HSS)
> >
> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold

> > Start)
> >
> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> > >Possible clarifications:
> > >ServiceChange on ROOT with method=restart (a registration):
> > >1) implies that all physical terminations on MG are also up.  
> > >Exceptions should be indicated by additional ServiceChanges on the 
> > >down terminations using Forced, preferrably in the same message and

> > >using wildcards where possible.
> > >2) implies that all physical terminations on MG are down.  Those 
> > >that are up will be indicated by additional ServiceChanges on the 
> > >up terminations using method=restart, preferrably in the same 
> > >message and using wildcards were possible.
> >
> > ...
> >
> > >Even though I think that most GWs probably would not register until

> > >all or most of their physical terminations are available, I would 
> > >probably prefer #2 since I can easily indicated them all up with 
> > >only one additional ServiceChange and it seems more natural to 
> > >indicate those up those that are down.  But I can be happy with 
> > >either #1 or #2.
> >
> >     #2 has the added (slight?) advantage that physical termination 
> > ID mis-matches (between MGC and MG) are identified when the MG sends
> > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on 
> > MGC discovering these (non-existent) terminations 1 at a time, when 
> > connections are attempted.  With #1, a mis-match of this type might 
> > go undetected for days, until the MGC attempted to use/audit that 
> > particular termination ID.
> >
> >     Terminations known only to the MGC will still go "undetected", 
> > but since no SVC(restart) is ever received for them, at least the 
> > MGC would not be trying to use them.  An audit might eventually 
> > reveal the reason for the OOS terminations.  (It is not unusual in 
> > "old" voice switches to have termination data populated without 
> > having the hardware yet in place, so a mis-match cannot be 
> > considered an error in all cases.)
> >
> >     Is there an assumption that MG SVC(ROOT,restart) implies the 
> > ephemeral
> > interface(s) are all operational?  If it makes sense to positively
assert
> > SVC(restart) on physical terminations, why wouldn't it also make
sense to
> > indicate availability of ephemeral interfaces?  I'm thinking
particularly
> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> >
> >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is 
> > not a big burden after MG restart.  If SVC is needed for every 
> > individual physical termination, then #1 becomes attractive.
> >
> > Al Varney
> >
> > _______________________________________________
> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
Lucent Technologies/INS/Voice Over IP Access Networks
Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
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  Fri Apr 19 12:53: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 MAA02925
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 12:53:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23876;
	Fri, 19 Apr 2002 12:27:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23848
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 12:27:40 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28898
	for <megaco@ietf.org>; Fri, 19 Apr 2002 12:27:32 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3JGRGK03733;
	Fri, 19 Apr 2002 12:27:16 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <girirs@netlab.hcltech.com>
Cc: <megaco@ietf.org>
Subject: RE: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
Date: Fri, 19 Apr 2002 12:27:43 -0400
Message-ID: <002b01c1e7bf$21930ea0$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.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <3CBFDB9B.A0EBA6FC@netlab.hcltech.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

The list of provisioned MGCs is a superset of list of active MGCs. In
other words, all provisioned MGCs need not be active at all the time.
And your understanding is correct about 'atmost one active MGC per
virtual MG' and they all combine to form the list of active MGCs.

The provisioned MGCs are created/maintained by the NMS to instruct the
MG to contact them in case they cannot communicate with the primary
(active) MGC.

Thanks
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Giri Rajasekhar Saladi
Sent: Friday, April 19, 2002 4:56 AM
To: Balasubramanian Pitchandi
Cc: megaco@ietf.org
Subject: Re: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress


Hi Bala/All,
	Are the list of provisioned MGCs and the list of active
MGCs same? I thought that the controller table corresponds to the list
of provisioned MGCs of all virtual MGs. And at any given point of time,
one(atmost) MGC of this list shall be active per virtual MG. Such one
active MGC per every virtual MG form the list of active MGCs. Is my
understanding correct? Thanks & Regds., Giri Balasubramanian Pitchandi
wrote:
> 
> The MG is provisioned with a list of Media Gateway Controllers through

> "medGwyGatewayControllerTable" and if the MG receives a message from 
> any other MGC than the one provisioned in the 
> "medGwyGatewayControllerTable", it would send this NOTIFICATION (Trap 
> -
> medGwyInvalidControllerAddress) to the NMS Manager.
> 
> Thanks
> Bala
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf 
> Of Venkatesh A
> Sent: Thursday, April 18, 2002 3:04 AM
> To: megaco@ietf.org
> Subject: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
> 
> Hi All,
> 
> This is regarding the NOTIFICATION medGwyInvalidControllerAddress in 
> megaco mib.  The draft says that this notfication has to be raised 
> whenever a message is received from a controller that did not match 
> any one valid controller IP address.  Here what is meant by "invalid 
> controller" ???  Does it mean to say the mgc should be present in the 
> pre provisioned list with mg?  In case of mg running on UDP, mg is not

> keeping the ip address of mgc whom it is talking to.  It simply 
> replies to the mgc from where the request came.  So, when / how should

> this NOTIFICATION be raised?
> 
> Thanks
> Venkatesh
> 
> _______________________________________________
> Megaco mailing 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 Apr 19 12:53: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 MAA02936
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 12:53:17 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA25449
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 12:53:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23876;
	Fri, 19 Apr 2002 12:27:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23848
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 12:27:40 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28898
	for <megaco@ietf.org>; Fri, 19 Apr 2002 12:27:32 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3JGRGK03733;
	Fri, 19 Apr 2002 12:27:16 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <girirs@netlab.hcltech.com>
Cc: <megaco@ietf.org>
Subject: RE: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
Date: Fri, 19 Apr 2002 12:27:43 -0400
Message-ID: <002b01c1e7bf$21930ea0$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.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <3CBFDB9B.A0EBA6FC@netlab.hcltech.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

The list of provisioned MGCs is a superset of list of active MGCs. In
other words, all provisioned MGCs need not be active at all the time.
And your understanding is correct about 'atmost one active MGC per
virtual MG' and they all combine to form the list of active MGCs.

The provisioned MGCs are created/maintained by the NMS to instruct the
MG to contact them in case they cannot communicate with the primary
(active) MGC.

Thanks
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Giri Rajasekhar Saladi
Sent: Friday, April 19, 2002 4:56 AM
To: Balasubramanian Pitchandi
Cc: megaco@ietf.org
Subject: Re: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress


Hi Bala/All,
	Are the list of provisioned MGCs and the list of active
MGCs same? I thought that the controller table corresponds to the list
of provisioned MGCs of all virtual MGs. And at any given point of time,
one(atmost) MGC of this list shall be active per virtual MG. Such one
active MGC per every virtual MG form the list of active MGCs. Is my
understanding correct? Thanks & Regds., Giri Balasubramanian Pitchandi
wrote:
> 
> The MG is provisioned with a list of Media Gateway Controllers through

> "medGwyGatewayControllerTable" and if the MG receives a message from 
> any other MGC than the one provisioned in the 
> "medGwyGatewayControllerTable", it would send this NOTIFICATION (Trap 
> -
> medGwyInvalidControllerAddress) to the NMS Manager.
> 
> Thanks
> Bala
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf 
> Of Venkatesh A
> Sent: Thursday, April 18, 2002 3:04 AM
> To: megaco@ietf.org
> Subject: [Megaco] NOTIFICATION - medGwyInvalidControllerAddress
> 
> Hi All,
> 
> This is regarding the NOTIFICATION medGwyInvalidControllerAddress in 
> megaco mib.  The draft says that this notfication has to be raised 
> whenever a message is received from a controller that did not match 
> any one valid controller IP address.  Here what is meant by "invalid 
> controller" ???  Does it mean to say the mgc should be present in the 
> pre provisioned list with mg?  In case of mg running on UDP, mg is not

> keeping the ip address of mgc whom it is talking to.  It simply 
> replies to the mgc from where the request came.  So, when / how should

> this NOTIFICATION be raised?
> 
> Thanks
> Venkatesh
> 
> _______________________________________________
> Megaco mailing 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 Apr 19 13: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 NAA11316
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 13:56:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27128;
	Fri, 19 Apr 2002 13:15:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27101
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 13:15:16 -0400 (EDT)
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 NAA05430
	for <megaco@ietf.org>; Fri, 19 Apr 2002 13:15:14 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3JHEh521690;
	Fri, 19 Apr 2002 13:14:43 -0400 (EDT)
Received: from sramannt-pc (SRAMANNT-PC.ho.lucent.com [135.112.32.220])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with SMTP id NAA28543;
	Fri, 19 Apr 2002 13:15:25 -0400 (EDT)
Message-Id: <200204191715.NAA28543@teton.ho.lucent.com>
X-Sender: sraman2@teton.mh.lucent.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Fri, 19 Apr 2002 13:14:24 -0400
To: Terry L Anderson <tla@lucent.com>,
        Christian Groves <Christian.Groves@ericsson.com.au>
From: Sankar Raman <sraman2@lucent.com>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
  Start)
Cc: vbajaj@hss.hns.com, Al Varney <varney@ieee.org>, megaco@ietf.org
In-Reply-To: <3CC03C05.6E10F89A@lucent.com>
References: <65256BA0.00178569.00@sandesh.hss.hns.com>
 <3CBFA31E.D0FB8548@ericsson.com.au>
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

Terry:

In my expereince working with different swicthes and gateways,
typical internal implementation of these boxes are such that when
the box comes up, all T1 lines are asumed down untill they come up
in which case the T1 framer chip notifies this event to the upper layers.
Typical implementation is such that when the T1 hardware is reset, no
events will be generated until a line comes up. Line down evets are
generated by T1 hardware only if the line was up before.
This means, if a MGC asssumes on registation, that all lines are up, and
if certain do not come up at the MG, the MG will not be able to indicate
this to
the MGC, unless the MG implelements periodic polling of some sort. 

I feel, it is better, that default state for physical terminations,
when MGC registers with ROOT in service, should be out of service.
Upon registration, the MGC assumes all lines are down until explicitly
indicated
by service change by the MG for the physical lines. As lines come up
at the MG, the MG will send svcchg in svc for each as it happens.
This will be simpler for MGs and go with their typical internal
implementation.
(although it may generate more traffic which can be cut down by using wildcard
for the lines).

Also, this way MGs do not have to worry about how long should it wait for
all lines
to come up before registering with MGC. Some lines may never come up due to
some
fault at the far end switch or may come up much later than some other lines.
 
At 11:47 AM 4/19/02 -0400, Terry L Anderson wrote:
>Christian
>Good point.  I missed the relevance of the ServiceState property in 7.1.5.
 There is
>states that "in service" is default.  While Service State is not defined
to be
>precisely the same as ServiceChange forced and restart (maybe it should be
for a
>termination), I agree that this default indicates the intention defaulting to
>inservice.  Thus I think that my assumption #1 is the more consistent.  I
still think
>that the link between ServiceState and ServiceChange for a termination is
ambiguous

>enough that it would be helpful to restate the assumption in 7.2.8.
>
>I propose we add the following to 7.2.8 at the end of the current Restart
entry:
>
>"When applied to ROOT, this specifies that the Media Gateway as a whole
will be in
>service and includes all its physical terminations which will be in their
default
>state ("in service").  Exceptions can be indicated by additional
ServiceChange
>commands."
>
>As Vikas points out, most uses of wildcard ALL assumes that MGC knows the
range of
>valid terminationIDs for the GW.  Packages have been proposed (but not yet
approved)
>for MGC to discover this range if it is not known from provisioning.  Sending
>individual (non-wildcard) ServiceChange for every distinct physical
termination would
>be legal but impractical for most large MGs.
>
>Al Varney asked:
>
>>  Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
>> interface(s) are all operational?  If it makes sense to positively assert
>> SVC(restart) on physical terminations, why wouldn't it also make sense to
>> indicate availability of ephemeral interfaces?  I'm thinking particularly
>> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>>
>
>There has been previous discussions about the applicability of
ServiceChange for
>ephemerals.  While there is nothing stating that one could not use
ServiceChange to
>take an ephemeral out of service, but since it would then be subtracted
from any
>context it was in, it would cease to exist and so could never be
"restarted".  Clearly
>serviceChange cannot be used to indicate whether an ephemeral Add will
succeed or not
>(availability of any underlying network or gateway resources).  I think
that the
>assumption is that if a GW is in service then any ephemeral Add can be
attempted.
>Failure of an underlying network can be indicated using nt/netfail, but
since events
>are only set on terminations, one must Add an ephemeral before such an
event can be
>used.
>
>I think we currently have no good way to announce that the MG is in
service but one or
>more classes of ephemerals are unavailable.  I think that a specific error
to indicate
>this after an Add attempt might be sufficient (I don't believe that there
is a good
>one now).
>
>
>Christian Groves wrote:
>
>> G'Day Vikas,
>>
>> I believe you are getting what you asked for. The default state of all
>> terminaton is "inservice".
>> If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can
assume
>> that:
>> o as the MG is running and
>> o a MG contains terminations and
>> o the termination's natural state is "inservice"

>> therefore the individual terminations are running also.
>>
>> Regards, Christian
>>
>> vbajaj@hss.hns.com wrote:
>> >
>> > Al,
>> >        The advantage you have cited below will hold true only under the
>> > assumption
>> >   that MG sends ServiceChange for individual terminations instead of
using a
>> > wildcard.
>> >   Sending ServiceChange for individual terminations would be too
expensive in
>> > terms
>> >   of network bandwidth as well as MG processing for extremely large sized
>> > Gateways.
>> >   I would expect that if MGC is interested in finding out configuration
>> > inconsistencies
>> >   with its MGs, it would do an Audit at lesiure in parallel to
handling normal
>> > calls.
>> >
>> >  IMHO, "ServiceChange on ROOT" should indicate all terminations are up
at the
>> > MG.
>> >  ServiceChange for Out Of Service Terminations can be sent
subsequently. Total
>> > number of messages required in this scenario would be
>> > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
>> > terminations)
>> >
>> > Even if we go by approach #2 suggested below, the latter step (i.e.
sending
>> > ServiceChange
>> > for Out Of Service Terminations) will anyway have to be executed.
>> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded
Termination Id
>> > to indicate that all terminations in the MG are In Service, it will
need to send
>> >  Out of Service ServiceChange for those terminations that have been
configured
>> >  but not hardware equipped. The number of messages required in this
scenario
>> > would be
>> >
>> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
>> > ServiceChange
>> >   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
>> >
>> > The MG may of course choose not to use a wildcarded
>> > termination signifiying all terminations on the MG and instead use
multiple
>> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that
siginfies a
>> > DS0 aggregation. In this case, the number of ServiceChange commands
would equal
>> > the number of such DS0 aggregations in the MG i.e. several ServiceChange
>> > messages
>> >  would be needed to complete the initial MG-MGC startup sequence. The
number of
>> >  messages required in this scenario would be
>> >
>> > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
>> > terminations
>> >     (Term Id = "/TG!/Fac1/*))
>> >
>> > {Assuming most of the terminations in MG would be In Service, n could
be a large
>> > value unless
>> >   the MG is intelligent and can optimize on the number of messages}
>> >
>> > To summarize, IMO that number of (ServiceChange) messages required at
startup
>> >  would turn out to be larger in approach #2 than in approach #1. So,
why not
>> > choose
>> >  a strategy that is optimal ?
>> >
>> > Rgds,
>> >
>> > Vikas Bajaj
>> > NGN Group
>> > Hughes Software Systems
>> > (www.hssworld.com)
>> >
>> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
>> >
>> > To:   megaco@ietf.org
>> > cc:    (bcc: Vikas Bajaj/HSS)
>> >
>> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold
Start)
>> >

>> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
>> > >Possible clarifications:
>> > >ServiceChange on ROOT with method=restart (a registration):
>> > >1) implies that all physical terminations on MG are also up.  Exceptions
>> > >should be indicated by additional ServiceChanges on the down
terminations
>> > >using Forced, preferrably in the same message and using wildcards where
>> > >possible.
>> > >2) implies that all physical terminations on MG are down.  Those that
are up
>> > >will be indicated by additional ServiceChanges on the up terminations
using
>> > >method=restart, preferrably in the same message and using wildcards were
>> > >possible.
>> >
>> > ...
>> >
>> > >Even though I think that most GWs probably would not register until
all or
>> > >most of their physical terminations are available, I would probably
prefer
>> > >#2 since I can easily indicated them all up with only one additional
>> > >ServiceChange and it seems more natural to indicate those up those
that are
>> > >down.  But I can be happy with either #1 or #2.
>> >
>> >     #2 has the added (slight?) advantage that physical termination ID
>> > mis-matches (between MGC and MG) are identified when the MG sends
>> > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
>> > discovering these (non-existent) terminations 1 at a time, when
connections
>> > are attempted.  With #1, a mis-match of this type might go undetected for
>> > days, until the MGC attempted to use/audit that particular termination
ID.
>> >
>> >     Terminations known only to the MGC will still go "undetected", but
>> > since no SVC(restart) is ever received for them, at least the MGC
would not
>> > be trying to use them.  An audit might eventually reveal the reason
for the
>> > OOS terminations.  (It is not unusual in "old" voice switches to have
>> > termination data populated without having the hardware yet in place, so a
>> > mis-match cannot be considered an error in all cases.)
>> >
>> >     Is there an assumption that MG SVC(ROOT,restart) implies the
ephemeral
>> > interface(s) are all operational?  If it makes sense to positively assert
>> > SVC(restart) on physical terminations, why wouldn't it also make sense to
>> > indicate availability of ephemeral interfaces?  I'm thinking particularly
>> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>> >
>> >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
>> > big burden after MG restart.  If SVC is needed for every individual
>> > physical termination, then #1 becomes attractive.
>> >
>> > Al Varney
>> >
>> > _______________________________________________
>> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
>Lucent Technologies/INS/Voice Over IP Access Networks
>Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
>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  Fri Apr 19 13: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 NAA11327
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 13:56:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA00314
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 13:56:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27128;
	Fri, 19 Apr 2002 13:15:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27101
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 13:15:16 -0400 (EDT)
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 NAA05430
	for <megaco@ietf.org>; Fri, 19 Apr 2002 13:15:14 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3JHEh521690;
	Fri, 19 Apr 2002 13:14:43 -0400 (EDT)
Received: from sramannt-pc (SRAMANNT-PC.ho.lucent.com [135.112.32.220])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with SMTP id NAA28543;
	Fri, 19 Apr 2002 13:15:25 -0400 (EDT)
Message-Id: <200204191715.NAA28543@teton.ho.lucent.com>
X-Sender: sraman2@teton.mh.lucent.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Fri, 19 Apr 2002 13:14:24 -0400
To: Terry L Anderson <tla@lucent.com>,
        Christian Groves <Christian.Groves@ericsson.com.au>
From: Sankar Raman <sraman2@lucent.com>
Subject: Re: [Megaco] ServiceChange for a single termination (Cold
  Start)
Cc: vbajaj@hss.hns.com, Al Varney <varney@ieee.org>, megaco@ietf.org
In-Reply-To: <3CC03C05.6E10F89A@lucent.com>
References: <65256BA0.00178569.00@sandesh.hss.hns.com>
 <3CBFA31E.D0FB8548@ericsson.com.au>
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

Terry:

In my expereince working with different swicthes and gateways,
typical internal implementation of these boxes are such that when
the box comes up, all T1 lines are asumed down untill they come up
in which case the T1 framer chip notifies this event to the upper layers.
Typical implementation is such that when the T1 hardware is reset, no
events will be generated until a line comes up. Line down evets are
generated by T1 hardware only if the line was up before.
This means, if a MGC asssumes on registation, that all lines are up, and
if certain do not come up at the MG, the MG will not be able to indicate
this to
the MGC, unless the MG implelements periodic polling of some sort. 

I feel, it is better, that default state for physical terminations,
when MGC registers with ROOT in service, should be out of service.
Upon registration, the MGC assumes all lines are down until explicitly
indicated
by service change by the MG for the physical lines. As lines come up
at the MG, the MG will send svcchg in svc for each as it happens.
This will be simpler for MGs and go with their typical internal
implementation.
(although it may generate more traffic which can be cut down by using wildcard
for the lines).

Also, this way MGs do not have to worry about how long should it wait for
all lines
to come up before registering with MGC. Some lines may never come up due to
some
fault at the far end switch or may come up much later than some other lines.
 
At 11:47 AM 4/19/02 -0400, Terry L Anderson wrote:
>Christian
>Good point.  I missed the relevance of the ServiceState property in 7.1.5.
 There is
>states that "in service" is default.  While Service State is not defined
to be
>precisely the same as ServiceChange forced and restart (maybe it should be
for a
>termination), I agree that this default indicates the intention defaulting to
>inservice.  Thus I think that my assumption #1 is the more consistent.  I
still think
>that the link between ServiceState and ServiceChange for a termination is
ambiguous

>enough that it would be helpful to restate the assumption in 7.2.8.
>
>I propose we add the following to 7.2.8 at the end of the current Restart
entry:
>
>"When applied to ROOT, this specifies that the Media Gateway as a whole
will be in
>service and includes all its physical terminations which will be in their
default
>state ("in service").  Exceptions can be indicated by additional
ServiceChange
>commands."
>
>As Vikas points out, most uses of wildcard ALL assumes that MGC knows the
range of
>valid terminationIDs for the GW.  Packages have been proposed (but not yet
approved)
>for MGC to discover this range if it is not known from provisioning.  Sending
>individual (non-wildcard) ServiceChange for every distinct physical
termination would
>be legal but impractical for most large MGs.
>
>Al Varney asked:
>
>>  Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
>> interface(s) are all operational?  If it makes sense to positively assert
>> SVC(restart) on physical terminations, why wouldn't it also make sense to
>> indicate availability of ephemeral interfaces?  I'm thinking particularly
>> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>>
>
>There has been previous discussions about the applicability of
ServiceChange for
>ephemerals.  While there is nothing stating that one could not use
ServiceChange to
>take an ephemeral out of service, but since it would then be subtracted
from any
>context it was in, it would cease to exist and so could never be
"restarted".  Clearly
>serviceChange cannot be used to indicate whether an ephemeral Add will
succeed or not
>(availability of any underlying network or gateway resources).  I think
that the
>assumption is that if a GW is in service then any ephemeral Add can be
attempted.
>Failure of an underlying network can be indicated using nt/netfail, but
since events
>are only set on terminations, one must Add an ephemeral before such an
event can be
>used.
>
>I think we currently have no good way to announce that the MG is in
service but one or
>more classes of ephemerals are unavailable.  I think that a specific error
to indicate
>this after an Add attempt might be sufficient (I don't believe that there
is a good
>one now).
>
>
>Christian Groves wrote:
>
>> G'Day Vikas,
>>
>> I believe you are getting what you asked for. The default state of all
>> terminaton is "inservice".
>> If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can
assume
>> that:
>> o as the MG is running and
>> o a MG contains terminations and
>> o the termination's natural state is "inservice"

>> therefore the individual terminations are running also.
>>
>> Regards, Christian
>>
>> vbajaj@hss.hns.com wrote:
>> >
>> > Al,
>> >        The advantage you have cited below will hold true only under the
>> > assumption
>> >   that MG sends ServiceChange for individual terminations instead of
using a
>> > wildcard.
>> >   Sending ServiceChange for individual terminations would be too
expensive in
>> > terms
>> >   of network bandwidth as well as MG processing for extremely large sized
>> > Gateways.
>> >   I would expect that if MGC is interested in finding out configuration
>> > inconsistencies
>> >   with its MGs, it would do an Audit at lesiure in parallel to
handling normal
>> > calls.
>> >
>> >  IMHO, "ServiceChange on ROOT" should indicate all terminations are up
at the
>> > MG.
>> >  ServiceChange for Out Of Service Terminations can be sent
subsequently. Total
>> > number of messages required in this scenario would be
>> > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
>> > terminations)
>> >
>> > Even if we go by approach #2 suggested below, the latter step (i.e.
sending
>> > ServiceChange
>> > for Out Of Service Terminations) will anyway have to be executed.
>> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded
Termination Id
>> > to indicate that all terminations in the MG are In Service, it will
need to send
>> >  Out of Service ServiceChange for those terminations that have been
configured
>> >  but not hardware equipped. The number of messages required in this
scenario
>> > would be
>> >
>> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
>> > ServiceChange
>> >   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
>> >
>> > The MG may of course choose not to use a wildcarded
>> > termination signifiying all terminations on the MG and instead use
multiple
>> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that
siginfies a
>> > DS0 aggregation. In this case, the number of ServiceChange commands
would equal
>> > the number of such DS0 aggregations in the MG i.e. several ServiceChange
>> > messages
>> >  would be needed to complete the initial MG-MGC startup sequence. The
number of
>> >  messages required in this scenario would be
>> >
>> > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
>> > terminations
>> >     (Term Id = "/TG!/Fac1/*))
>> >
>> > {Assuming most of the terminations in MG would be In Service, n could
be a large
>> > value unless
>> >   the MG is intelligent and can optimize on the number of messages}
>> >
>> > To summarize, IMO that number of (ServiceChange) messages required at
startup
>> >  would turn out to be larger in approach #2 than in approach #1. So,
why not
>> > choose
>> >  a strategy that is optimal ?
>> >
>> > Rgds,
>> >
>> > Vikas Bajaj
>> > NGN Group
>> > Hughes Software Systems
>> > (www.hssworld.com)
>> >
>> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
>> >
>> > To:   megaco@ietf.org
>> > cc:    (bcc: Vikas Bajaj/HSS)
>> >
>> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold
Start)
>> >

>> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
>> > >Possible clarifications:
>> > >ServiceChange on ROOT with method=restart (a registration):
>> > >1) implies that all physical terminations on MG are also up.  Exceptions
>> > >should be indicated by additional ServiceChanges on the down
terminations
>> > >using Forced, preferrably in the same message and using wildcards where
>> > >possible.
>> > >2) implies that all physical terminations on MG are down.  Those that
are up
>> > >will be indicated by additional ServiceChanges on the up terminations
using
>> > >method=restart, preferrably in the same message and using wildcards were
>> > >possible.
>> >
>> > ...
>> >
>> > >Even though I think that most GWs probably would not register until
all or
>> > >most of their physical terminations are available, I would probably
prefer
>> > >#2 since I can easily indicated them all up with only one additional
>> > >ServiceChange and it seems more natural to indicate those up those
that are
>> > >down.  But I can be happy with either #1 or #2.
>> >
>> >     #2 has the added (slight?) advantage that physical termination ID
>> > mis-matches (between MGC and MG) are identified when the MG sends
>> > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
>> > discovering these (non-existent) terminations 1 at a time, when
connections
>> > are attempted.  With #1, a mis-match of this type might go undetected for
>> > days, until the MGC attempted to use/audit that particular termination
ID.
>> >
>> >     Terminations known only to the MGC will still go "undetected", but
>> > since no SVC(restart) is ever received for them, at least the MGC
would not
>> > be trying to use them.  An audit might eventually reveal the reason
for the
>> > OOS terminations.  (It is not unusual in "old" voice switches to have
>> > termination data populated without having the hardware yet in place, so a
>> > mis-match cannot be considered an error in all cases.)
>> >
>> >     Is there an assumption that MG SVC(ROOT,restart) implies the
ephemeral
>> > interface(s) are all operational?  If it makes sense to positively assert
>> > SVC(restart) on physical terminations, why wouldn't it also make sense to
>> > indicate availability of ephemeral interfaces?  I'm thinking particularly
>> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>> >
>> >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
>> > big burden after MG restart.  If SVC is needed for every individual
>> > physical termination, then #1 becomes attractive.
>> >
>> > Al Varney
>> >
>> > _______________________________________________
>> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
>Lucent Technologies/INS/Voice Over IP Access Networks
>Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
>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  Fri Apr 19 19:23: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 TAA17813
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 19:23:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA16109;
	Fri, 19 Apr 2002 19:03:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA16006
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 19:03:15 -0400 (EDT)
Received: from smtp.comcast.net (smtp.comcast.net [24.153.64.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15844
	for <megaco@ietf.org>; Fri, 19 Apr 2002 19:03:13 -0400 (EDT)
Received: from Sluggo (pcp334822pcs.howard01.md.comcast.net [68.54.127.67])
 by mtaout02.icomcast.net
 (iPlanet Messaging Server 5.1 HotFix 0.3 (built Apr  8 2002))
 with SMTP id <0GUU0004G80IBQ@mtaout02.icomcast.net> for megaco@ietf.org; Fri,
 19 Apr 2002 19:02:44 -0400 (EDT)
Date: Fri, 19 Apr 2002 19:00:00 -0400
From: Root Mean Square <rms@acc.com>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold  Start)
In-reply-to: <200204191715.NAA28543@teton.ho.lucent.com>
To: Sankar Raman <sraman2@lucent.com>, Terry L Anderson <tla@lucent.com>,
        Christian Groves <Christian.Groves@ericsson.com.au>
Cc: vbajaj@hss.hns.com, Al Varney <varney@ieee.org>, megaco@ietf.org
Reply-to: rms@acc.com
Message-id: <PLEEKKMMGAAKNGECENOPAEGICIAA.rms@acc.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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

Sankar,

I think I agree with everything you said.  In our case we have
administrative and operational states for individual interfaces as well as
the gateway as a whole.  If the administrative state of the MG is enabled,
it will attempt to register with the MGC as soon as the MG cold starts.
Individual interfaces may be adminsitratively disabled, or may be in an
alarm or offline condition (e.g., physically removed from the chasis).
Also, most of our interfaces are intelligent peripherals that need to
download their code image after a cold start, and this may take several
seconds, so they do not come online immediately.  We could wait several
seconds after a cold start before attempting to register with the MGC, but
we still need to deal with interfaces that are administratively disabled,
are temporarily out-of-service or have fault conditions pending.

I understand that it would be optimal if the MG only had to send a single
service change on root if all of its terminations are in-service and
operational when it registers with the MGC.  However, making the default
service state in-service has always seemed a little goofy to me.  If the
default state were out-of-service, it may not reflect reality when the MG
sends its initial service change on root, but it doesn't have any adverse
side effects.  On the other hand, making the default state in-service does.

Making the default termination state out-of-service would seem to be more
consistent with how large media gateways in fact operate -- that is, the
service state of the signaling path between the MG and MGC is independent of
the service state of individual terminations.  Using a technique similar to
what Terry Anderson proposes may overcome most of the inefficiences
associated with having to register interfaces or terminations as they come
into service.  In our particular case, I would prefer to establish an
association with the MGC, negotiate the protocol version and profile, and
then deal with which terminations are in-service or not.  I don't think this
can be cleanly done with a single service change command on root -- perhaps
on a residential GW with a couple of terminations, but not on a large
trunking GW with 1000's of terminations.

Cheers,
Ron Stoughton

> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Sankar Raman
> Sent: Friday, April 19, 2002 1:14 PM
> To: Terry L Anderson; Christian Groves
> Cc: vbajaj@hss.hns.com; Al Varney; megaco@ietf.org
> Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
>
> Terry:
>
> In my expereince working with different swicthes and gateways,
> typical internal implementation of these boxes are such that when
> the box comes up, all T1 lines are asumed down untill they come up
> in which case the T1 framer chip notifies this event to the upper layers.
> Typical implementation is such that when the T1 hardware is reset, no
> events will be generated until a line comes up. Line down evets are
> generated by T1 hardware only if the line was up before.
> This means, if a MGC asssumes on registation, that all lines are up, and
> if certain do not come up at the MG, the MG will not be able to indicate
> this to
> the MGC, unless the MG implelements periodic polling of some sort.
>
> I feel, it is better, that default state for physical terminations,
> when MGC registers with ROOT in service, should be out of service.
> Upon registration, the MGC assumes all lines are down until explicitly
> indicated
> by service change by the MG for the physical lines. As lines come up
> at the MG, the MG will send svcchg in svc for each as it happens.
> This will be simpler for MGs and go with their typical internal
> implementation.
> (although it may generate more traffic which can be cut down by
> using wildcard
> for the lines).
>
> Also, this way MGs do not have to worry about how long should it wait for
> all lines
> to come up before registering with MGC. Some lines may never come
> up due to
> some
> fault at the far end switch or may come up much later than some
> other lines.
>
> At 11:47 AM 4/19/02 -0400, Terry L Anderson wrote:
> >Christian
> >Good point.  I missed the relevance of the ServiceState property
> in 7.1.5.
>  There is
> >states that "in service" is default.  While Service State is not defined
> to be
> >precisely the same as ServiceChange forced and restart (maybe it
> should be
> for a
> >termination), I agree that this default indicates the intention
> defaulting to
> >inservice.  Thus I think that my assumption #1 is the more consistent.  I
> still think
> >that the link between ServiceState and ServiceChange for a termination is
> ambiguous
>
> >enough that it would be helpful to restate the assumption in 7.2.8.
> >
> >I propose we add the following to 7.2.8 at the end of the current Restart
> entry:
> >
> >"When applied to ROOT, this specifies that the Media Gateway as a whole
> will be in
> >service and includes all its physical terminations which will be in their
> default
> >state ("in service").  Exceptions can be indicated by additional
> ServiceChange
> >commands."
> >
> >As Vikas points out, most uses of wildcard ALL assumes that MGC knows the
> range of
> >valid terminationIDs for the GW.  Packages have been proposed
> (but not yet
> approved)
> >for MGC to discover this range if it is not known from
> provisioning.  Sending
> >individual (non-wildcard) ServiceChange for every distinct physical
> termination would
> >be legal but impractical for most large MGs.
> >
> >Al Varney asked:
> >
> >>  Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> >> interface(s) are all operational?  If it makes sense to
> positively assert
> >> SVC(restart) on physical terminations, why wouldn't it also
> make sense to
> >> indicate availability of ephemeral interfaces?  I'm thinking
> particularly
> >> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> >>
> >
> >There has been previous discussions about the applicability of
> ServiceChange for
> >ephemerals.  While there is nothing stating that one could not use
> ServiceChange to
> >take an ephemeral out of service, but since it would then be subtracted
> from any
> >context it was in, it would cease to exist and so could never be
> "restarted".  Clearly
> >serviceChange cannot be used to indicate whether an ephemeral Add will
> succeed or not
> >(availability of any underlying network or gateway resources).  I think
> that the
> >assumption is that if a GW is in service then any ephemeral Add can be
> attempted.
> >Failure of an underlying network can be indicated using nt/netfail, but
> since events
> >are only set on terminations, one must Add an ephemeral before such an
> event can be
> >used.
> >
> >I think we currently have no good way to announce that the MG is in
> service but one or
> >more classes of ephemerals are unavailable.  I think that a
> specific error
> to indicate
> >this after an Add attempt might be sufficient (I don't believe that there
> is a good
> >one now).
> >
> >
> >Christian Groves wrote:
> >
> >> G'Day Vikas,
> >>
> >> I believe you are getting what you asked for. The default state of all
> >> terminaton is "inservice".
> >> If the MG cold starts and sends ServiceChange on "ROOT" then
> the MGC can
> assume
> >> that:
> >> o as the MG is running and
> >> o a MG contains terminations and
> >> o the termination's natural state is "inservice"
>
> >> therefore the individual terminations are running also.
> >>
> >> Regards, Christian
> >>
> >> vbajaj@hss.hns.com wrote:
> >> >
> >> > Al,
> >> >        The advantage you have cited below will hold true
> only under the
> >> > assumption
> >> >   that MG sends ServiceChange for individual terminations instead of
> using a
> >> > wildcard.
> >> >   Sending ServiceChange for individual terminations would be too
> expensive in
> >> > terms
> >> >   of network bandwidth as well as MG processing for
> extremely large sized
> >> > Gateways.
> >> >   I would expect that if MGC is interested in finding out
> configuration
> >> > inconsistencies
> >> >   with its MGs, it would do an Audit at lesiure in parallel to
> handling normal
> >> > calls.
> >> >
> >> >  IMHO, "ServiceChange on ROOT" should indicate all
> terminations are up
> at the
> >> > MG.
> >> >  ServiceChange for Out Of Service Terminations can be sent
> subsequently. Total
> >> > number of messages required in this scenario would be
> >> > (1 ServiceChange on ROOT + x ServiceChange for configured
> but unequipped
> >> > terminations)
> >> >
> >> > Even if we go by approach #2 suggested below, the latter step (i.e.
> sending
> >> > ServiceChange
> >> > for Out Of Service Terminations) will anyway have to be executed.
> >> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded
> Termination Id
> >> > to indicate that all terminations in the MG are In Service, it will
> need to send
> >> >  Out of Service ServiceChange for those terminations that have been
> configured
> >> >  but not hardware equipped. The number of messages required in this
> scenario
> >> > would be
> >> >
> >> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> >> > ServiceChange
> >> >   for configured but unequipped terminations (Term Id =
> "/TG!/Fac1/*))
> >> >
> >> > The MG may of course choose not to use a wildcarded
> >> > termination signifiying all terminations on the MG and instead use
> multiple
> >> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that
> siginfies a
> >> > DS0 aggregation. In this case, the number of ServiceChange commands
> would equal
> >> > the number of such DS0 aggregations in the MG i.e. several
> ServiceChange
> >> > messages
> >> >  would be needed to complete the initial MG-MGC startup sequence. The
> number of
> >> >  messages required in this scenario would be
> >> >
> >> > (1 ServiceChange on ROOT + n ServiceChange for configured
> and equipped
> >> > terminations
> >> >     (Term Id = "/TG!/Fac1/*))
> >> >
> >> > {Assuming most of the terminations in MG would be In Service, n could
> be a large
> >> > value unless
> >> >   the MG is intelligent and can optimize on the number of messages}
> >> >
> >> > To summarize, IMO that number of (ServiceChange) messages required at
> startup
> >> >  would turn out to be larger in approach #2 than in approach #1. So,
> why not
> >> > choose
> >> >  a strategy that is optimal ?
> >> >
> >> > Rgds,
> >> >
> >> > Vikas Bajaj
> >> > NGN Group
> >> > Hughes Software Systems
> >> > (www.hssworld.com)
> >> >
> >> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> >> >
> >> > To:   megaco@ietf.org
> >> > cc:    (bcc: Vikas Bajaj/HSS)
> >> >
> >> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold
> Start)
> >> >
>
> >> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> >> > >Possible clarifications:
> >> > >ServiceChange on ROOT with method=restart (a registration):
> >> > >1) implies that all physical terminations on MG are also
> up.  Exceptions
> >> > >should be indicated by additional ServiceChanges on the down
> terminations
> >> > >using Forced, preferrably in the same message and using
> wildcards where
> >> > >possible.
> >> > >2) implies that all physical terminations on MG are down.
> Those that
> are up
> >> > >will be indicated by additional ServiceChanges on the up
> terminations
> using
> >> > >method=restart, preferrably in the same message and using
> wildcards were
> >> > >possible.
> >> >
> >> > ...
> >> >
> >> > >Even though I think that most GWs probably would not register until
> all or
> >> > >most of their physical terminations are available, I would probably
> prefer
> >> > >#2 since I can easily indicated them all up with only one additional
> >> > >ServiceChange and it seems more natural to indicate those up those
> that are
> >> > >down.  But I can be happy with either #1 or #2.
> >> >
> >> >     #2 has the added (slight?) advantage that physical termination ID
> >> > mis-matches (between MGC and MG) are identified when the MG sends
> >> > SVC(restart) on a termination ID unknown to the MGC.  #1
> relies on MGC
> >> > discovering these (non-existent) terminations 1 at a time, when
> connections
> >> > are attempted.  With #1, a mis-match of this type might go
> undetected for
> >> > days, until the MGC attempted to use/audit that particular
> termination
> ID.
> >> >
> >> >     Terminations known only to the MGC will still go
> "undetected", but
> >> > since no SVC(restart) is ever received for them, at least the MGC
> would not
> >> > be trying to use them.  An audit might eventually reveal the reason
> for the
> >> > OOS terminations.  (It is not unusual in "old" voice switches to have
> >> > termination data populated without having the hardware yet
> in place, so a
> >> > mis-match cannot be considered an error in all cases.)
> >> >
> >> >     Is there an assumption that MG SVC(ROOT,restart) implies the
> ephemeral
> >> > interface(s) are all operational?  If it makes sense to
> positively assert
> >> > SVC(restart) on physical terminations, why wouldn't it also
> make sense to
> >> > indicate availability of ephemeral interfaces?  I'm thinking
> particularly
> >> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> >> >
> >> >     Assuming a reasonable SVC mechanism with "ranges"
> exists, #2 is not a
> >> > big burden after MG restart.  If SVC is needed for every individual
> >> > physical termination, then #1 becomes attractive.
> >> >
> >> > Al Varney
> >> >
> >> > _______________________________________________
> >> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
> >Lucent Technologies/INS/Voice Over IP Access Networks
> >Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> >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@ns.ietf.org  Fri Apr 19 19:23: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 TAA17826
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 19:23:02 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA16854
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 19:23:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA16109;
	Fri, 19 Apr 2002 19:03:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA16006
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 19:03:15 -0400 (EDT)
Received: from smtp.comcast.net (smtp.comcast.net [24.153.64.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15844
	for <megaco@ietf.org>; Fri, 19 Apr 2002 19:03:13 -0400 (EDT)
Received: from Sluggo (pcp334822pcs.howard01.md.comcast.net [68.54.127.67])
 by mtaout02.icomcast.net
 (iPlanet Messaging Server 5.1 HotFix 0.3 (built Apr  8 2002))
 with SMTP id <0GUU0004G80IBQ@mtaout02.icomcast.net> for megaco@ietf.org; Fri,
 19 Apr 2002 19:02:44 -0400 (EDT)
Date: Fri, 19 Apr 2002 19:00:00 -0400
From: Root Mean Square <rms@acc.com>
Subject: RE: [Megaco] ServiceChange for a single termination (Cold  Start)
In-reply-to: <200204191715.NAA28543@teton.ho.lucent.com>
To: Sankar Raman <sraman2@lucent.com>, Terry L Anderson <tla@lucent.com>,
        Christian Groves <Christian.Groves@ericsson.com.au>
Cc: vbajaj@hss.hns.com, Al Varney <varney@ieee.org>, megaco@ietf.org
Reply-to: rms@acc.com
Message-id: <PLEEKKMMGAAKNGECENOPAEGICIAA.rms@acc.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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

Sankar,

I think I agree with everything you said.  In our case we have
administrative and operational states for individual interfaces as well as
the gateway as a whole.  If the administrative state of the MG is enabled,
it will attempt to register with the MGC as soon as the MG cold starts.
Individual interfaces may be adminsitratively disabled, or may be in an
alarm or offline condition (e.g., physically removed from the chasis).
Also, most of our interfaces are intelligent peripherals that need to
download their code image after a cold start, and this may take several
seconds, so they do not come online immediately.  We could wait several
seconds after a cold start before attempting to register with the MGC, but
we still need to deal with interfaces that are administratively disabled,
are temporarily out-of-service or have fault conditions pending.

I understand that it would be optimal if the MG only had to send a single
service change on root if all of its terminations are in-service and
operational when it registers with the MGC.  However, making the default
service state in-service has always seemed a little goofy to me.  If the
default state were out-of-service, it may not reflect reality when the MG
sends its initial service change on root, but it doesn't have any adverse
side effects.  On the other hand, making the default state in-service does.

Making the default termination state out-of-service would seem to be more
consistent with how large media gateways in fact operate -- that is, the
service state of the signaling path between the MG and MGC is independent of
the service state of individual terminations.  Using a technique similar to
what Terry Anderson proposes may overcome most of the inefficiences
associated with having to register interfaces or terminations as they come
into service.  In our particular case, I would prefer to establish an
association with the MGC, negotiate the protocol version and profile, and
then deal with which terminations are in-service or not.  I don't think this
can be cleanly done with a single service change command on root -- perhaps
on a residential GW with a couple of terminations, but not on a large
trunking GW with 1000's of terminations.

Cheers,
Ron Stoughton

> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Sankar Raman
> Sent: Friday, April 19, 2002 1:14 PM
> To: Terry L Anderson; Christian Groves
> Cc: vbajaj@hss.hns.com; Al Varney; megaco@ietf.org
> Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> Start)
>
>
> Terry:
>
> In my expereince working with different swicthes and gateways,
> typical internal implementation of these boxes are such that when
> the box comes up, all T1 lines are asumed down untill they come up
> in which case the T1 framer chip notifies this event to the upper layers.
> Typical implementation is such that when the T1 hardware is reset, no
> events will be generated until a line comes up. Line down evets are
> generated by T1 hardware only if the line was up before.
> This means, if a MGC asssumes on registation, that all lines are up, and
> if certain do not come up at the MG, the MG will not be able to indicate
> this to
> the MGC, unless the MG implelements periodic polling of some sort.
>
> I feel, it is better, that default state for physical terminations,
> when MGC registers with ROOT in service, should be out of service.
> Upon registration, the MGC assumes all lines are down until explicitly
> indicated
> by service change by the MG for the physical lines. As lines come up
> at the MG, the MG will send svcchg in svc for each as it happens.
> This will be simpler for MGs and go with their typical internal
> implementation.
> (although it may generate more traffic which can be cut down by
> using wildcard
> for the lines).
>
> Also, this way MGs do not have to worry about how long should it wait for
> all lines
> to come up before registering with MGC. Some lines may never come
> up due to
> some
> fault at the far end switch or may come up much later than some
> other lines.
>
> At 11:47 AM 4/19/02 -0400, Terry L Anderson wrote:
> >Christian
> >Good point.  I missed the relevance of the ServiceState property
> in 7.1.5.
>  There is
> >states that "in service" is default.  While Service State is not defined
> to be
> >precisely the same as ServiceChange forced and restart (maybe it
> should be
> for a
> >termination), I agree that this default indicates the intention
> defaulting to
> >inservice.  Thus I think that my assumption #1 is the more consistent.  I
> still think
> >that the link between ServiceState and ServiceChange for a termination is
> ambiguous
>
> >enough that it would be helpful to restate the assumption in 7.2.8.
> >
> >I propose we add the following to 7.2.8 at the end of the current Restart
> entry:
> >
> >"When applied to ROOT, this specifies that the Media Gateway as a whole
> will be in
> >service and includes all its physical terminations which will be in their
> default
> >state ("in service").  Exceptions can be indicated by additional
> ServiceChange
> >commands."
> >
> >As Vikas points out, most uses of wildcard ALL assumes that MGC knows the
> range of
> >valid terminationIDs for the GW.  Packages have been proposed
> (but not yet
> approved)
> >for MGC to discover this range if it is not known from
> provisioning.  Sending
> >individual (non-wildcard) ServiceChange for every distinct physical
> termination would
> >be legal but impractical for most large MGs.
> >
> >Al Varney asked:
> >
> >>  Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> >> interface(s) are all operational?  If it makes sense to
> positively assert
> >> SVC(restart) on physical terminations, why wouldn't it also
> make sense to
> >> indicate availability of ephemeral interfaces?  I'm thinking
> particularly
> >> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> >>
> >
> >There has been previous discussions about the applicability of
> ServiceChange for
> >ephemerals.  While there is nothing stating that one could not use
> ServiceChange to
> >take an ephemeral out of service, but since it would then be subtracted
> from any
> >context it was in, it would cease to exist and so could never be
> "restarted".  Clearly
> >serviceChange cannot be used to indicate whether an ephemeral Add will
> succeed or not
> >(availability of any underlying network or gateway resources).  I think
> that the
> >assumption is that if a GW is in service then any ephemeral Add can be
> attempted.
> >Failure of an underlying network can be indicated using nt/netfail, but
> since events
> >are only set on terminations, one must Add an ephemeral before such an
> event can be
> >used.
> >
> >I think we currently have no good way to announce that the MG is in
> service but one or
> >more classes of ephemerals are unavailable.  I think that a
> specific error
> to indicate
> >this after an Add attempt might be sufficient (I don't believe that there
> is a good
> >one now).
> >
> >
> >Christian Groves wrote:
> >
> >> G'Day Vikas,
> >>
> >> I believe you are getting what you asked for. The default state of all
> >> terminaton is "inservice".
> >> If the MG cold starts and sends ServiceChange on "ROOT" then
> the MGC can
> assume
> >> that:
> >> o as the MG is running and
> >> o a MG contains terminations and
> >> o the termination's natural state is "inservice"
>
> >> therefore the individual terminations are running also.
> >>
> >> Regards, Christian
> >>
> >> vbajaj@hss.hns.com wrote:
> >> >
> >> > Al,
> >> >        The advantage you have cited below will hold true
> only under the
> >> > assumption
> >> >   that MG sends ServiceChange for individual terminations instead of
> using a
> >> > wildcard.
> >> >   Sending ServiceChange for individual terminations would be too
> expensive in
> >> > terms
> >> >   of network bandwidth as well as MG processing for
> extremely large sized
> >> > Gateways.
> >> >   I would expect that if MGC is interested in finding out
> configuration
> >> > inconsistencies
> >> >   with its MGs, it would do an Audit at lesiure in parallel to
> handling normal
> >> > calls.
> >> >
> >> >  IMHO, "ServiceChange on ROOT" should indicate all
> terminations are up
> at the
> >> > MG.
> >> >  ServiceChange for Out Of Service Terminations can be sent
> subsequently. Total
> >> > number of messages required in this scenario would be
> >> > (1 ServiceChange on ROOT + x ServiceChange for configured
> but unequipped
> >> > terminations)
> >> >
> >> > Even if we go by approach #2 suggested below, the latter step (i.e.
> sending
> >> > ServiceChange
> >> > for Out Of Service Terminations) will anyway have to be executed.
> >> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded
> Termination Id
> >> > to indicate that all terminations in the MG are In Service, it will
> need to send
> >> >  Out of Service ServiceChange for those terminations that have been
> configured
> >> >  but not hardware equipped. The number of messages required in this
> scenario
> >> > would be
> >> >
> >> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> >> > ServiceChange
> >> >   for configured but unequipped terminations (Term Id =
> "/TG!/Fac1/*))
> >> >
> >> > The MG may of course choose not to use a wildcarded
> >> > termination signifiying all terminations on the MG and instead use
> multiple
> >> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that
> siginfies a
> >> > DS0 aggregation. In this case, the number of ServiceChange commands
> would equal
> >> > the number of such DS0 aggregations in the MG i.e. several
> ServiceChange
> >> > messages
> >> >  would be needed to complete the initial MG-MGC startup sequence. The
> number of
> >> >  messages required in this scenario would be
> >> >
> >> > (1 ServiceChange on ROOT + n ServiceChange for configured
> and equipped
> >> > terminations
> >> >     (Term Id = "/TG!/Fac1/*))
> >> >
> >> > {Assuming most of the terminations in MG would be In Service, n could
> be a large
> >> > value unless
> >> >   the MG is intelligent and can optimize on the number of messages}
> >> >
> >> > To summarize, IMO that number of (ServiceChange) messages required at
> startup
> >> >  would turn out to be larger in approach #2 than in approach #1. So,
> why not
> >> > choose
> >> >  a strategy that is optimal ?
> >> >
> >> > Rgds,
> >> >
> >> > Vikas Bajaj
> >> > NGN Group
> >> > Hughes Software Systems
> >> > (www.hssworld.com)
> >> >
> >> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> >> >
> >> > To:   megaco@ietf.org
> >> > cc:    (bcc: Vikas Bajaj/HSS)
> >> >
> >> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold
> Start)
> >> >
>
> >> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> >> > >Possible clarifications:
> >> > >ServiceChange on ROOT with method=restart (a registration):
> >> > >1) implies that all physical terminations on MG are also
> up.  Exceptions
> >> > >should be indicated by additional ServiceChanges on the down
> terminations
> >> > >using Forced, preferrably in the same message and using
> wildcards where
> >> > >possible.
> >> > >2) implies that all physical terminations on MG are down.
> Those that
> are up
> >> > >will be indicated by additional ServiceChanges on the up
> terminations
> using
> >> > >method=restart, preferrably in the same message and using
> wildcards were
> >> > >possible.
> >> >
> >> > ...
> >> >
> >> > >Even though I think that most GWs probably would not register until
> all or
> >> > >most of their physical terminations are available, I would probably
> prefer
> >> > >#2 since I can easily indicated them all up with only one additional
> >> > >ServiceChange and it seems more natural to indicate those up those
> that are
> >> > >down.  But I can be happy with either #1 or #2.
> >> >
> >> >     #2 has the added (slight?) advantage that physical termination ID
> >> > mis-matches (between MGC and MG) are identified when the MG sends
> >> > SVC(restart) on a termination ID unknown to the MGC.  #1
> relies on MGC
> >> > discovering these (non-existent) terminations 1 at a time, when
> connections
> >> > are attempted.  With #1, a mis-match of this type might go
> undetected for
> >> > days, until the MGC attempted to use/audit that particular
> termination
> ID.
> >> >
> >> >     Terminations known only to the MGC will still go
> "undetected", but
> >> > since no SVC(restart) is ever received for them, at least the MGC
> would not
> >> > be trying to use them.  An audit might eventually reveal the reason
> for the
> >> > OOS terminations.  (It is not unusual in "old" voice switches to have
> >> > termination data populated without having the hardware yet
> in place, so a
> >> > mis-match cannot be considered an error in all cases.)
> >> >
> >> >     Is there an assumption that MG SVC(ROOT,restart) implies the
> ephemeral
> >> > interface(s) are all operational?  If it makes sense to
> positively assert
> >> > SVC(restart) on physical terminations, why wouldn't it also
> make sense to
> >> > indicate availability of ephemeral interfaces?  I'm thinking
> particularly
> >> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> >> >
> >> >     Assuming a reasonable SVC mechanism with "ranges"
> exists, #2 is not a
> >> > big burden after MG restart.  If SVC is needed for every individual
> >> > physical termination, then #1 becomes attractive.
> >> >
> >> > Al Varney
> >> >
> >> > _______________________________________________
> >> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
> >Lucent Technologies/INS/Voice Over IP Access Networks
> >Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> >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  Fri Apr 19 20: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 UAA25768
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 20:41:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA18998;
	Fri, 19 Apr 2002 20:16:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA18968
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 20:16:30 -0400 (EDT)
Received: from blaze.hcltech.com ([203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23083
	for <megaco@ietf.org>; Fri, 19 Apr 2002 20:16:26 -0400 (EDT)
Received: from venkateshpc (venkatesh.hclt-guindy.co.in [192.168.201.131])
	by blaze.hcltech.com (8.9.3/8.9.3) with SMTP id FAA26366
	for <megaco@ietf.org>; Sat, 20 Apr 2002 05:44:48 +0530
From: "Venkatesh A" <venkatesh@netlab.hcltech.com>
To: <megaco@ietf.org>
Date: Sat, 20 Apr 2002 05:48:00 +0530
Message-ID: <BCEGLBPKBLPEGJMFNDJMEECHCLAA.venkatesh@netlab.hcltech.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.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Invalid Controller 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: 7bit

Hi All,

In case of TCP nobody other than the active controller can send messages to
an MG.  But in case of UDP, anybody can simply throw a message at an open
UDP port of an MG.  Should the MG check the source IP address of each
message that it is receiving from an MGC is the same as the one to which it
sent the Service Change or the one specified in the ServiceChangeAddress?
So, how will a megaco stack running on UDP and which does not support
authentication, avoid getting messages from anybody other than its active
controller?  Should this be taken care by implementation or is there any
specification about this ?

Thanks
Venkatesh


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


From daemon@ns.ietf.org  Fri Apr 19 20: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 UAA25781
	for <megaco-archive@odin.ietf.org>; Fri, 19 Apr 2002 20:41:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA19946
	for megaco-archive@odin.ietf.org; Fri, 19 Apr 2002 20:41:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA18998;
	Fri, 19 Apr 2002 20:16:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA18968
	for <megaco@ns.ietf.org>; Fri, 19 Apr 2002 20:16:30 -0400 (EDT)
Received: from blaze.hcltech.com ([203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23083
	for <megaco@ietf.org>; Fri, 19 Apr 2002 20:16:26 -0400 (EDT)
Received: from venkateshpc (venkatesh.hclt-guindy.co.in [192.168.201.131])
	by blaze.hcltech.com (8.9.3/8.9.3) with SMTP id FAA26366
	for <megaco@ietf.org>; Sat, 20 Apr 2002 05:44:48 +0530
From: "Venkatesh A" <venkatesh@netlab.hcltech.com>
To: <megaco@ietf.org>
Date: Sat, 20 Apr 2002 05:48:00 +0530
Message-ID: <BCEGLBPKBLPEGJMFNDJMEECHCLAA.venkatesh@netlab.hcltech.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.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Invalid Controller 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: 7bit

Hi All,

In case of TCP nobody other than the active controller can send messages to
an MG.  But in case of UDP, anybody can simply throw a message at an open
UDP port of an MG.  Should the MG check the source IP address of each
message that it is receiving from an MGC is the same as the one to which it
sent the Service Change or the one specified in the ServiceChangeAddress?
So, how will a megaco stack running on UDP and which does not support
authentication, avoid getting messages from anybody other than its active
controller?  Should this be taken care by implementation or is there any
specification about this ?

Thanks
Venkatesh


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



From megaco-admin@ietf.org  Mon Apr 22 01:36: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 BAA08646
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 01:36:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA11322;
	Mon, 22 Apr 2002 01:10:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA11240
	for <megaco@optimus.ietf.org>; Mon, 22 Apr 2002 01:10:42 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08451
	for <megaco@ietf.org>; Mon, 22 Apr 2002 01:10:40 -0400 (EDT)
From: vbajaj@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 g3M53Dc18359;
	Mon, 22 Apr 2002 10:33:14 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA3.001B733B ; Mon, 22 Apr 2002 10:29:49 +0530
X-Lotus-FromDomain: HSS
To: Sankar Raman <sraman2@lucent.com>
cc: Terry L Anderson <tla@lucent.com>,
        Christian Groves <Christian.Groves@ericsson.com.au>,
        Al Varney <varney@ieee.org>, megaco@ietf.org
Message-ID: <65256BA3.001B3B81.00@sandesh.hss.hns.com>
Date: Mon, 22 Apr 2002 10:30:09 +0530
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
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



Sankar,
            IMHO that, while it is right to refer to legacy switching to ensure
that we don't miss out on something
 obvious, we need not adopt all strategies that have been used in the past. The
architecture that has
 evolved for the new networks is different (it is distributed and has in its
core a packet network) and
a different strategy may need to be evolved to account for these changes. It is
possible to implement
 a solution in conformance to a defined protocol but it may not be easy to come
out with new revisions
of the protocol to address deployment issues. Hence, in my opinion whatever
through discussions
seems to be optimal from deployment perspective should be adopted.

Rgds,

Vikas Bajaj
NGN Group
Hughes Softsware Systems
(www.hssworld.com)





Sankar Raman <sraman2@lucent.com> on 04/19/2002 10:44:24 PM

To:   Terry L Anderson <tla@lucent.com>, Christian Groves
      <Christian.Groves@ericsson.com.au>
cc:   Vikas Bajaj/HSS@HSS, Al Varney <varney@ieee.org>, megaco@ietf.org

Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)




Terry:

In my expereince working with different swicthes and gateways,
typical internal implementation of these boxes are such that when
the box comes up, all T1 lines are asumed down untill they come up
in which case the T1 framer chip notifies this event to the upper layers.
Typical implementation is such that when the T1 hardware is reset, no
events will be generated until a line comes up. Line down evets are
generated by T1 hardware only if the line was up before.
This means, if a MGC asssumes on registation, that all lines are up, and
if certain do not come up at the MG, the MG will not be able to indicate
this to
the MGC, unless the MG implelements periodic polling of some sort.

I feel, it is better, that default state for physical terminations,
when MGC registers with ROOT in service, should be out of service.
Upon registration, the MGC assumes all lines are down until explicitly
indicated
by service change by the MG for the physical lines. As lines come up
at the MG, the MG will send svcchg in svc for each as it happens.
This will be simpler for MGs and go with their typical internal
implementation.
(although it may generate more traffic which can be cut down by using wildcard
for the lines).

Also, this way MGs do not have to worry about how long should it wait for
all lines
to come up before registering with MGC. Some lines may never come up due to
some
fault at the far end switch or may come up much later than some other lines.

At 11:47 AM 4/19/02 -0400, Terry L Anderson wrote:
>Christian
>Good point.  I missed the relevance of the ServiceState property in 7.1.5.
 There is
>states that "in service" is default.  While Service State is not defined
to be
>precisely the same as ServiceChange forced and restart (maybe it should be
for a
>termination), I agree that this default indicates the intention defaulting to
>inservice.  Thus I think that my assumption #1 is the more consistent.  I
still think
>that the link between ServiceState and ServiceChange for a termination is
ambiguous

>enough that it would be helpful to restate the assumption in 7.2.8.
>
>I propose we add the following to 7.2.8 at the end of the current Restart
entry:
>
>"When applied to ROOT, this specifies that the Media Gateway as a whole
will be in
>service and includes all its physical terminations which will be in their
default
>state ("in service").  Exceptions can be indicated by additional
ServiceChange
>commands."
>
>As Vikas points out, most uses of wildcard ALL assumes that MGC knows the
range of
>valid terminationIDs for the GW.  Packages have been proposed (but not yet
approved)
>for MGC to discover this range if it is not known from provisioning.  Sending
>individual (non-wildcard) ServiceChange for every distinct physical
termination would
>be legal but impractical for most large MGs.
>
>Al Varney asked:
>
>>  Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
>> interface(s) are all operational?  If it makes sense to positively assert
>> SVC(restart) on physical terminations, why wouldn't it also make sense to
>> indicate availability of ephemeral interfaces?  I'm thinking particularly
>> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>>
>
>There has been previous discussions about the applicability of
ServiceChange for
>ephemerals.  While there is nothing stating that one could not use
ServiceChange to
>take an ephemeral out of service, but since it would then be subtracted
from any
>context it was in, it would cease to exist and so could never be
"restarted".  Clearly
>serviceChange cannot be used to indicate whether an ephemeral Add will
succeed or not
>(availability of any underlying network or gateway resources).  I think
that the
>assumption is that if a GW is in service then any ephemeral Add can be
attempted.
>Failure of an underlying network can be indicated using nt/netfail, but
since events
>are only set on terminations, one must Add an ephemeral before such an
event can be
>used.
>
>I think we currently have no good way to announce that the MG is in
service but one or
>more classes of ephemerals are unavailable.  I think that a specific error
to indicate
>this after an Add attempt might be sufficient (I don't believe that there
is a good
>one now).
>
>
>Christian Groves wrote:
>
>> G'Day Vikas,
>>
>> I believe you are getting what you asked for. The default state of all
>> terminaton is "inservice".
>> If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can
assume
>> that:
>> o as the MG is running and
>> o a MG contains terminations and
>> o the termination's natural state is "inservice"

>> therefore the individual terminations are running also.
>>
>> Regards, Christian
>>
>> vbajaj@hss.hns.com wrote:
>> >
>> > Al,
>> >        The advantage you have cited below will hold true only under the
>> > assumption
>> >   that MG sends ServiceChange for individual terminations instead of
using a
>> > wildcard.
>> >   Sending ServiceChange for individual terminations would be too
expensive in
>> > terms
>> >   of network bandwidth as well as MG processing for extremely large sized
>> > Gateways.
>> >   I would expect that if MGC is interested in finding out configuration
>> > inconsistencies
>> >   with its MGs, it would do an Audit at lesiure in parallel to
handling normal
>> > calls.
>> >
>> >  IMHO, "ServiceChange on ROOT" should indicate all terminations are up
at the
>> > MG.
>> >  ServiceChange for Out Of Service Terminations can be sent
subsequently. Total
>> > number of messages required in this scenario would be
>> > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
>> > terminations)
>> >
>> > Even if we go by approach #2 suggested below, the latter step (i.e.
sending
>> > ServiceChange
>> > for Out Of Service Terminations) will anyway have to be executed.
>> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded
Termination Id
>> > to indicate that all terminations in the MG are In Service, it will
need to send
>> >  Out of Service ServiceChange for those terminations that have been
configured
>> >  but not hardware equipped. The number of messages required in this
scenario
>> > would be
>> >
>> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
>> > ServiceChange
>> >   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
>> >
>> > The MG may of course choose not to use a wildcarded
>> > termination signifiying all terminations on the MG and instead use
multiple
>> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that
siginfies a
>> > DS0 aggregation. In this case, the number of ServiceChange commands
would equal
>> > the number of such DS0 aggregations in the MG i.e. several ServiceChange
>> > messages
>> >  would be needed to complete the initial MG-MGC startup sequence. The
number of
>> >  messages required in this scenario would be
>> >
>> > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
>> > terminations
>> >     (Term Id = "/TG!/Fac1/*))
>> >
>> > {Assuming most of the terminations in MG would be In Service, n could
be a large
>> > value unless
>> >   the MG is intelligent and can optimize on the number of messages}
>> >
>> > To summarize, IMO that number of (ServiceChange) messages required at
startup
>> >  would turn out to be larger in approach #2 than in approach #1. So,
why not
>> > choose
>> >  a strategy that is optimal ?
>> >
>> > Rgds,
>> >
>> > Vikas Bajaj
>> > NGN Group
>> > Hughes Software Systems
>> > (www.hssworld.com)
>> >
>> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
>> >
>> > To:   megaco@ietf.org
>> > cc:    (bcc: Vikas Bajaj/HSS)
>> >
>> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold
Start)
>> >

>> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
>> > >Possible clarifications:
>> > >ServiceChange on ROOT with method=restart (a registration):
>> > >1) implies that all physical terminations on MG are also up.  Exceptions
>> > >should be indicated by additional ServiceChanges on the down
terminations
>> > >using Forced, preferrably in the same message and using wildcards where
>> > >possible.
>> > >2) implies that all physical terminations on MG are down.  Those that
are up
>> > >will be indicated by additional ServiceChanges on the up terminations
using
>> > >method=restart, preferrably in the same message and using wildcards were
>> > >possible.
>> >
>> > ...
>> >
>> > >Even though I think that most GWs probably would not register until
all or
>> > >most of their physical terminations are available, I would probably
prefer
>> > >#2 since I can easily indicated them all up with only one additional
>> > >ServiceChange and it seems more natural to indicate those up those
that are
>> > >down.  But I can be happy with either #1 or #2.
>> >
>> >     #2 has the added (slight?) advantage that physical termination ID
>> > mis-matches (between MGC and MG) are identified when the MG sends
>> > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
>> > discovering these (non-existent) terminations 1 at a time, when
connections
>> > are attempted.  With #1, a mis-match of this type might go undetected for
>> > days, until the MGC attempted to use/audit that particular termination
ID.
>> >
>> >     Terminations known only to the MGC will still go "undetected", but
>> > since no SVC(restart) is ever received for them, at least the MGC
would not
>> > be trying to use them.  An audit might eventually reveal the reason
for the
>> > OOS terminations.  (It is not unusual in "old" voice switches to have
>> > termination data populated without having the hardware yet in place, so a
>> > mis-match cannot be considered an error in all cases.)
>> >
>> >     Is there an assumption that MG SVC(ROOT,restart) implies the
ephemeral
>> > interface(s) are all operational?  If it makes sense to positively assert
>> > SVC(restart) on physical terminations, why wouldn't it also make sense to
>> > indicate availability of ephemeral interfaces?  I'm thinking particularly
>> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>> >
>> >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
>> > big burden after MG restart.  If SVC is needed for every individual
>> > physical termination, then #1 becomes attractive.
>> >
>> > Al Varney
>> >
>> > _______________________________________________
>> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
>Lucent Technologies/INS/Voice Over IP Access Networks
>Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
>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  Mon Apr 22 01:36: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 BAA08660
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 01:36:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA18644
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 01:36:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA11322;
	Mon, 22 Apr 2002 01:10:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA11240
	for <megaco@optimus.ietf.org>; Mon, 22 Apr 2002 01:10:42 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08451
	for <megaco@ietf.org>; Mon, 22 Apr 2002 01:10:40 -0400 (EDT)
From: vbajaj@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 g3M53Dc18359;
	Mon, 22 Apr 2002 10:33:14 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA3.001B733B ; Mon, 22 Apr 2002 10:29:49 +0530
X-Lotus-FromDomain: HSS
To: Sankar Raman <sraman2@lucent.com>
cc: Terry L Anderson <tla@lucent.com>,
        Christian Groves <Christian.Groves@ericsson.com.au>,
        Al Varney <varney@ieee.org>, megaco@ietf.org
Message-ID: <65256BA3.001B3B81.00@sandesh.hss.hns.com>
Date: Mon, 22 Apr 2002 10:30:09 +0530
Subject: Re: [Megaco] ServiceChange for a single termination (Cold Start)
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



Sankar,
            IMHO that, while it is right to refer to legacy switching to ensure
that we don't miss out on something
 obvious, we need not adopt all strategies that have been used in the past. The
architecture that has
 evolved for the new networks is different (it is distributed and has in its
core a packet network) and
a different strategy may need to be evolved to account for these changes. It is
possible to implement
 a solution in conformance to a defined protocol but it may not be easy to come
out with new revisions
of the protocol to address deployment issues. Hence, in my opinion whatever
through discussions
seems to be optimal from deployment perspective should be adopted.

Rgds,

Vikas Bajaj
NGN Group
Hughes Softsware Systems
(www.hssworld.com)





Sankar Raman <sraman2@lucent.com> on 04/19/2002 10:44:24 PM

To:   Terry L Anderson <tla@lucent.com>, Christian Groves
      <Christian.Groves@ericsson.com.au>
cc:   Vikas Bajaj/HSS@HSS, Al Varney <varney@ieee.org>, megaco@ietf.org

Subject:  Re: [Megaco] ServiceChange for a single termination (Cold  Start)




Terry:

In my expereince working with different swicthes and gateways,
typical internal implementation of these boxes are such that when
the box comes up, all T1 lines are asumed down untill they come up
in which case the T1 framer chip notifies this event to the upper layers.
Typical implementation is such that when the T1 hardware is reset, no
events will be generated until a line comes up. Line down evets are
generated by T1 hardware only if the line was up before.
This means, if a MGC asssumes on registation, that all lines are up, and
if certain do not come up at the MG, the MG will not be able to indicate
this to
the MGC, unless the MG implelements periodic polling of some sort.

I feel, it is better, that default state for physical terminations,
when MGC registers with ROOT in service, should be out of service.
Upon registration, the MGC assumes all lines are down until explicitly
indicated
by service change by the MG for the physical lines. As lines come up
at the MG, the MG will send svcchg in svc for each as it happens.
This will be simpler for MGs and go with their typical internal
implementation.
(although it may generate more traffic which can be cut down by using wildcard
for the lines).

Also, this way MGs do not have to worry about how long should it wait for
all lines
to come up before registering with MGC. Some lines may never come up due to
some
fault at the far end switch or may come up much later than some other lines.

At 11:47 AM 4/19/02 -0400, Terry L Anderson wrote:
>Christian
>Good point.  I missed the relevance of the ServiceState property in 7.1.5.
 There is
>states that "in service" is default.  While Service State is not defined
to be
>precisely the same as ServiceChange forced and restart (maybe it should be
for a
>termination), I agree that this default indicates the intention defaulting to
>inservice.  Thus I think that my assumption #1 is the more consistent.  I
still think
>that the link between ServiceState and ServiceChange for a termination is
ambiguous

>enough that it would be helpful to restate the assumption in 7.2.8.
>
>I propose we add the following to 7.2.8 at the end of the current Restart
entry:
>
>"When applied to ROOT, this specifies that the Media Gateway as a whole
will be in
>service and includes all its physical terminations which will be in their
default
>state ("in service").  Exceptions can be indicated by additional
ServiceChange
>commands."
>
>As Vikas points out, most uses of wildcard ALL assumes that MGC knows the
range of
>valid terminationIDs for the GW.  Packages have been proposed (but not yet
approved)
>for MGC to discover this range if it is not known from provisioning.  Sending
>individual (non-wildcard) ServiceChange for every distinct physical
termination would
>be legal but impractical for most large MGs.
>
>Al Varney asked:
>
>>  Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
>> interface(s) are all operational?  If it makes sense to positively assert
>> SVC(restart) on physical terminations, why wouldn't it also make sense to
>> indicate availability of ephemeral interfaces?  I'm thinking particularly
>> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>>
>
>There has been previous discussions about the applicability of
ServiceChange for
>ephemerals.  While there is nothing stating that one could not use
ServiceChange to
>take an ephemeral out of service, but since it would then be subtracted
from any
>context it was in, it would cease to exist and so could never be
"restarted".  Clearly
>serviceChange cannot be used to indicate whether an ephemeral Add will
succeed or not
>(availability of any underlying network or gateway resources).  I think
that the
>assumption is that if a GW is in service then any ephemeral Add can be
attempted.
>Failure of an underlying network can be indicated using nt/netfail, but
since events
>are only set on terminations, one must Add an ephemeral before such an
event can be
>used.
>
>I think we currently have no good way to announce that the MG is in
service but one or
>more classes of ephemerals are unavailable.  I think that a specific error
to indicate
>this after an Add attempt might be sufficient (I don't believe that there
is a good
>one now).
>
>
>Christian Groves wrote:
>
>> G'Day Vikas,
>>
>> I believe you are getting what you asked for. The default state of all
>> terminaton is "inservice".
>> If the MG cold starts and sends ServiceChange on "ROOT" then the MGC can
assume
>> that:
>> o as the MG is running and
>> o a MG contains terminations and
>> o the termination's natural state is "inservice"

>> therefore the individual terminations are running also.
>>
>> Regards, Christian
>>
>> vbajaj@hss.hns.com wrote:
>> >
>> > Al,
>> >        The advantage you have cited below will hold true only under the
>> > assumption
>> >   that MG sends ServiceChange for individual terminations instead of
using a
>> > wildcard.
>> >   Sending ServiceChange for individual terminations would be too
expensive in
>> > terms
>> >   of network bandwidth as well as MG processing for extremely large sized
>> > Gateways.
>> >   I would expect that if MGC is interested in finding out configuration
>> > inconsistencies
>> >   with its MGs, it would do an Audit at lesiure in parallel to
handling normal
>> > calls.
>> >
>> >  IMHO, "ServiceChange on ROOT" should indicate all terminations are up
at the
>> > MG.
>> >  ServiceChange for Out Of Service Terminations can be sent
subsequently. Total
>> > number of messages required in this scenario would be
>> > (1 ServiceChange on ROOT + x ServiceChange for configured but unequipped
>> > terminations)
>> >
>> > Even if we go by approach #2 suggested below, the latter step (i.e.
sending
>> > ServiceChange
>> > for Out Of Service Terminations) will anyway have to be executed.
>> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded
Termination Id
>> > to indicate that all terminations in the MG are In Service, it will
need to send
>> >  Out of Service ServiceChange for those terminations that have been
configured
>> >  but not hardware equipped. The number of messages required in this
scenario
>> > would be
>> >
>> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
>> > ServiceChange
>> >   for configured but unequipped terminations (Term Id = "/TG!/Fac1/*))
>> >
>> > The MG may of course choose not to use a wildcarded
>> > termination signifiying all terminations on the MG and instead use
multiple
>> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that
siginfies a
>> > DS0 aggregation. In this case, the number of ServiceChange commands
would equal
>> > the number of such DS0 aggregations in the MG i.e. several ServiceChange
>> > messages
>> >  would be needed to complete the initial MG-MGC startup sequence. The
number of
>> >  messages required in this scenario would be
>> >
>> > (1 ServiceChange on ROOT + n ServiceChange for configured and equipped
>> > terminations
>> >     (Term Id = "/TG!/Fac1/*))
>> >
>> > {Assuming most of the terminations in MG would be In Service, n could
be a large
>> > value unless
>> >   the MG is intelligent and can optimize on the number of messages}
>> >
>> > To summarize, IMO that number of (ServiceChange) messages required at
startup
>> >  would turn out to be larger in approach #2 than in approach #1. So,
why not
>> > choose
>> >  a strategy that is optimal ?
>> >
>> > Rgds,
>> >
>> > Vikas Bajaj
>> > NGN Group
>> > Hughes Software Systems
>> > (www.hssworld.com)
>> >
>> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
>> >
>> > To:   megaco@ietf.org
>> > cc:    (bcc: Vikas Bajaj/HSS)
>> >
>> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold
Start)
>> >

>> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
>> > >Possible clarifications:
>> > >ServiceChange on ROOT with method=restart (a registration):
>> > >1) implies that all physical terminations on MG are also up.  Exceptions
>> > >should be indicated by additional ServiceChanges on the down
terminations
>> > >using Forced, preferrably in the same message and using wildcards where
>> > >possible.
>> > >2) implies that all physical terminations on MG are down.  Those that
are up
>> > >will be indicated by additional ServiceChanges on the up terminations
using
>> > >method=restart, preferrably in the same message and using wildcards were
>> > >possible.
>> >
>> > ...
>> >
>> > >Even though I think that most GWs probably would not register until
all or
>> > >most of their physical terminations are available, I would probably
prefer
>> > >#2 since I can easily indicated them all up with only one additional
>> > >ServiceChange and it seems more natural to indicate those up those
that are
>> > >down.  But I can be happy with either #1 or #2.
>> >
>> >     #2 has the added (slight?) advantage that physical termination ID
>> > mis-matches (between MGC and MG) are identified when the MG sends
>> > SVC(restart) on a termination ID unknown to the MGC.  #1 relies on MGC
>> > discovering these (non-existent) terminations 1 at a time, when
connections
>> > are attempted.  With #1, a mis-match of this type might go undetected for
>> > days, until the MGC attempted to use/audit that particular termination
ID.
>> >
>> >     Terminations known only to the MGC will still go "undetected", but
>> > since no SVC(restart) is ever received for them, at least the MGC
would not
>> > be trying to use them.  An audit might eventually reveal the reason
for the
>> > OOS terminations.  (It is not unusual in "old" voice switches to have
>> > termination data populated without having the hardware yet in place, so a
>> > mis-match cannot be considered an error in all cases.)
>> >
>> >     Is there an assumption that MG SVC(ROOT,restart) implies the
ephemeral
>> > interface(s) are all operational?  If it makes sense to positively assert
>> > SVC(restart) on physical terminations, why wouldn't it also make sense to
>> > indicate availability of ephemeral interfaces?  I'm thinking particularly
>> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
>> >
>> >     Assuming a reasonable SVC mechanism with "ranges" exists, #2 is not a
>> > big burden after MG restart.  If SVC is needed for every individual
>> > physical termination, then #1 becomes attractive.
>> >
>> > Al Varney
>> >
>> > _______________________________________________
>> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
>Lucent Technologies/INS/Voice Over IP Access Networks
>Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
>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  Mon Apr 22 04:06: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 EAA18800
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 04:06:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA24941;
	Mon, 22 Apr 2002 03:42:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA24910
	for <megaco@optimus.ietf.org>; Mon, 22 Apr 2002 03:42:38 -0400 (EDT)
Received: from ish7.ericsson.com.au (ish7.ericsson.com.au [203.61.155.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18453
	for <megaco@ietf.org>; Mon, 22 Apr 2002 03:42:35 -0400 (EDT)
Received: from brsf10.epa.ericsson.se (brsf10 [146.11.8.4])
	by ish7.ericsson.com.au (8.11.6+Sun/8.11.6) with ESMTP id g3M7f1017474
	for <megaco@ietf.org>; Mon, 22 Apr 2002 17:41:01 +1000 (EST)
Received: from ericsson.com.au (dhcp-239-110.epa.ericsson.se [146.11.239.110])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id RAA22245
	for <megaco@ietf.org>; Mon, 22 Apr 2002 17:42:36 +1000 (EST)
Message-ID: <3CC35E76.3B37C8F1@ericsson.com.au>
Date: Mon, 22 Apr 2002 10:51:02 +1000
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] ServiceChange for a single termination (Cold  Start)
References: <PLEEKKMMGAAKNGECENOPAEGICIAA.rms@acc.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,

In both H.248/Megaco v1 and v2 we have sect 7.1.5 stating that the default is
"in-service". I think now it is too late to change this to "inactive". It would
be a backwards incompatible change. Whilst not everyone will like it because
they have either big or small MG/MGCs, we had chosen to go done the "in-service"
path. 

The MGC can discover what terminations are on the MG by other means ie.
Provisioning, MIB or via the termination package.

Regards, Christian

Root Mean Square wrote:
> 
> Sankar,
> 
> I think I agree with everything you said.  In our case we have
> administrative and operational states for individual interfaces as well as
> the gateway as a whole.  If the administrative state of the MG is enabled,
> it will attempt to register with the MGC as soon as the MG cold starts.
> Individual interfaces may be adminsitratively disabled, or may be in an
> alarm or offline condition (e.g., physically removed from the chasis).
> Also, most of our interfaces are intelligent peripherals that need to
> download their code image after a cold start, and this may take several
> seconds, so they do not come online immediately.  We could wait several
> seconds after a cold start before attempting to register with the MGC, but
> we still need to deal with interfaces that are administratively disabled,
> are temporarily out-of-service or have fault conditions pending.
> 
> I understand that it would be optimal if the MG only had to send a single
> service change on root if all of its terminations are in-service and
> operational when it registers with the MGC.  However, making the default
> service state in-service has always seemed a little goofy to me.  If the
> default state were out-of-service, it may not reflect reality when the MG
> sends its initial service change on root, but it doesn't have any adverse
> side effects.  On the other hand, making the default state in-service does.
> 
> Making the default termination state out-of-service would seem to be more
> consistent with how large media gateways in fact operate -- that is, the
> service state of the signaling path between the MG and MGC is independent of
> the service state of individual terminations.  Using a technique similar to
> what Terry Anderson proposes may overcome most of the inefficiences
> associated with having to register interfaces or terminations as they come
> into service.  In our particular case, I would prefer to establish an
> association with the MGC, negotiate the protocol version and profile, and
> then deal with which terminations are in-service or not.  I don't think this
> can be cleanly done with a single service change command on root -- perhaps
> on a residential GW with a couple of terminations, but not on a large
> trunking GW with 1000's of terminations.
> 
> Cheers,
> Ron Stoughton
> 
> > -----Original Message-----
> > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> > Sankar Raman
> > Sent: Friday, April 19, 2002 1:14 PM
> > To: Terry L Anderson; Christian Groves
> > Cc: vbajaj@hss.hns.com; Al Varney; megaco@ietf.org
> > Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> >
> > Terry:
> >
> > In my expereince working with different swicthes and gateways,
> > typical internal implementation of these boxes are such that when
> > the box comes up, all T1 lines are asumed down untill they come up
> > in which case the T1 framer chip notifies this event to the upper layers.
> > Typical implementation is such that when the T1 hardware is reset, no
> > events will be generated until a line comes up. Line down evets are
> > generated by T1 hardware only if the line was up before.
> > This means, if a MGC asssumes on registation, that all lines are up, and
> > if certain do not come up at the MG, the MG will not be able to indicate
> > this to
> > the MGC, unless the MG implelements periodic polling of some sort.
> >
> > I feel, it is better, that default state for physical terminations,
> > when MGC registers with ROOT in service, should be out of service.
> > Upon registration, the MGC assumes all lines are down until explicitly
> > indicated
> > by service change by the MG for the physical lines. As lines come up
> > at the MG, the MG will send svcchg in svc for each as it happens.
> > This will be simpler for MGs and go with their typical internal
> > implementation.
> > (although it may generate more traffic which can be cut down by
> > using wildcard
> > for the lines).
> >
> > Also, this way MGs do not have to worry about how long should it wait for
> > all lines
> > to come up before registering with MGC. Some lines may never come
> > up due to
> > some
> > fault at the far end switch or may come up much later than some
> > other lines.
> >
> > At 11:47 AM 4/19/02 -0400, Terry L Anderson wrote:
> > >Christian
> > >Good point.  I missed the relevance of the ServiceState property
> > in 7.1.5.
> >  There is
> > >states that "in service" is default.  While Service State is not defined
> > to be
> > >precisely the same as ServiceChange forced and restart (maybe it
> > should be
> > for a
> > >termination), I agree that this default indicates the intention
> > defaulting to
> > >inservice.  Thus I think that my assumption #1 is the more consistent.  I
> > still think
> > >that the link between ServiceState and ServiceChange for a termination is
> > ambiguous
> >
> > >enough that it would be helpful to restate the assumption in 7.2.8.
> > >
> > >I propose we add the following to 7.2.8 at the end of the current Restart
> > entry:
> > >
> > >"When applied to ROOT, this specifies that the Media Gateway as a whole
> > will be in
> > >service and includes all its physical terminations which will be in their
> > default
> > >state ("in service").  Exceptions can be indicated by additional
> > ServiceChange
> > >commands."
> > >
> > >As Vikas points out, most uses of wildcard ALL assumes that MGC knows the
> > range of
> > >valid terminationIDs for the GW.  Packages have been proposed
> > (but not yet
> > approved)
> > >for MGC to discover this range if it is not known from
> > provisioning.  Sending
> > >individual (non-wildcard) ServiceChange for every distinct physical
> > termination would
> > >be legal but impractical for most large MGs.
> > >
> > >Al Varney asked:
> > >
> > >>  Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> > >> interface(s) are all operational?  If it makes sense to
> > positively assert
> > >> SVC(restart) on physical terminations, why wouldn't it also
> > make sense to
> > >> indicate availability of ephemeral interfaces?  I'm thinking
> > particularly
> > >> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> > >>
> > >
> > >There has been previous discussions about the applicability of
> > ServiceChange for
> > >ephemerals.  While there is nothing stating that one could not use
> > ServiceChange to
> > >take an ephemeral out of service, but since it would then be subtracted
> > from any
> > >context it was in, it would cease to exist and so could never be
> > "restarted".  Clearly
> > >serviceChange cannot be used to indicate whether an ephemeral Add will
> > succeed or not
> > >(availability of any underlying network or gateway resources).  I think
> > that the
> > >assumption is that if a GW is in service then any ephemeral Add can be
> > attempted.
> > >Failure of an underlying network can be indicated using nt/netfail, but
> > since events
> > >are only set on terminations, one must Add an ephemeral before such an
> > event can be
> > >used.
> > >
> > >I think we currently have no good way to announce that the MG is in
> > service but one or
> > >more classes of ephemerals are unavailable.  I think that a
> > specific error
> > to indicate
> > >this after an Add attempt might be sufficient (I don't believe that there
> > is a good
> > >one now).
> > >
> > >
> > >Christian Groves wrote:
> > >
> > >> G'Day Vikas,
> > >>
> > >> I believe you are getting what you asked for. The default state of all
> > >> terminaton is "inservice".
> > >> If the MG cold starts and sends ServiceChange on "ROOT" then
> > the MGC can
> > assume
> > >> that:
> > >> o as the MG is running and
> > >> o a MG contains terminations and
> > >> o the termination's natural state is "inservice"
> >
> > >> therefore the individual terminations are running also.
> > >>
> > >> Regards, Christian
> > >>
> > >> vbajaj@hss.hns.com wrote:
> > >> >
> > >> > Al,
> > >> >        The advantage you have cited below will hold true
> > only under the
> > >> > assumption
> > >> >   that MG sends ServiceChange for individual terminations instead of
> > using a
> > >> > wildcard.
> > >> >   Sending ServiceChange for individual terminations would be too
> > expensive in
> > >> > terms
> > >> >   of network bandwidth as well as MG processing for
> > extremely large sized
> > >> > Gateways.
> > >> >   I would expect that if MGC is interested in finding out
> > configuration
> > >> > inconsistencies
> > >> >   with its MGs, it would do an Audit at lesiure in parallel to
> > handling normal
> > >> > calls.
> > >> >
> > >> >  IMHO, "ServiceChange on ROOT" should indicate all
> > terminations are up
> > at the
> > >> > MG.
> > >> >  ServiceChange for Out Of Service Terminations can be sent
> > subsequently. Total
> > >> > number of messages required in this scenario would be
> > >> > (1 ServiceChange on ROOT + x ServiceChange for configured
> > but unequipped
> > >> > terminations)
> > >> >
> > >> > Even if we go by approach #2 suggested below, the latter step (i.e.
> > sending
> > >> > ServiceChange
> > >> > for Out Of Service Terminations) will anyway have to be executed.
> > >> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded
> > Termination Id
> > >> > to indicate that all terminations in the MG are In Service, it will
> > need to send
> > >> >  Out of Service ServiceChange for those terminations that have been
> > configured
> > >> >  but not hardware equipped. The number of messages required in this
> > scenario
> > >> > would be
> > >> >
> > >> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> > >> > ServiceChange
> > >> >   for configured but unequipped terminations (Term Id =
> > "/TG!/Fac1/*))
> > >> >
> > >> > The MG may of course choose not to use a wildcarded
> > >> > termination signifiying all terminations on the MG and instead use
> > multiple
> > >> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that
> > siginfies a
> > >> > DS0 aggregation. In this case, the number of ServiceChange commands
> > would equal
> > >> > the number of such DS0 aggregations in the MG i.e. several
> > ServiceChange
> > >> > messages
> > >> >  would be needed to complete the initial MG-MGC startup sequence. The
> > number of
> > >> >  messages required in this scenario would be
> > >> >
> > >> > (1 ServiceChange on ROOT + n ServiceChange for configured
> > and equipped
> > >> > terminations
> > >> >     (Term Id = "/TG!/Fac1/*))
> > >> >
> > >> > {Assuming most of the terminations in MG would be In Service, n could
> > be a large
> > >> > value unless
> > >> >   the MG is intelligent and can optimize on the number of messages}
> > >> >
> > >> > To summarize, IMO that number of (ServiceChange) messages required at
> > startup
> > >> >  would turn out to be larger in approach #2 than in approach #1. So,
> > why not
> > >> > choose
> > >> >  a strategy that is optimal ?
> > >> >
> > >> > Rgds,
> > >> >
> > >> > Vikas Bajaj
> > >> > NGN Group
> > >> > Hughes Software Systems
> > >> > (www.hssworld.com)
> > >> >
> > >> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> > >> >
> > >> > To:   megaco@ietf.org
> > >> > cc:    (bcc: Vikas Bajaj/HSS)
> > >> >
> > >> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> > >> >
> >
> > >> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> > >> > >Possible clarifications:
> > >> > >ServiceChange on ROOT with method=restart (a registration):
> > >> > >1) implies that all physical terminations on MG are also
> > up.  Exceptions
> > >> > >should be indicated by additional ServiceChanges on the down
> > terminations
> > >> > >using Forced, preferrably in the same message and using
> > wildcards where
> > >> > >possible.
> > >> > >2) implies that all physical terminations on MG are down.
> > Those that
> > are up
> > >> > >will be indicated by additional ServiceChanges on the up
> > terminations
> > using
> > >> > >method=restart, preferrably in the same message and using
> > wildcards were
> > >> > >possible.
> > >> >
> > >> > ...
> > >> >
> > >> > >Even though I think that most GWs probably would not register until
> > all or
> > >> > >most of their physical terminations are available, I would probably
> > prefer
> > >> > >#2 since I can easily indicated them all up with only one additional
> > >> > >ServiceChange and it seems more natural to indicate those up those
> > that are
> > >> > >down.  But I can be happy with either #1 or #2.
> > >> >
> > >> >     #2 has the added (slight?) advantage that physical termination ID
> > >> > mis-matches (between MGC and MG) are identified when the MG sends
> > >> > SVC(restart) on a termination ID unknown to the MGC.  #1
> > relies on MGC
> > >> > discovering these (non-existent) terminations 1 at a time, when
> > connections
> > >> > are attempted.  With #1, a mis-match of this type might go
> > undetected for
> > >> > days, until the MGC attempted to use/audit that particular
> > termination
> > ID.
> > >> >
> > >> >     Terminations known only to the MGC will still go
> > "undetected", but
> > >> > since no SVC(restart) is ever received for them, at least the MGC
> > would not
> > >> > be trying to use them.  An audit might eventually reveal the reason
> > for the
> > >> > OOS terminations.  (It is not unusual in "old" voice switches to have
> > >> > termination data populated without having the hardware yet
> > in place, so a
> > >> > mis-match cannot be considered an error in all cases.)
> > >> >
> > >> >     Is there an assumption that MG SVC(ROOT,restart) implies the
> > ephemeral
> > >> > interface(s) are all operational?  If it makes sense to
> > positively assert
> > >> > SVC(restart) on physical terminations, why wouldn't it also
> > make sense to
> > >> > indicate availability of ephemeral interfaces?  I'm thinking
> > particularly
> > >> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> > >> >
> > >> >     Assuming a reasonable SVC mechanism with "ranges"
> > exists, #2 is not a
> > >> > big burden after MG restart.  If SVC is needed for every individual
> > >> > physical termination, then #1 becomes attractive.
> > >> >
> > >> > Al Varney
> > >> >
> > >> > _______________________________________________
> > >> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
> > >Lucent Technologies/INS/Voice Over IP Access Networks
> > >Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > >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  Mon Apr 22 04:06: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 EAA18813
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 04:06:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA26136
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 04:06:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA24941;
	Mon, 22 Apr 2002 03:42:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA24910
	for <megaco@optimus.ietf.org>; Mon, 22 Apr 2002 03:42:38 -0400 (EDT)
Received: from ish7.ericsson.com.au (ish7.ericsson.com.au [203.61.155.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18453
	for <megaco@ietf.org>; Mon, 22 Apr 2002 03:42:35 -0400 (EDT)
Received: from brsf10.epa.ericsson.se (brsf10 [146.11.8.4])
	by ish7.ericsson.com.au (8.11.6+Sun/8.11.6) with ESMTP id g3M7f1017474
	for <megaco@ietf.org>; Mon, 22 Apr 2002 17:41:01 +1000 (EST)
Received: from ericsson.com.au (dhcp-239-110.epa.ericsson.se [146.11.239.110])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id RAA22245
	for <megaco@ietf.org>; Mon, 22 Apr 2002 17:42:36 +1000 (EST)
Message-ID: <3CC35E76.3B37C8F1@ericsson.com.au>
Date: Mon, 22 Apr 2002 10:51:02 +1000
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] ServiceChange for a single termination (Cold  Start)
References: <PLEEKKMMGAAKNGECENOPAEGICIAA.rms@acc.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,

In both H.248/Megaco v1 and v2 we have sect 7.1.5 stating that the default is
"in-service". I think now it is too late to change this to "inactive". It would
be a backwards incompatible change. Whilst not everyone will like it because
they have either big or small MG/MGCs, we had chosen to go done the "in-service"
path. 

The MGC can discover what terminations are on the MG by other means ie.
Provisioning, MIB or via the termination package.

Regards, Christian

Root Mean Square wrote:
> 
> Sankar,
> 
> I think I agree with everything you said.  In our case we have
> administrative and operational states for individual interfaces as well as
> the gateway as a whole.  If the administrative state of the MG is enabled,
> it will attempt to register with the MGC as soon as the MG cold starts.
> Individual interfaces may be adminsitratively disabled, or may be in an
> alarm or offline condition (e.g., physically removed from the chasis).
> Also, most of our interfaces are intelligent peripherals that need to
> download their code image after a cold start, and this may take several
> seconds, so they do not come online immediately.  We could wait several
> seconds after a cold start before attempting to register with the MGC, but
> we still need to deal with interfaces that are administratively disabled,
> are temporarily out-of-service or have fault conditions pending.
> 
> I understand that it would be optimal if the MG only had to send a single
> service change on root if all of its terminations are in-service and
> operational when it registers with the MGC.  However, making the default
> service state in-service has always seemed a little goofy to me.  If the
> default state were out-of-service, it may not reflect reality when the MG
> sends its initial service change on root, but it doesn't have any adverse
> side effects.  On the other hand, making the default state in-service does.
> 
> Making the default termination state out-of-service would seem to be more
> consistent with how large media gateways in fact operate -- that is, the
> service state of the signaling path between the MG and MGC is independent of
> the service state of individual terminations.  Using a technique similar to
> what Terry Anderson proposes may overcome most of the inefficiences
> associated with having to register interfaces or terminations as they come
> into service.  In our particular case, I would prefer to establish an
> association with the MGC, negotiate the protocol version and profile, and
> then deal with which terminations are in-service or not.  I don't think this
> can be cleanly done with a single service change command on root -- perhaps
> on a residential GW with a couple of terminations, but not on a large
> trunking GW with 1000's of terminations.
> 
> Cheers,
> Ron Stoughton
> 
> > -----Original Message-----
> > From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> > Sankar Raman
> > Sent: Friday, April 19, 2002 1:14 PM
> > To: Terry L Anderson; Christian Groves
> > Cc: vbajaj@hss.hns.com; Al Varney; megaco@ietf.org
> > Subject: Re: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> >
> >
> > Terry:
> >
> > In my expereince working with different swicthes and gateways,
> > typical internal implementation of these boxes are such that when
> > the box comes up, all T1 lines are asumed down untill they come up
> > in which case the T1 framer chip notifies this event to the upper layers.
> > Typical implementation is such that when the T1 hardware is reset, no
> > events will be generated until a line comes up. Line down evets are
> > generated by T1 hardware only if the line was up before.
> > This means, if a MGC asssumes on registation, that all lines are up, and
> > if certain do not come up at the MG, the MG will not be able to indicate
> > this to
> > the MGC, unless the MG implelements periodic polling of some sort.
> >
> > I feel, it is better, that default state for physical terminations,
> > when MGC registers with ROOT in service, should be out of service.
> > Upon registration, the MGC assumes all lines are down until explicitly
> > indicated
> > by service change by the MG for the physical lines. As lines come up
> > at the MG, the MG will send svcchg in svc for each as it happens.
> > This will be simpler for MGs and go with their typical internal
> > implementation.
> > (although it may generate more traffic which can be cut down by
> > using wildcard
> > for the lines).
> >
> > Also, this way MGs do not have to worry about how long should it wait for
> > all lines
> > to come up before registering with MGC. Some lines may never come
> > up due to
> > some
> > fault at the far end switch or may come up much later than some
> > other lines.
> >
> > At 11:47 AM 4/19/02 -0400, Terry L Anderson wrote:
> > >Christian
> > >Good point.  I missed the relevance of the ServiceState property
> > in 7.1.5.
> >  There is
> > >states that "in service" is default.  While Service State is not defined
> > to be
> > >precisely the same as ServiceChange forced and restart (maybe it
> > should be
> > for a
> > >termination), I agree that this default indicates the intention
> > defaulting to
> > >inservice.  Thus I think that my assumption #1 is the more consistent.  I
> > still think
> > >that the link between ServiceState and ServiceChange for a termination is
> > ambiguous
> >
> > >enough that it would be helpful to restate the assumption in 7.2.8.
> > >
> > >I propose we add the following to 7.2.8 at the end of the current Restart
> > entry:
> > >
> > >"When applied to ROOT, this specifies that the Media Gateway as a whole
> > will be in
> > >service and includes all its physical terminations which will be in their
> > default
> > >state ("in service").  Exceptions can be indicated by additional
> > ServiceChange
> > >commands."
> > >
> > >As Vikas points out, most uses of wildcard ALL assumes that MGC knows the
> > range of
> > >valid terminationIDs for the GW.  Packages have been proposed
> > (but not yet
> > approved)
> > >for MGC to discover this range if it is not known from
> > provisioning.  Sending
> > >individual (non-wildcard) ServiceChange for every distinct physical
> > termination would
> > >be legal but impractical for most large MGs.
> > >
> > >Al Varney asked:
> > >
> > >>  Is there an assumption that MG SVC(ROOT,restart) implies the ephemeral
> > >> interface(s) are all operational?  If it makes sense to
> > positively assert
> > >> SVC(restart) on physical terminations, why wouldn't it also
> > make sense to
> > >> indicate availability of ephemeral interfaces?  I'm thinking
> > particularly
> > >> of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> > >>
> > >
> > >There has been previous discussions about the applicability of
> > ServiceChange for
> > >ephemerals.  While there is nothing stating that one could not use
> > ServiceChange to
> > >take an ephemeral out of service, but since it would then be subtracted
> > from any
> > >context it was in, it would cease to exist and so could never be
> > "restarted".  Clearly
> > >serviceChange cannot be used to indicate whether an ephemeral Add will
> > succeed or not
> > >(availability of any underlying network or gateway resources).  I think
> > that the
> > >assumption is that if a GW is in service then any ephemeral Add can be
> > attempted.
> > >Failure of an underlying network can be indicated using nt/netfail, but
> > since events
> > >are only set on terminations, one must Add an ephemeral before such an
> > event can be
> > >used.
> > >
> > >I think we currently have no good way to announce that the MG is in
> > service but one or
> > >more classes of ephemerals are unavailable.  I think that a
> > specific error
> > to indicate
> > >this after an Add attempt might be sufficient (I don't believe that there
> > is a good
> > >one now).
> > >
> > >
> > >Christian Groves wrote:
> > >
> > >> G'Day Vikas,
> > >>
> > >> I believe you are getting what you asked for. The default state of all
> > >> terminaton is "inservice".
> > >> If the MG cold starts and sends ServiceChange on "ROOT" then
> > the MGC can
> > assume
> > >> that:
> > >> o as the MG is running and
> > >> o a MG contains terminations and
> > >> o the termination's natural state is "inservice"
> >
> > >> therefore the individual terminations are running also.
> > >>
> > >> Regards, Christian
> > >>
> > >> vbajaj@hss.hns.com wrote:
> > >> >
> > >> > Al,
> > >> >        The advantage you have cited below will hold true
> > only under the
> > >> > assumption
> > >> >   that MG sends ServiceChange for individual terminations instead of
> > using a
> > >> > wildcard.
> > >> >   Sending ServiceChange for individual terminations would be too
> > expensive in
> > >> > terms
> > >> >   of network bandwidth as well as MG processing for
> > extremely large sized
> > >> > Gateways.
> > >> >   I would expect that if MGC is interested in finding out
> > configuration
> > >> > inconsistencies
> > >> >   with its MGs, it would do an Audit at lesiure in parallel to
> > handling normal
> > >> > calls.
> > >> >
> > >> >  IMHO, "ServiceChange on ROOT" should indicate all
> > terminations are up
> > at the
> > >> > MG.
> > >> >  ServiceChange for Out Of Service Terminations can be sent
> > subsequently. Total
> > >> > number of messages required in this scenario would be
> > >> > (1 ServiceChange on ROOT + x ServiceChange for configured
> > but unequipped
> > >> > terminations)
> > >> >
> > >> > Even if we go by approach #2 suggested below, the latter step (i.e.
> > sending
> > >> > ServiceChange
> > >> > for Out Of Service Terminations) will anyway have to be executed.
> > >> >  Subsequent to a ServiceChange on ROOT, if MG uses Wildcarded
> > Termination Id
> > >> > to indicate that all terminations in the MG are In Service, it will
> > need to send
> > >> >  Out of Service ServiceChange for those terminations that have been
> > configured
> > >> >  but not hardware equipped. The number of messages required in this
> > scenario
> > >> > would be
> > >> >
> > >> > (1 ServiceChange on ROOT + 1 ServiceChange with Termination Id "*"+ n
> > >> > ServiceChange
> > >> >   for configured but unequipped terminations (Term Id =
> > "/TG!/Fac1/*))
> > >> >
> > >> > The MG may of course choose not to use a wildcarded
> > >> > termination signifiying all terminations on the MG and instead use
> > multiple
> > >> > ServiceChange commands each with a Termination Id (tg1/fac1/*) that
> > siginfies a
> > >> > DS0 aggregation. In this case, the number of ServiceChange commands
> > would equal
> > >> > the number of such DS0 aggregations in the MG i.e. several
> > ServiceChange
> > >> > messages
> > >> >  would be needed to complete the initial MG-MGC startup sequence. The
> > number of
> > >> >  messages required in this scenario would be
> > >> >
> > >> > (1 ServiceChange on ROOT + n ServiceChange for configured
> > and equipped
> > >> > terminations
> > >> >     (Term Id = "/TG!/Fac1/*))
> > >> >
> > >> > {Assuming most of the terminations in MG would be In Service, n could
> > be a large
> > >> > value unless
> > >> >   the MG is intelligent and can optimize on the number of messages}
> > >> >
> > >> > To summarize, IMO that number of (ServiceChange) messages required at
> > startup
> > >> >  would turn out to be larger in approach #2 than in approach #1. So,
> > why not
> > >> > choose
> > >> >  a strategy that is optimal ?
> > >> >
> > >> > Rgds,
> > >> >
> > >> > Vikas Bajaj
> > >> > NGN Group
> > >> > Hughes Software Systems
> > >> > (www.hssworld.com)
> > >> >
> > >> > Al Varney <varney@ieee.org> on 04/19/2002 04:59:53 AM
> > >> >
> > >> > To:   megaco@ietf.org
> > >> > cc:    (bcc: Vikas Bajaj/HSS)
> > >> >
> > >> > Subject:  Re: [Megaco] ServiceChange for a single termination (Cold
> > Start)
> > >> >
> >
> > >> > At 02:46 PM 4/18/02 -0400, Terry L Anderson wrote:
> > >> > >Possible clarifications:
> > >> > >ServiceChange on ROOT with method=restart (a registration):
> > >> > >1) implies that all physical terminations on MG are also
> > up.  Exceptions
> > >> > >should be indicated by additional ServiceChanges on the down
> > terminations
> > >> > >using Forced, preferrably in the same message and using
> > wildcards where
> > >> > >possible.
> > >> > >2) implies that all physical terminations on MG are down.
> > Those that
> > are up
> > >> > >will be indicated by additional ServiceChanges on the up
> > terminations
> > using
> > >> > >method=restart, preferrably in the same message and using
> > wildcards were
> > >> > >possible.
> > >> >
> > >> > ...
> > >> >
> > >> > >Even though I think that most GWs probably would not register until
> > all or
> > >> > >most of their physical terminations are available, I would probably
> > prefer
> > >> > >#2 since I can easily indicated them all up with only one additional
> > >> > >ServiceChange and it seems more natural to indicate those up those
> > that are
> > >> > >down.  But I can be happy with either #1 or #2.
> > >> >
> > >> >     #2 has the added (slight?) advantage that physical termination ID
> > >> > mis-matches (between MGC and MG) are identified when the MG sends
> > >> > SVC(restart) on a termination ID unknown to the MGC.  #1
> > relies on MGC
> > >> > discovering these (non-existent) terminations 1 at a time, when
> > connections
> > >> > are attempted.  With #1, a mis-match of this type might go
> > undetected for
> > >> > days, until the MGC attempted to use/audit that particular
> > termination
> > ID.
> > >> >
> > >> >     Terminations known only to the MGC will still go
> > "undetected", but
> > >> > since no SVC(restart) is ever received for them, at least the MGC
> > would not
> > >> > be trying to use them.  An audit might eventually reveal the reason
> > for the
> > >> > OOS terminations.  (It is not unusual in "old" voice switches to have
> > >> > termination data populated without having the hardware yet
> > in place, so a
> > >> > mis-match cannot be considered an error in all cases.)
> > >> >
> > >> >     Is there an assumption that MG SVC(ROOT,restart) implies the
> > ephemeral
> > >> > interface(s) are all operational?  If it makes sense to
> > positively assert
> > >> > SVC(restart) on physical terminations, why wouldn't it also
> > make sense to
> > >> > indicate availability of ephemeral interfaces?  I'm thinking
> > particularly
> > >> > of MGs with multiple ephemeral interfaces (IP, ATM, etc.).
> > >> >
> > >> >     Assuming a reasonable SVC mechanism with "ranges"
> > exists, #2 is not a
> > >> > big burden after MG restart.  If SVC is needed for every individual
> > >> > physical termination, then #1 becomes attractive.
> > >> >
> > >> > Al Varney
> > >> >
> > >> > _______________________________________________
> > >> > Megaco mailing 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:732.949.5628   Fax:732.949.7016
> > >Lucent Technologies/INS/Voice Over IP Access Networks
> > >Rm 2G-219A, 101 Crawfords Corner Rd, Holmdel, NJ 07733-3030
> > >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  Mon Apr 22 05:28: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 FAA20097
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 05:28:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA00918;
	Mon, 22 Apr 2002 05:10:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA00888
	for <megaco@optimus.ietf.org>; Mon, 22 Apr 2002 05:10:49 -0400 (EDT)
Received: from mx3.rambler.ru (mx3.rambler.ru [217.73.192.139])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19782
	for <megaco@ietf.org>; Mon, 22 Apr 2002 05:10:45 -0400 (EDT)
Received: from mail2.rambler.ru (mail2.rambler.ru [217.73.192.31])
	by mx3.rambler.ru (Postfix) with SMTP id D5A7912BB9D
	for <megaco@ietf.org>; Mon, 22 Apr 2002 13:09:40 +0400 (MSD)
Received: from 217.73.192.36 by rambler.ru with SMTP id AA27791 for
 megaco@ietf.org; Mon, 22 Apr 2002 13:08:38 +0400 (MSD)
From: Fhuval Hittay <fhuval@rambler.ru>
To: megaco@ietf.org
Message-Id: <3CC3D25F.AA06586@mb3.rambler.ru>
Content-Type: text/plain; charset=koi8-r
MIME-Version: 1.0
Date: Mon, 22 Apr 2002 13:05:35 +0400 (MSD)
Subject: [Megaco] Conferencing in 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


 Could anyone, please, clarify conferencing operations described in 
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the 
main button to form a conference, but how MGC could know, that "FlashHook" mean 
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the 
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

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


From daemon@optimus.ietf.org  Mon Apr 22 05:28: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 FAA20109
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 05:28:56 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA01687
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 05:29:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA00918;
	Mon, 22 Apr 2002 05:10:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA00888
	for <megaco@optimus.ietf.org>; Mon, 22 Apr 2002 05:10:49 -0400 (EDT)
Received: from mx3.rambler.ru (mx3.rambler.ru [217.73.192.139])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19782
	for <megaco@ietf.org>; Mon, 22 Apr 2002 05:10:45 -0400 (EDT)
Received: from mail2.rambler.ru (mail2.rambler.ru [217.73.192.31])
	by mx3.rambler.ru (Postfix) with SMTP id D5A7912BB9D
	for <megaco@ietf.org>; Mon, 22 Apr 2002 13:09:40 +0400 (MSD)
Received: from 217.73.192.36 by rambler.ru with SMTP id AA27791 for
 megaco@ietf.org; Mon, 22 Apr 2002 13:08:38 +0400 (MSD)
From: Fhuval Hittay <fhuval@rambler.ru>
To: megaco@ietf.org
Message-Id: <3CC3D25F.AA06586@mb3.rambler.ru>
Content-Type: text/plain; charset=koi8-r
MIME-Version: 1.0
Date: Mon, 22 Apr 2002 13:05:35 +0400 (MSD)
Subject: [Megaco] Conferencing in 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


 Could anyone, please, clarify conferencing operations described in 
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the 
main button to form a conference, but how MGC could know, that "FlashHook" mean 
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the 
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

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



From megaco-admin@ietf.org  Mon Apr 22 08: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 IAA24098
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 08:57:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11523;
	Mon, 22 Apr 2002 08:33:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11417
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 08:33:35 -0400 (EDT)
Received: from postman ([217.31.228.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23678
	for <megaco@ietf.org>; Mon, 22 Apr 2002 08:33:31 -0400 (EDT)
To: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF14BF3FC3.27340600-ONC2256BA3.00438402@LocalDomain>
From: "IPEK SARAC" <ipek.sarac@o2.com.tr>
Date: Mon, 22 Apr 2002 14:31:01 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 04/22/2002
 03:31:41 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Megaco] MGCP CRCX message Connection ID parameter placement
Sender: megaco-admin@ietf.org
Errors-To: 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,

As far as i know there is no seperate mailing list for MGCP so i am writing
here, if there is one please let me know.
While implementing MGCP we realized that ConnectionIdentifier parameter
which is the mandatory parameter for CreateConnectionResponse message ( and
also for that JAIN object constructor) can be anywhere within the response
message, this is not nice since every parameter involved in the response
message before that parameter must be stored until JAIN object is created.
For example :

a.)
This is a CRCX response message that can be created and filled up as a JAIN
object easily:

200 1059 ok
i:456789fedcba5
z2: ds/oc3-1@tgw1.whatever.net
i2: 657349af5647ffa4

v=0
o=- 23456789 98765432 IN IP4 192.168.5.7
s=-
c=IN IP4 192.168.5.7
t=0 0
m=audio 6058 RTP/AVP 0

b.)
For this one parameters before "i" parameter (second endpoint id and second
connection id parameters) must be stored in order not to read the whole
message for the second time while parsing.

200 1059 ok
z2: ds/oc3-1@tgw1.whatever.net
i2: 657349af5647ffa4
i:456789fedcba5

v=0
o=- 23456789 98765432 IN IP4 192.168.5.7
s=-
c=IN IP4 192.168.5.7
t=0 0
m=audio 6058 RTP/AVP 0

I couldn't find a constraint in RFC 2705 ( MGCP RFC) saying that mandatory
parameters come first in a message. Can you please explain why don't we
have such a constraint while it makes life much more easier and quicker in
terms of parsing.

Thank you.

Ipek Sarac


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


From daemon@ns.ietf.org  Mon Apr 22 08:58: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 IAA24108
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 08:58:00 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA12252
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 08:58:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11523;
	Mon, 22 Apr 2002 08:33:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11417
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 08:33:35 -0400 (EDT)
Received: from postman ([217.31.228.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23678
	for <megaco@ietf.org>; Mon, 22 Apr 2002 08:33:31 -0400 (EDT)
To: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.6a  January 17, 2001
Message-ID: <OF14BF3FC3.27340600-ONC2256BA3.00438402@LocalDomain>
From: "IPEK SARAC" <ipek.sarac@o2.com.tr>
Date: Mon, 22 Apr 2002 14:31:01 +0200
X-MIMETrack: Serialize by Router on OKSIJEN/OKSIJEN(Release 5.0.8 |June 18, 2001) at 04/22/2002
 03:31:41 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Megaco] MGCP CRCX message Connection ID parameter placement
Sender: megaco-admin@ietf.org
Errors-To: 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,

As far as i know there is no seperate mailing list for MGCP so i am writing
here, if there is one please let me know.
While implementing MGCP we realized that ConnectionIdentifier parameter
which is the mandatory parameter for CreateConnectionResponse message ( and
also for that JAIN object constructor) can be anywhere within the response
message, this is not nice since every parameter involved in the response
message before that parameter must be stored until JAIN object is created.
For example :

a.)
This is a CRCX response message that can be created and filled up as a JAIN
object easily:

200 1059 ok
i:456789fedcba5
z2: ds/oc3-1@tgw1.whatever.net
i2: 657349af5647ffa4

v=0
o=- 23456789 98765432 IN IP4 192.168.5.7
s=-
c=IN IP4 192.168.5.7
t=0 0
m=audio 6058 RTP/AVP 0

b.)
For this one parameters before "i" parameter (second endpoint id and second
connection id parameters) must be stored in order not to read the whole
message for the second time while parsing.

200 1059 ok
z2: ds/oc3-1@tgw1.whatever.net
i2: 657349af5647ffa4
i:456789fedcba5

v=0
o=- 23456789 98765432 IN IP4 192.168.5.7
s=-
c=IN IP4 192.168.5.7
t=0 0
m=audio 6058 RTP/AVP 0

I couldn't find a constraint in RFC 2705 ( MGCP RFC) saying that mandatory
parameters come first in a message. Can you please explain why don't we
have such a constraint while it makes life much more easier and quicker in
terms of parsing.

Thank you.

Ipek Sarac


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



From megaco-admin@ietf.org  Mon Apr 22 09:55: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 JAA25869
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 09:55:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13695;
	Mon, 22 Apr 2002 09:26:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13659
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 09:26:28 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24846
	for <megaco@ietf.org>; Mon, 22 Apr 2002 09:26:24 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3MDPNK12823;
	Mon, 22 Apr 2002 09:25:23 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'IPEK SARAC'" <ipek.sarac@o2.com.tr>, <megaco@ietf.org>
Cc: <mgcp@vovida.org>, "'MGCP Discussion List'" <MGCP@LISTSERV.PULVER.COM>
Subject: RE: [Megaco] MGCP CRCX message Connection ID parameter placement
Date: Mon, 22 Apr 2002 09:25:40 -0400
Message-ID: <000001c1ea01$32e0e170$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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <OF14BF3FC3.27340600-ONC2256BA3.00438402@LocalDomain>
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

Please mail your MGCP questions to the MGCP mailing list:

MGCP@LISTSERV.PULVER.COM

and/or

mgcp@vovida.org

Thanks
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
IPEK SARAC
Sent: Monday, April 22, 2002 8:31 AM
To: megaco@ietf.org
Subject: [Megaco] MGCP CRCX message Connection ID parameter placement


Hello,

As far as i know there is no seperate mailing list for MGCP so i am
writing here, if there is one please let me know. While implementing
MGCP we realized that ConnectionIdentifier parameter which is the
mandatory parameter for CreateConnectionResponse message ( and also for
that JAIN object constructor) can be anywhere within the response
message, this is not nice since every parameter involved in the response
message before that parameter must be stored until JAIN object is
created. For example :

a.)
This is a CRCX response message that can be created and filled up as a
JAIN object easily:

200 1059 ok
i:456789fedcba5
z2: ds/oc3-1@tgw1.whatever.net
i2: 657349af5647ffa4

v=0
o=- 23456789 98765432 IN IP4 192.168.5.7
s=-
c=IN IP4 192.168.5.7
t=0 0
m=audio 6058 RTP/AVP 0

b.)
For this one parameters before "i" parameter (second endpoint id and
second connection id parameters) must be stored in order not to read the
whole message for the second time while parsing.

200 1059 ok
z2: ds/oc3-1@tgw1.whatever.net
i2: 657349af5647ffa4
i:456789fedcba5

v=0
o=- 23456789 98765432 IN IP4 192.168.5.7
s=-
c=IN IP4 192.168.5.7
t=0 0
m=audio 6058 RTP/AVP 0

I couldn't find a constraint in RFC 2705 ( MGCP RFC) saying that
mandatory parameters come first in a message. Can you please explain why
don't we have such a constraint while it makes life much more easier and
quicker in terms of parsing.

Thank you.

Ipek Sarac


_______________________________________________
Megaco mailing list
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  Mon Apr 22 09: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 JAA25888
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 09:55:13 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA15666
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 09:55:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13695;
	Mon, 22 Apr 2002 09:26:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13659
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 09:26:28 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24846
	for <megaco@ietf.org>; Mon, 22 Apr 2002 09:26:24 -0400 (EDT)
Received: from Bala ([172.16.137.54])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3MDPNK12823;
	Mon, 22 Apr 2002 09:25:23 -0400 (EDT)
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'IPEK SARAC'" <ipek.sarac@o2.com.tr>, <megaco@ietf.org>
Cc: <mgcp@vovida.org>, "'MGCP Discussion List'" <MGCP@LISTSERV.PULVER.COM>
Subject: RE: [Megaco] MGCP CRCX message Connection ID parameter placement
Date: Mon, 22 Apr 2002 09:25:40 -0400
Message-ID: <000001c1ea01$32e0e170$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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
In-Reply-To: <OF14BF3FC3.27340600-ONC2256BA3.00438402@LocalDomain>
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

Please mail your MGCP questions to the MGCP mailing list:

MGCP@LISTSERV.PULVER.COM

and/or

mgcp@vovida.org

Thanks
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
IPEK SARAC
Sent: Monday, April 22, 2002 8:31 AM
To: megaco@ietf.org
Subject: [Megaco] MGCP CRCX message Connection ID parameter placement


Hello,

As far as i know there is no seperate mailing list for MGCP so i am
writing here, if there is one please let me know. While implementing
MGCP we realized that ConnectionIdentifier parameter which is the
mandatory parameter for CreateConnectionResponse message ( and also for
that JAIN object constructor) can be anywhere within the response
message, this is not nice since every parameter involved in the response
message before that parameter must be stored until JAIN object is
created. For example :

a.)
This is a CRCX response message that can be created and filled up as a
JAIN object easily:

200 1059 ok
i:456789fedcba5
z2: ds/oc3-1@tgw1.whatever.net
i2: 657349af5647ffa4

v=0
o=- 23456789 98765432 IN IP4 192.168.5.7
s=-
c=IN IP4 192.168.5.7
t=0 0
m=audio 6058 RTP/AVP 0

b.)
For this one parameters before "i" parameter (second endpoint id and
second connection id parameters) must be stored in order not to read the
whole message for the second time while parsing.

200 1059 ok
z2: ds/oc3-1@tgw1.whatever.net
i2: 657349af5647ffa4
i:456789fedcba5

v=0
o=- 23456789 98765432 IN IP4 192.168.5.7
s=-
c=IN IP4 192.168.5.7
t=0 0
m=audio 6058 RTP/AVP 0

I couldn't find a constraint in RFC 2705 ( MGCP RFC) saying that
mandatory parameters come first in a message. Can you please explain why
don't we have such a constraint while it makes life much more easier and
quicker in terms of parsing.

Thank you.

Ipek Sarac


_______________________________________________
Megaco mailing list
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 Apr 22 10:01: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 KAA26016
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 10:01:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA14556;
	Mon, 22 Apr 2002 09:34:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA01753
	for <megaco@optimus.ietf.org>; Mon, 22 Apr 2002 05:29:39 -0400 (EDT)
Received: from mail.szutstar.com ([210.21.224.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20159
	for <megaco@ietf.org>; Mon, 22 Apr 2002 05:29:34 -0400 (EDT)
Received: from minliu (nokia [172.16.250.1])
	by mail.szutstar.com (8.11.1/8.11.1) with SMTP id g3M9SMg03451;
	Mon, 22 Apr 2002 17:28:23 +0800
From: "Jackson.liu" <Jackson.liu@utstar.com>
To: <taylor@nortelnetworks.com>
Cc: <megaco@ietf.org>
Date: Mon, 22 Apr 2002 17:30:23 +0800
Message-ID: <NFBBJMGDGLMJFGMOPMEBOEAKCCAA.Jackson.liu@utstar.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id FAA01754
Subject: [Megaco] About mdeia negociation
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

Dear Taylor:
   I have some questions about media negociation. Would you so kind to solve the problerms?
   For instance, before establishing RTP connection, media negociation should be done. MG1 suports PCMA ,and ptime = 20, 30, 40 can be choosed.At the same time MG1 supports G.723 ,and ptime = 20, 40 can be supported. MG2 suports PCMA ,and ptime = 30, 40 can be choosed.At the same time MG2 supports G.722 ,and ptime = 40 can be supported. How can MG2 get the media capability of MG1's RTP port.
Do you think the following procedure is right or not? Let's highlight at the SDP session:
Step1:
    MGC to MG1:
          Local{
                       v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP $
                    }
Step2:
    MG1 to MGC:
              Local{
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:20
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:30
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:40
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:30
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:40
                     }
Step 3:
     MGC to MG2
                   Local{
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 8
                      a=ptime:20
                      v=0
                      c=IN IP4  $
                      m=audio $ RTP/AVP 8
                      a=ptime:30
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 8
                      a=ptime:40
                     v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 4
                      a=ptime:30
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 4
                      a=ptime:40
                       }        
Step3:
    MG2 to MGC:
              Local{
                      v=0
                      c=IN IP4 209.110.59.34
                      m=audio 1050 RTP/AVP 8
                      a=ptime:30  
                       }      
Step 4 
     MGC to MG1:
              remote{
                      v=0
                      c=IN IP4 209.110.59.34
                      m=audio 1050 RTP/AVP 8
                      a=ptime:30  
                           }

    It seems so clumsy to negotiate media information in this way. Is there any other efficient method?

Best Regards

Jackson.liu


              
 


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


From daemon@ns.ietf.org  Mon Apr 22 10:01: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 KAA26025
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 10:01:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA16323
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 10:01:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA14556;
	Mon, 22 Apr 2002 09:34:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA01753
	for <megaco@optimus.ietf.org>; Mon, 22 Apr 2002 05:29:39 -0400 (EDT)
Received: from mail.szutstar.com ([210.21.224.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20159
	for <megaco@ietf.org>; Mon, 22 Apr 2002 05:29:34 -0400 (EDT)
Received: from minliu (nokia [172.16.250.1])
	by mail.szutstar.com (8.11.1/8.11.1) with SMTP id g3M9SMg03451;
	Mon, 22 Apr 2002 17:28:23 +0800
From: "Jackson.liu" <Jackson.liu@utstar.com>
To: <taylor@nortelnetworks.com>
Cc: <megaco@ietf.org>
Date: Mon, 22 Apr 2002 17:30:23 +0800
Message-ID: <NFBBJMGDGLMJFGMOPMEBOEAKCCAA.Jackson.liu@utstar.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id FAA01754
Subject: [Megaco] About mdeia negociation
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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

Dear Taylor:
   I have some questions about media negociation. Would you so kind to solve the problerms?
   For instance, before establishing RTP connection, media negociation should be done. MG1 suports PCMA ,and ptime = 20, 30, 40 can be choosed.At the same time MG1 supports G.723 ,and ptime = 20, 40 can be supported. MG2 suports PCMA ,and ptime = 30, 40 can be choosed.At the same time MG2 supports G.722 ,and ptime = 40 can be supported. How can MG2 get the media capability of MG1's RTP port.
Do you think the following procedure is right or not? Let's highlight at the SDP session:
Step1:
    MGC to MG1:
          Local{
                       v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP $
                    }
Step2:
    MG1 to MGC:
              Local{
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:20
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:30
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:40
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:30
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:40
                     }
Step 3:
     MGC to MG2
                   Local{
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 8
                      a=ptime:20
                      v=0
                      c=IN IP4  $
                      m=audio $ RTP/AVP 8
                      a=ptime:30
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 8
                      a=ptime:40
                     v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 4
                      a=ptime:30
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 4
                      a=ptime:40
                       }        
Step3:
    MG2 to MGC:
              Local{
                      v=0
                      c=IN IP4 209.110.59.34
                      m=audio 1050 RTP/AVP 8
                      a=ptime:30  
                       }      
Step 4 
     MGC to MG1:
              remote{
                      v=0
                      c=IN IP4 209.110.59.34
                      m=audio 1050 RTP/AVP 8
                      a=ptime:30  
                           }

    It seems so clumsy to negotiate media information in this way. Is there any other efficient method?

Best Regards

Jackson.liu


              
 


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



From megaco-admin@ietf.org  Mon Apr 22 11:16: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 LAA28738
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 11:16:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19526;
	Mon, 22 Apr 2002 10:54:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19497
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 10:54:54 -0400 (EDT)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28009
	for <megaco@ietf.org>; Mon, 22 Apr 2002 10:54:50 -0400 (EDT)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AHY99377;
	Mon, 22 Apr 2002 10:54:16 -0400 (EDT)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Fhuval Hittay'" <fhuval@rambler.ru>, <megaco@ietf.org>
Subject: RE: [Megaco] Conferencing in MEGACO
Date: Mon, 22 Apr 2002 10:47:47 -0400
Message-ID: <04bb01c1ea0c$abf82cc0$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <3CC3D25F.AA06586@mb3.rambler.ru>
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 Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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


From daemon@ns.ietf.org  Mon Apr 22 11:17: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 LAA28755
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 11:17:03 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA20848
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 11:17:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19526;
	Mon, 22 Apr 2002 10:54:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19497
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 10:54:54 -0400 (EDT)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28009
	for <megaco@ietf.org>; Mon, 22 Apr 2002 10:54:50 -0400 (EDT)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AHY99377;
	Mon, 22 Apr 2002 10:54:16 -0400 (EDT)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'Fhuval Hittay'" <fhuval@rambler.ru>, <megaco@ietf.org>
Subject: RE: [Megaco] Conferencing in MEGACO
Date: Mon, 22 Apr 2002 10:47:47 -0400
Message-ID: <04bb01c1ea0c$abf82cc0$c500a8c0@MBRAHMANAPALLY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <3CC3D25F.AA06586@mb3.rambler.ru>
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 Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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



From megaco-admin@ietf.org  Mon Apr 22 12:05: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 MAA00506
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 12:05:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21061;
	Mon, 22 Apr 2002 11:20:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21007
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 11:20:52 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28809
	for <megaco@ietf.org>; Mon, 22 Apr 2002 11:20:47 -0400 (EDT)
From: rezhirpavai@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 g3MFLQc01304;
	Mon, 22 Apr 2002 20:51:26 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA3.005407FD ; Mon, 22 Apr 2002 20:47:50 +0530
X-Lotus-FromDomain: HSS
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
cc: "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
Message-ID: <65256BA3.0053F6B2.00@sandesh.hss.hns.com>
Date: Mon, 22 Apr 2002 20:49:44 +0530
Subject: RE: [Megaco] Conferencing in MEGACO
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



Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing a
hookflash. Only difference is the action that follow subscriber going on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47 PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



_______________________________________________
Megaco mailing list
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  Mon Apr 22 12:05: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 MAA00523
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 12:05:09 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA25478
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 12:05:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21061;
	Mon, 22 Apr 2002 11:20:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21007
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 11:20:52 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28809
	for <megaco@ietf.org>; Mon, 22 Apr 2002 11:20:47 -0400 (EDT)
From: rezhirpavai@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 g3MFLQc01304;
	Mon, 22 Apr 2002 20:51:26 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA3.005407FD ; Mon, 22 Apr 2002 20:47:50 +0530
X-Lotus-FromDomain: HSS
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
cc: "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
Message-ID: <65256BA3.0053F6B2.00@sandesh.hss.hns.com>
Date: Mon, 22 Apr 2002 20:49:44 +0530
Subject: RE: [Megaco] Conferencing in MEGACO
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



Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing a
hookflash. Only difference is the action that follow subscriber going on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47 PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



_______________________________________________
Megaco mailing list
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 Apr 22 12:10: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 MAA00802
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 12:10:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA22919;
	Mon, 22 Apr 2002 11:48:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA22890
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 11:48:44 -0400 (EDT)
Received: from ns1.ottawa.alcatel.ca (ns1.ottawa.alcatel.ca [192.75.23.67])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA29619
	for <megaco@ietf.org>; Mon, 22 Apr 2002 11:48:39 -0400 (EDT)
Received: (qmail 6070 invoked from network); 22 Apr 2002 15:34:39 -0000
Received: from portal.ottawa.alcatel.ca (HELO mx1.ca.alcatel.com) (192.75.23.76)
  by ns1.ottawa.alcatel.ca with SMTP; 22 Apr 2002 15:34:39 -0000
Received: (qmail 3182 invoked from network); 22 Apr 2002 15:50:37 -0000
Received: (ofmipd 138.120.45.50); 22 Apr 2002 15:50:15 -0000
Date: 22 Apr 2002 11:48:29 -0400
Message-ID: <3CC430CD.646E1EEF@alcatel.com>
From: "Ian Leighton" <Ian.Leighton@alcatel.com>
To: "Jackson.liu" <Jackson.liu@utstar.com>
Cc: megaco@ietf.org
X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: [Megaco] About mdeia negociation
References: <NFBBJMGDGLMJFGMOPMEBOEAKCCAA.Jackson.liu@utstar.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 Jackson

As an alternative the message from MGC to MG2 in step 3 could include a Local descriptor with $ in the c line <connection-address > field and $ in the <port> and <fmt> fields of the m line. Also the Local descriptor from MG1 could be encoded in the Remote descriptor to MG2. For example

     MGC to MG2
          Local{
                       v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP $
                    }
           Remote{
                      v=0
                      o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:20
                      v=0
                      o=- blah blah blah
                      s=-
                      t=0 0
                     c=IN IP4  209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:30
                      v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:40
                     v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:30
                      v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:40
                       }

In other words the MGC requests MG2 to select its Local characteristics based one of the alternatives included in the Remote Descriptor.

Also note that I have added the o, t and s lines which should be included in SDP's sent from the MG.

Regards
Ian Leighton

"Jackson.liu" wrote:

> Dear Taylor:
>    I have some questions about media negociation. Would you so kind to solve the problerms?
>    For instance, before establishing RTP connection, media negociation should be done. MG1 suports PCMA ,and ptime = 20, 30, 40 can be choosed.At the same time MG1 supports G.723 ,and ptime = 20, 40 can be supported. MG2 suports PCMA ,and ptime = 30, 40 can be choosed.At the same time MG2 supports G.722 ,and ptime = 40 can be supported. How can MG2 get the media capability of MG1's RTP port.
> Do you think the following procedure is right or not? Let's highlight at the SDP session:
> Step1:
>     MGC to MG1:
>           Local{
>                        v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP $
>                     }
> Step2:
>     MG1 to MGC:
>               Local{
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:20
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:40
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 4
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 4
>                       a=ptime:40
>                      }
> Step 3:
>      MGC to MG2
>                    Local{
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:20
>                       v=0
>                       c=IN IP4  $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:40
>                      v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 4
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 4
>                       a=ptime:40
>                        }
> Step3:
>     MG2 to MGC:
>               Local{
>                       v=0
>                       c=IN IP4 209.110.59.34
>                       m=audio 1050 RTP/AVP 8
>                       a=ptime:30
>                        }
> Step 4
>      MGC to MG1:
>               remote{
>                       v=0
>                       c=IN IP4 209.110.59.34
>                       m=audio 1050 RTP/AVP 8
>                       a=ptime:30
>                            }
>
>     It seems so clumsy to negotiate media information in this way. Is there any other efficient method?
>
> Best Regards
>
> Jackson.liu
>
>
>
>
> _______________________________________________
> Megaco mailing list
> 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  Mon Apr 22 12:10: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 MAA00814
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 12:10:52 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA25789
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 12:10:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA22919;
	Mon, 22 Apr 2002 11:48:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA22890
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 11:48:44 -0400 (EDT)
Received: from ns1.ottawa.alcatel.ca (ns1.ottawa.alcatel.ca [192.75.23.67])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA29619
	for <megaco@ietf.org>; Mon, 22 Apr 2002 11:48:39 -0400 (EDT)
Received: (qmail 6070 invoked from network); 22 Apr 2002 15:34:39 -0000
Received: from portal.ottawa.alcatel.ca (HELO mx1.ca.alcatel.com) (192.75.23.76)
  by ns1.ottawa.alcatel.ca with SMTP; 22 Apr 2002 15:34:39 -0000
Received: (qmail 3182 invoked from network); 22 Apr 2002 15:50:37 -0000
Received: (ofmipd 138.120.45.50); 22 Apr 2002 15:50:15 -0000
Date: 22 Apr 2002 11:48:29 -0400
Message-ID: <3CC430CD.646E1EEF@alcatel.com>
From: "Ian Leighton" <Ian.Leighton@alcatel.com>
To: "Jackson.liu" <Jackson.liu@utstar.com>
Cc: megaco@ietf.org
X-Mailer: Mozilla 4.73 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: [Megaco] About mdeia negociation
References: <NFBBJMGDGLMJFGMOPMEBOEAKCCAA.Jackson.liu@utstar.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 Jackson

As an alternative the message from MGC to MG2 in step 3 could include a Local descriptor with $ in the c line <connection-address > field and $ in the <port> and <fmt> fields of the m line. Also the Local descriptor from MG1 could be encoded in the Remote descriptor to MG2. For example

     MGC to MG2
          Local{
                       v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP $
                    }
           Remote{
                      v=0
                      o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:20
                      v=0
                      o=- blah blah blah
                      s=-
                      t=0 0
                     c=IN IP4  209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:30
                      v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:40
                     v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:30
                      v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:40
                       }

In other words the MGC requests MG2 to select its Local characteristics based one of the alternatives included in the Remote Descriptor.

Also note that I have added the o, t and s lines which should be included in SDP's sent from the MG.

Regards
Ian Leighton

"Jackson.liu" wrote:

> Dear Taylor:
>    I have some questions about media negociation. Would you so kind to solve the problerms?
>    For instance, before establishing RTP connection, media negociation should be done. MG1 suports PCMA ,and ptime = 20, 30, 40 can be choosed.At the same time MG1 supports G.723 ,and ptime = 20, 40 can be supported. MG2 suports PCMA ,and ptime = 30, 40 can be choosed.At the same time MG2 supports G.722 ,and ptime = 40 can be supported. How can MG2 get the media capability of MG1's RTP port.
> Do you think the following procedure is right or not? Let's highlight at the SDP session:
> Step1:
>     MGC to MG1:
>           Local{
>                        v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP $
>                     }
> Step2:
>     MG1 to MGC:
>               Local{
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:20
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:40
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 4
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 4
>                       a=ptime:40
>                      }
> Step 3:
>      MGC to MG2
>                    Local{
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:20
>                       v=0
>                       c=IN IP4  $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:40
>                      v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 4
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 4
>                       a=ptime:40
>                        }
> Step3:
>     MG2 to MGC:
>               Local{
>                       v=0
>                       c=IN IP4 209.110.59.34
>                       m=audio 1050 RTP/AVP 8
>                       a=ptime:30
>                        }
> Step 4
>      MGC to MG1:
>               remote{
>                       v=0
>                       c=IN IP4 209.110.59.34
>                       m=audio 1050 RTP/AVP 8
>                       a=ptime:30
>                            }
>
>     It seems so clumsy to negotiate media information in this way. Is there any other efficient method?
>
> Best Regards
>
> Jackson.liu
>
>
>
>
> _______________________________________________
> Megaco mailing list
> 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 Apr 22 16:12: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 QAA11271
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 16:12:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15034;
	Mon, 22 Apr 2002 15:53:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15004
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 15:53:20 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10646
	for <megaco@ietf.org>; Mon, 22 Apr 2002 15:53:15 -0400 (EDT)
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 g3MJqkP12575
	for <megaco@ietf.org>; Mon, 22 Apr 2002 15:52:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCV20TRF>; Mon, 22 Apr 2002 15:52:47 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A34D@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Jackson.liu'" <Jackson.liu@utstar.com>
Cc: megaco@ietf.org
Date: Mon, 22 Apr 2002 15:52:46 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: About mdeia negociation
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Half of the clumsiness can be eliminated.  We require the MG to send
SDP-conformant Local and Remote descriptors to the MGC, so the latter can
pass them on unchanged when using SIP.  (But SIP puts a limit on the
information that can be exchanged which means the MGC has to do some editing
in any event.)  However, in the MGC to MG direction we can use ranges, for
one thing, so your third message from MGC to MG2 can be shortened to:

 Local{
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 8
                      a=ptime:[20:40]
                     v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 4
                      a=ptime:[30:40]
                       } 

-----Original Message-----
From: Jackson.liu [mailto:Jackson.liu@utstar.com]
Sent: Monday, April 22, 2002 5:30 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: About mdeia negociation


Dear Taylor:
   I have some questions about media negociation. Would you so kind to solve
the problerms?
   For instance, before establishing RTP connection, media negociation
should be done. MG1 suports PCMA ,and ptime = 20, 30, 40 can be choosed.At
the same time MG1 supports G.723 ,and ptime = 20, 40 can be supported. MG2
suports PCMA ,and ptime = 30, 40 can be choosed.At the same time MG2
supports G.722 ,and ptime = 40 can be supported. How can MG2 get the media
capability of MG1's RTP port.
Do you think the following procedure is right or not? Let's highlight at the
SDP session:
Step1:
    MGC to MG1:
          Local{
                       v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP $
                    }
Step2:
    MG1 to MGC:
              Local{
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:20
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:30
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:40
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:30
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:40
                     }
Step 3:
     MGC to MG2
                   Local{
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 8
                      a=ptime:20
                      v=0
                      c=IN IP4  $
                      m=audio $ RTP/AVP 8
                      a=ptime:30
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 8
                      a=ptime:40
                     v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 4
                      a=ptime:30
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 4
                      a=ptime:40
                       }        
Step3:
    MG2 to MGC:
              Local{
                      v=0
                      c=IN IP4 209.110.59.34
                      m=audio 1050 RTP/AVP 8
                      a=ptime:30  
                       }      
Step 4 
     MGC to MG1:
              remote{
                      v=0
                      c=IN IP4 209.110.59.34
                      m=audio 1050 RTP/AVP 8
                      a=ptime:30  
                           }

    It seems so clumsy to negotiate media information in this way. Is there
any other efficient method?

Best Regards

Jackson.liu


              
 

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


From daemon@ns.ietf.org  Mon Apr 22 16:12: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 QAA11281
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 16:12:56 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA16421
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 16:13:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15034;
	Mon, 22 Apr 2002 15:53:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA15004
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 15:53:20 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10646
	for <megaco@ietf.org>; Mon, 22 Apr 2002 15:53:15 -0400 (EDT)
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 g3MJqkP12575
	for <megaco@ietf.org>; Mon, 22 Apr 2002 15:52:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCV20TRF>; Mon, 22 Apr 2002 15:52:47 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A34D@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Jackson.liu'" <Jackson.liu@utstar.com>
Cc: megaco@ietf.org
Date: Mon, 22 Apr 2002 15:52:46 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: About mdeia negociation
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Half of the clumsiness can be eliminated.  We require the MG to send
SDP-conformant Local and Remote descriptors to the MGC, so the latter can
pass them on unchanged when using SIP.  (But SIP puts a limit on the
information that can be exchanged which means the MGC has to do some editing
in any event.)  However, in the MGC to MG direction we can use ranges, for
one thing, so your third message from MGC to MG2 can be shortened to:

 Local{
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 8
                      a=ptime:[20:40]
                     v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 4
                      a=ptime:[30:40]
                       } 

-----Original Message-----
From: Jackson.liu [mailto:Jackson.liu@utstar.com]
Sent: Monday, April 22, 2002 5:30 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: About mdeia negociation


Dear Taylor:
   I have some questions about media negociation. Would you so kind to solve
the problerms?
   For instance, before establishing RTP connection, media negociation
should be done. MG1 suports PCMA ,and ptime = 20, 30, 40 can be choosed.At
the same time MG1 supports G.723 ,and ptime = 20, 40 can be supported. MG2
suports PCMA ,and ptime = 30, 40 can be choosed.At the same time MG2
supports G.722 ,and ptime = 40 can be supported. How can MG2 get the media
capability of MG1's RTP port.
Do you think the following procedure is right or not? Let's highlight at the
SDP session:
Step1:
    MGC to MG1:
          Local{
                       v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP $
                    }
Step2:
    MG1 to MGC:
              Local{
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:20
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:30
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:40
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:30
                      v=0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:40
                     }
Step 3:
     MGC to MG2
                   Local{
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 8
                      a=ptime:20
                      v=0
                      c=IN IP4  $
                      m=audio $ RTP/AVP 8
                      a=ptime:30
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 8
                      a=ptime:40
                     v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 4
                      a=ptime:30
                      v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP 4
                      a=ptime:40
                       }        
Step3:
    MG2 to MGC:
              Local{
                      v=0
                      c=IN IP4 209.110.59.34
                      m=audio 1050 RTP/AVP 8
                      a=ptime:30  
                       }      
Step 4 
     MGC to MG1:
              remote{
                      v=0
                      c=IN IP4 209.110.59.34
                      m=audio 1050 RTP/AVP 8
                      a=ptime:30  
                           }

    It seems so clumsy to negotiate media information in this way. Is there
any other efficient method?

Best Regards

Jackson.liu


              
 

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



From megaco-admin@ietf.org  Mon Apr 22 18:30: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 SAA16772
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 18:30:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25352;
	Mon, 22 Apr 2002 18:14:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25308
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 18:14:18 -0400 (EDT)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16505
	for <megaco@ietf.org>; Mon, 22 Apr 2002 18:14:12 -0400 (EDT)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AHZ20532;
	Mon, 22 Apr 2002 18:13:34 -0400 (EDT)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: <rezhirpavai@hss.hns.com>
Cc: "'Fhuval Hittay'" <fhuval@rambler.ru>, <megaco@ietf.org>
Subject: RE: [Megaco] Conferencing in MEGACO
Date: Mon, 22 Apr 2002 18:07:02 -0400
Message-ID: <04d001c1ea4a$099d0750$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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <65256BA3.0053F6B2.00@sandesh.hss.hns.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 Pavai,
What is this "service requirement" that disallows a user from having both
the call transfer and 3 way calling feature???
Regards
Madhubabu

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Monday, April 22, 2002 11:20 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing
a
hookflash. Only difference is the action that follow subscriber going
on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47 PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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




---
[This E-mail was scanned for viruses and is clean.]



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


From daemon@ns.ietf.org  Mon Apr 22 18:30: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 SAA16787
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 18:30:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA26160
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 18:30:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25352;
	Mon, 22 Apr 2002 18:14:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25308
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 18:14:18 -0400 (EDT)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16505
	for <megaco@ietf.org>; Mon, 22 Apr 2002 18:14:12 -0400 (EDT)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AHZ20532;
	Mon, 22 Apr 2002 18:13:34 -0400 (EDT)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: <rezhirpavai@hss.hns.com>
Cc: "'Fhuval Hittay'" <fhuval@rambler.ru>, <megaco@ietf.org>
Subject: RE: [Megaco] Conferencing in MEGACO
Date: Mon, 22 Apr 2002 18:07:02 -0400
Message-ID: <04d001c1ea4a$099d0750$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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <65256BA3.0053F6B2.00@sandesh.hss.hns.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 Pavai,
What is this "service requirement" that disallows a user from having both
the call transfer and 3 way calling feature???
Regards
Madhubabu

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Monday, April 22, 2002 11:20 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing
a
hookflash. Only difference is the action that follow subscriber going
on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47 PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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




---
[This E-mail was scanned for viruses and is clean.]



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



From megaco-admin@ietf.org  Mon Apr 22 19:26: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 TAA17748
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 19:26:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28250;
	Mon, 22 Apr 2002 19:06:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28220
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 19:06:54 -0400 (EDT)
Received: from exchange.cedarpointcom.com (mail.cedarpointcom.com [64.80.26.186])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17431
	for <megaco@ietf.org>; Mon, 22 Apr 2002 19:06:50 -0400 (EDT)
Content-Class: urn:content-classes:message
Subject: RE: [Megaco] Conferencing in MEGACO
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Date: Mon, 22 Apr 2002 19:06:52 -0400
Message-ID: <66F2ACFAB4E7764EAF85274020DD5342440C5D@exchange.cedarpointcom.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Topic: [Megaco] Conferencing in MEGACO
Thread-Index: AcHqE641BM8X/OZrSzi71LM+APBsqQAPUSDQ
From: "Mishra, Rajesh" <rmishra@cedarpointcom.com>
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>,
        "Fhuval Hittay" <fhuval@rambler.ru>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id TAA28221
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 Fhuval!
   I do not see problem with the call flow, to further clarify let's take the following example:

A calls B and they are in session.

then B does Hook Flash

at this time (assuming B has subscribed to any of the flash based services) the voice path between A and B will be broken and 
B will be fed secondary dial tone. A is put on hold.

Please note that at this we do not attach any meaning to the flash (whether TWC or CT) at this time.

now B dials a new number (let's say C) and B and C are in conversation state.

Now B's flash has lot's of  different meaning depending on how services are implemented 

e.g. : 1. One can implement flash from B meaning conf among A, B & C typical north American style.
        2. Other options could be flash followed by digit 1 means  B talking to A and C is put on hold then Flash followed by digit 2 means B talking to C again and A is put on hold.  Flash followed by digit 3 mean conf.

Typically in north America conf is flash (as in case 1) and transfer is B goes on hook while talking to C in that case A is transferred to C.

So it really depends on how services are implemented.


regards,
Rajesh Mishra

	

-----Original Message-----
From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
Sent: Monday, April 22, 2002 10:48 AM
To: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO


hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



_______________________________________________
Megaco mailing list
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  Mon Apr 22 19:26: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 TAA17763
	for <megaco-archive@odin.ietf.org>; Mon, 22 Apr 2002 19:26:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA28993
	for megaco-archive@odin.ietf.org; Mon, 22 Apr 2002 19:26:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28250;
	Mon, 22 Apr 2002 19:06:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28220
	for <megaco@ns.ietf.org>; Mon, 22 Apr 2002 19:06:54 -0400 (EDT)
Received: from exchange.cedarpointcom.com (mail.cedarpointcom.com [64.80.26.186])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17431
	for <megaco@ietf.org>; Mon, 22 Apr 2002 19:06:50 -0400 (EDT)
Content-Class: urn:content-classes:message
Subject: RE: [Megaco] Conferencing in MEGACO
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Date: Mon, 22 Apr 2002 19:06:52 -0400
Message-ID: <66F2ACFAB4E7764EAF85274020DD5342440C5D@exchange.cedarpointcom.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Topic: [Megaco] Conferencing in MEGACO
Thread-Index: AcHqE641BM8X/OZrSzi71LM+APBsqQAPUSDQ
From: "Mishra, Rajesh" <rmishra@cedarpointcom.com>
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>,
        "Fhuval Hittay" <fhuval@rambler.ru>, <megaco@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id TAA28221
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 Fhuval!
   I do not see problem with the call flow, to further clarify let's take the following example:

A calls B and they are in session.

then B does Hook Flash

at this time (assuming B has subscribed to any of the flash based services) the voice path between A and B will be broken and 
B will be fed secondary dial tone. A is put on hold.

Please note that at this we do not attach any meaning to the flash (whether TWC or CT) at this time.

now B dials a new number (let's say C) and B and C are in conversation state.

Now B's flash has lot's of  different meaning depending on how services are implemented 

e.g. : 1. One can implement flash from B meaning conf among A, B & C typical north American style.
        2. Other options could be flash followed by digit 1 means  B talking to A and C is put on hold then Flash followed by digit 2 means B talking to C again and A is put on hold.  Flash followed by digit 3 mean conf.

Typically in north America conf is flash (as in case 1) and transfer is B goes on hook while talking to C in that case A is transferred to C.

So it really depends on how services are implemented.


regards,
Rajesh Mishra

	

-----Original Message-----
From: Madhu Babu Brahmanapally [mailto:madhubabu@kenetec.com]
Sent: Monday, April 22, 2002 10:48 AM
To: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO


hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



_______________________________________________
Megaco mailing list
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 Apr 23 00:24: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 AAA25395
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 00:24:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA14985;
	Tue, 23 Apr 2002 00:02:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA14945
	for <megaco@optimus.ietf.org>; Tue, 23 Apr 2002 00:02:04 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24514
	for <megaco@ietf.org>; Tue, 23 Apr 2002 00:02:01 -0400 (EDT)
From: rezhirpavai@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 g3N42Ic22499;
	Tue, 23 Apr 2002 09:32:19 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA4.0015D96C ; Tue, 23 Apr 2002 09:28:39 +0530
X-Lotus-FromDomain: HSS
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
cc: "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
Message-ID: <65256BA4.0015BC84.00@sandesh.hss.hns.com>
Date: Tue, 23 Apr 2002 09:30:07 +0530
Subject: RE: [Megaco] Conferencing in MEGACO
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



Hello Madhu,
     By "Service Requirement" I mean the service specifications of these
services. It disallows both these services for single subscriber as the exchange
(MGC in our case) should know whether the subscriber wants to transfer the call
or clear the call when the subscriber invoking the conference disconnects the
call.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/23/2002 03:37:02 AM

To:   R Ezhirpavai/HSS@HSS
cc:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org

Subject:  RE: [Megaco] Conferencing in MEGACO




HI Pavai,
What is this "service requirement" that disallows a user from having both
the call transfer and 3 way calling feature???
Regards
Madhubabu

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Monday, April 22, 2002 11:20 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing
a
hookflash. Only difference is the action that follow subscriber going
on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47 PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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




---
[This E-mail was scanned for viruses and is clean.]







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


From daemon@optimus.ietf.org  Tue Apr 23 00:24: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 AAA25409
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 00:24:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA15748
	for megaco-archive@odin.ietf.org; Tue, 23 Apr 2002 00:24:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA14985;
	Tue, 23 Apr 2002 00:02:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA14945
	for <megaco@optimus.ietf.org>; Tue, 23 Apr 2002 00:02:04 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24514
	for <megaco@ietf.org>; Tue, 23 Apr 2002 00:02:01 -0400 (EDT)
From: rezhirpavai@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 g3N42Ic22499;
	Tue, 23 Apr 2002 09:32:19 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA4.0015D96C ; Tue, 23 Apr 2002 09:28:39 +0530
X-Lotus-FromDomain: HSS
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
cc: "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
Message-ID: <65256BA4.0015BC84.00@sandesh.hss.hns.com>
Date: Tue, 23 Apr 2002 09:30:07 +0530
Subject: RE: [Megaco] Conferencing in MEGACO
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



Hello Madhu,
     By "Service Requirement" I mean the service specifications of these
services. It disallows both these services for single subscriber as the exchange
(MGC in our case) should know whether the subscriber wants to transfer the call
or clear the call when the subscriber invoking the conference disconnects the
call.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/23/2002 03:37:02 AM

To:   R Ezhirpavai/HSS@HSS
cc:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org

Subject:  RE: [Megaco] Conferencing in MEGACO




HI Pavai,
What is this "service requirement" that disallows a user from having both
the call transfer and 3 way calling feature???
Regards
Madhubabu

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Monday, April 22, 2002 11:20 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing
a
hookflash. Only difference is the action that follow subscriber going
on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47 PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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




---
[This E-mail was scanned for viruses and is clean.]







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



From megaco-admin@ietf.org  Tue Apr 23 01:29: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 BAA28331
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 01:29:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA17655;
	Tue, 23 Apr 2002 01:03:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA17627
	for <megaco@optimus.ietf.org>; Tue, 23 Apr 2002 01:03:23 -0400 (EDT)
Received: from mailgate.sbell.com.cn (mailgate.sbell.com.cn [202.96.203.173])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27881
	for <megaco@ietf.org>; Tue, 23 Apr 2002 01:03:19 -0400 (EDT)
Received: from bellnet-mail4.sbell.com.cn (bellnet-mail4.sbell.com.cn [202.96.203.174])
	by mailgate.sbell.com.cn (8.9.2/8.9.2) with ESMTP id MAA07698;
	Tue, 23 Apr 2002 12:50:38 +0800 (CST)
Received: from bellnet-mail1.sbell.com.cn ([202.96.203.171]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 23 Apr 2002 13:02:41 +0800
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="gb2312"
Subject: RE: [Megaco] About mdeia negociation
Date: Tue, 23 Apr 2002 13:02:41 +0800
Message-ID: <C65F869D22451348A9970B1670ED366301999D9E@bellnet-mail1.sbell.com.cn>
Thread-Topic: [Megaco] About mdeia negociation
Thread-Index: AcHqGgfUyVyRo+0NT5yVSB9AhM7xKwAaNwPA
From: "SRD Wang JuLin" <WangJL2@sbell.com.cn>
To: "Ian Leighton" <Ian.Leighton@alcatel.com>,
        "Jackson.liu" <Jackson.liu@utstar.com>
Cc: <megaco@ietf.org>
X-OriginalArrivalTime: 23 Apr 2002 05:02:41.0936 (UTC) FILETIME=[19040100:01C1EA84]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA17628
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 would prefer that MGC exchange the caller and callee 's codec info using local and remote media descriptor.Just as Ian Leighton had commented.
While anther way is that MGC hold the GWs' media info provisioned statically.So when net payload is heavy,it can specify the codec both slave  side supported.

best  regards
> :-)Jerry Wang
tel:(8621)58541240 ext 9615
mailto:wangjl2@sbell.com.cn
Shanghai Bell Co.LTD



-----Original Message-----
From: Ian Leighton [mailto:Ian.Leighton@alcatel.com]
Sent: Monday, April 22, 2002 11:48 PM
To: Jackson.liu
Cc: megaco@ietf.org
Subject: Re: [Megaco] About mdeia negociation


Hi Jackson

As an alternative the message from MGC to MG2 in step 3 could include a Local descriptor with $ in the c line <connection-address > field and $ in the <port> and <fmt> fields of the m line. Also the Local descriptor from MG1 could be encoded in the Remote descriptor to MG2. For example

     MGC to MG2
          Local{
                       v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP $
                    }
           Remote{
                      v=0
                      o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:20
                      v=0
                      o=- blah blah blah
                      s=-
                      t=0 0
                     c=IN IP4  209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:30
                      v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:40
                     v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:30
                      v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:40
                       }

In other words the MGC requests MG2 to select its Local characteristics based one of the alternatives included in the Remote Descriptor.

Also note that I have added the o, t and s lines which should be included in SDP's sent from the MG.

Regards
Ian Leighton

"Jackson.liu" wrote:

> Dear Taylor:
>    I have some questions about media negociation. Would you so kind to solve the problerms?
>    For instance, before establishing RTP connection, media negociation should be done. MG1 suports PCMA ,and ptime = 20, 30, 40 can be choosed.At the same time MG1 supports G.723 ,and ptime = 20, 40 can be supported. MG2 suports PCMA ,and ptime = 30, 40 can be choosed.At the same time MG2 supports G.722 ,and ptime = 40 can be supported. How can MG2 get the media capability of MG1's RTP port.
> Do you think the following procedure is right or not? Let's highlight at the SDP session:
> Step1:
>     MGC to MG1:
>           Local{
>                        v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP $
>                     }
> Step2:
>     MG1 to MGC:
>               Local{
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:20
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:40
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 4
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 4
>                       a=ptime:40
>                      }
> Step 3:
>      MGC to MG2
>                    Local{
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:20
>                       v=0
>                       c=IN IP4  $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:40
>                      v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 4
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 4
>                       a=ptime:40
>                        }
> Step3:
>     MG2 to MGC:
>               Local{
>                       v=0
>                       c=IN IP4 209.110.59.34
>                       m=audio 1050 RTP/AVP 8
>                       a=ptime:30
>                        }
> Step 4
>      MGC to MG1:
>               remote{
>                       v=0
>                       c=IN IP4 209.110.59.34
>                       m=audio 1050 RTP/AVP 8
>                       a=ptime:30
>                            }
>
>     It seems so clumsy to negotiate media information in this way. Is there any other efficient method?
>
> Best Regards
>
> Jackson.liu
>
>
>
>
> _______________________________________________
> Megaco mailing 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 Apr 23 01:29: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 BAA28346
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 01:29:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA29129
	for megaco-archive@odin.ietf.org; Tue, 23 Apr 2002 01:29:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA17655;
	Tue, 23 Apr 2002 01:03:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA17627
	for <megaco@optimus.ietf.org>; Tue, 23 Apr 2002 01:03:23 -0400 (EDT)
Received: from mailgate.sbell.com.cn (mailgate.sbell.com.cn [202.96.203.173])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27881
	for <megaco@ietf.org>; Tue, 23 Apr 2002 01:03:19 -0400 (EDT)
Received: from bellnet-mail4.sbell.com.cn (bellnet-mail4.sbell.com.cn [202.96.203.174])
	by mailgate.sbell.com.cn (8.9.2/8.9.2) with ESMTP id MAA07698;
	Tue, 23 Apr 2002 12:50:38 +0800 (CST)
Received: from bellnet-mail1.sbell.com.cn ([202.96.203.171]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 23 Apr 2002 13:02:41 +0800
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="gb2312"
Subject: RE: [Megaco] About mdeia negociation
Date: Tue, 23 Apr 2002 13:02:41 +0800
Message-ID: <C65F869D22451348A9970B1670ED366301999D9E@bellnet-mail1.sbell.com.cn>
Thread-Topic: [Megaco] About mdeia negociation
Thread-Index: AcHqGgfUyVyRo+0NT5yVSB9AhM7xKwAaNwPA
From: "SRD Wang JuLin" <WangJL2@sbell.com.cn>
To: "Ian Leighton" <Ian.Leighton@alcatel.com>,
        "Jackson.liu" <Jackson.liu@utstar.com>
Cc: <megaco@ietf.org>
X-OriginalArrivalTime: 23 Apr 2002 05:02:41.0936 (UTC) FILETIME=[19040100:01C1EA84]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id BAA17628
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.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 would prefer that MGC exchange the caller and callee 's codec info using local and remote media descriptor.Just as Ian Leighton had commented.
While anther way is that MGC hold the GWs' media info provisioned statically.So when net payload is heavy,it can specify the codec both slave  side supported.

best  regards
> :-)Jerry Wang
tel:(8621)58541240 ext 9615
mailto:wangjl2@sbell.com.cn
Shanghai Bell Co.LTD



-----Original Message-----
From: Ian Leighton [mailto:Ian.Leighton@alcatel.com]
Sent: Monday, April 22, 2002 11:48 PM
To: Jackson.liu
Cc: megaco@ietf.org
Subject: Re: [Megaco] About mdeia negociation


Hi Jackson

As an alternative the message from MGC to MG2 in step 3 could include a Local descriptor with $ in the c line <connection-address > field and $ in the <port> and <fmt> fields of the m line. Also the Local descriptor from MG1 could be encoded in the Remote descriptor to MG2. For example

     MGC to MG2
          Local{
                       v=0
                      c=IN IP4 $
                      m=audio $ RTP/AVP $
                    }
           Remote{
                      v=0
                      o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:20
                      v=0
                      o=- blah blah blah
                      s=-
                      t=0 0
                     c=IN IP4  209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:30
                      v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 8
                      a=ptime:40
                     v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:30
                      v=0
                       o=- blah blah blah
                      s=-
                      t=0 0
                      c=IN IP4 209.110.59.33
                      m=audio 1000 RTP/AVP 4
                      a=ptime:40
                       }

In other words the MGC requests MG2 to select its Local characteristics based one of the alternatives included in the Remote Descriptor.

Also note that I have added the o, t and s lines which should be included in SDP's sent from the MG.

Regards
Ian Leighton

"Jackson.liu" wrote:

> Dear Taylor:
>    I have some questions about media negociation. Would you so kind to solve the problerms?
>    For instance, before establishing RTP connection, media negociation should be done. MG1 suports PCMA ,and ptime = 20, 30, 40 can be choosed.At the same time MG1 supports G.723 ,and ptime = 20, 40 can be supported. MG2 suports PCMA ,and ptime = 30, 40 can be choosed.At the same time MG2 supports G.722 ,and ptime = 40 can be supported. How can MG2 get the media capability of MG1's RTP port.
> Do you think the following procedure is right or not? Let's highlight at the SDP session:
> Step1:
>     MGC to MG1:
>           Local{
>                        v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP $
>                     }
> Step2:
>     MG1 to MGC:
>               Local{
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:20
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 8
>                       a=ptime:40
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 4
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 209.110.59.33
>                       m=audio 1000 RTP/AVP 4
>                       a=ptime:40
>                      }
> Step 3:
>      MGC to MG2
>                    Local{
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:20
>                       v=0
>                       c=IN IP4  $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 8
>                       a=ptime:40
>                      v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 4
>                       a=ptime:30
>                       v=0
>                       c=IN IP4 $
>                       m=audio $ RTP/AVP 4
>                       a=ptime:40
>                        }
> Step3:
>     MG2 to MGC:
>               Local{
>                       v=0
>                       c=IN IP4 209.110.59.34
>                       m=audio 1050 RTP/AVP 8
>                       a=ptime:30
>                        }
> Step 4
>      MGC to MG1:
>               remote{
>                       v=0
>                       c=IN IP4 209.110.59.34
>                       m=audio 1050 RTP/AVP 8
>                       a=ptime:30
>                            }
>
>     It seems so clumsy to negotiate media information in this way. Is there any other efficient method?
>
> Best Regards
>
> Jackson.liu
>
>
>
>
> _______________________________________________
> Megaco mailing 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 Apr 23 09:42: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 JAA17370
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 09:42:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29307;
	Tue, 23 Apr 2002 09:20:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12080
	for <megaco@optimus.ietf.org>; Tue, 23 Apr 2002 05:37:46 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09996
	for <megaco@ietf.org>; Tue, 23 Apr 2002 05:37:40 -0400 (EDT)
Received: from Rajeev ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GV0LAY01.7GE for
          <megaco@ietf.org>; Tue, 23 Apr 2002 17:35:22 +0800 
Message-ID: <001c01c1eaaa$3f713c10$4a080b0a@Rajeev>
From: "Rajeev K R" <rajeev@huawei.com>
To: "Megaco" <megaco@ietf.org>
Date: Tue, 23 Apr 2002 17:35:47 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0019_01C1EAED.4D7EF840"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Subject: [Megaco] How to display string at terminal
Sender: megaco-admin@ietf.org
Errors-To: 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_0019_01C1EAED.4D7EF840
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,
Is there any package which has defined some method to display a string =
at the H.248 Terminal ?
Basically I want to display the caller number and name on the called =
terminal.

I am looking for something similar to the adsi("quoted string") in MGCP.
Please help..
Regards,
Rajeev



------=_NextPart_000_0019_01C1EAED.4D7EF840
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.3315.2870" 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>Is there any package which has defined =
some method=20
to display a string at the H.248 Terminal ?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Basically I want to display the caller =
number and=20
name on the called terminal.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I am looking for something similar to =
the=20
adsi("quoted string") in MGCP.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Please help..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Rajeev</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0019_01C1EAED.4D7EF840--



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


From daemon@ns.ietf.org  Tue Apr 23 09:42: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 JAA17380
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 09:42:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA00953
	for megaco-archive@odin.ietf.org; Tue, 23 Apr 2002 09:42:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29307;
	Tue, 23 Apr 2002 09:20:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12080
	for <megaco@optimus.ietf.org>; Tue, 23 Apr 2002 05:37:46 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09996
	for <megaco@ietf.org>; Tue, 23 Apr 2002 05:37:40 -0400 (EDT)
Received: from Rajeev ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GV0LAY01.7GE for
          <megaco@ietf.org>; Tue, 23 Apr 2002 17:35:22 +0800 
Message-ID: <001c01c1eaaa$3f713c10$4a080b0a@Rajeev>
From: "Rajeev K R" <rajeev@huawei.com>
To: "Megaco" <megaco@ietf.org>
Date: Tue, 23 Apr 2002 17:35:47 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0019_01C1EAED.4D7EF840"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Subject: [Megaco] How to display string at terminal
Sender: megaco-admin@ietf.org
Errors-To: 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_0019_01C1EAED.4D7EF840
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,
Is there any package which has defined some method to display a string =
at the H.248 Terminal ?
Basically I want to display the caller number and name on the called =
terminal.

I am looking for something similar to the adsi("quoted string") in MGCP.
Please help..
Regards,
Rajeev



------=_NextPart_000_0019_01C1EAED.4D7EF840
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.3315.2870" 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>Is there any package which has defined =
some method=20
to display a string at the H.248 Terminal ?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Basically I want to display the caller =
number and=20
name on the called terminal.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I am looking for something similar to =
the=20
adsi("quoted string") in MGCP.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Please help..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Rajeev</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0019_01C1EAED.4D7EF840--



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



From megaco-admin@ietf.org  Tue Apr 23 10:09: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 KAA18434
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 10:09:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01152;
	Tue, 23 Apr 2002 09:45:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29398
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 09:22:50 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16672
	for <megaco@ietf.org>; Tue, 23 Apr 2002 09:22:45 -0400 (EDT)
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 g3NDMBY06902
	for <megaco@ietf.org>; Tue, 23 Apr 2002 15:22:11 +0200 (MEST)
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 PAA26030
	for <megaco@ietf.org>; Tue, 23 Apr 2002 15:21:57 +0200 (MET DST)
Message-ID: <3CC55E05.47421F04@alcatel.es>
Date: Tue, 23 Apr 2002 15:13:41 +0200
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 <megaco@ietf.org>
Subject: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt
References: <200204101213.IAA16176@ietf.org>
Content-Type: multipart/alternative;
 boundary="------------0261F6B4631AA9BA10FFD3A1"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

Hi all,

After this draft I am still missing something...

As RFC2805 states in 11.2.5 the protocol must support:
"   g.   Ability for the MGC to direct the NAS to connect to a specific
        tunnel, for example to an LNS, or to an AAA server."

But I cannot find a way using this package to  indicate (from the MGC to the MG)
the AAA server to use. I think that something like the following should be added
in the BASE NAS PACKAGE:

5.1.3. Authentication server address

PropertyId: aaaaddr

Description: AAA server address where the MG must establish the session.

Type: unicast  address, as in SDP

Defined in: Termination state for NAS Termination

Characteristics: read/write

5.1.4. Authentication server port

PropertyId: aaaport

Description: AAA server port where the MG must establish the session.

Type: integer

Defined in: Termination state for NAS Termination

Characteristics: read/write


Maybe I am missing something too...
Comments are welcome

Fernando Vallejo
Alcatel Spain


Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Media Gateway Control Working Group of the IETF.
>
>         Title           : Megaco/H.248 NAS Package
>         Author(s)       : J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam
>         Filename        : draft-ietf-megaco-naspkg-04.txt
>         Pages           : 18
>         Date            : 09-Apr-02
>
> This document is intended to satisfy the requirements in section
> 11.2.5 of the Megaco/H.248 requirements document.  It defines five
> packages:
> - the base NAS package contains properties and events supported by
> all NAS terminations;
> - the NAS Incoming package contains properties and events
> supported by NAS terminations involved in calls initiated by the
> circuit network;
> - the NAS Outgoing package contains properties supported by NAS
> terminations involved in calls outgoing to the circuit network;
> - the NAS Control package contains an event supported by a NAS
> Control termination, which allows the MG to indicate a request to
> initiate a data connection to a terminal served by the switched
> circuit network;
> - the NAS ROOT package contains properties supported by an MG which
> is also capable of supporting at least the NAS and NAS Incoming
> packages.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the message.
>
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-ietf-megaco-naspkg-04.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
>         mailserv@ietf.org.
> In the body type:
>         "FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt".
>
> NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>   ------------------------------------------------------------------------
> Content-Type: text/plain
> Content-ID:     <20020409132359.I-D@ietf.org>

--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



--------------0261F6B4631AA9BA10FFD3A1
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>After this draft I am still missing something...
<p>As RFC2805 states in 11.2.5 the protocol must support:
<br>"&nbsp;&nbsp; g.&nbsp;&nbsp; Ability for the MGC to direct the NAS
to connect to a specific
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tunnel, for example to an
LNS, or to an AAA server."
<p>But I cannot find a way using this package to&nbsp; indicate (from the
MGC to the MG)
<br>the AAA server to use. I think that something like the following should
be added
<br>in the BASE&nbsp;NAS&nbsp;PACKAGE:
<p>5.1.3. Authentication server address
<p>PropertyId: aaaaddr
<p>Description: AAA server address where the MG must establish the session.
<p>Type: unicast&nbsp; address, as in SDP
<p>Defined in: Termination state for NAS Termination
<p>Characteristics: read/write
<p>5.1.4. Authentication server port
<p>PropertyId: aaaport
<p>Description: AAA server port where the MG must establish the session.
<p>Type: integer
<p>Defined in: Termination state for NAS Termination
<p>Characteristics: read/write
<br>&nbsp;
<p>Maybe I am missing something too...
<br>Comments are welcome
<p>Fernando Vallejo
<br>Alcatel Spain
<br>&nbsp;
<p>Internet-Drafts@ietf.org wrote:
<blockquote TYPE=CITE>A New Internet-Draft is available from the on-line
Internet-Drafts directories.
<br>This draft is a work item of the Media Gateway Control Working Group
of the IETF.
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: Megaco/H.248 NAS Package
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: draft-ietf-megaco-naspkg-04.txt
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: 18
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: 09-Apr-02
<p>This document is intended to satisfy the requirements in section
<br>11.2.5 of the Megaco/H.248 requirements document.&nbsp; It defines
five
<br>packages:
<br>- the base NAS package contains properties and events supported by
<br>all NAS terminations;
<br>- the NAS Incoming package contains properties and events
<br>supported by NAS terminations involved in calls initiated by the
<br>circuit network;
<br>- the NAS Outgoing package contains properties supported by NAS
<br>terminations involved in calls outgoing to the circuit network;
<br>- the NAS Control package contains an event supported by a NAS
<br>Control termination, which allows the MG to indicate a request to
<br>initiate a data connection to a terminal served by the switched
<br>circuit network;
<br>- the NAS ROOT package contains properties supported by an MG which
<br>is also capable of supporting at least the NAS and NAS Incoming
<br>packages.
<p>A URL for this Internet-Draft is:
<br><a href="http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt">http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt</a>
<p>To remove yourself from the IETF Announcement list, send a message to
<br>ietf-announce-request with the word unsubscribe in the body of the
message.
<p>Internet-Drafts are also available by anonymous FTP. Login with the
username
<br>"anonymous" and a password of your e-mail address. After logging in,
<br>type "cd internet-drafts" and then
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "get draft-ietf-megaco-naspkg-04.txt".
<p>A list of Internet-Drafts directories can be found in
<br><a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>
<br>or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a>
<p>Internet-Drafts can also be obtained by e-mail.
<p>Send a message to:
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mailserv@ietf.org.
<br>In the body type:
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt".
<p>NOTE:&nbsp;&nbsp; The mail server at ietf.org can return the document
in
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MIME-encoded form by using
the "mpack" utility.&nbsp; To use this
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature, insert the command
"ENCODING mime" before the "FILE"
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command.&nbsp; To decode
the response(s), you will need "munpack" or
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a MIME-compliant mail reader.&nbsp;
Different MIME-compliant mail readers
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exhibit different behavior,
especially when dealing with
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "multipart" MIME messages
(i.e. documents which have been split
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; up into multiple messages),
so check your local documentation on
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to manipulate these
messages.
<br>&nbsp;
<p>Below is the data which will enable a MIME compliant mail reader
<br>implementation to automatically retrieve the ASCII version of the
<br>Internet-Draft.
<p>&nbsp; ------------------------------------------------------------------------
<br>Content-Type: text/plain
<br>Content-ID:&nbsp;&nbsp;&nbsp;&nbsp; &lt;20020409132359.I-D@ietf.org></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>

--------------0261F6B4631AA9BA10FFD3A1--



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


From daemon@ns.ietf.org  Tue Apr 23 10:09: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 KAA18453
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 10:09:33 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA02774
	for megaco-archive@odin.ietf.org; Tue, 23 Apr 2002 10:09:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01152;
	Tue, 23 Apr 2002 09:45:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29398
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 09:22:50 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16672
	for <megaco@ietf.org>; Tue, 23 Apr 2002 09:22:45 -0400 (EDT)
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 g3NDMBY06902
	for <megaco@ietf.org>; Tue, 23 Apr 2002 15:22:11 +0200 (MEST)
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 PAA26030
	for <megaco@ietf.org>; Tue, 23 Apr 2002 15:21:57 +0200 (MET DST)
Message-ID: <3CC55E05.47421F04@alcatel.es>
Date: Tue, 23 Apr 2002 15:13:41 +0200
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 <megaco@ietf.org>
Subject: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt
References: <200204101213.IAA16176@ietf.org>
Content-Type: multipart/alternative;
 boundary="------------0261F6B4631AA9BA10FFD3A1"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

Hi all,

After this draft I am still missing something...

As RFC2805 states in 11.2.5 the protocol must support:
"   g.   Ability for the MGC to direct the NAS to connect to a specific
        tunnel, for example to an LNS, or to an AAA server."

But I cannot find a way using this package to  indicate (from the MGC to the MG)
the AAA server to use. I think that something like the following should be added
in the BASE NAS PACKAGE:

5.1.3. Authentication server address

PropertyId: aaaaddr

Description: AAA server address where the MG must establish the session.

Type: unicast  address, as in SDP

Defined in: Termination state for NAS Termination

Characteristics: read/write

5.1.4. Authentication server port

PropertyId: aaaport

Description: AAA server port where the MG must establish the session.

Type: integer

Defined in: Termination state for NAS Termination

Characteristics: read/write


Maybe I am missing something too...
Comments are welcome

Fernando Vallejo
Alcatel Spain


Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Media Gateway Control Working Group of the IETF.
>
>         Title           : Megaco/H.248 NAS Package
>         Author(s)       : J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam
>         Filename        : draft-ietf-megaco-naspkg-04.txt
>         Pages           : 18
>         Date            : 09-Apr-02
>
> This document is intended to satisfy the requirements in section
> 11.2.5 of the Megaco/H.248 requirements document.  It defines five
> packages:
> - the base NAS package contains properties and events supported by
> all NAS terminations;
> - the NAS Incoming package contains properties and events
> supported by NAS terminations involved in calls initiated by the
> circuit network;
> - the NAS Outgoing package contains properties supported by NAS
> terminations involved in calls outgoing to the circuit network;
> - the NAS Control package contains an event supported by a NAS
> Control termination, which allows the MG to indicate a request to
> initiate a data connection to a terminal served by the switched
> circuit network;
> - the NAS ROOT package contains properties supported by an MG which
> is also capable of supporting at least the NAS and NAS Incoming
> packages.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt
>
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the message.
>
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-ietf-megaco-naspkg-04.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
>         mailserv@ietf.org.
> In the body type:
>         "FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt".
>
> NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>   ------------------------------------------------------------------------
> Content-Type: text/plain
> Content-ID:     <20020409132359.I-D@ietf.org>

--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



--------------0261F6B4631AA9BA10FFD3A1
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>After this draft I am still missing something...
<p>As RFC2805 states in 11.2.5 the protocol must support:
<br>"&nbsp;&nbsp; g.&nbsp;&nbsp; Ability for the MGC to direct the NAS
to connect to a specific
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tunnel, for example to an
LNS, or to an AAA server."
<p>But I cannot find a way using this package to&nbsp; indicate (from the
MGC to the MG)
<br>the AAA server to use. I think that something like the following should
be added
<br>in the BASE&nbsp;NAS&nbsp;PACKAGE:
<p>5.1.3. Authentication server address
<p>PropertyId: aaaaddr
<p>Description: AAA server address where the MG must establish the session.
<p>Type: unicast&nbsp; address, as in SDP
<p>Defined in: Termination state for NAS Termination
<p>Characteristics: read/write
<p>5.1.4. Authentication server port
<p>PropertyId: aaaport
<p>Description: AAA server port where the MG must establish the session.
<p>Type: integer
<p>Defined in: Termination state for NAS Termination
<p>Characteristics: read/write
<br>&nbsp;
<p>Maybe I am missing something too...
<br>Comments are welcome
<p>Fernando Vallejo
<br>Alcatel Spain
<br>&nbsp;
<p>Internet-Drafts@ietf.org wrote:
<blockquote TYPE=CITE>A New Internet-Draft is available from the on-line
Internet-Drafts directories.
<br>This draft is a work item of the Media Gateway Control Working Group
of the IETF.
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: Megaco/H.248 NAS Package
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: draft-ietf-megaco-naspkg-04.txt
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: 18
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
: 09-Apr-02
<p>This document is intended to satisfy the requirements in section
<br>11.2.5 of the Megaco/H.248 requirements document.&nbsp; It defines
five
<br>packages:
<br>- the base NAS package contains properties and events supported by
<br>all NAS terminations;
<br>- the NAS Incoming package contains properties and events
<br>supported by NAS terminations involved in calls initiated by the
<br>circuit network;
<br>- the NAS Outgoing package contains properties supported by NAS
<br>terminations involved in calls outgoing to the circuit network;
<br>- the NAS Control package contains an event supported by a NAS
<br>Control termination, which allows the MG to indicate a request to
<br>initiate a data connection to a terminal served by the switched
<br>circuit network;
<br>- the NAS ROOT package contains properties supported by an MG which
<br>is also capable of supporting at least the NAS and NAS Incoming
<br>packages.
<p>A URL for this Internet-Draft is:
<br><a href="http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt">http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt</a>
<p>To remove yourself from the IETF Announcement list, send a message to
<br>ietf-announce-request with the word unsubscribe in the body of the
message.
<p>Internet-Drafts are also available by anonymous FTP. Login with the
username
<br>"anonymous" and a password of your e-mail address. After logging in,
<br>type "cd internet-drafts" and then
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "get draft-ietf-megaco-naspkg-04.txt".
<p>A list of Internet-Drafts directories can be found in
<br><a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>
<br>or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a>
<p>Internet-Drafts can also be obtained by e-mail.
<p>Send a message to:
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mailserv@ietf.org.
<br>In the body type:
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt".
<p>NOTE:&nbsp;&nbsp; The mail server at ietf.org can return the document
in
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MIME-encoded form by using
the "mpack" utility.&nbsp; To use this
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature, insert the command
"ENCODING mime" before the "FILE"
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command.&nbsp; To decode
the response(s), you will need "munpack" or
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a MIME-compliant mail reader.&nbsp;
Different MIME-compliant mail readers
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exhibit different behavior,
especially when dealing with
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "multipart" MIME messages
(i.e. documents which have been split
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; up into multiple messages),
so check your local documentation on
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to manipulate these
messages.
<br>&nbsp;
<p>Below is the data which will enable a MIME compliant mail reader
<br>implementation to automatically retrieve the ASCII version of the
<br>Internet-Draft.
<p>&nbsp; ------------------------------------------------------------------------
<br>Content-Type: text/plain
<br>Content-ID:&nbsp;&nbsp;&nbsp;&nbsp; &lt;20020409132359.I-D@ietf.org></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>

--------------0261F6B4631AA9BA10FFD3A1--



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



From megaco-admin@ietf.org  Tue Apr 23 10:13: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 KAA18655
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 10:13:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01708;
	Tue, 23 Apr 2002 09:54:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01679
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 09:54:11 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17851
	for <megaco@ietf.org>; Tue, 23 Apr 2002 09:54:06 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3NDrcM17241
	for <megaco@ietf.org>; Tue, 23 Apr 2002 09:53:38 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCV2086W>; Tue, 23 Apr 2002 09:53:39 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A352@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Rajeev K R'" <rajeev@huawei.com>, Megaco <megaco@ietf.org>
Subject: RE: [Megaco] How to display string at terminal
Date: Tue, 23 Apr 2002 09:53:36 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

You have two possibilities.  The one you probably want is andisp/dwa in
draft-boyle-megaco-alerting-xx.txt (Enhanced Alerting Packages for
Megaco/H.248).  You can also look at the business set packages in Annex G.

-----Original Message-----
From: Rajeev K R [mailto:rajeev@huawei.com]
Sent: Tuesday, April 23, 2002 5:36 AM
To: Megaco
Subject: [Megaco] How to display string at terminal


Hi All,
Is there any package which has defined some method to display a string at
the H.248 Terminal ?
Basically I want to display the caller number and name on the called
terminal.

I am looking for something similar to the adsi("quoted string") in MGCP.
Please help..
Regards,
Rajeev

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


From daemon@ns.ietf.org  Tue Apr 23 10: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 KAA18667
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 10:13:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA02872
	for megaco-archive@odin.ietf.org; Tue, 23 Apr 2002 10:13:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01708;
	Tue, 23 Apr 2002 09:54:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01679
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 09:54:11 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17851
	for <megaco@ietf.org>; Tue, 23 Apr 2002 09:54:06 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3NDrcM17241
	for <megaco@ietf.org>; Tue, 23 Apr 2002 09:53:38 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCV2086W>; Tue, 23 Apr 2002 09:53:39 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A352@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Rajeev K R'" <rajeev@huawei.com>, Megaco <megaco@ietf.org>
Subject: RE: [Megaco] How to display string at terminal
Date: Tue, 23 Apr 2002 09:53:36 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

You have two possibilities.  The one you probably want is andisp/dwa in
draft-boyle-megaco-alerting-xx.txt (Enhanced Alerting Packages for
Megaco/H.248).  You can also look at the business set packages in Annex G.

-----Original Message-----
From: Rajeev K R [mailto:rajeev@huawei.com]
Sent: Tuesday, April 23, 2002 5:36 AM
To: Megaco
Subject: [Megaco] How to display string at terminal


Hi All,
Is there any package which has defined some method to display a string at
the H.248 Terminal ?
Basically I want to display the caller number and name on the called
terminal.

I am looking for something similar to the adsi("quoted string") in MGCP.
Please help..
Regards,
Rajeev

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



From megaco-admin@ietf.org  Tue Apr 23 10:17: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 KAA18757
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 10:17:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01810;
	Tue, 23 Apr 2002 09:57:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01786
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 09:57:16 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18011
	for <megaco@ietf.org>; Tue, 23 Apr 2002 09:57:11 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3NDudM17530
	for <megaco@ietf.org>; Tue, 23 Apr 2002 09:56:40 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCV2080H>; Tue, 23 Apr 2002 09:56:40 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A353@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Fernando Vallejo Lazaro'" <Fernando.Vallejo_Lazaro@alcatel.es>,
        Megaco
	 <megaco@ietf.org>
Subject: RE: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt
Date: Tue, 23 Apr 2002 09:56:37 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Thank you for your comments.  I'll look into adding these fields, perhaps
after examination of Diameter to see how requests are routed.

-----Original Message-----
From: Fernando Vallejo Lazaro [mailto:Fernando.Vallejo_Lazaro@alcatel.es]
Sent: Tuesday, April 23, 2002 9:14 AM
To: Megaco
Subject: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt


Hi all, 
After this draft I am still missing something... 
As RFC2805 states in 11.2.5 the protocol must support: 
"   g.   Ability for the MGC to direct the NAS to connect to a specific 
        tunnel, for example to an LNS, or to an AAA server." 
But I cannot find a way using this package to  indicate (from the MGC to the
MG) 
the AAA server to use. I think that something like the following should be
added 
in the BASE NAS PACKAGE: 
5.1.3. Authentication server address 
PropertyId: aaaaddr 
Description: AAA server address where the MG must establish the session. 
Type: unicast  address, as in SDP 
Defined in: Termination state for NAS Termination 
Characteristics: read/write 
5.1.4. Authentication server port 
PropertyId: aaaport 
Description: AAA server port where the MG must establish the session. 
Type: integer 
Defined in: Termination state for NAS Termination 
Characteristics: read/write 
  
Maybe I am missing something too... 
Comments are welcome 
Fernando Vallejo 
Alcatel Spain 
  
Internet-Drafts@ietf.org wrote: 
A New Internet-Draft is available from the on-line Internet-Drafts
directories. 
This draft is a work item of the Media Gateway Control Working Group of the
IETF. 
        Title           : Megaco/H.248 NAS Package 
        Author(s)       : J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam

        Filename        : draft-ietf-megaco-naspkg-04.txt 
        Pages           : 18 
        Date            : 09-Apr-02 
This document is intended to satisfy the requirements in section 
11.2.5 of the Megaco/H.248 requirements document.  It defines five 
packages: 
- the base NAS package contains properties and events supported by 
all NAS terminations; 
- the NAS Incoming package contains properties and events 
supported by NAS terminations involved in calls initiated by the 
circuit network; 
- the NAS Outgoing package contains properties supported by NAS 
terminations involved in calls outgoing to the circuit network; 
- the NAS Control package contains an event supported by a NAS 
Control termination, which allows the MG to indicate a request to 
initiate a data connection to a terminal served by the switched 
circuit network; 
- the NAS ROOT package contains properties supported by an MG which 
is also capable of supporting at least the NAS and NAS Incoming 
packages. 
A URL for this Internet-Draft is: 
http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt 
To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message. 
Internet-Drafts are also available by anonymous FTP. Login with the username

"anonymous" and a password of your e-mail address. After logging in, 
type "cd internet-drafts" and then 
        "get draft-ietf-megaco-naspkg-04.txt". 
A list of Internet-Drafts directories can be found in 
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt 
Internet-Drafts can also be obtained by e-mail. 
Send a message to: 
        mailserv@ietf.org. 
In the body type: 
        "FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt". 
NOTE:   The mail server at ietf.org can return the document in 
        MIME-encoded form by using the "mpack" utility.  To use this 
        feature, insert the command "ENCODING mime" before the "FILE" 
        command.  To decode the response(s), you will need "munpack" or 
        a MIME-compliant mail reader.  Different MIME-compliant mail readers

        exhibit different behavior, especially when dealing with 
        "multipart" MIME messages (i.e. documents which have been split 
        up into multiple messages), so check your local documentation on 
        how to manipulate these messages. 
  
Below is the data which will enable a MIME compliant mail reader 
implementation to automatically retrieve the ASCII version of the 
Internet-Draft. 
  ------------------------------------------------------------------------ 
Content-Type: text/plain 
Content-ID:     <20020409132359.I-D@ietf.org>
-- 
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL
  

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


From megaco-admin@ietf.org  Tue Apr 23 11:08: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 LAA21650
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 11:08:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04737;
	Tue, 23 Apr 2002 10:38:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04707
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 10:38:52 -0400 (EDT)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19908
	for <megaco@ietf.org>; Tue, 23 Apr 2002 10:38:48 -0400 (EDT)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <J35HJYH6>; Tue, 23 Apr 2002 10:38:21 -0400
Message-ID: <2415C206C515244DBFB12EC0C064A448404D23@wench>
From: Carl Rutter <crutter@telica.com>
To: Megaco <megaco@ietf.org>
Date: Tue, 23 Apr 2002 10:38:21 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Packages a Physical Termination Supports
Sender: megaco-admin@ietf.org
Errors-To: 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 you have DS0s that support difference Packages
how is that conveyed to the MGC.
I would have thought AuditCapabilities but it doesn't support
packages?

Thx,
Carl


-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Tuesday, April 23, 2002 9:57 AM
To: 'Fernando Vallejo Lazaro'; Megaco
Subject: RE: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt


Thank you for your comments.  I'll look into adding these fields, perhaps
after examination of Diameter to see how requests are routed.

-----Original Message-----
From: Fernando Vallejo Lazaro [mailto:Fernando.Vallejo_Lazaro@alcatel.es]
Sent: Tuesday, April 23, 2002 9:14 AM
To: Megaco
Subject: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt


Hi all, 
After this draft I am still missing something... 
As RFC2805 states in 11.2.5 the protocol must support: 
"   g.   Ability for the MGC to direct the NAS to connect to a specific 
        tunnel, for example to an LNS, or to an AAA server." 
But I cannot find a way using this package to  indicate (from the MGC to the
MG) 
the AAA server to use. I think that something like the following should be
added 
in the BASE NAS PACKAGE: 
5.1.3. Authentication server address 
PropertyId: aaaaddr 
Description: AAA server address where the MG must establish the session. 
Type: unicast  address, as in SDP 
Defined in: Termination state for NAS Termination 
Characteristics: read/write 
5.1.4. Authentication server port 
PropertyId: aaaport 
Description: AAA server port where the MG must establish the session. 
Type: integer 
Defined in: Termination state for NAS Termination 
Characteristics: read/write 
  
Maybe I am missing something too... 
Comments are welcome 
Fernando Vallejo 
Alcatel Spain 
  
Internet-Drafts@ietf.org wrote: 
A New Internet-Draft is available from the on-line Internet-Drafts
directories. 
This draft is a work item of the Media Gateway Control Working Group of the
IETF. 
        Title           : Megaco/H.248 NAS Package 
        Author(s)       : J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam

        Filename        : draft-ietf-megaco-naspkg-04.txt 
        Pages           : 18 
        Date            : 09-Apr-02 
This document is intended to satisfy the requirements in section 
11.2.5 of the Megaco/H.248 requirements document.  It defines five 
packages: 
- the base NAS package contains properties and events supported by 
all NAS terminations; 
- the NAS Incoming package contains properties and events 
supported by NAS terminations involved in calls initiated by the 
circuit network; 
- the NAS Outgoing package contains properties supported by NAS 
terminations involved in calls outgoing to the circuit network; 
- the NAS Control package contains an event supported by a NAS 
Control termination, which allows the MG to indicate a request to 
initiate a data connection to a terminal served by the switched 
circuit network; 
- the NAS ROOT package contains properties supported by an MG which 
is also capable of supporting at least the NAS and NAS Incoming 
packages. 
A URL for this Internet-Draft is: 
http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt 
To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message. 
Internet-Drafts are also available by anonymous FTP. Login with the username

"anonymous" and a password of your e-mail address. After logging in, 
type "cd internet-drafts" and then 
        "get draft-ietf-megaco-naspkg-04.txt". 
A list of Internet-Drafts directories can be found in 
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt 
Internet-Drafts can also be obtained by e-mail. 
Send a message to: 
        mailserv@ietf.org. 
In the body type: 
        "FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt". 
NOTE:   The mail server at ietf.org can return the document in 
        MIME-encoded form by using the "mpack" utility.  To use this 
        feature, insert the command "ENCODING mime" before the "FILE" 
        command.  To decode the response(s), you will need "munpack" or 
        a MIME-compliant mail reader.  Different MIME-compliant mail readers

        exhibit different behavior, especially when dealing with 
        "multipart" MIME messages (i.e. documents which have been split 
        up into multiple messages), so check your local documentation on 
        how to manipulate these messages. 
  
Below is the data which will enable a MIME compliant mail reader 
implementation to automatically retrieve the ASCII version of the 
Internet-Draft. 
  ------------------------------------------------------------------------ 
Content-Type: text/plain 
Content-ID:     <20020409132359.I-D@ietf.org>
-- 
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL
  

_______________________________________________
Megaco mailing list
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 Apr 23 11:08: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 LAA21662
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 11:08:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA06863
	for megaco-archive@odin.ietf.org; Tue, 23 Apr 2002 11:08:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04737;
	Tue, 23 Apr 2002 10:38:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04707
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 10:38:52 -0400 (EDT)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19908
	for <megaco@ietf.org>; Tue, 23 Apr 2002 10:38:48 -0400 (EDT)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <J35HJYH6>; Tue, 23 Apr 2002 10:38:21 -0400
Message-ID: <2415C206C515244DBFB12EC0C064A448404D23@wench>
From: Carl Rutter <crutter@telica.com>
To: Megaco <megaco@ietf.org>
Date: Tue, 23 Apr 2002 10:38:21 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Packages a Physical Termination Supports
Sender: megaco-admin@ietf.org
Errors-To: 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 you have DS0s that support difference Packages
how is that conveyed to the MGC.
I would have thought AuditCapabilities but it doesn't support
packages?

Thx,
Carl


-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Tuesday, April 23, 2002 9:57 AM
To: 'Fernando Vallejo Lazaro'; Megaco
Subject: RE: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt


Thank you for your comments.  I'll look into adding these fields, perhaps
after examination of Diameter to see how requests are routed.

-----Original Message-----
From: Fernando Vallejo Lazaro [mailto:Fernando.Vallejo_Lazaro@alcatel.es]
Sent: Tuesday, April 23, 2002 9:14 AM
To: Megaco
Subject: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt


Hi all, 
After this draft I am still missing something... 
As RFC2805 states in 11.2.5 the protocol must support: 
"   g.   Ability for the MGC to direct the NAS to connect to a specific 
        tunnel, for example to an LNS, or to an AAA server." 
But I cannot find a way using this package to  indicate (from the MGC to the
MG) 
the AAA server to use. I think that something like the following should be
added 
in the BASE NAS PACKAGE: 
5.1.3. Authentication server address 
PropertyId: aaaaddr 
Description: AAA server address where the MG must establish the session. 
Type: unicast  address, as in SDP 
Defined in: Termination state for NAS Termination 
Characteristics: read/write 
5.1.4. Authentication server port 
PropertyId: aaaport 
Description: AAA server port where the MG must establish the session. 
Type: integer 
Defined in: Termination state for NAS Termination 
Characteristics: read/write 
  
Maybe I am missing something too... 
Comments are welcome 
Fernando Vallejo 
Alcatel Spain 
  
Internet-Drafts@ietf.org wrote: 
A New Internet-Draft is available from the on-line Internet-Drafts
directories. 
This draft is a work item of the Media Gateway Control Working Group of the
IETF. 
        Title           : Megaco/H.248 NAS Package 
        Author(s)       : J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam

        Filename        : draft-ietf-megaco-naspkg-04.txt 
        Pages           : 18 
        Date            : 09-Apr-02 
This document is intended to satisfy the requirements in section 
11.2.5 of the Megaco/H.248 requirements document.  It defines five 
packages: 
- the base NAS package contains properties and events supported by 
all NAS terminations; 
- the NAS Incoming package contains properties and events 
supported by NAS terminations involved in calls initiated by the 
circuit network; 
- the NAS Outgoing package contains properties supported by NAS 
terminations involved in calls outgoing to the circuit network; 
- the NAS Control package contains an event supported by a NAS 
Control termination, which allows the MG to indicate a request to 
initiate a data connection to a terminal served by the switched 
circuit network; 
- the NAS ROOT package contains properties supported by an MG which 
is also capable of supporting at least the NAS and NAS Incoming 
packages. 
A URL for this Internet-Draft is: 
http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt 
To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message. 
Internet-Drafts are also available by anonymous FTP. Login with the username

"anonymous" and a password of your e-mail address. After logging in, 
type "cd internet-drafts" and then 
        "get draft-ietf-megaco-naspkg-04.txt". 
A list of Internet-Drafts directories can be found in 
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt 
Internet-Drafts can also be obtained by e-mail. 
Send a message to: 
        mailserv@ietf.org. 
In the body type: 
        "FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt". 
NOTE:   The mail server at ietf.org can return the document in 
        MIME-encoded form by using the "mpack" utility.  To use this 
        feature, insert the command "ENCODING mime" before the "FILE" 
        command.  To decode the response(s), you will need "munpack" or 
        a MIME-compliant mail reader.  Different MIME-compliant mail readers

        exhibit different behavior, especially when dealing with 
        "multipart" MIME messages (i.e. documents which have been split 
        up into multiple messages), so check your local documentation on 
        how to manipulate these messages. 
  
Below is the data which will enable a MIME compliant mail reader 
implementation to automatically retrieve the ASCII version of the 
Internet-Draft. 
  ------------------------------------------------------------------------ 
Content-Type: text/plain 
Content-ID:     <20020409132359.I-D@ietf.org>
-- 
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL
  

_______________________________________________
Megaco mailing list
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 Apr 23 11:11: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 KAA18769
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 10:17:14 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA03056
	for megaco-archive@odin.ietf.org; Tue, 23 Apr 2002 10:17:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01810;
	Tue, 23 Apr 2002 09:57:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01786
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 09:57:16 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18011
	for <megaco@ietf.org>; Tue, 23 Apr 2002 09:57:11 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3NDudM17530
	for <megaco@ietf.org>; Tue, 23 Apr 2002 09:56:40 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCV2080H>; Tue, 23 Apr 2002 09:56:40 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A353@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Fernando Vallejo Lazaro'" <Fernando.Vallejo_Lazaro@alcatel.es>,
        Megaco
	 <megaco@ietf.org>
Subject: RE: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt
Date: Tue, 23 Apr 2002 09:56:37 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Thank you for your comments.  I'll look into adding these fields, perhaps
after examination of Diameter to see how requests are routed.

-----Original Message-----
From: Fernando Vallejo Lazaro [mailto:Fernando.Vallejo_Lazaro@alcatel.es]
Sent: Tuesday, April 23, 2002 9:14 AM
To: Megaco
Subject: [Megaco] comments about draft-ietf-megaco-naspkg-04.txt


Hi all, 
After this draft I am still missing something... 
As RFC2805 states in 11.2.5 the protocol must support: 
"   g.   Ability for the MGC to direct the NAS to connect to a specific 
        tunnel, for example to an LNS, or to an AAA server." 
But I cannot find a way using this package to  indicate (from the MGC to the
MG) 
the AAA server to use. I think that something like the following should be
added 
in the BASE NAS PACKAGE: 
5.1.3. Authentication server address 
PropertyId: aaaaddr 
Description: AAA server address where the MG must establish the session. 
Type: unicast  address, as in SDP 
Defined in: Termination state for NAS Termination 
Characteristics: read/write 
5.1.4. Authentication server port 
PropertyId: aaaport 
Description: AAA server port where the MG must establish the session. 
Type: integer 
Defined in: Termination state for NAS Termination 
Characteristics: read/write 
  
Maybe I am missing something too... 
Comments are welcome 
Fernando Vallejo 
Alcatel Spain 
  
Internet-Drafts@ietf.org wrote: 
A New Internet-Draft is available from the on-line Internet-Drafts
directories. 
This draft is a work item of the Media Gateway Control Working Group of the
IETF. 
        Title           : Megaco/H.248 NAS Package 
        Author(s)       : J. Mitchell, t. Taylor, A. Whitton, R. Subramaniam

        Filename        : draft-ietf-megaco-naspkg-04.txt 
        Pages           : 18 
        Date            : 09-Apr-02 
This document is intended to satisfy the requirements in section 
11.2.5 of the Megaco/H.248 requirements document.  It defines five 
packages: 
- the base NAS package contains properties and events supported by 
all NAS terminations; 
- the NAS Incoming package contains properties and events 
supported by NAS terminations involved in calls initiated by the 
circuit network; 
- the NAS Outgoing package contains properties supported by NAS 
terminations involved in calls outgoing to the circuit network; 
- the NAS Control package contains an event supported by a NAS 
Control termination, which allows the MG to indicate a request to 
initiate a data connection to a terminal served by the switched 
circuit network; 
- the NAS ROOT package contains properties supported by an MG which 
is also capable of supporting at least the NAS and NAS Incoming 
packages. 
A URL for this Internet-Draft is: 
http://www.ietf.org/internet-drafts/draft-ietf-megaco-naspkg-04.txt 
To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message. 
Internet-Drafts are also available by anonymous FTP. Login with the username

"anonymous" and a password of your e-mail address. After logging in, 
type "cd internet-drafts" and then 
        "get draft-ietf-megaco-naspkg-04.txt". 
A list of Internet-Drafts directories can be found in 
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt 
Internet-Drafts can also be obtained by e-mail. 
Send a message to: 
        mailserv@ietf.org. 
In the body type: 
        "FILE /internet-drafts/draft-ietf-megaco-naspkg-04.txt". 
NOTE:   The mail server at ietf.org can return the document in 
        MIME-encoded form by using the "mpack" utility.  To use this 
        feature, insert the command "ENCODING mime" before the "FILE" 
        command.  To decode the response(s), you will need "munpack" or 
        a MIME-compliant mail reader.  Different MIME-compliant mail readers

        exhibit different behavior, especially when dealing with 
        "multipart" MIME messages (i.e. documents which have been split 
        up into multiple messages), so check your local documentation on 
        how to manipulate these messages. 
  
Below is the data which will enable a MIME compliant mail reader 
implementation to automatically retrieve the ASCII version of the 
Internet-Draft. 
  ------------------------------------------------------------------------ 
Content-Type: text/plain 
Content-ID:     <20020409132359.I-D@ietf.org>
-- 
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL
  

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



From megaco-admin@ietf.org  Tue Apr 23 19: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 TAA09313
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 19:08:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06056;
	Tue, 23 Apr 2002 18:48:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06029
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 18:48:20 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08818
	for <megaco@ietf.org>; Tue, 23 Apr 2002 18:48:14 -0400 (EDT)
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 g3NMlkv16215
	for <megaco@ietf.org>; Tue, 23 Apr 2002 18:47:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJAM40>; Tue, 23 Apr 2002 18:47:48 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A35B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 23 Apr 2002 18:47:48 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Access To The Megaco FTP Site
Sender: megaco-admin@ietf.org
Errors-To: 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 had a few inquiries about access to the Megaco FTP site.  It turns out
our server was hit by a virus a few weeks ago, and the administrator was
waiting for people to notice that their stuff wasn't available any more.
(The server supported a number of efforts, many apparently dormant, besides
Megaco.)  The Megaco files were restored just before the administrator went
on vacation.  I wasn't able to verify access right away because of some
other problem.  I'll see if I can sort things out now, but it may be
necessary to wait until John gets back from vacation.

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  Tue Apr 23 19:08: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 TAA09324
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 19:08:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA07139
	for megaco-archive@odin.ietf.org; Tue, 23 Apr 2002 19:08:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06056;
	Tue, 23 Apr 2002 18:48:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06029
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 18:48:20 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08818
	for <megaco@ietf.org>; Tue, 23 Apr 2002 18:48:14 -0400 (EDT)
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 g3NMlkv16215
	for <megaco@ietf.org>; Tue, 23 Apr 2002 18:47:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJAM40>; Tue, 23 Apr 2002 18:47:48 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A35B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Tue, 23 Apr 2002 18:47:48 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Access To The Megaco FTP Site
Sender: megaco-admin@ietf.org
Errors-To: 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 had a few inquiries about access to the Megaco FTP site.  It turns out
our server was hit by a virus a few weeks ago, and the administrator was
waiting for people to notice that their stuff wasn't available any more.
(The server supported a number of efforts, many apparently dormant, besides
Megaco.)  The Megaco files were restored just before the administrator went
on vacation.  I wasn't able to verify access right away because of some
other problem.  I'll see if I can sort things out now, but it may be
necessary to wait until John gets back from vacation.

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 Apr 23 21:07: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 VAA10805
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 21:07:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11240;
	Tue, 23 Apr 2002 20:41:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11205
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 20:41:02 -0400 (EDT)
Received: from hotmail.com (f39.law15.hotmail.com [64.4.23.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10576
	for <megaco@ietf.org>; Tue, 23 Apr 2002 20:40:58 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 23 Apr 2002 17:40:30 -0700
Received: from 210.21.224.51 by lw15fd.law15.hotmail.msn.com with HTTP;
	Wed, 24 Apr 2002 00:40:30 GMT
X-Originating-IP: [210.21.224.51]
From: "=?gb2312?B?5LuYIOWujw==?=" <juniperfu@hotmail.com>
To: taylor@nortelnetworks.com
Cc: megaco@ietf.org
Date: Wed, 24 Apr 2002 08:40:30 +0800
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <F39wJHpeVvVNgBdXY7v00001aa4@hotmail.com>
X-OriginalArrivalTime: 24 Apr 2002 00:40:30.0969 (UTC) FILETIME=[A30AAE90:01C1EB28]
Subject: [Megaco] about eventbuffer 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

All,
   In section 7.1.10 of megaco, there is a description about eventbuffer:
    'the Eventbuffer descriptor contains a list of events, with their 
parameters if any, that the MG is requested to detect and buffer when 
eventbufferControl equals LocaStep'
   from the descrition, I think it means the eventbuffer descriptor include 
many request event from MGC and the MG should detect the event by the 
eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it 
right?

Mark
 


_________________________________________________________________
Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp


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


From daemon@optimus.ietf.org  Tue Apr 23 21:07: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 VAA10817
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 21:07:06 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA12418
	for megaco-archive@odin.ietf.org; Tue, 23 Apr 2002 21:07:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11240;
	Tue, 23 Apr 2002 20:41:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11205
	for <megaco@ns.ietf.org>; Tue, 23 Apr 2002 20:41:02 -0400 (EDT)
Received: from hotmail.com (f39.law15.hotmail.com [64.4.23.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10576
	for <megaco@ietf.org>; Tue, 23 Apr 2002 20:40:58 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 23 Apr 2002 17:40:30 -0700
Received: from 210.21.224.51 by lw15fd.law15.hotmail.msn.com with HTTP;
	Wed, 24 Apr 2002 00:40:30 GMT
X-Originating-IP: [210.21.224.51]
From: "=?gb2312?B?5LuYIOWujw==?=" <juniperfu@hotmail.com>
To: taylor@nortelnetworks.com
Cc: megaco@ietf.org
Date: Wed, 24 Apr 2002 08:40:30 +0800
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <F39wJHpeVvVNgBdXY7v00001aa4@hotmail.com>
X-OriginalArrivalTime: 24 Apr 2002 00:40:30.0969 (UTC) FILETIME=[A30AAE90:01C1EB28]
Subject: [Megaco] about eventbuffer 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

All,
   In section 7.1.10 of megaco, there is a description about eventbuffer:
    'the Eventbuffer descriptor contains a list of events, with their 
parameters if any, that the MG is requested to detect and buffer when 
eventbufferControl equals LocaStep'
   from the descrition, I think it means the eventbuffer descriptor include 
many request event from MGC and the MG should detect the event by the 
eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it 
right?

Mark
 


_________________________________________________________________
Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp


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



From megaco-admin@ietf.org  Tue Apr 23 21: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 VAA12290
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 21:49:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA13458;
	Tue, 23 Apr 2002 21:33:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA13428
	for <megaco@optimus.ietf.org>; Tue, 23 Apr 2002 21:33:37 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11112
	for <megaco@ietf.org>; Tue, 23 Apr 2002 21:33:33 -0400 (EDT)
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 g3O1X5v20011
	for <megaco@ietf.org>; Tue, 23 Apr 2002 21:33:05 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJANT6>; Tue, 23 Apr 2002 21:33:06 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A35E@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'???'" <juniperfu@hotmail.com>
Cc: megaco@ietf.org
Date: Tue, 23 Apr 2002 21:33:07 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: about eventbuffer 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

Yes.  When running in LockStep mode the MGC specifies both the Events
Descriptor and the EventBuffer descriptor, and either can contain multiple
events.  The Events Descriptor determines what events are reported, and the
EventBuffer Descriptor determines what events are saved for processing
against the next Events descriptor after an event notification has been
sent.

-----Original Message-----
From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
Sent: Tuesday, April 23, 2002 8:41 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: about eventbuffer descriptor


All,
   In section 7.1.10 of megaco, there is a description about eventbuffer:
    'the Eventbuffer descriptor contains a list of events, with their 
parameters if any, that the MG is requested to detect and buffer when 
eventbufferControl equals LocaStep'
   from the descrition, I think it means the eventbuffer descriptor include 
many request event from MGC and the MG should detect the event by the 
eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it 
right?

Mark
 


_________________________________________________________________
Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp


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


From daemon@optimus.ietf.org  Tue Apr 23 21: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 VAA12302
	for <megaco-archive@odin.ietf.org>; Tue, 23 Apr 2002 21:49:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA14002
	for megaco-archive@odin.ietf.org; Tue, 23 Apr 2002 21:49:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA13458;
	Tue, 23 Apr 2002 21:33:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA13428
	for <megaco@optimus.ietf.org>; Tue, 23 Apr 2002 21:33:37 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11112
	for <megaco@ietf.org>; Tue, 23 Apr 2002 21:33:33 -0400 (EDT)
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 g3O1X5v20011
	for <megaco@ietf.org>; Tue, 23 Apr 2002 21:33:05 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJANT6>; Tue, 23 Apr 2002 21:33:06 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A35E@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'???'" <juniperfu@hotmail.com>
Cc: megaco@ietf.org
Date: Tue, 23 Apr 2002 21:33:07 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: about eventbuffer 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

Yes.  When running in LockStep mode the MGC specifies both the Events
Descriptor and the EventBuffer descriptor, and either can contain multiple
events.  The Events Descriptor determines what events are reported, and the
EventBuffer Descriptor determines what events are saved for processing
against the next Events descriptor after an event notification has been
sent.

-----Original Message-----
From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
Sent: Tuesday, April 23, 2002 8:41 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: about eventbuffer descriptor


All,
   In section 7.1.10 of megaco, there is a description about eventbuffer:
    'the Eventbuffer descriptor contains a list of events, with their 
parameters if any, that the MG is requested to detect and buffer when 
eventbufferControl equals LocaStep'
   from the descrition, I think it means the eventbuffer descriptor include 
many request event from MGC and the MG should detect the event by the 
eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it 
right?

Mark
 


_________________________________________________________________
Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp


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



From megaco-admin@ietf.org  Wed Apr 24 00:27: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 AAA16073
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 00:27:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA20133;
	Wed, 24 Apr 2002 00:06:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA20104
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 00:06:45 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15594
	for <megaco@ietf.org>; Wed, 24 Apr 2002 00:06:43 -0400 (EDT)
From: rezhirpavai@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 g3O47Hc09905;
	Wed, 24 Apr 2002 09:37:18 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA5.00165220 ; Wed, 24 Apr 2002 09:33:48 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "'???'" <juniperfu@hotmail.com>, megaco@ietf.org
Message-ID: <65256BA5.00164B1A.00@sandesh.hss.hns.com>
Date: Wed, 24 Apr 2002 09:36:13 +0530
Subject: Re: [Megaco] RE: about eventbuffer descriptor
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



Hello Tom,
     According to a statement in the protocol, Events mentioned in event
descriptor remain active in MG till next event descriptor is received. (An
exception to this is the digit map event). Thus if an MGC wants that none of the
events being detetced at MG be lost, it can send all required events on that
termination in a single event descriptor and then get the events as and when
they are detected at MG without sending a second event descriptor. It can send
the next event descriptor only when subtract is sent. If this is a valid
sequence, then where and why would an MGC use event buffer descriptor and thus a
lockstep mode.

Regards,
- R. Ezhirpavai





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 04/24/2002 07:03:07 AM

To:   "'???'" <juniperfu@hotmail.com>
cc:   megaco@ietf.org (bcc: R Ezhirpavai/HSS)

Subject:  [Megaco] RE: about eventbuffer descriptor




Yes.  When running in LockStep mode the MGC specifies both the Events
Descriptor and the EventBuffer descriptor, and either can contain multiple
events.  The Events Descriptor determines what events are reported, and the
EventBuffer Descriptor determines what events are saved for processing
against the next Events descriptor after an event notification has been
sent.

-----Original Message-----
From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
Sent: Tuesday, April 23, 2002 8:41 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: about eventbuffer descriptor


All,
   In section 7.1.10 of megaco, there is a description about eventbuffer:
    'the Eventbuffer descriptor contains a list of events, with their
parameters if any, that the MG is requested to detect and buffer when
eventbufferControl equals LocaStep'
   from the descrition, I think it means the eventbuffer descriptor include
many request event from MGC and the MG should detect the event by the
eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it
right?

Mark



_________________________________________________________________
???????? MSN Explorer??http://explorer.msn.com/lccn/intl.asp


_______________________________________________
Megaco mailing list
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 Apr 24 00:27: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 AAA16084
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 00:27:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA20789
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 00:27:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA20133;
	Wed, 24 Apr 2002 00:06:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA20104
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 00:06:45 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15594
	for <megaco@ietf.org>; Wed, 24 Apr 2002 00:06:43 -0400 (EDT)
From: rezhirpavai@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 g3O47Hc09905;
	Wed, 24 Apr 2002 09:37:18 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA5.00165220 ; Wed, 24 Apr 2002 09:33:48 +0530
X-Lotus-FromDomain: HSS
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>
cc: "'???'" <juniperfu@hotmail.com>, megaco@ietf.org
Message-ID: <65256BA5.00164B1A.00@sandesh.hss.hns.com>
Date: Wed, 24 Apr 2002 09:36:13 +0530
Subject: Re: [Megaco] RE: about eventbuffer descriptor
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



Hello Tom,
     According to a statement in the protocol, Events mentioned in event
descriptor remain active in MG till next event descriptor is received. (An
exception to this is the digit map event). Thus if an MGC wants that none of the
events being detetced at MG be lost, it can send all required events on that
termination in a single event descriptor and then get the events as and when
they are detected at MG without sending a second event descriptor. It can send
the next event descriptor only when subtract is sent. If this is a valid
sequence, then where and why would an MGC use event buffer descriptor and thus a
lockstep mode.

Regards,
- R. Ezhirpavai





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 04/24/2002 07:03:07 AM

To:   "'???'" <juniperfu@hotmail.com>
cc:   megaco@ietf.org (bcc: R Ezhirpavai/HSS)

Subject:  [Megaco] RE: about eventbuffer descriptor




Yes.  When running in LockStep mode the MGC specifies both the Events
Descriptor and the EventBuffer descriptor, and either can contain multiple
events.  The Events Descriptor determines what events are reported, and the
EventBuffer Descriptor determines what events are saved for processing
against the next Events descriptor after an event notification has been
sent.

-----Original Message-----
From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
Sent: Tuesday, April 23, 2002 8:41 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: about eventbuffer descriptor


All,
   In section 7.1.10 of megaco, there is a description about eventbuffer:
    'the Eventbuffer descriptor contains a list of events, with their
parameters if any, that the MG is requested to detect and buffer when
eventbufferControl equals LocaStep'
   from the descrition, I think it means the eventbuffer descriptor include
many request event from MGC and the MG should detect the event by the
eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it
right?

Mark



_________________________________________________________________
???????? MSN Explorer??http://explorer.msn.com/lccn/intl.asp


_______________________________________________
Megaco mailing list
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 Apr 24 02:03: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 CAA21829
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 02:03:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA04800;
	Wed, 24 Apr 2002 01:45:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA04771
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 01:45:18 -0400 (EDT)
Received: from telesoft.indts.com (IDENT:root@[164.164.71.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16929
	for <megaco@ietf.org>; Wed, 24 Apr 2002 01:45:13 -0400 (EDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id LAA25678
	for <megaco@ietf.org>; Wed, 24 Apr 2002 11:48:50 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <GWSJC2DA>; Wed, 24 Apr 2002 11:19:38 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337263B3BE@INDTS_FS>
From: Anil Jangam <anilj@indts.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 24 Apr 2002 11:19:37 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Audit &  contextTerminationAudit??
Sender: megaco-admin@ietf.org
Errors-To: 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,

1. How one should use/issue the 'Audit' command from the MGC persepective?
Is it necesary to 'Audit' the endpoint/gateway every time before a call
initiated? 

2. In the 'AuditValue' return parameter in the 'auditReply' what is the
'contextTerminationAudit' return option? Under what circumstances,  the
Audit command would return it and what are implications/effects of this
return on the actual call processing/control?

I am not able to understand the meaning of the 'contextTerminationAudit' and
couldn't proceed to change the call handling state machine.

Regds,
/anil.

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


From daemon@optimus.ietf.org  Wed Apr 24 02:03: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 CAA21847
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 02:03:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA05696
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 02:03:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA04800;
	Wed, 24 Apr 2002 01:45:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA04771
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 01:45:18 -0400 (EDT)
Received: from telesoft.indts.com (IDENT:root@[164.164.71.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16929
	for <megaco@ietf.org>; Wed, 24 Apr 2002 01:45:13 -0400 (EDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id LAA25678
	for <megaco@ietf.org>; Wed, 24 Apr 2002 11:48:50 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <GWSJC2DA>; Wed, 24 Apr 2002 11:19:38 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337263B3BE@INDTS_FS>
From: Anil Jangam <anilj@indts.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 24 Apr 2002 11:19:37 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Audit &  contextTerminationAudit??
Sender: megaco-admin@ietf.org
Errors-To: 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,

1. How one should use/issue the 'Audit' command from the MGC persepective?
Is it necesary to 'Audit' the endpoint/gateway every time before a call
initiated? 

2. In the 'AuditValue' return parameter in the 'auditReply' what is the
'contextTerminationAudit' return option? Under what circumstances,  the
Audit command would return it and what are implications/effects of this
return on the actual call processing/control?

I am not able to understand the meaning of the 'contextTerminationAudit' and
couldn't proceed to change the call handling state machine.

Regds,
/anil.

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



From megaco-admin@ietf.org  Wed Apr 24 02:56: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 CAA26125
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 02:56:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06677;
	Wed, 24 Apr 2002 02:36:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06649
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 02:35:58 -0400 (EDT)
Received: from telesoft.indts.com (IDENT:root@[164.164.71.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25776
	for <megaco@ietf.org>; Wed, 24 Apr 2002 02:35:52 -0400 (EDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id MAA17196
	for <megaco@ietf.org>; Wed, 24 Apr 2002 12:39:22 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <GWSJC2H4>; Wed, 24 Apr 2002 12:10:10 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337263B3BF@INDTS_FS>
From: Anil Jangam <anilj@indts.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 24 Apr 2002 12:10:09 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Subject: [Megaco] Deleting termination from the Context
Sender: megaco-admin@ietf.org
Errors-To: 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,

Is it possible to issue a 'Subtract' command to delete a Termination with
'Context' as a '*'.
I am looking at subtract command which essentially deletes a Termination
from the context, when I don't have the information about the context, in
which the Termination is present. Thus with 'Context' as '*', it would try
to find out the TerminastionId in all the contexts present and delete it. 

regds,
/anil.

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


From daemon@optimus.ietf.org  Wed Apr 24 02:56: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 CAA26137
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 02:56:11 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA07396
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 02:56:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06677;
	Wed, 24 Apr 2002 02:36:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06649
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 02:35:58 -0400 (EDT)
Received: from telesoft.indts.com (IDENT:root@[164.164.71.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25776
	for <megaco@ietf.org>; Wed, 24 Apr 2002 02:35:52 -0400 (EDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id MAA17196
	for <megaco@ietf.org>; Wed, 24 Apr 2002 12:39:22 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <GWSJC2H4>; Wed, 24 Apr 2002 12:10:10 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337263B3BF@INDTS_FS>
From: Anil Jangam <anilj@indts.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 24 Apr 2002 12:10:09 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Subject: [Megaco] Deleting termination from the Context
Sender: megaco-admin@ietf.org
Errors-To: 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,

Is it possible to issue a 'Subtract' command to delete a Termination with
'Context' as a '*'.
I am looking at subtract command which essentially deletes a Termination
from the context, when I don't have the information about the context, in
which the Termination is present. Thus with 'Context' as '*', it would try
to find out the TerminastionId in all the contexts present and delete it. 

regds,
/anil.

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



From megaco-admin@ietf.org  Wed Apr 24 04:44: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 EAA27722
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 04:44:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12518;
	Wed, 24 Apr 2002 04:22:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12490
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 04:22:12 -0400 (EDT)
Received: from hotmail.com (f194.law15.hotmail.com [64.4.23.194])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27325
	for <megaco@ietf.org>; Wed, 24 Apr 2002 04:22:09 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 24 Apr 2002 01:21:20 -0700
Received: from 210.21.224.51 by lw15fd.law15.hotmail.msn.com with HTTP;
	Wed, 24 Apr 2002 08:21:19 GMT
X-Originating-IP: [210.21.224.51]
From: "=?gb2312?B?5LuYIOWujw==?=" <juniperfu@hotmail.com>
To: taylor@nortelnetworks.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] RE: about eventbuffer descriptor
Date: Wed, 24 Apr 2002 16:21:19 +0800
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <F194JX7rVGSLsNhIIqg00001e4e@hotmail.com>
X-OriginalArrivalTime: 24 Apr 2002 08:21:20.0084 (UTC) FILETIME=[0332D140:01C1EB69]
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

    When running in LockStep mode, If MG detected event which exist in 
EventBuffer, It should put the event in the EventBuffer£¬Is it right?
    If it is right, Then the EventBuffer include requested event and the 
observedevent, and how can i distinguish them?

Mark


>From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
>To: "'???'" <juniperfu@hotmail.com>
>CC: megaco@ietf.org
>Subject: [Megaco] RE: about eventbuffer descriptor
>Date: Tue, 23 Apr 2002 21:33:07 -0400
>
>Yes.  When running in LockStep mode the MGC specifies both the Events
>Descriptor and the EventBuffer descriptor, and either can contain multiple
>events.  The Events Descriptor determines what events are reported, and 
the
>EventBuffer Descriptor determines what events are saved for processing
>against the next Events descriptor after an event notification has been
>sent.
>
>-----Original Message-----
>From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
>Sent: Tuesday, April 23, 2002 8:41 PM
>To: Taylor, Tom-PT [CAR:B800:EXCH]
>Cc: megaco@ietf.org
>Subject: about eventbuffer descriptor
>
>
>All,
>    In section 7.1.10 of megaco, there is a description about eventbuffer:
>     'the Eventbuffer descriptor contains a list of events, with their
>parameters if any, that the MG is requested to detect and buffer when
>eventbufferControl equals LocaStep'
>    from the descrition, I think it means the eventbuffer descriptor 
include
>many request event from MGC and the MG should detect the event by the
>eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it
>right?
>
>Mark
>
>
>
>_________________________________________________________________
>Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco




_________________________________________________________________
ÓëÁª»úµÄÅóÓÑ½øÐÐ½»Á÷£¬ÇëÊ¹ÓÃ MSN Messenger: 
http://messenger.microsoft.com/cn


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


From daemon@optimus.ietf.org  Wed Apr 24 04:44: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 EAA27733
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 04:44:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA14005
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 04:44:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12518;
	Wed, 24 Apr 2002 04:22:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12490
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 04:22:12 -0400 (EDT)
Received: from hotmail.com (f194.law15.hotmail.com [64.4.23.194])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27325
	for <megaco@ietf.org>; Wed, 24 Apr 2002 04:22:09 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 24 Apr 2002 01:21:20 -0700
Received: from 210.21.224.51 by lw15fd.law15.hotmail.msn.com with HTTP;
	Wed, 24 Apr 2002 08:21:19 GMT
X-Originating-IP: [210.21.224.51]
From: "=?gb2312?B?5LuYIOWujw==?=" <juniperfu@hotmail.com>
To: taylor@nortelnetworks.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] RE: about eventbuffer descriptor
Date: Wed, 24 Apr 2002 16:21:19 +0800
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <F194JX7rVGSLsNhIIqg00001e4e@hotmail.com>
X-OriginalArrivalTime: 24 Apr 2002 08:21:20.0084 (UTC) FILETIME=[0332D140:01C1EB69]
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

    When running in LockStep mode, If MG detected event which exist in 
EventBuffer, It should put the event in the EventBuffer£¬Is it right?
    If it is right, Then the EventBuffer include requested event and the 
observedevent, and how can i distinguish them?

Mark


>From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
>To: "'???'" <juniperfu@hotmail.com>
>CC: megaco@ietf.org
>Subject: [Megaco] RE: about eventbuffer descriptor
>Date: Tue, 23 Apr 2002 21:33:07 -0400
>
>Yes.  When running in LockStep mode the MGC specifies both the Events
>Descriptor and the EventBuffer descriptor, and either can contain multiple
>events.  The Events Descriptor determines what events are reported, and 
the
>EventBuffer Descriptor determines what events are saved for processing
>against the next Events descriptor after an event notification has been
>sent.
>
>-----Original Message-----
>From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
>Sent: Tuesday, April 23, 2002 8:41 PM
>To: Taylor, Tom-PT [CAR:B800:EXCH]
>Cc: megaco@ietf.org
>Subject: about eventbuffer descriptor
>
>
>All,
>    In section 7.1.10 of megaco, there is a description about eventbuffer:
>     'the Eventbuffer descriptor contains a list of events, with their
>parameters if any, that the MG is requested to detect and buffer when
>eventbufferControl equals LocaStep'
>    from the descrition, I think it means the eventbuffer descriptor 
include
>many request event from MGC and the MG should detect the event by the
>eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it
>right?
>
>Mark
>
>
>
>_________________________________________________________________
>Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco




_________________________________________________________________
ÓëÁª»úµÄÅóÓÑ½øÐÐ½»Á÷£¬ÇëÊ¹ÓÃ MSN Messenger: 
http://messenger.microsoft.com/cn


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



From megaco-admin@ietf.org  Wed Apr 24 06:07: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 GAA28722
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 06:07:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA16647;
	Wed, 24 Apr 2002 05:46:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA16620
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 05:46:40 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28513
	for <megaco@ietf.org>; Wed, 24 Apr 2002 05:46:35 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002368512@fsnt.future.futsoft.com>;
 Wed, 24 Apr 2002 15:35:21 +0530
Received: from elangok (elangok.future.futsoft.com [10.2.7.29])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g3O9jlh17668;
	Wed, 24 Apr 2002 15:15:47 +0530
Reply-To: <elangok@future.futsoft.com>
From: "Elango K" <elangok@future.futsoft.com>
To: "'Anil Jangam'" <anilj@indts.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Deleting termination from the Context
Date: Wed, 24 Apr 2002 15:17:37 +0530
Message-Id: <002f01c1eb75$117d2640$1d07020a@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
In-Reply-To: <F73B646FCC01D5118F530002B32C337263B3BF@INDTS_FS>
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 Anil,

Use of Subtract command with Context as '*' is permissible. This would
delete all ephemeral terminations and return all physical terminations to
null context.

Hope this helps.

Regards,
Elango.


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Anil Jangam
Sent: Wednesday, 24 April 2002 12:10 PM
To: 'megaco@ietf.org'
Subject: [Megaco] Deleting termination from the Context


Hi,

Is it possible to issue a 'Subtract' command to delete a Termination with
'Context' as a '*'.
I am looking at subtract command which essentially deletes a Termination
from the context, when I don't have the information about the context, in
which the Termination is present. Thus with 'Context' as '*', it would try
to find out the TerminastionId in all the contexts present and delete it.

regds,
/anil.

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

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
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. 
FSL 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  Wed Apr 24 06:07: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 GAA28737
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 06:07:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA17713
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 06:07:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA16647;
	Wed, 24 Apr 2002 05:46:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA16620
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 05:46:40 -0400 (EDT)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28513
	for <megaco@ietf.org>; Wed, 24 Apr 2002 05:46:35 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0002368512@fsnt.future.futsoft.com>;
 Wed, 24 Apr 2002 15:35:21 +0530
Received: from elangok (elangok.future.futsoft.com [10.2.7.29])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id g3O9jlh17668;
	Wed, 24 Apr 2002 15:15:47 +0530
Reply-To: <elangok@future.futsoft.com>
From: "Elango K" <elangok@future.futsoft.com>
To: "'Anil Jangam'" <anilj@indts.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Deleting termination from the Context
Date: Wed, 24 Apr 2002 15:17:37 +0530
Message-Id: <002f01c1eb75$117d2640$1d07020a@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
In-Reply-To: <F73B646FCC01D5118F530002B32C337263B3BF@INDTS_FS>
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 Anil,

Use of Subtract command with Context as '*' is permissible. This would
delete all ephemeral terminations and return all physical terminations to
null context.

Hope this helps.

Regards,
Elango.


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Anil Jangam
Sent: Wednesday, 24 April 2002 12:10 PM
To: 'megaco@ietf.org'
Subject: [Megaco] Deleting termination from the Context


Hi,

Is it possible to issue a 'Subtract' command to delete a Termination with
'Context' as a '*'.
I am looking at subtract command which essentially deletes a Termination
from the context, when I don't have the information about the context, in
which the Termination is present. Thus with 'Context' as '*', it would try
to find out the TerminastionId in all the contexts present and delete it.

regds,
/anil.

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

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
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. 
FSL 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 megaco-admin@ietf.org  Wed Apr 24 07: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 HAA29469
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 07:18:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA20136;
	Wed, 24 Apr 2002 07:01:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA20107
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 07:01:54 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29269
	for <megaco@ietf.org>; Wed, 24 Apr 2002 07:01:50 -0400 (EDT)
From: shbansal@hss.hns.com
Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id g3OB2Xc15110;
	Wed, 24 Apr 2002 16:32:33 +0530 (IST)
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by ultra.hss.co.in (8.10.0/8.10.0) with SMTP id g3OB2QM03930;
	Wed, 24 Apr 2002 16:32:26 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA5.003C55D8 ; Wed, 24 Apr 2002 16:29:01 +0530
X-Lotus-FromDomain: HSS
To: Anil Jangam <anilj@indts.com>
cc: "'elangok@future.futsoft.com'" <elangok@future.futsoft.com>,
        megaco@ietf.org
Message-ID: <65256BA5.003C4373.00@sandesh.hss.hns.com>
Date: Wed, 24 Apr 2002 16:33:22 +0530
Subject: RE: [Megaco] Deleting termination from the Context
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 Anil

It is possible to send subtract command with context ALL and termination fully
specified.
In such a case if the specified termination is present in any non null context,
it will get subtracted otherwise an error will be returned

Regards
Shobhit




Anil Jangam <anilj@indts.com> on 04/24/2002 04:27:19 PM

To:   "'elangok@future.futsoft.com'" <elangok@future.futsoft.com>,
      megaco@ietf.org
cc:    (bcc: Shobhit Bansal/HSS)

Subject:  RE: [Megaco] Deleting termination from the Context




Hi Elango,

Apparently this is the case when it is required to delete all terminations
in all the context. Does it mean that I can specify a specific Termination
ID and try to delete it with the method you have mentioned? In my case, I
want to delete a *given termination only* and not all.

/anil.

> -----Original Message-----
> From: Elango K [mailto:elangok@future.futsoft.com]
> Sent: Wednesday, April 24, 2002 3:18 PM
> To: 'Anil Jangam'; megaco@ietf.org
> Subject: RE: [Megaco] Deleting termination from the Context
>
>
> Hi Anil,
>
> Use of Subtract command with Context as '*' is permissible. This would
> delete all ephemeral terminations and return all physical
> terminations to
> null context.
>
> Hope this helps.
>
> Regards,
> Elango.
>
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Anil Jangam
> Sent: Wednesday, 24 April 2002 12:10 PM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Deleting termination from the Context
>
>
> Hi,
>
> Is it possible to issue a 'Subtract' command to delete a
> Termination with
> 'Context' as a '*'.
> I am looking at subtract command which essentially deletes a
> Termination
> from the context, when I don't have the information about the
> context, in
> which the Termination is present. Thus with 'Context' as '*',
> it would try
> to find out the TerminastionId in all the contexts present
> and delete it.
>
> regds,
> /anil.
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>
> **************************************************************
> *************
> This message is proprietary to Future Software Limited (FSL)
> 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.
> FSL 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





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


From daemon@optimus.ietf.org  Wed Apr 24 07:18: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 HAA29484
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 07:18:15 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA20832
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 07:18:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA20136;
	Wed, 24 Apr 2002 07:01:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA20107
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 07:01:54 -0400 (EDT)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29269
	for <megaco@ietf.org>; Wed, 24 Apr 2002 07:01:50 -0400 (EDT)
From: shbansal@hss.hns.com
Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id g3OB2Xc15110;
	Wed, 24 Apr 2002 16:32:33 +0530 (IST)
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by ultra.hss.co.in (8.10.0/8.10.0) with SMTP id g3OB2QM03930;
	Wed, 24 Apr 2002 16:32:26 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256BA5.003C55D8 ; Wed, 24 Apr 2002 16:29:01 +0530
X-Lotus-FromDomain: HSS
To: Anil Jangam <anilj@indts.com>
cc: "'elangok@future.futsoft.com'" <elangok@future.futsoft.com>,
        megaco@ietf.org
Message-ID: <65256BA5.003C4373.00@sandesh.hss.hns.com>
Date: Wed, 24 Apr 2002 16:33:22 +0530
Subject: RE: [Megaco] Deleting termination from the Context
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 Anil

It is possible to send subtract command with context ALL and termination fully
specified.
In such a case if the specified termination is present in any non null context,
it will get subtracted otherwise an error will be returned

Regards
Shobhit




Anil Jangam <anilj@indts.com> on 04/24/2002 04:27:19 PM

To:   "'elangok@future.futsoft.com'" <elangok@future.futsoft.com>,
      megaco@ietf.org
cc:    (bcc: Shobhit Bansal/HSS)

Subject:  RE: [Megaco] Deleting termination from the Context




Hi Elango,

Apparently this is the case when it is required to delete all terminations
in all the context. Does it mean that I can specify a specific Termination
ID and try to delete it with the method you have mentioned? In my case, I
want to delete a *given termination only* and not all.

/anil.

> -----Original Message-----
> From: Elango K [mailto:elangok@future.futsoft.com]
> Sent: Wednesday, April 24, 2002 3:18 PM
> To: 'Anil Jangam'; megaco@ietf.org
> Subject: RE: [Megaco] Deleting termination from the Context
>
>
> Hi Anil,
>
> Use of Subtract command with Context as '*' is permissible. This would
> delete all ephemeral terminations and return all physical
> terminations to
> null context.
>
> Hope this helps.
>
> Regards,
> Elango.
>
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Anil Jangam
> Sent: Wednesday, 24 April 2002 12:10 PM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Deleting termination from the Context
>
>
> Hi,
>
> Is it possible to issue a 'Subtract' command to delete a
> Termination with
> 'Context' as a '*'.
> I am looking at subtract command which essentially deletes a
> Termination
> from the context, when I don't have the information about the
> context, in
> which the Termination is present. Thus with 'Context' as '*',
> it would try
> to find out the TerminastionId in all the contexts present
> and delete it.
>
> regds,
> /anil.
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>
> **************************************************************
> *************
> This message is proprietary to Future Software Limited (FSL)
> 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.
> FSL 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





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



From megaco-admin@ietf.org  Wed Apr 24 07:19: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 HAA29554
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 07:19:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19492;
	Wed, 24 Apr 2002 06:54:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19465
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 06:53:58 -0400 (EDT)
Received: from telesoft.indts.com (IDENT:root@[164.164.71.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29139
	for <megaco@ietf.org>; Wed, 24 Apr 2002 06:53:53 -0400 (EDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id QAA19856;
	Wed, 24 Apr 2002 16:56:31 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <GWSJCJAG>; Wed, 24 Apr 2002 16:27:19 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337263B3C0@INDTS_FS>
From: Anil Jangam <anilj@indts.com>
To: "'elangok@future.futsoft.com'" <elangok@future.futsoft.com>,
        megaco@ietf.org
Subject: RE: [Megaco] Deleting termination from the Context
Date: Wed, 24 Apr 2002 16:27:19 +0530
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

Hi Elango,

Apparently this is the case when it is required to delete all terminations
in all the context. Does it mean that I can specify a specific Termination
ID and try to delete it with the method you have mentioned? In my case, I
want to delete a *given termination only* and not all.

/anil.

> -----Original Message-----
> From: Elango K [mailto:elangok@future.futsoft.com]
> Sent: Wednesday, April 24, 2002 3:18 PM
> To: 'Anil Jangam'; megaco@ietf.org
> Subject: RE: [Megaco] Deleting termination from the Context
> 
> 
> Hi Anil,
> 
> Use of Subtract command with Context as '*' is permissible. This would
> delete all ephemeral terminations and return all physical 
> terminations to
> null context.
> 
> Hope this helps.
> 
> Regards,
> Elango.
> 
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Anil Jangam
> Sent: Wednesday, 24 April 2002 12:10 PM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Deleting termination from the Context
> 
> 
> Hi,
> 
> Is it possible to issue a 'Subtract' command to delete a 
> Termination with
> 'Context' as a '*'.
> I am looking at subtract command which essentially deletes a 
> Termination
> from the context, when I don't have the information about the 
> context, in
> which the Termination is present. Thus with 'Context' as '*', 
> it would try
> to find out the TerminastionId in all the contexts present 
> and delete it.
> 
> regds,
> /anil.
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> **************************************************************
> *************
> This message is proprietary to Future Software Limited (FSL) 
> 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. 
> FSL 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  Wed Apr 24 08: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 HAA29562
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 07:19:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA21194
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 07:19:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19492;
	Wed, 24 Apr 2002 06:54:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19465
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 06:53:58 -0400 (EDT)
Received: from telesoft.indts.com (IDENT:root@[164.164.71.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29139
	for <megaco@ietf.org>; Wed, 24 Apr 2002 06:53:53 -0400 (EDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id QAA19856;
	Wed, 24 Apr 2002 16:56:31 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <GWSJCJAG>; Wed, 24 Apr 2002 16:27:19 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337263B3C0@INDTS_FS>
From: Anil Jangam <anilj@indts.com>
To: "'elangok@future.futsoft.com'" <elangok@future.futsoft.com>,
        megaco@ietf.org
Subject: RE: [Megaco] Deleting termination from the Context
Date: Wed, 24 Apr 2002 16:27:19 +0530
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

Hi Elango,

Apparently this is the case when it is required to delete all terminations
in all the context. Does it mean that I can specify a specific Termination
ID and try to delete it with the method you have mentioned? In my case, I
want to delete a *given termination only* and not all.

/anil.

> -----Original Message-----
> From: Elango K [mailto:elangok@future.futsoft.com]
> Sent: Wednesday, April 24, 2002 3:18 PM
> To: 'Anil Jangam'; megaco@ietf.org
> Subject: RE: [Megaco] Deleting termination from the Context
> 
> 
> Hi Anil,
> 
> Use of Subtract command with Context as '*' is permissible. This would
> delete all ephemeral terminations and return all physical 
> terminations to
> null context.
> 
> Hope this helps.
> 
> Regards,
> Elango.
> 
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Anil Jangam
> Sent: Wednesday, 24 April 2002 12:10 PM
> To: 'megaco@ietf.org'
> Subject: [Megaco] Deleting termination from the Context
> 
> 
> Hi,
> 
> Is it possible to issue a 'Subtract' command to delete a 
> Termination with
> 'Context' as a '*'.
> I am looking at subtract command which essentially deletes a 
> Termination
> from the context, when I don't have the information about the 
> context, in
> which the Termination is present. Thus with 'Context' as '*', 
> it would try
> to find out the TerminastionId in all the contexts present 
> and delete it.
> 
> regds,
> /anil.
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> **************************************************************
> *************
> This message is proprietary to Future Software Limited (FSL) 
> 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. 
> FSL 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 megaco-admin@ietf.org  Wed Apr 24 08:26: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 IAA01320
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 08:26:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24208;
	Wed, 24 Apr 2002 08:01:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24177
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 08:01:51 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00577
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:01:49 -0400 (EDT)
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 g3OC1JT02047
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:01:19 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJARPH>; Wed, 24 Apr 2002 08:01:21 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A367@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'rezhirpavai@hss.hns.com'" <rezhirpavai@hss.hns.com>
Cc: "'???'" <juniperfu@hotmail.com>, megaco@ietf.org
Subject: RE: [Megaco] RE: about eventbuffer descriptor
Date: Wed, 24 Apr 2002 08:01:22 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Right after the statement you quote is this paragraph:

<quote>
If the value of the EventBufferControl property equals LockStep, following
detection of such an event, normal handling of events is suspended. Any
event which is subsequently detected and occurs in the EventBuffer
Descriptor is added to the end of the EventBuffer (a FIFO queue), along with
the time that it was detected.   The MG SHALL wait for a new
EventsDescriptor to be loaded.  A new EventsDescriptor can be loaded either
as the result of receiving a command with a new EventsDescriptor, or by
activating an embedded EventsDescriptor.
</quote>

Some people wanted Lockstep mode because it guarantees the correct sequence
of event notifications at the MGC if one is using UDP transport.

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Wednesday, April 24, 2002 12:06 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: '???'; megaco@ietf.org
Subject: Re: [Megaco] RE: about eventbuffer descriptor




Hello Tom,
     According to a statement in the protocol, Events mentioned in event
descriptor remain active in MG till next event descriptor is received. (An
exception to this is the digit map event). Thus if an MGC wants that none of
the
events being detetced at MG be lost, it can send all required events on that
termination in a single event descriptor and then get the events as and when
they are detected at MG without sending a second event descriptor. It can
send
the next event descriptor only when subtract is sent. If this is a valid
sequence, then where and why would an MGC use event buffer descriptor and
thus a
lockstep mode.

Regards,
- R. Ezhirpavai





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 04/24/2002 07:03:07 AM

To:   "'???'" <juniperfu@hotmail.com>
cc:   megaco@ietf.org (bcc: R Ezhirpavai/HSS)

Subject:  [Megaco] RE: about eventbuffer descriptor




Yes.  When running in LockStep mode the MGC specifies both the Events
Descriptor and the EventBuffer descriptor, and either can contain multiple
events.  The Events Descriptor determines what events are reported, and the
EventBuffer Descriptor determines what events are saved for processing
against the next Events descriptor after an event notification has been
sent.

-----Original Message-----
From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
Sent: Tuesday, April 23, 2002 8:41 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: about eventbuffer descriptor


All,
   In section 7.1.10 of megaco, there is a description about eventbuffer:
    'the Eventbuffer descriptor contains a list of events, with their
parameters if any, that the MG is requested to detect and buffer when
eventbufferControl equals LocaStep'
   from the descrition, I think it means the eventbuffer descriptor include
many request event from MGC and the MG should detect the event by the
eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it
right?

Mark



_________________________________________________________________
???????? MSN Explorer??http://explorer.msn.com/lccn/intl.asp


_______________________________________________
Megaco mailing list
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 Apr 24 08: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 IAA01334
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 08:26:17 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA25275
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 08:26:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24208;
	Wed, 24 Apr 2002 08:01:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24177
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 08:01:51 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00577
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:01:49 -0400 (EDT)
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 g3OC1JT02047
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:01:19 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJARPH>; Wed, 24 Apr 2002 08:01:21 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A367@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'rezhirpavai@hss.hns.com'" <rezhirpavai@hss.hns.com>
Cc: "'???'" <juniperfu@hotmail.com>, megaco@ietf.org
Subject: RE: [Megaco] RE: about eventbuffer descriptor
Date: Wed, 24 Apr 2002 08:01:22 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Right after the statement you quote is this paragraph:

<quote>
If the value of the EventBufferControl property equals LockStep, following
detection of such an event, normal handling of events is suspended. Any
event which is subsequently detected and occurs in the EventBuffer
Descriptor is added to the end of the EventBuffer (a FIFO queue), along with
the time that it was detected.   The MG SHALL wait for a new
EventsDescriptor to be loaded.  A new EventsDescriptor can be loaded either
as the result of receiving a command with a new EventsDescriptor, or by
activating an embedded EventsDescriptor.
</quote>

Some people wanted Lockstep mode because it guarantees the correct sequence
of event notifications at the MGC if one is using UDP transport.

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Wednesday, April 24, 2002 12:06 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: '???'; megaco@ietf.org
Subject: Re: [Megaco] RE: about eventbuffer descriptor




Hello Tom,
     According to a statement in the protocol, Events mentioned in event
descriptor remain active in MG till next event descriptor is received. (An
exception to this is the digit map event). Thus if an MGC wants that none of
the
events being detetced at MG be lost, it can send all required events on that
termination in a single event descriptor and then get the events as and when
they are detected at MG without sending a second event descriptor. It can
send
the next event descriptor only when subtract is sent. If this is a valid
sequence, then where and why would an MGC use event buffer descriptor and
thus a
lockstep mode.

Regards,
- R. Ezhirpavai





"Tom-PT Taylor" <taylor@nortelnetworks.com> on 04/24/2002 07:03:07 AM

To:   "'???'" <juniperfu@hotmail.com>
cc:   megaco@ietf.org (bcc: R Ezhirpavai/HSS)

Subject:  [Megaco] RE: about eventbuffer descriptor




Yes.  When running in LockStep mode the MGC specifies both the Events
Descriptor and the EventBuffer descriptor, and either can contain multiple
events.  The Events Descriptor determines what events are reported, and the
EventBuffer Descriptor determines what events are saved for processing
against the next Events descriptor after an event notification has been
sent.

-----Original Message-----
From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
Sent: Tuesday, April 23, 2002 8:41 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: about eventbuffer descriptor


All,
   In section 7.1.10 of megaco, there is a description about eventbuffer:
    'the Eventbuffer descriptor contains a list of events, with their
parameters if any, that the MG is requested to detect and buffer when
eventbufferControl equals LocaStep'
   from the descrition, I think it means the eventbuffer descriptor include
many request event from MGC and the MG should detect the event by the
eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it
right?

Mark



_________________________________________________________________
???????? MSN Explorer??http://explorer.msn.com/lccn/intl.asp


_______________________________________________
Megaco mailing list
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 Apr 24 08:36: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 IAA01615
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 08:36:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24541;
	Wed, 24 Apr 2002 08:08:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24509
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 08:08:37 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00866
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:08:34 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3OC85B17043
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:08:05 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJARSX>; Wed, 24 Apr 2002 08:08:06 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A368@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'???'" <juniperfu@hotmail.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] RE: about eventbuffer descriptor
Date: Wed, 24 Apr 2002 08:08:07 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

You have to keep four different logical concepts separate in your mind.  The
first three are syntactic constructs used in the messaging between the MGC
and MG.  The fourth exists only in the MG.
  (1) the Events Descriptor, naming the events for which the MGC wants
notifications to be generated;
  (2) the EventBuffer DESCRIPTOR, naming the events the MGC wants buffered
during Lockstep mode while waiting for a new Events descriptor;
  (3) the ObservedEvents Descriptor, used in the Notify request to report
observed events to the MGC;
  (4) the EventBuffer, which, unlike the DESCRIPTORs listed above, is a
purely logical concept used to describe MG behaviour during event
processing.

-----Original Message-----
From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
Sent: Wednesday, April 24, 2002 4:21 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: Re: [Megaco] RE: about eventbuffer descriptor


    When running in LockStep mode, If MG detected event which exist in 
EventBuffer, It should put the event in the EventBuffer£¬Is it right?
    If it is right, Then the EventBuffer include requested event and the 
observedevent, and how can i distinguish them?

Mark


>From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
>To: "'???'" <juniperfu@hotmail.com>
>CC: megaco@ietf.org
>Subject: [Megaco] RE: about eventbuffer descriptor
>Date: Tue, 23 Apr 2002 21:33:07 -0400
>
>Yes.  When running in LockStep mode the MGC specifies both the Events
>Descriptor and the EventBuffer descriptor, and either can contain multiple
>events.  The Events Descriptor determines what events are reported, and 
the
>EventBuffer Descriptor determines what events are saved for processing
>against the next Events descriptor after an event notification has been
>sent.
>
>-----Original Message-----
>From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
>Sent: Tuesday, April 23, 2002 8:41 PM
>To: Taylor, Tom-PT [CAR:B800:EXCH]
>Cc: megaco@ietf.org
>Subject: about eventbuffer descriptor
>
>
>All,
>    In section 7.1.10 of megaco, there is a description about eventbuffer:
>     'the Eventbuffer descriptor contains a list of events, with their
>parameters if any, that the MG is requested to detect and buffer when
>eventbufferControl equals LocaStep'
>    from the descrition, I think it means the eventbuffer descriptor 
include
>many request event from MGC and the MG should detect the event by the
>eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it
>right?
>
>Mark
>
>
>
>_________________________________________________________________
>Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco




_________________________________________________________________
ÓëÁª»úµÄÅóÓÑ½øÐÐ½»Á÷£¬ÇëÊ¹ÓÃ MSN Messenger: 
http://messenger.microsoft.com/cn


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


From daemon@optimus.ietf.org  Wed Apr 24 08:36: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 IAA01625
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 08:36:30 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA26123
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 08:36:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24541;
	Wed, 24 Apr 2002 08:08:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24509
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 08:08:37 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00866
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:08:34 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3OC85B17043
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:08:05 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJARSX>; Wed, 24 Apr 2002 08:08:06 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A368@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'???'" <juniperfu@hotmail.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] RE: about eventbuffer descriptor
Date: Wed, 24 Apr 2002 08:08:07 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

You have to keep four different logical concepts separate in your mind.  The
first three are syntactic constructs used in the messaging between the MGC
and MG.  The fourth exists only in the MG.
  (1) the Events Descriptor, naming the events for which the MGC wants
notifications to be generated;
  (2) the EventBuffer DESCRIPTOR, naming the events the MGC wants buffered
during Lockstep mode while waiting for a new Events descriptor;
  (3) the ObservedEvents Descriptor, used in the Notify request to report
observed events to the MGC;
  (4) the EventBuffer, which, unlike the DESCRIPTORs listed above, is a
purely logical concept used to describe MG behaviour during event
processing.

-----Original Message-----
From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
Sent: Wednesday, April 24, 2002 4:21 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: megaco@ietf.org
Subject: Re: [Megaco] RE: about eventbuffer descriptor


    When running in LockStep mode, If MG detected event which exist in 
EventBuffer, It should put the event in the EventBuffer£¬Is it right?
    If it is right, Then the EventBuffer include requested event and the 
observedevent, and how can i distinguish them?

Mark


>From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
>To: "'???'" <juniperfu@hotmail.com>
>CC: megaco@ietf.org
>Subject: [Megaco] RE: about eventbuffer descriptor
>Date: Tue, 23 Apr 2002 21:33:07 -0400
>
>Yes.  When running in LockStep mode the MGC specifies both the Events
>Descriptor and the EventBuffer descriptor, and either can contain multiple
>events.  The Events Descriptor determines what events are reported, and 
the
>EventBuffer Descriptor determines what events are saved for processing
>against the next Events descriptor after an event notification has been
>sent.
>
>-----Original Message-----
>From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
>Sent: Tuesday, April 23, 2002 8:41 PM
>To: Taylor, Tom-PT [CAR:B800:EXCH]
>Cc: megaco@ietf.org
>Subject: about eventbuffer descriptor
>
>
>All,
>    In section 7.1.10 of megaco, there is a description about eventbuffer:
>     'the Eventbuffer descriptor contains a list of events, with their
>parameters if any, that the MG is requested to detect and buffer when
>eventbufferControl equals LocaStep'
>    from the descrition, I think it means the eventbuffer descriptor 
include
>many request event from MGC and the MG should detect the event by the
>eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it
>right?
>
>Mark
>
>
>
>_________________________________________________________________
>Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco




_________________________________________________________________
ÓëÁª»úµÄÅóÓÑ½øÐÐ½»Á÷£¬ÇëÊ¹ÓÃ MSN Messenger: 
http://messenger.microsoft.com/cn


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



From megaco-admin@ietf.org  Wed Apr 24 09:13: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 JAA03042
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 09:13:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27315;
	Wed, 24 Apr 2002 08:54:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27282
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 08:54:19 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02121
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:54:16 -0400 (EDT)
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 g3OCrkT04391
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:53:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJASVZ>; Wed, 24 Apr 2002 08:53:48 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A36B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Anil Jangam'" <anilj@indts.com>, "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Audit &  contextTerminationAudit??
Date: Wed, 24 Apr 2002 08:53:05 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Hi.  Answers marked with [PTT].

-----Original Message-----
From: Anil Jangam [mailto:anilj@indts.com]
Sent: Wednesday, April 24, 2002 1:50 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Audit & contextTerminationAudit??


Hi,

1. How one should use/issue the 'Audit' command from the MGC persepective?
Is it necesary to 'Audit' the endpoint/gateway every time before a call
initiated? 

[PTT]
In my opinion, audits should be used in two ways:
 - at startup of an association or after the MGC recognizes a discontinuity
or inconsistency, to (re)synchronize state between the MG and MGC
 - as a low-level continuously running background task, to assure state
consistency between the MG and MGC.

2. In the 'AuditValue' return parameter in the 'auditReply' what is the
'contextTerminationAudit' return option? Under what circumstances,  the
Audit command would return it and what are implications/effects of this
return on the actual call processing/control?

[PTT]
Look in section 7.2.5, paragraph beginning "EventBuffer returns the set of
events and associated parameter values ...", final three sentences.

I am not able to understand the meaning of the 'contextTerminationAudit' and
couldn't proceed to change the call handling state machine.

Regds,
/anil.

_______________________________________________
Megaco mailing list
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 Apr 24 09:13: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 JAA03055
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 09:13:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA28662
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 09:13:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27315;
	Wed, 24 Apr 2002 08:54:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27282
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 08:54:19 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02121
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:54:16 -0400 (EDT)
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 g3OCrkT04391
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:53:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJASVZ>; Wed, 24 Apr 2002 08:53:48 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A36B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Anil Jangam'" <anilj@indts.com>, "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Audit &  contextTerminationAudit??
Date: Wed, 24 Apr 2002 08:53:05 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Hi.  Answers marked with [PTT].

-----Original Message-----
From: Anil Jangam [mailto:anilj@indts.com]
Sent: Wednesday, April 24, 2002 1:50 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Audit & contextTerminationAudit??


Hi,

1. How one should use/issue the 'Audit' command from the MGC persepective?
Is it necesary to 'Audit' the endpoint/gateway every time before a call
initiated? 

[PTT]
In my opinion, audits should be used in two ways:
 - at startup of an association or after the MGC recognizes a discontinuity
or inconsistency, to (re)synchronize state between the MG and MGC
 - as a low-level continuously running background task, to assure state
consistency between the MG and MGC.

2. In the 'AuditValue' return parameter in the 'auditReply' what is the
'contextTerminationAudit' return option? Under what circumstances,  the
Audit command would return it and what are implications/effects of this
return on the actual call processing/control?

[PTT]
Look in section 7.2.5, paragraph beginning "EventBuffer returns the set of
events and associated parameter values ...", final three sentences.

I am not able to understand the meaning of the 'contextTerminationAudit' and
couldn't proceed to change the call handling state machine.

Regds,
/anil.

_______________________________________________
Megaco mailing list
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 Apr 24 09:20: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 JAA03311
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 09:20:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27540;
	Wed, 24 Apr 2002 08:58:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27437
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 08:58:29 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02202
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:58:26 -0400 (EDT)
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 g3OCvHT04553;
	Wed, 24 Apr 2002 08:57:17 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJASYR>; Wed, 24 Apr 2002 08:57:18 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A36C@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Anil Jangam'" <anilj@indts.com>, "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Deleting termination from the Context
Date: Wed, 24 Apr 2002 08:55:36 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1EB8F.426F8EA4"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1EB8F.426F8EA4
Content-Type: text/plain;
	charset="ISO-8859-1"

Following the precedent set with the Audit commands, I think this should be
possible.

-----Original Message-----
From: Anil Jangam [mailto:anilj@indts.com]
Sent: Wednesday, April 24, 2002 2:40 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Deleting termination from the Context


Hi,

Is it possible to issue a 'Subtract' command to delete a Termination with
'Context' as a '*'.
I am looking at subtract command which essentially deletes a Termination
from the context, when I don't have the information about the context, in
which the Termination is present. Thus with 'Context' as '*', it would try
to find out the TerminastionId in all the contexts present and delete it. 

regds,
/anil.

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

------_=_NextPart_001_01C1EB8F.426F8EA4
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.2655.35">
<TITLE>RE: [Megaco] Deleting termination from the Context</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Following the precedent set with the Audit commands, =
I think this should be possible.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Anil Jangam [<A =
HREF=3D"mailto:anilj@indts.com">mailto:anilj@indts.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, April 24, 2002 2:40 AM</FONT>
<BR><FONT SIZE=3D2>To: 'megaco@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Deleting termination from the =
Context</FONT>
</P>
<BR>

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

<P><FONT SIZE=3D2>Is it possible to issue a 'Subtract' command to =
delete a Termination with</FONT>
<BR><FONT SIZE=3D2>'Context' as a '*'.</FONT>
<BR><FONT SIZE=3D2>I am looking at subtract command which essentially =
deletes a Termination</FONT>
<BR><FONT SIZE=3D2>from the context, when I don't have the information =
about the context, in</FONT>
<BR><FONT SIZE=3D2>which the Termination is present. Thus with =
'Context' as '*', it would try</FONT>
<BR><FONT SIZE=3D2>to find out the TerminastionId in all the contexts =
present and delete it. </FONT>
</P>

<P><FONT SIZE=3D2>regds,</FONT>
<BR><FONT SIZE=3D2>/anil.</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_01C1EB8F.426F8EA4--

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


From daemon@optimus.ietf.org  Wed Apr 24 09: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 JAA03322
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 09:20:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA29042
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 09:20:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27540;
	Wed, 24 Apr 2002 08:58:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27437
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 08:58:29 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02202
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:58:26 -0400 (EDT)
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 g3OCvHT04553;
	Wed, 24 Apr 2002 08:57:17 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJASYR>; Wed, 24 Apr 2002 08:57:18 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A36C@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Anil Jangam'" <anilj@indts.com>, "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] Deleting termination from the Context
Date: Wed, 24 Apr 2002 08:55:36 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1EB8F.426F8EA4"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1EB8F.426F8EA4
Content-Type: text/plain;
	charset="ISO-8859-1"

Following the precedent set with the Audit commands, I think this should be
possible.

-----Original Message-----
From: Anil Jangam [mailto:anilj@indts.com]
Sent: Wednesday, April 24, 2002 2:40 AM
To: 'megaco@ietf.org'
Subject: [Megaco] Deleting termination from the Context


Hi,

Is it possible to issue a 'Subtract' command to delete a Termination with
'Context' as a '*'.
I am looking at subtract command which essentially deletes a Termination
from the context, when I don't have the information about the context, in
which the Termination is present. Thus with 'Context' as '*', it would try
to find out the TerminastionId in all the contexts present and delete it. 

regds,
/anil.

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

------_=_NextPart_001_01C1EB8F.426F8EA4
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.2655.35">
<TITLE>RE: [Megaco] Deleting termination from the Context</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Following the precedent set with the Audit commands, =
I think this should be possible.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Anil Jangam [<A =
HREF=3D"mailto:anilj@indts.com">mailto:anilj@indts.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Wednesday, April 24, 2002 2:40 AM</FONT>
<BR><FONT SIZE=3D2>To: 'megaco@ietf.org'</FONT>
<BR><FONT SIZE=3D2>Subject: [Megaco] Deleting termination from the =
Context</FONT>
</P>
<BR>

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

<P><FONT SIZE=3D2>Is it possible to issue a 'Subtract' command to =
delete a Termination with</FONT>
<BR><FONT SIZE=3D2>'Context' as a '*'.</FONT>
<BR><FONT SIZE=3D2>I am looking at subtract command which essentially =
deletes a Termination</FONT>
<BR><FONT SIZE=3D2>from the context, when I don't have the information =
about the context, in</FONT>
<BR><FONT SIZE=3D2>which the Termination is present. Thus with =
'Context' as '*', it would try</FONT>
<BR><FONT SIZE=3D2>to find out the TerminastionId in all the contexts =
present and delete it. </FONT>
</P>

<P><FONT SIZE=3D2>regds,</FONT>
<BR><FONT SIZE=3D2>/anil.</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_01C1EB8F.426F8EA4--

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



From megaco-admin@ietf.org  Wed Apr 24 09:21: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 JAA03371
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 09:21:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27414;
	Wed, 24 Apr 2002 08:58:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27378
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 08:58:11 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02192
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:58:08 -0400 (EDT)
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 g3OCvcT04686
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:57:38 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJAS6K>; Wed, 24 Apr 2002 08:57:40 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A36D@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'elangok@future.futsoft.com'" <elangok@future.futsoft.com>,
        "'Anil Jangam'" <anilj@indts.com>, megaco@ietf.org
Subject: RE: [Megaco] Deleting termination from the Context
Date: Wed, 24 Apr 2002 08:57:39 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

You're thinking of ContextId=*{Subtract=*{}}}.  Anil was asking about 
ContextId=*{Subtract=specific{}}}.

-----Original Message-----
From: Elango K [mailto:elangok@future.futsoft.com]
Sent: Wednesday, April 24, 2002 5:48 AM
To: 'Anil Jangam'; megaco@ietf.org
Subject: RE: [Megaco] Deleting termination from the Context


Hi Anil,

Use of Subtract command with Context as '*' is permissible. This would
delete all ephemeral terminations and return all physical terminations to
null context.

Hope this helps.

Regards,
Elango.


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Anil Jangam
Sent: Wednesday, 24 April 2002 12:10 PM
To: 'megaco@ietf.org'
Subject: [Megaco] Deleting termination from the Context


Hi,

Is it possible to issue a 'Subtract' command to delete a Termination with
'Context' as a '*'.
I am looking at subtract command which essentially deletes a Termination
from the context, when I don't have the information about the context, in
which the Termination is present. Thus with 'Context' as '*', it would try
to find out the TerminastionId in all the contexts present and delete it.

regds,
/anil.

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

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
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. 
FSL 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

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


From daemon@optimus.ietf.org  Wed Apr 24 09:21: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 JAA03384
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 09:21:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA29162
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 09:21:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27414;
	Wed, 24 Apr 2002 08:58:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27378
	for <megaco@optimus.ietf.org>; Wed, 24 Apr 2002 08:58:11 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02192
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:58:08 -0400 (EDT)
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 g3OCvcT04686
	for <megaco@ietf.org>; Wed, 24 Apr 2002 08:57:38 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCVJAS6K>; Wed, 24 Apr 2002 08:57:40 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A36D@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'elangok@future.futsoft.com'" <elangok@future.futsoft.com>,
        "'Anil Jangam'" <anilj@indts.com>, megaco@ietf.org
Subject: RE: [Megaco] Deleting termination from the Context
Date: Wed, 24 Apr 2002 08:57:39 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

You're thinking of ContextId=*{Subtract=*{}}}.  Anil was asking about 
ContextId=*{Subtract=specific{}}}.

-----Original Message-----
From: Elango K [mailto:elangok@future.futsoft.com]
Sent: Wednesday, April 24, 2002 5:48 AM
To: 'Anil Jangam'; megaco@ietf.org
Subject: RE: [Megaco] Deleting termination from the Context


Hi Anil,

Use of Subtract command with Context as '*' is permissible. This would
delete all ephemeral terminations and return all physical terminations to
null context.

Hope this helps.

Regards,
Elango.


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Anil Jangam
Sent: Wednesday, 24 April 2002 12:10 PM
To: 'megaco@ietf.org'
Subject: [Megaco] Deleting termination from the Context


Hi,

Is it possible to issue a 'Subtract' command to delete a Termination with
'Context' as a '*'.
I am looking at subtract command which essentially deletes a Termination
from the context, when I don't have the information about the context, in
which the Termination is present. Thus with 'Context' as '*', it would try
to find out the TerminastionId in all the contexts present and delete it.

regds,
/anil.

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

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
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. 
FSL 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

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



From megaco-admin@ietf.org  Wed Apr 24 20:53: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 UAA12551
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 20:53:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11481;
	Wed, 24 Apr 2002 20:29:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11452
	for <megaco@ns.ietf.org>; Wed, 24 Apr 2002 20:29:41 -0400 (EDT)
Received: from hotmail.com (f222.law15.hotmail.com [64.4.23.222])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12215
	for <megaco@ietf.org>; Wed, 24 Apr 2002 20:29:37 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 24 Apr 2002 17:29:09 -0700
Received: from 210.21.224.51 by lw15fd.law15.hotmail.msn.com with HTTP;
	Thu, 25 Apr 2002 00:29:09 GMT
X-Originating-IP: [210.21.224.51]
From: "=?gb2312?B?5LuYIOWujw==?=" <juniperfu@hotmail.com>
To: taylor@nortelnetworks.com
Cc: megaco@ietf.org
Subject: RE: [Megaco] RE: about eventbuffer descriptor
Date: Thu, 25 Apr 2002 08:29:09 +0800
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <F222ririOCag4SfKekF00002e54@hotmail.com>
X-OriginalArrivalTime: 25 Apr 2002 00:29:09.0250 (UTC) FILETIME=[371E5E20:01C1EBF0]
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Thanks, taylor.


>From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
>To: "'???'" <juniperfu@hotmail.com>
>CC: megaco@ietf.org
>Subject: RE: [Megaco] RE: about eventbuffer descriptor
>Date: Wed, 24 Apr 2002 08:08:07 -0400
>
>You have to keep four different logical concepts separate in your mind.  
The
>first three are syntactic constructs used in the messaging between the MGC
>and MG.  The fourth exists only in the MG.
>   (1) the Events Descriptor, naming the events for which the MGC wants
>notifications to be generated;
>   (2) the EventBuffer DESCRIPTOR, naming the events the MGC wants 
buffered
>during Lockstep mode while waiting for a new Events descriptor;
>   (3) the ObservedEvents Descriptor, used in the Notify request to report
>observed events to the MGC;
>   (4) the EventBuffer, which, unlike the DESCRIPTORs listed above, is a
>purely logical concept used to describe MG behaviour during event
>processing.
>
>-----Original Message-----
>From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
>Sent: Wednesday, April 24, 2002 4:21 AM
>To: Taylor, Tom-PT [CAR:B800:EXCH]
>Cc: megaco@ietf.org
>Subject: Re: [Megaco] RE: about eventbuffer descriptor
>
>
>     When running in LockStep mode, If MG detected event which exist in
>EventBuffer, It should put the event in the EventBuffer£¬Is it right?
>     If it is right, Then the EventBuffer include requested event and the
>observedevent, and how can i distinguish them?
>
>Mark
>
>
> >From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
> >To: "'???'" <juniperfu@hotmail.com>
> >CC: megaco@ietf.org
> >Subject: [Megaco] RE: about eventbuffer descriptor
> >Date: Tue, 23 Apr 2002 21:33:07 -0400
> >
> >Yes.  When running in LockStep mode the MGC specifies both the Events
> >Descriptor and the EventBuffer descriptor, and either can contain 
multiple
> >events.  The Events Descriptor determines what events are reported, and
>the
> >EventBuffer Descriptor determines what events are saved for processing
> >against the next Events descriptor after an event notification has been
> >sent.
> >
> >-----Original Message-----
> >From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
> >Sent: Tuesday, April 23, 2002 8:41 PM
> >To: Taylor, Tom-PT [CAR:B800:EXCH]
> >Cc: megaco@ietf.org
> >Subject: about eventbuffer descriptor
> >
> >
> >All,
> >    In section 7.1.10 of megaco, there is a description about 
eventbuffer:
> >     'the Eventbuffer descriptor contains a list of events, with their
> >parameters if any, that the MG is requested to detect and buffer when
> >eventbufferControl equals LocaStep'
> >    from the descrition, I think it means the eventbuffer descriptor
>include
> >many request event from MGC and the MG should detect the event by the
> >eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it
> >right?
> >
> >Mark
> >
> >
> >
> >_________________________________________________________________
> >Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp
> >
> >
> >_______________________________________________
> >Megaco mailing list
> >Megaco@ietf.org
> >https://www1.ietf.org/mailman/listinfo/megaco
>
>
>
>
>_________________________________________________________________
>ÓëÁª»úµÄÅóÓÑ½øÐÐ½»Á÷£¬ÇëÊ¹ÓÃ MSN Messenger:
>http://messenger.microsoft.com/cn
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco




_________________________________________________________________
Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp


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


From daemon@ns.ietf.org  Wed Apr 24 20:53: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 UAA12562
	for <megaco-archive@odin.ietf.org>; Wed, 24 Apr 2002 20:53:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA12819
	for megaco-archive@odin.ietf.org; Wed, 24 Apr 2002 20:53:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11481;
	Wed, 24 Apr 2002 20:29:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11452
	for <megaco@ns.ietf.org>; Wed, 24 Apr 2002 20:29:41 -0400 (EDT)
Received: from hotmail.com (f222.law15.hotmail.com [64.4.23.222])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12215
	for <megaco@ietf.org>; Wed, 24 Apr 2002 20:29:37 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 24 Apr 2002 17:29:09 -0700
Received: from 210.21.224.51 by lw15fd.law15.hotmail.msn.com with HTTP;
	Thu, 25 Apr 2002 00:29:09 GMT
X-Originating-IP: [210.21.224.51]
From: "=?gb2312?B?5LuYIOWujw==?=" <juniperfu@hotmail.com>
To: taylor@nortelnetworks.com
Cc: megaco@ietf.org
Subject: RE: [Megaco] RE: about eventbuffer descriptor
Date: Thu, 25 Apr 2002 08:29:09 +0800
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <F222ririOCag4SfKekF00002e54@hotmail.com>
X-OriginalArrivalTime: 25 Apr 2002 00:29:09.0250 (UTC) FILETIME=[371E5E20:01C1EBF0]
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Thanks, taylor.


>From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
>To: "'???'" <juniperfu@hotmail.com>
>CC: megaco@ietf.org
>Subject: RE: [Megaco] RE: about eventbuffer descriptor
>Date: Wed, 24 Apr 2002 08:08:07 -0400
>
>You have to keep four different logical concepts separate in your mind.  
The
>first three are syntactic constructs used in the messaging between the MGC
>and MG.  The fourth exists only in the MG.
>   (1) the Events Descriptor, naming the events for which the MGC wants
>notifications to be generated;
>   (2) the EventBuffer DESCRIPTOR, naming the events the MGC wants 
buffered
>during Lockstep mode while waiting for a new Events descriptor;
>   (3) the ObservedEvents Descriptor, used in the Notify request to report
>observed events to the MGC;
>   (4) the EventBuffer, which, unlike the DESCRIPTORs listed above, is a
>purely logical concept used to describe MG behaviour during event
>processing.
>
>-----Original Message-----
>From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
>Sent: Wednesday, April 24, 2002 4:21 AM
>To: Taylor, Tom-PT [CAR:B800:EXCH]
>Cc: megaco@ietf.org
>Subject: Re: [Megaco] RE: about eventbuffer descriptor
>
>
>     When running in LockStep mode, If MG detected event which exist in
>EventBuffer, It should put the event in the EventBuffer£¬Is it right?
>     If it is right, Then the EventBuffer include requested event and the
>observedevent, and how can i distinguish them?
>
>Mark
>
>
> >From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
> >To: "'???'" <juniperfu@hotmail.com>
> >CC: megaco@ietf.org
> >Subject: [Megaco] RE: about eventbuffer descriptor
> >Date: Tue, 23 Apr 2002 21:33:07 -0400
> >
> >Yes.  When running in LockStep mode the MGC specifies both the Events
> >Descriptor and the EventBuffer descriptor, and either can contain 
multiple
> >events.  The Events Descriptor determines what events are reported, and
>the
> >EventBuffer Descriptor determines what events are saved for processing
> >against the next Events descriptor after an event notification has been
> >sent.
> >
> >-----Original Message-----
> >From: juniperfu@hotmail.com [mailto:juniperfu@hotmail.com]
> >Sent: Tuesday, April 23, 2002 8:41 PM
> >To: Taylor, Tom-PT [CAR:B800:EXCH]
> >Cc: megaco@ietf.org
> >Subject: about eventbuffer descriptor
> >
> >
> >All,
> >    In section 7.1.10 of megaco, there is a description about 
eventbuffer:
> >     'the Eventbuffer descriptor contains a list of events, with their
> >parameters if any, that the MG is requested to detect and buffer when
> >eventbufferControl equals LocaStep'
> >    from the descrition, I think it means the eventbuffer descriptor
>include
> >many request event from MGC and the MG should detect the event by the
> >eventbuffer descriptor if the eventbuffercontrol equals LockStep.Is it
> >right?
> >
> >Mark
> >
> >
> >
> >_________________________________________________________________
> >Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp
> >
> >
> >_______________________________________________
> >Megaco mailing list
> >Megaco@ietf.org
> >https://www1.ietf.org/mailman/listinfo/megaco
>
>
>
>
>_________________________________________________________________
>ÓëÁª»úµÄÅóÓÑ½øÐÐ½»Á÷£¬ÇëÊ¹ÓÃ MSN Messenger:
>http://messenger.microsoft.com/cn
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco




_________________________________________________________________
Ãâ·ÑÏÂÔØ MSN Explorer£ºhttp://explorer.msn.com/lccn/intl.asp


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



From megaco-admin@ietf.org  Thu Apr 25 08:49: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 IAA03917
	for <megaco-archive@odin.ietf.org>; Thu, 25 Apr 2002 08:49:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02322;
	Thu, 25 Apr 2002 08:28:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02293
	for <megaco@optimus.ietf.org>; Thu, 25 Apr 2002 08:28:53 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03260
	for <megaco@ietf.org>; Thu, 25 Apr 2002 08:28:49 -0400 (EDT)
Received: from suman ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GV4IK200.9H4 for
          <megaco@ietf.org>; Thu, 25 Apr 2002 20:26:26 +0800 
Message-ID: <005001c1f0c0$4cad56e0$d5190b0a@huawei.com>
From: "Suman Choudhary" <sumanc@huawei.com>
To: <megaco@ietf.org>
Date: Tue, 30 Apr 2002 20:28:45 -0700
Organization: Huawei Technologies
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_004D_01C1F085.A0348E40"
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
Subject: [Megaco] Query
Sender: megaco-admin@ietf.org
Errors-To: 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_004D_01C1F085.A0348E40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,

When termination goes out of service, MGW will inform MGC
with the following parameters.

Context ID =3D Contexts / Null / All
Termination ID =3D Termination(s)
Service Change Reason =3D Transmission failure / Termination =
malfunctioning /=20
                                        Loss of lower layer connectivity =
/ Termination taken out of service
Service Change Method =3D Graceful / Forced
Is wildcarding of terminations allowed in this transaction. ?

If context ID is ALL, should MGC assume that all terminations in all =
active contexts are out of service ??

What if the context id is NULL ?

Can the MGW send this message even for ephemeral terminations ?

Thanx in advance,

Suman


------=_NextPart_000_004D_01C1F085.A0348E40
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.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#fffbf0>
<DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>When&nbsp;termination goes out of =
service, MGW will=20
inform MGC</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>with the following =
parameters.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Context ID =3D=20
Contexts&nbsp;/&nbsp;Null&nbsp;/&nbsp;All</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Termination ID =3D =
Termination(s)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Service Change Reason =3D =
Transmission&nbsp;failure /=20
Termination&nbsp;malfunctioning / </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
Loss&nbsp;of&nbsp;lower&nbsp;layer&nbsp;connectivity /=20
Termination&nbsp;taken&nbsp;out&nbsp;of&nbsp;service</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Service Change Method =3D=20
Graceful&nbsp;/&nbsp;Forced</FONT></DIV>
<DIV>
<P><STRONG><FONT face=3DArial>Is wildcarding of terminations allowed in =
this=20
transaction. ?</FONT></STRONG></P><FONT face=3DArial>
<P><STRONG><FONT face=3DArial>If context ID is ALL, should MGC assume =
that all=20
terminations in all active contexts are out of service =
??</FONT></STRONG></P>
<P><STRONG>What if the context id is NULL ?</STRONG></P></FONT>
<P><FONT face=3DArial><STRONG>Can&nbsp;the MGW send this message even =
for=20
ephemeral terminations ?</STRONG></FONT></P>
<P>Thanx in advance,</P>
<P>Suman</P></DIV></BODY></HTML>

------=_NextPart_000_004D_01C1F085.A0348E40--


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


From daemon@optimus.ietf.org  Thu Apr 25 08:49: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 IAA03933
	for <megaco-archive@odin.ietf.org>; Thu, 25 Apr 2002 08:49:41 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA03860
	for megaco-archive@odin.ietf.org; Thu, 25 Apr 2002 08:49:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02322;
	Thu, 25 Apr 2002 08:28:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02293
	for <megaco@optimus.ietf.org>; Thu, 25 Apr 2002 08:28:53 -0400 (EDT)
Received: from smtp.huawei.com ([61.144.161.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03260
	for <megaco@ietf.org>; Thu, 25 Apr 2002 08:28:49 -0400 (EDT)
Received: from suman ([172.17.254.1]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GV4IK200.9H4 for
          <megaco@ietf.org>; Thu, 25 Apr 2002 20:26:26 +0800 
Message-ID: <005001c1f0c0$4cad56e0$d5190b0a@huawei.com>
From: "Suman Choudhary" <sumanc@huawei.com>
To: <megaco@ietf.org>
Date: Tue, 30 Apr 2002 20:28:45 -0700
Organization: Huawei Technologies
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_004D_01C1F085.A0348E40"
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
Subject: [Megaco] Query
Sender: megaco-admin@ietf.org
Errors-To: 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_004D_01C1F085.A0348E40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,

When termination goes out of service, MGW will inform MGC
with the following parameters.

Context ID =3D Contexts / Null / All
Termination ID =3D Termination(s)
Service Change Reason =3D Transmission failure / Termination =
malfunctioning /=20
                                        Loss of lower layer connectivity =
/ Termination taken out of service
Service Change Method =3D Graceful / Forced
Is wildcarding of terminations allowed in this transaction. ?

If context ID is ALL, should MGC assume that all terminations in all =
active contexts are out of service ??

What if the context id is NULL ?

Can the MGW send this message even for ephemeral terminations ?

Thanx in advance,

Suman


------=_NextPart_000_004D_01C1F085.A0348E40
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.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#fffbf0>
<DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>When&nbsp;termination goes out of =
service, MGW will=20
inform MGC</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>with the following =
parameters.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Context ID =3D=20
Contexts&nbsp;/&nbsp;Null&nbsp;/&nbsp;All</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Termination ID =3D =
Termination(s)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Service Change Reason =3D =
Transmission&nbsp;failure /=20
Termination&nbsp;malfunctioning / </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
Loss&nbsp;of&nbsp;lower&nbsp;layer&nbsp;connectivity /=20
Termination&nbsp;taken&nbsp;out&nbsp;of&nbsp;service</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Service Change Method =3D=20
Graceful&nbsp;/&nbsp;Forced</FONT></DIV>
<DIV>
<P><STRONG><FONT face=3DArial>Is wildcarding of terminations allowed in =
this=20
transaction. ?</FONT></STRONG></P><FONT face=3DArial>
<P><STRONG><FONT face=3DArial>If context ID is ALL, should MGC assume =
that all=20
terminations in all active contexts are out of service =
??</FONT></STRONG></P>
<P><STRONG>What if the context id is NULL ?</STRONG></P></FONT>
<P><FONT face=3DArial><STRONG>Can&nbsp;the MGW send this message even =
for=20
ephemeral terminations ?</STRONG></FONT></P>
<P>Thanx in advance,</P>
<P>Suman</P></DIV></BODY></HTML>

------=_NextPart_000_004D_01C1F085.A0348E40--


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



From megaco-admin@ietf.org  Thu Apr 25 09:28: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 JAA05155
	for <megaco-archive@odin.ietf.org>; Thu, 25 Apr 2002 09:27:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05357;
	Thu, 25 Apr 2002 09:09:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05329
	for <megaco@optimus.ietf.org>; Thu, 25 Apr 2002 09:09:09 -0400 (EDT)
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 JAA04663
	for <megaco@ietf.org>; Thu, 25 Apr 2002 09:09:01 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3PD8XZ00957
	for <megaco@ietf.org>; Thu, 25 Apr 2002 09:08:33 -0400 (EDT)
Received: from lucent.com (tla.lra.lucent.com [192.11.63.180])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA20549
	for <megaco@ietf.org>; Thu, 25 Apr 2002 09:09:13 -0400 (EDT)
Message-ID: <3CC7FFB4.D1C5B54B@lucent.com>
Date: Thu, 25 Apr 2002 09:08:04 -0400
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>
Content-Type: multipart/mixed;
 boundary="------------4839B9699D1E46BEEDD13333"
Subject: [Megaco] draft-ietf-megaco-r2package
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------4839B9699D1E46BEEDD13333
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

draft-ietf-megaco-r2package-02.txt is a MEGACO workitem but the draft
expired some time ago.  Tom, can you or the authors clarify its future?
Is a new draft planned or is the work with MEGACO being dropped?

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------4839B9699D1E46BEEDD13333
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------4839B9699D1E46BEEDD13333--


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


From daemon@optimus.ietf.org  Thu Apr 25 09:28: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 JAA05218
	for <megaco-archive@odin.ietf.org>; Thu, 25 Apr 2002 09:28:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA06275
	for megaco-archive@odin.ietf.org; Thu, 25 Apr 2002 09:28:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05357;
	Thu, 25 Apr 2002 09:09:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05329
	for <megaco@optimus.ietf.org>; Thu, 25 Apr 2002 09:09:09 -0400 (EDT)
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 JAA04663
	for <megaco@ietf.org>; Thu, 25 Apr 2002 09:09:01 -0400 (EDT)
Received: from teton.ho.lucent.com (h135-112-32-10.lucent.com [135.112.32.10])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3PD8XZ00957
	for <megaco@ietf.org>; Thu, 25 Apr 2002 09:08:33 -0400 (EDT)
Received: from lucent.com (tla.lra.lucent.com [192.11.63.180])
	by teton.ho.lucent.com (8.8.8+Sun/8.8.8) with ESMTP id JAA20549
	for <megaco@ietf.org>; Thu, 25 Apr 2002 09:09:13 -0400 (EDT)
Message-ID: <3CC7FFB4.D1C5B54B@lucent.com>
Date: Thu, 25 Apr 2002 09:08:04 -0400
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>
Content-Type: multipart/mixed;
 boundary="------------4839B9699D1E46BEEDD13333"
Subject: [Megaco] draft-ietf-megaco-r2package
Sender: megaco-admin@ietf.org
Errors-To: 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.
--------------4839B9699D1E46BEEDD13333
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

draft-ietf-megaco-r2package-02.txt is a MEGACO workitem but the draft
expired some time ago.  Tom, can you or the authors clarify its future?
Is a new draft planned or is the work with MEGACO being dropped?

--
-------------------------------------------------------
Terry L Anderson, DMTS                   tla@lucent.com
Lucent Technologies /INS/ Voice over IP Access Networks
Rm 2B-121,   600 Mountain Ave, Murray Hill, NJ 07974
Voice:908 582-7013  FAX:908 582-6226   Org:18E75000000
http://its.lucent.com/~tla  (Lucent internal)
http://www.gti.net/tla
-------------------------------------------------------


--------------4839B9699D1E46BEEDD13333
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:+1.732.949.7016
tel;work:+1.732.949.5628
x-mozilla-html:TRUE
url:http://its.lucent.com/~tla
org:Lucent / Integrated Network Solutions;VoIP Access Networks
adr;quoted-printable:;;Rm 2B-121=0D=0A600 Mountain Ave;Murray Hill;NJ;07974;USA
adr:;;2G-219A, 101 Crawfords Corner Rd, PO Box 3030;Holmdel;NJ;07733-3030;U S
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)
x-mozilla-cpt:;32208
fn:Terry L Anderson
end:vcard

--------------4839B9699D1E46BEEDD13333--


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



From megaco-admin@ietf.org  Thu Apr 25 12: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 MAA26286
	for <megaco-archive@odin.ietf.org>; Thu, 25 Apr 2002 12:27:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15692;
	Thu, 25 Apr 2002 11:44:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA25419
	for <megaco@optimus.ietf.org>; Thu, 25 Apr 2002 07:08:49 -0400 (EDT)
Received: from 1aurora.enabtech ([203.215.160.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01020
	for <megaco@ietf.org>; Thu, 25 Apr 2002 07:08:45 -0400 (EDT)
Received: by 1aurora.enabtech with Internet Mail Service (5.5.2650.21)
	id <JNZ61HK9>; Thu, 25 Apr 2002 17:07:51 +0500
Message-ID: <10C6C1971DA00C4BB87AC0206E3CA3823E8B50@1aurora.enabtech>
From: asrar ashraf <asrar@enabtech.com>
To: megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO
Date: Thu, 25 Apr 2002 17:07:46 +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


hello List!
  Is it protocol compliance requirement that Same sequence as specified in
Madhu-babu's draft, be followed for Creation/Modification of Ephemeral Terms
for 3-Way Calling(Conferencing) OR instead We can use any Sequence remaining
in Limits of Megaco.
  That is instead of
        1)	EphA-PhysA and EphB-PhysB Creation
        2)  At First Flash, EphA(Recv Only), EphC-PhysC Creation and Eph-B
(Modify Remote)
	  3)  At Second Flash,
		i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and Then

		ii)Secondly EphF-PhyB Creation and EphA (Modify-SendRecv).
  Can We Do
	 1)	EphA-PhysA and EphB-PhysB Creation
       2)   At First Flash, not Do EphA(Recv Only), EphC-PhysC Creation and
instead of Eph-B (Modify Remote), Create EphF- 
            PhysB
	 3)   At Second Flash,
		i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and no
need for EphA (Modify-SendRecv). 

Regards
Asrar

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
rezhirpavai@hss.hns.com
Sent: Tuesday, April 23, 2002 9:00 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Hello Madhu,
     By "Service Requirement" I mean the service specifications of these
services. It disallows both these services for single subscriber as the
exchange
(MGC in our case) should know whether the subscriber wants to transfer the
call
or clear the call when the subscriber invoking the conference disconnects
the
call.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/23/2002 03:37:02 AM

To:   R Ezhirpavai/HSS@HSS
cc:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org

Subject:  RE: [Megaco] Conferencing in MEGACO




HI Pavai,
What is this "service requirement" that disallows a user from having both
the call transfer and 3 way calling feature???
Regards
Madhubabu

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Monday, April 22, 2002 11:20 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing
a
hookflash. Only difference is the action that follow subscriber going
on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47 PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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




---
[This E-mail was scanned for viruses and is clean.]







_______________________________________________
Megaco mailing list
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 Apr 25 12:27: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 MAA26296
	for <megaco-archive@odin.ietf.org>; Thu, 25 Apr 2002 12:27:17 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA19939
	for megaco-archive@odin.ietf.org; Thu, 25 Apr 2002 12:27:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15692;
	Thu, 25 Apr 2002 11:44:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA25419
	for <megaco@optimus.ietf.org>; Thu, 25 Apr 2002 07:08:49 -0400 (EDT)
Received: from 1aurora.enabtech ([203.215.160.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01020
	for <megaco@ietf.org>; Thu, 25 Apr 2002 07:08:45 -0400 (EDT)
Received: by 1aurora.enabtech with Internet Mail Service (5.5.2650.21)
	id <JNZ61HK9>; Thu, 25 Apr 2002 17:07:51 +0500
Message-ID: <10C6C1971DA00C4BB87AC0206E3CA3823E8B50@1aurora.enabtech>
From: asrar ashraf <asrar@enabtech.com>
To: megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO
Date: Thu, 25 Apr 2002 17:07:46 +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


hello List!
  Is it protocol compliance requirement that Same sequence as specified in
Madhu-babu's draft, be followed for Creation/Modification of Ephemeral Terms
for 3-Way Calling(Conferencing) OR instead We can use any Sequence remaining
in Limits of Megaco.
  That is instead of
        1)	EphA-PhysA and EphB-PhysB Creation
        2)  At First Flash, EphA(Recv Only), EphC-PhysC Creation and Eph-B
(Modify Remote)
	  3)  At Second Flash,
		i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and Then

		ii)Secondly EphF-PhyB Creation and EphA (Modify-SendRecv).
  Can We Do
	 1)	EphA-PhysA and EphB-PhysB Creation
       2)   At First Flash, not Do EphA(Recv Only), EphC-PhysC Creation and
instead of Eph-B (Modify Remote), Create EphF- 
            PhysB
	 3)   At Second Flash,
		i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and no
need for EphA (Modify-SendRecv). 

Regards
Asrar

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
rezhirpavai@hss.hns.com
Sent: Tuesday, April 23, 2002 9:00 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Hello Madhu,
     By "Service Requirement" I mean the service specifications of these
services. It disallows both these services for single subscriber as the
exchange
(MGC in our case) should know whether the subscriber wants to transfer the
call
or clear the call when the subscriber invoking the conference disconnects
the
call.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/23/2002 03:37:02 AM

To:   R Ezhirpavai/HSS@HSS
cc:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org

Subject:  RE: [Megaco] Conferencing in MEGACO




HI Pavai,
What is this "service requirement" that disallows a user from having both
the call transfer and 3 way calling feature???
Regards
Madhubabu

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Monday, April 22, 2002 11:20 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing
a
hookflash. Only difference is the action that follow subscriber going
on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47 PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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




---
[This E-mail was scanned for viruses and is clean.]







_______________________________________________
Megaco mailing list
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 Apr 25 14: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 OAA00038
	for <megaco-archive@odin.ietf.org>; Thu, 25 Apr 2002 14:07:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26054;
	Thu, 25 Apr 2002 13:42:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26025
	for <megaco@optimus.ietf.org>; Thu, 25 Apr 2002 13:42:12 -0400 (EDT)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28956
	for <megaco@ietf.org>; Thu, 25 Apr 2002 13:42:09 -0400 (EDT)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AIA71233;
	Thu, 25 Apr 2002 13:41:05 -0400 (EDT)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'asrar ashraf'" <asrar@enabtech.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Conferencing in MEGACO
Date: Thu, 25 Apr 2002 13:34:20 -0400
Message-ID: <060201c1ec7f$6fae2510$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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <10C6C1971DA00C4BB87AC0206E3CA3823E8B50@1aurora.enabtech>
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 Asrar,All,
The call flow draft is to illustrate sample messages between MGC and MG for
different call scenarios. There is no requirement that the same sequence
need to be followed.

Regards
Madhubabu Brahmanapally.


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
asrar ashraf
Sent: Thursday, April 25, 2002 8:08 AM
To: megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO



hello List!
  Is it protocol compliance requirement that Same sequence as specified in
Madhu-babu's draft, be followed for Creation/Modification of Ephemeral Terms
for 3-Way Calling(Conferencing) OR instead We can use any Sequence remaining
in Limits of Megaco.
  That is instead of
        1)	EphA-PhysA and EphB-PhysB Creation
        2)  At First Flash, EphA(Recv Only), EphC-PhysC Creation and Eph-B
(Modify Remote)
	  3)  At Second Flash,
		i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and Then

		ii)Secondly EphF-PhyB Creation and EphA (Modify-SendRecv).
  Can We Do
	 1)	EphA-PhysA and EphB-PhysB Creation
       2)   At First Flash, not Do EphA(Recv Only), EphC-PhysC Creation and
instead of Eph-B (Modify Remote), Create EphF-
            PhysB
	 3)   At Second Flash,
		i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and no
need for EphA (Modify-SendRecv).

Regards
Asrar

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
rezhirpavai@hss.hns.com
Sent: Tuesday, April 23, 2002 9:00 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Hello Madhu,
     By "Service Requirement" I mean the service specifications of these
services. It disallows both these services for single subscriber as the
exchange
(MGC in our case) should know whether the subscriber wants to transfer the
call
or clear the call when the subscriber invoking the conference disconnects
the
call.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/23/2002 03:37:02 AM

To:   R Ezhirpavai/HSS@HSS
cc:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org

Subject:  RE: [Megaco] Conferencing in MEGACO




HI Pavai,
What is this "service requirement" that disallows a user from having both
the call transfer and 3 way calling feature???
Regards
Madhubabu

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Monday, April 22, 2002 11:20 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing
a
hookflash. Only difference is the action that follow subscriber going
on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47 PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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




---
[This E-mail was scanned for viruses and is clean.]







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


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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


From daemon@optimus.ietf.org  Thu Apr 25 14: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 OAA00051
	for <megaco-archive@odin.ietf.org>; Thu, 25 Apr 2002 14:07:00 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA28434
	for megaco-archive@odin.ietf.org; Thu, 25 Apr 2002 14:07:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26054;
	Thu, 25 Apr 2002 13:42:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26025
	for <megaco@optimus.ietf.org>; Thu, 25 Apr 2002 13:42:12 -0400 (EDT)
Received: from muninn.ctccom.net (Muninn.CTCCom.net [207.190.194.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28956
	for <megaco@ietf.org>; Thu, 25 Apr 2002 13:42:09 -0400 (EDT)
Received: from MBRAHMANAPALLY ([64.69.123.121])
	by muninn.ctccom.net (Mirapoint)
	with ESMTP id AIA71233;
	Thu, 25 Apr 2002 13:41:05 -0400 (EDT)
From: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
To: "'asrar ashraf'" <asrar@enabtech.com>, <megaco@ietf.org>
Subject: RE: [Megaco] Conferencing in MEGACO
Date: Thu, 25 Apr 2002 13:34:20 -0400
Message-ID: <060201c1ec7f$6fae2510$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)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <10C6C1971DA00C4BB87AC0206E3CA3823E8B50@1aurora.enabtech>
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 Asrar,All,
The call flow draft is to illustrate sample messages between MGC and MG for
different call scenarios. There is no requirement that the same sequence
need to be followed.

Regards
Madhubabu Brahmanapally.


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
asrar ashraf
Sent: Thursday, April 25, 2002 8:08 AM
To: megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO



hello List!
  Is it protocol compliance requirement that Same sequence as specified in
Madhu-babu's draft, be followed for Creation/Modification of Ephemeral Terms
for 3-Way Calling(Conferencing) OR instead We can use any Sequence remaining
in Limits of Megaco.
  That is instead of
        1)	EphA-PhysA and EphB-PhysB Creation
        2)  At First Flash, EphA(Recv Only), EphC-PhysC Creation and Eph-B
(Modify Remote)
	  3)  At Second Flash,
		i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and Then

		ii)Secondly EphF-PhyB Creation and EphA (Modify-SendRecv).
  Can We Do
	 1)	EphA-PhysA and EphB-PhysB Creation
       2)   At First Flash, not Do EphA(Recv Only), EphC-PhysC Creation and
instead of Eph-B (Modify Remote), Create EphF-
            PhysB
	 3)   At Second Flash,
		i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and no
need for EphA (Modify-SendRecv).

Regards
Asrar

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
rezhirpavai@hss.hns.com
Sent: Tuesday, April 23, 2002 9:00 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Hello Madhu,
     By "Service Requirement" I mean the service specifications of these
services. It disallows both these services for single subscriber as the
exchange
(MGC in our case) should know whether the subscriber wants to transfer the
call
or clear the call when the subscriber invoking the conference disconnects
the
call.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/23/2002 03:37:02 AM

To:   R Ezhirpavai/HSS@HSS
cc:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org

Subject:  RE: [Megaco] Conferencing in MEGACO




HI Pavai,
What is this "service requirement" that disallows a user from having both
the call transfer and 3 way calling feature???
Regards
Madhubabu

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Monday, April 22, 2002 11:20 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing
a
hookflash. Only difference is the action that follow subscriber going
on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47 PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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




---
[This E-mail was scanned for viruses and is clean.]







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


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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



From megaco-admin@ietf.org  Thu Apr 25 14:30: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 OAA01173
	for <megaco-archive@odin.ietf.org>; Thu, 25 Apr 2002 14:30:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28939;
	Thu, 25 Apr 2002 14:11:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28912
	for <megaco@optimus.ietf.org>; Thu, 25 Apr 2002 14:11:10 -0400 (EDT)
Received: from gateus.nmss.com (gateus.nmss.com [208.236.204.65])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA00303
	for <megaco@ietf.org>; Thu, 25 Apr 2002 14:11:06 -0400 (EDT)
From: David_Franklin@nmss.com
Received: from NAMASMTP01 by gateus.nmss.com
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 25 Apr 2002 13:07:09 UT
Subject: RE: [Megaco] Conferencing in MEGACO
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
Cc: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF4C6C3FC2.128B13E8-ON85256BA6.0063074B@nmss.com>
Date: Thu, 25 Apr 2002 14:12:18 -0400
X-MIMETrack: Serialize by Router on NAMASMTP01/Natural MicroSystems/US(Release 5.0.10 |March
 22, 2002) at 04/25/2002 02:11:21 PM
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



And in fact you wouldn't necessarily want to do it that way for large
conferences. The number of terminations per context and the number of media
streams connecting the participants both go up as the square of the number
of participants. That is, (n^2 + n)/2, for n participants. Of course one
could argue that voice activity detection would mitigate the need for a lot
of bandwidth, statistically speaking.

However, the call flows for conferencing do work well for completely
distributed conferencing with a small number of participants.

- Dave

David Franklin
Principal Software Engineer
NMS Communications
david_franklin@nmss.com
tel. +1.508.271.1038




                                                                                             
                      "Madhu Babu                                                            
                      Brahmanapally"           To:       "'asrar ashraf'"                    
                      <madhubabu@kenete         <asrar@enabtech.com>, <megaco@ietf.org>      
                      c.com>                   cc:                                           
                      Sent by:                 Subject:  RE: [Megaco] Conferencing in MEGACO 
                      megaco-admin@ietf                                                      
                      .org                                                                   
                                                                                             
                                                                                             
                      04/25/02 01:34 PM                                                      
                                                                                             
                                                                                             




HI Asrar,All,
The call flow draft is to illustrate sample messages between MGC and MG for
different call scenarios. There is no requirement that the same sequence
need to be followed.

Regards
Madhubabu Brahmanapally.


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
asrar ashraf
Sent: Thursday, April 25, 2002 8:08 AM
To: megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO



hello List!
  Is it protocol compliance requirement that Same sequence as specified in
Madhu-babu's draft, be followed for Creation/Modification of Ephemeral
Terms
for 3-Way Calling(Conferencing) OR instead We can use any Sequence
remaining
in Limits of Megaco.
  That is instead of
        1)  EphA-PhysA and EphB-PhysB Creation
        2)  At First Flash, EphA(Recv Only), EphC-PhysC Creation and Eph-B
(Modify Remote)
   3)  At Second Flash,
  i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and Then

  ii)Secondly EphF-PhyB Creation and EphA (Modify-SendRecv).
  Can We Do
  1)  EphA-PhysA and EphB-PhysB Creation
       2)   At First Flash, not Do EphA(Recv Only), EphC-PhysC Creation and
instead of Eph-B (Modify Remote), Create EphF-
            PhysB
  3)   At Second Flash,
  i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and no
need for EphA (Modify-SendRecv).

Regards
Asrar

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
rezhirpavai@hss.hns.com
Sent: Tuesday, April 23, 2002 9:00 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Hello Madhu,
     By "Service Requirement" I mean the service specifications of these
services. It disallows both these services for single subscriber as the
exchange
(MGC in our case) should know whether the subscriber wants to transfer the
call
or clear the call when the subscriber invoking the conference disconnects
the
call.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/23/2002 03:37:02
AM

To:   R Ezhirpavai/HSS@HSS
cc:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org

Subject:  RE: [Megaco] Conferencing in MEGACO




HI Pavai,
What is this "service requirement" that disallows a user from having both
the call transfer and 3 way calling feature???
Regards
Madhubabu

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Monday, April 22, 2002 11:20 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing
a
hookflash. Only difference is the action that follow subscriber going
on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47
PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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




---
[This E-mail was scanned for viruses and is clean.]







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


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



_______________________________________________
Megaco mailing list
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 Apr 25 14:30: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 OAA01184
	for <megaco-archive@odin.ietf.org>; Thu, 25 Apr 2002 14:30:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA00428
	for megaco-archive@odin.ietf.org; Thu, 25 Apr 2002 14:30:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28939;
	Thu, 25 Apr 2002 14:11:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28912
	for <megaco@optimus.ietf.org>; Thu, 25 Apr 2002 14:11:10 -0400 (EDT)
Received: from gateus.nmss.com (gateus.nmss.com [208.236.204.65])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA00303
	for <megaco@ietf.org>; Thu, 25 Apr 2002 14:11:06 -0400 (EDT)
From: David_Franklin@nmss.com
Received: from NAMASMTP01 by gateus.nmss.com
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 25 Apr 2002 13:07:09 UT
Subject: RE: [Megaco] Conferencing in MEGACO
To: "Madhu Babu Brahmanapally" <madhubabu@kenetec.com>
Cc: megaco@ietf.org
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF4C6C3FC2.128B13E8-ON85256BA6.0063074B@nmss.com>
Date: Thu, 25 Apr 2002 14:12:18 -0400
X-MIMETrack: Serialize by Router on NAMASMTP01/Natural MicroSystems/US(Release 5.0.10 |March
 22, 2002) at 04/25/2002 02:11:21 PM
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



And in fact you wouldn't necessarily want to do it that way for large
conferences. The number of terminations per context and the number of media
streams connecting the participants both go up as the square of the number
of participants. That is, (n^2 + n)/2, for n participants. Of course one
could argue that voice activity detection would mitigate the need for a lot
of bandwidth, statistically speaking.

However, the call flows for conferencing do work well for completely
distributed conferencing with a small number of participants.

- Dave

David Franklin
Principal Software Engineer
NMS Communications
david_franklin@nmss.com
tel. +1.508.271.1038




                                                                                             
                      "Madhu Babu                                                            
                      Brahmanapally"           To:       "'asrar ashraf'"                    
                      <madhubabu@kenete         <asrar@enabtech.com>, <megaco@ietf.org>      
                      c.com>                   cc:                                           
                      Sent by:                 Subject:  RE: [Megaco] Conferencing in MEGACO 
                      megaco-admin@ietf                                                      
                      .org                                                                   
                                                                                             
                                                                                             
                      04/25/02 01:34 PM                                                      
                                                                                             
                                                                                             




HI Asrar,All,
The call flow draft is to illustrate sample messages between MGC and MG for
different call scenarios. There is no requirement that the same sequence
need to be followed.

Regards
Madhubabu Brahmanapally.


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
asrar ashraf
Sent: Thursday, April 25, 2002 8:08 AM
To: megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO



hello List!
  Is it protocol compliance requirement that Same sequence as specified in
Madhu-babu's draft, be followed for Creation/Modification of Ephemeral
Terms
for 3-Way Calling(Conferencing) OR instead We can use any Sequence
remaining
in Limits of Megaco.
  That is instead of
        1)  EphA-PhysA and EphB-PhysB Creation
        2)  At First Flash, EphA(Recv Only), EphC-PhysC Creation and Eph-B
(Modify Remote)
   3)  At Second Flash,
  i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and Then

  ii)Secondly EphF-PhyB Creation and EphA (Modify-SendRecv).
  Can We Do
  1)  EphA-PhysA and EphB-PhysB Creation
       2)   At First Flash, not Do EphA(Recv Only), EphC-PhysC Creation and
instead of Eph-B (Modify Remote), Create EphF-
            PhysB
  3)   At Second Flash,
  i) Fisrt EphD-PhyC creation and EphE-PhyA creation  and no
need for EphA (Modify-SendRecv).

Regards
Asrar

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
rezhirpavai@hss.hns.com
Sent: Tuesday, April 23, 2002 9:00 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Hello Madhu,
     By "Service Requirement" I mean the service specifications of these
services. It disallows both these services for single subscriber as the
exchange
(MGC in our case) should know whether the subscriber wants to transfer the
call
or clear the call when the subscriber invoking the conference disconnects
the
call.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/23/2002 03:37:02
AM

To:   R Ezhirpavai/HSS@HSS
cc:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org

Subject:  RE: [Megaco] Conferencing in MEGACO




HI Pavai,
What is this "service requirement" that disallows a user from having both
the call transfer and 3 way calling feature???
Regards
Madhubabu

-----Original Message-----
From: rezhirpavai@hss.hns.com [mailto:rezhirpavai@hss.hns.com]
Sent: Monday, April 22, 2002 11:20 AM
To: Madhu Babu Brahmanapally
Cc: 'Fhuval Hittay'; megaco@ietf.org
Subject: RE: [Megaco] Conferencing in MEGACO




Madhu,
     I beg to differ that MGC would not be aware of it in first hookflash.
According to the service requirement, a subscriber can have either "call
transfer" facility or "Three way calling" facility. Even in call transfer
service, the subscriber can bring the other two into conference after doing
a
hookflash. Only difference is the action that follow subscriber going
on-hook.
In one case the call is transfered and in other the call is released.

Regards,
- R. Ezhirpavai





"Madhu Babu Brahmanapally" <madhubabu@kenetec.com> on 04/22/2002 08:17:47
PM

To:   "'Fhuval Hittay'" <fhuval@rambler.ru>, megaco@ietf.org
cc:    (bcc: R Ezhirpavai/HSS)

Subject:  RE: [Megaco] Conferencing in MEGACO




hi Fhuval,
Its true that "flash hook" is the main button or trigger for both "call
transfer" and "conference". Infact there is no difference till party B
getting "connected" to party C. After that based on the User B action the
scenario changes. If the UserB goes onhook, the MGC connects party A and
Party C thus enabling the call transfer. If UserB does a "flash hook", the
MGC connects all the three parties. Even the MGC may not be aware whether
the first "flash hook" is for call transfer of conference.
Regards
Madhubabu.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Fhuval Hittay
Sent: Monday, April 22, 2002 5:06 AM
To: megaco@ietf.org
Subject: [Megaco] Conferencing in MEGACO



 Could anyone, please, clarify conferencing operations described in
"draft-ietf-megaco-callflows-00.txt" ? In that document, "FlashHook" is the
main button to form a conference, but how MGC could know, that "FlashHook"
mean
"form a conference", not a "call transfer" or something else?
 And if in a conference there are more than three participants, what is the
main actions must perform every participant to enter the conference?
----
  http://www.rambler.ru

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



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




---
[This E-mail was scanned for viruses and is clean.]







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


_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
---
[This E-mail was scanned for viruses and is clean.]



_______________________________________________
Megaco mailing list
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 Apr 26 00:59: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 AAA16403
	for <megaco-archive@odin.ietf.org>; Fri, 26 Apr 2002 00:59:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04144;
	Fri, 26 Apr 2002 00:34:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04113
	for <megaco@ns.ietf.org>; Fri, 26 Apr 2002 00:34:11 -0400 (EDT)
Received: from telesoft.indts.com (IDENT:root@[164.164.71.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16059
	for <megaco@ietf.org>; Fri, 26 Apr 2002 00:34:01 -0400 (EDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id KAA12844
	for <megaco@ietf.org>; Fri, 26 Apr 2002 10:37:47 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <GWSJCM40>; Fri, 26 Apr 2002 10:08:29 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337263B3C5@INDTS_FS>
From: Anil Jangam <anilj@indts.com>
To: megaco@ietf.org
Date: Fri, 26 Apr 2002 10:08:22 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Command returning the context.
Sender: megaco-admin@ietf.org
Errors-To: 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,

How it is possible to retrieve the context ID given the Termination ID?

Thanks in advance,
/anil.

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


From daemon@ns.ietf.org  Fri Apr 26 00:59: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 AAA16417
	for <megaco-archive@odin.ietf.org>; Fri, 26 Apr 2002 00:59:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA04777
	for megaco-archive@odin.ietf.org; Fri, 26 Apr 2002 01:00:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04144;
	Fri, 26 Apr 2002 00:34:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04113
	for <megaco@ns.ietf.org>; Fri, 26 Apr 2002 00:34:11 -0400 (EDT)
Received: from telesoft.indts.com (IDENT:root@[164.164.71.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16059
	for <megaco@ietf.org>; Fri, 26 Apr 2002 00:34:01 -0400 (EDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id KAA12844
	for <megaco@ietf.org>; Fri, 26 Apr 2002 10:37:47 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <GWSJCM40>; Fri, 26 Apr 2002 10:08:29 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337263B3C5@INDTS_FS>
From: Anil Jangam <anilj@indts.com>
To: megaco@ietf.org
Date: Fri, 26 Apr 2002 10:08:22 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Command returning the context.
Sender: megaco-admin@ietf.org
Errors-To: 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,

How it is possible to retrieve the context ID given the Termination ID?

Thanks in advance,
/anil.

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



From megaco-admin@ietf.org  Fri Apr 26 01: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 BAA16654
	for <megaco-archive@odin.ietf.org>; Fri, 26 Apr 2002 01:14:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04529;
	Fri, 26 Apr 2002 00:48:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04499
	for <megaco@ns.ietf.org>; Fri, 26 Apr 2002 00:48:24 -0400 (EDT)
Received: from blaze.hcltech.com ([203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16210
	for <megaco@ietf.org>; Fri, 26 Apr 2002 00:48:20 -0400 (EDT)
Received: from rajesh.netlab.hcltech.com (rajesh.hclt-guindy.co.in [192.168.201.84])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id KAA18678;
	Fri, 26 Apr 2002 10:10:09 +0530
Message-Id: <4.3.2.7.1.20020426100051.00c263a0@192.168.201.1>
X-Sender: nrajesh@192.168.201.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 26 Apr 2002 10:04:19 +0530
To: Anil Jangam <anilj@indts.com>, megaco@ietf.org
From: Rajesh N <nrajesh@netlab.hcltech.com>
Subject: Re: [Megaco] Command returning the context.
In-Reply-To: <F73B646FCC01D5118F530002B32C337263B3C5@INDTS_FS>
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

Hi,

An auditvalue command from MGC with context id as 'ALL' and the specific 
termination ID should return the context ID in which the termination 
currently exists.

More on this on the section describing Auditvalue command in the draft.


At 10:08 AM 4/26/02 +0530, Anil Jangam wrote:
>Hi,
>
>How it is possible to retrieve the context ID given the Termination ID?
>
>Thanks in advance,
>/anil.
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco

Regards,
Rajesh N


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


From daemon@ns.ietf.org  Fri Apr 26 01:14: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 BAA16667
	for <megaco-archive@odin.ietf.org>; Fri, 26 Apr 2002 01:14:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA12260
	for megaco-archive@odin.ietf.org; Fri, 26 Apr 2002 01:14:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04529;
	Fri, 26 Apr 2002 00:48:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04499
	for <megaco@ns.ietf.org>; Fri, 26 Apr 2002 00:48:24 -0400 (EDT)
Received: from blaze.hcltech.com ([203.199.199.225])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16210
	for <megaco@ietf.org>; Fri, 26 Apr 2002 00:48:20 -0400 (EDT)
Received: from rajesh.netlab.hcltech.com (rajesh.hclt-guindy.co.in [192.168.201.84])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id KAA18678;
	Fri, 26 Apr 2002 10:10:09 +0530
Message-Id: <4.3.2.7.1.20020426100051.00c263a0@192.168.201.1>
X-Sender: nrajesh@192.168.201.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 26 Apr 2002 10:04:19 +0530
To: Anil Jangam <anilj@indts.com>, megaco@ietf.org
From: Rajesh N <nrajesh@netlab.hcltech.com>
Subject: Re: [Megaco] Command returning the context.
In-Reply-To: <F73B646FCC01D5118F530002B32C337263B3C5@INDTS_FS>
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

Hi,

An auditvalue command from MGC with context id as 'ALL' and the specific 
termination ID should return the context ID in which the termination 
currently exists.

More on this on the section describing Auditvalue command in the draft.


At 10:08 AM 4/26/02 +0530, Anil Jangam wrote:
>Hi,
>
>How it is possible to retrieve the context ID given the Termination ID?
>
>Thanks in advance,
>/anil.
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco

Regards,
Rajesh N


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



From megaco-admin@ietf.org  Fri Apr 26 10:15: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 KAA05221
	for <megaco-archive@odin.ietf.org>; Fri, 26 Apr 2002 10:15:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12814;
	Fri, 26 Apr 2002 09:48:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12783
	for <megaco@optimus.ietf.org>; Fri, 26 Apr 2002 09:48:22 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04252
	for <megaco@ietf.org>; Fri, 26 Apr 2002 09:48:14 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3QDlZb16497;
	Fri, 26 Apr 2002 09:47:35 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <J4NBMLSP>; Fri, 26 Apr 2002 09:47:36 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A38B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Suman Choudhary'" <sumanc@huawei.com>, megaco@ietf.org
Subject: RE: [Megaco] Query
Date: Fri, 26 Apr 2002 09:47:34 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


Hi.  Answers below, marked with [PTT].

-----Original Message-----
From: Suman Choudhary [mailto:sumanc@huawei.com]
Sent: Tuesday, April 30, 2002 11:29 PM
To: megaco@ietf.org
Subject: [Megaco] Query


Hi All,

When termination goes out of service, MGW will inform MGC
with the following parameters.
 
Context ID = Contexts / Null / All
Termination ID = Termination(s)
Service Change Reason = Transmission failure / Termination malfunctioning / 
                                        Loss of lower layer connectivity /
Termination taken out of service
Service Change Method = Graceful / Forced
Is wildcarding of terminations allowed in this transaction. ?

[PTT] Yes, and it will often be needed.

If context ID is ALL, should MGC assume that all terminations in all active
contexts are out of service ??

[PTT] Only if the terminationID is also ALL.  Otherwise it would be the
termination(s) designated by the terminationID, provided they are in active
contexts.  Other people may want to comment on this interpretation.

What if the context id is NULL ?

[PTT] It is valid to report that a termination in the NULL context is out of
service.  Where we get problems is when you are not sure whether the
termination is in the acti
 
Can the MGW send this message even for ephemeral terminations ?

[PTT] Yes, it can.  There has been some debate over what this means.  At a
minimum, it means that no traffic is flowing through the termination.
Probably the MGC should subtract it and, if possible, create a replacement.

Thanx in advance,
Suman

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


From daemon@optimus.ietf.org  Fri Apr 26 10:15: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 KAA05231
	for <megaco-archive@odin.ietf.org>; Fri, 26 Apr 2002 10:15:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA14793
	for megaco-archive@odin.ietf.org; Fri, 26 Apr 2002 10:15:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12814;
	Fri, 26 Apr 2002 09:48:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12783
	for <megaco@optimus.ietf.org>; Fri, 26 Apr 2002 09:48:22 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04252
	for <megaco@ietf.org>; Fri, 26 Apr 2002 09:48:14 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3QDlZb16497;
	Fri, 26 Apr 2002 09:47:35 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <J4NBMLSP>; Fri, 26 Apr 2002 09:47:36 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A38B@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Suman Choudhary'" <sumanc@huawei.com>, megaco@ietf.org
Subject: RE: [Megaco] Query
Date: Fri, 26 Apr 2002 09:47:34 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


Hi.  Answers below, marked with [PTT].

-----Original Message-----
From: Suman Choudhary [mailto:sumanc@huawei.com]
Sent: Tuesday, April 30, 2002 11:29 PM
To: megaco@ietf.org
Subject: [Megaco] Query


Hi All,

When termination goes out of service, MGW will inform MGC
with the following parameters.
 
Context ID = Contexts / Null / All
Termination ID = Termination(s)
Service Change Reason = Transmission failure / Termination malfunctioning / 
                                        Loss of lower layer connectivity /
Termination taken out of service
Service Change Method = Graceful / Forced
Is wildcarding of terminations allowed in this transaction. ?

[PTT] Yes, and it will often be needed.

If context ID is ALL, should MGC assume that all terminations in all active
contexts are out of service ??

[PTT] Only if the terminationID is also ALL.  Otherwise it would be the
termination(s) designated by the terminationID, provided they are in active
contexts.  Other people may want to comment on this interpretation.

What if the context id is NULL ?

[PTT] It is valid to report that a termination in the NULL context is out of
service.  Where we get problems is when you are not sure whether the
termination is in the acti
 
Can the MGW send this message even for ephemeral terminations ?

[PTT] Yes, it can.  There has been some debate over what this means.  At a
minimum, it means that no traffic is flowing through the termination.
Probably the MGC should subtract it and, if possible, create a replacement.

Thanx in advance,
Suman

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



From megaco-admin@ietf.org  Mon Apr 29 03:53: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 DAA09018
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 03:53:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00514;
	Mon, 29 Apr 2002 03:18:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00471
	for <megaco@ns.ietf.org>; Mon, 29 Apr 2002 03:18:28 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05947
	for <megaco@ietf.org>; Mon, 29 Apr 2002 03:18:23 -0400 (EDT)
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 g3T7Hiu12347
	for <megaco@ietf.org>; Mon, 29 Apr 2002 09:17:44 +0200 (MEST)
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 JAA10631
	for <megaco@ietf.org>; Mon, 29 Apr 2002 09:17:30 +0200 (MET DST)
Message-ID: <3CCCF196.FCDBE042@alcatel.es>
Date: Mon, 29 Apr 2002 09:09:11 +0200
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 <megaco@ietf.org>
Subject: [Megaco] Version 1 and 1.0
Content-Type: multipart/alternative;
 boundary="------------95E16A5F1308998FA9F7E6BC"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

Hi all,

Can we consider that version 1 is the same that version 1.0?
(for the negotiation in the ServiceChange)

Regards
Fernando


--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



--------------95E16A5F1308998FA9F7E6BC
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>Can we consider that version 1 is the same that version 1.0?
<br>(for the negotiation in the ServiceChange)
<p>Regards
<br>Fernando
<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>

--------------95E16A5F1308998FA9F7E6BC--


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


From daemon@ns.ietf.org  Mon Apr 29 03:53: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 DAA09027
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 03:53:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA02340
	for megaco-archive@odin.ietf.org; Mon, 29 Apr 2002 03:53:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00514;
	Mon, 29 Apr 2002 03:18:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA00471
	for <megaco@ns.ietf.org>; Mon, 29 Apr 2002 03:18:28 -0400 (EDT)
Received: from sess01.rdp.asi.alcatel.es (sess01.rdp.asi.alcatel.es [159.23.144.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05947
	for <megaco@ietf.org>; Mon, 29 Apr 2002 03:18:23 -0400 (EDT)
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 g3T7Hiu12347
	for <megaco@ietf.org>; Mon, 29 Apr 2002 09:17:44 +0200 (MEST)
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 JAA10631
	for <megaco@ietf.org>; Mon, 29 Apr 2002 09:17:30 +0200 (MET DST)
Message-ID: <3CCCF196.FCDBE042@alcatel.es>
Date: Mon, 29 Apr 2002 09:09:11 +0200
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 <megaco@ietf.org>
Subject: [Megaco] Version 1 and 1.0
Content-Type: multipart/alternative;
 boundary="------------95E16A5F1308998FA9F7E6BC"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


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

Hi all,

Can we consider that version 1 is the same that version 1.0?
(for the negotiation in the ServiceChange)

Regards
Fernando


--
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL



--------------95E16A5F1308998FA9F7E6BC
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>Can we consider that version 1 is the same that version 1.0?
<br>(for the negotiation in the ServiceChange)
<p>Regards
<br>Fernando
<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>

--------------95E16A5F1308998FA9F7E6BC--


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



From megaco-admin@ietf.org  Mon Apr 29 04:18: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 EAA10909
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 04:18:25 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA02301;
	Mon, 29 Apr 2002 03:52:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA02270
	for <megaco@ns.ietf.org>; Mon, 29 Apr 2002 03:52:42 -0400 (EDT)
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 DAA08995
	for <megaco@ietf.org>; Mon, 29 Apr 2002 03:52:39 -0400 (EDT)
Received: through eSafe SMTP Relay 1019111027; Mon Apr 29 10:51:53 2002
Received: by EXCHANGE with Internet Mail Service (5.5.2653.19)
	id <2WRMG2FQ>; Mon, 29 Apr 2002 10:50:11 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF01BF66F3@EXCHANGE>
From: Raphael Tryster <raphael@tdsoft.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Mon, 29 Apr 2002 10:50:10 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1EF5A.DEED6700"
Subject: [Megaco] reply to sender of 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

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_01C1EF5A.DEED6700
Content-Type: text/plain;
	charset="iso-8859-1"

I have seen a number of discussions in the archive about the following
statement:

"Responses must be sent to the address and port from which the corresponding
commands were sent".

The discussions relate mostly to failover and handover situations, but I
could not find any discussion of what happens when a rogue MGC sends a
command to an MG with which it has not established a control association.
One rule that may be relevant here is:

"It is possible that the reply to a ServiceChange with Restart will be lost,
and a command will be received by the MG prior to the receipt of the
ServiceChange response.  The MG shall issue error 505 - Command Received
before Restart Response".

Does the MG send error 505 if it has not received a restart response from
the SENDING MGC, or from ANY MGC?  If the answer is ANY MGC, how does the MG
protect itself from being sent commands by unauthorized entities?


Raphael Tryster

------_=_NextPart_001_01C1EF5A.DEED6700
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>reply to sender of command</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have seen a number of discussions in t=
he archive about the following statement:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">"</FONT><FONT SIZE=3D2 FACE=3D"Arial">Re=
sponses</FONT><FONT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D=
"Arial">must be sent to the address and port from which the corresponding=
</FONT><FONT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial=
">commands were sent</FONT><FONT SIZE=3D2 FACE=3D"Arial">"</FONT><FONT SI=
ZE=3D2 FACE=3D"Arial">.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The discussions relate mostly to failove=
r and handover situations, but I could not find any discussion of what ha=
ppens when a rogue MGC sends a command to an MG with which it has not est=
ablished a control association.&nbsp;&nbsp; One rule that may be relevant=
 here is:</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">"</FONT><FONT SIZE=3D2 FACE=3D"Arial">It=
 is possible that the reply to a ServiceChange with Restart will be</FONT=
><FONT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">lost=
, and a command will be received by the MG prior to the receipt</FONT><FO=
NT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">of the S=
erviceChange response.&nbsp; The MG shall issue error 505 -</FONT><FONT S=
IZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Command Rece=
ived before Restart Response</FONT><FONT SIZE=3D2 FACE=3D"Arial">"</FONT>=
<FONT SIZE=3D2 FACE=3D"Arial">.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Does the MG send error 505 if it has not=
 received a restart response from the SENDING MGC, or from ANY MGC?&nbsp;=
 If the answer is ANY MGC, how does the MG protect itself from being sent=
 commands by unauthorized entities?</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1EF5A.DEED6700--

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


From daemon@ns.ietf.org  Mon Apr 29 04:18: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 EAA10920
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 04:18:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA03864
	for megaco-archive@odin.ietf.org; Mon, 29 Apr 2002 04:18:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA02301;
	Mon, 29 Apr 2002 03:52:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA02270
	for <megaco@ns.ietf.org>; Mon, 29 Apr 2002 03:52:42 -0400 (EDT)
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 DAA08995
	for <megaco@ietf.org>; Mon, 29 Apr 2002 03:52:39 -0400 (EDT)
Received: through eSafe SMTP Relay 1019111027; Mon Apr 29 10:51:53 2002
Received: by EXCHANGE with Internet Mail Service (5.5.2653.19)
	id <2WRMG2FQ>; Mon, 29 Apr 2002 10:50:11 +0200
Message-ID: <B1584457374ED211B7A90008C7242DEF01BF66F3@EXCHANGE>
From: Raphael Tryster <raphael@tdsoft.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Mon, 29 Apr 2002 10:50:10 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1EF5A.DEED6700"
Subject: [Megaco] reply to sender of 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

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_01C1EF5A.DEED6700
Content-Type: text/plain;
	charset="iso-8859-1"

I have seen a number of discussions in the archive about the following
statement:

"Responses must be sent to the address and port from which the corresponding
commands were sent".

The discussions relate mostly to failover and handover situations, but I
could not find any discussion of what happens when a rogue MGC sends a
command to an MG with which it has not established a control association.
One rule that may be relevant here is:

"It is possible that the reply to a ServiceChange with Restart will be lost,
and a command will be received by the MG prior to the receipt of the
ServiceChange response.  The MG shall issue error 505 - Command Received
before Restart Response".

Does the MG send error 505 if it has not received a restart response from
the SENDING MGC, or from ANY MGC?  If the answer is ANY MGC, how does the MG
protect itself from being sent commands by unauthorized entities?


Raphael Tryster

------_=_NextPart_001_01C1EF5A.DEED6700
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>reply to sender of command</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have seen a number of discussions in t=
he archive about the following statement:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">"</FONT><FONT SIZE=3D2 FACE=3D"Arial">Re=
sponses</FONT><FONT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D=
"Arial">must be sent to the address and port from which the corresponding=
</FONT><FONT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial=
">commands were sent</FONT><FONT SIZE=3D2 FACE=3D"Arial">"</FONT><FONT SI=
ZE=3D2 FACE=3D"Arial">.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The discussions relate mostly to failove=
r and handover situations, but I could not find any discussion of what ha=
ppens when a rogue MGC sends a command to an MG with which it has not est=
ablished a control association.&nbsp;&nbsp; One rule that may be relevant=
 here is:</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">"</FONT><FONT SIZE=3D2 FACE=3D"Arial">It=
 is possible that the reply to a ServiceChange with Restart will be</FONT=
><FONT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">lost=
, and a command will be received by the MG prior to the receipt</FONT><FO=
NT SIZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">of the S=
erviceChange response.&nbsp; The MG shall issue error 505 -</FONT><FONT S=
IZE=3D2 FACE=3D"Arial"></FONT> <FONT SIZE=3D2 FACE=3D"Arial">Command Rece=
ived before Restart Response</FONT><FONT SIZE=3D2 FACE=3D"Arial">"</FONT>=
<FONT SIZE=3D2 FACE=3D"Arial">.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Does the MG send error 505 if it has not=
 received a restart response from the SENDING MGC, or from ANY MGC?&nbsp;=
 If the answer is ANY MGC, how does the MG protect itself from being sent=
 commands by unauthorized entities?</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1EF5A.DEED6700--

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



From megaco-admin@ietf.org  Mon Apr 29 08:24: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 IAA28258
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 08:24:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15506;
	Mon, 29 Apr 2002 08:05:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15475
	for <megaco@optimus.ietf.org>; Mon, 29 Apr 2002 08:05:30 -0400 (EDT)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26570
	for <megaco@ietf.org>; Mon, 29 Apr 2002 08:05:28 -0400 (EDT)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <J5SXN9B0>; Mon, 29 Apr 2002 08:05:00 -0400
Message-ID: <2415C206C515244DBFB12EC0C064A448404D56@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Fernando Vallejo Lazaro'" <Fernando.Vallejo_Lazaro@alcatel.es>,
        Megaco
	 <megaco@ietf.org>
Subject: RE: [Megaco] Version 1 and 1.0
Date: Mon, 29 Apr 2002 08:04:59 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1EF76.160E4D60"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1EF76.160E4D60
Content-Type: text/plain;
	charset="iso-8859-1"

Actually the older V12 version used "/1.0" where V1  uses "/1"
 
Carl

-----Original Message-----
From: Fernando Vallejo Lazaro [mailto:Fernando.Vallejo_Lazaro@alcatel.es]
Sent: Monday, April 29, 2002 3:09 AM
To: Megaco
Subject: [Megaco] Version 1 and 1.0


Hi all, 

Can we consider that version 1 is the same that version 1.0? 
(for the negotiation in the ServiceChange) 


Regards 
Fernando 
  

-- 

Fernando Vallejo Lazaro

Phone:  +34 91 330 8279

SW  Wireline ASD-Madrid

       ALCATEL
  


------_=_NextPart_001_01C1EF76.160E4D60
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">


<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=517300412-29042002><FONT face=Arial color=#0000ff 
size=2>Actually the older V12 version used "/1.0" where V1&nbsp; uses 
"/1"</FONT></SPAN></DIV>
<DIV><SPAN class=517300412-29042002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=517300412-29042002><FONT face=Arial color=#0000ff 
size=2>Carl</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Fernando Vallejo Lazaro 
  [mailto:Fernando.Vallejo_Lazaro@alcatel.es]<BR><B>Sent:</B> Monday, April 29, 
  2002 3:09 AM<BR><B>To:</B> Megaco<BR><B>Subject:</B> [Megaco] Version 1 and 
  1.0<BR><BR></FONT></DIV>Hi all, 
  <P>Can we consider that version 1 is the same that version 1.0? <BR>(for the 
  negotiation in the ServiceChange) 
  <P>Regards <BR>Fernando <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; 
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1EF76.160E4D60--

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


From daemon@optimus.ietf.org  Mon Apr 29 08:24: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 IAA28271
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 08:24:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA16631
	for megaco-archive@odin.ietf.org; Mon, 29 Apr 2002 08:24:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15506;
	Mon, 29 Apr 2002 08:05:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15475
	for <megaco@optimus.ietf.org>; Mon, 29 Apr 2002 08:05:30 -0400 (EDT)
Received: from wench.telica.com (bouncer.telica.com [4.19.224.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26570
	for <megaco@ietf.org>; Mon, 29 Apr 2002 08:05:28 -0400 (EDT)
Received: by wench with Internet Mail Service (5.5.2653.19)
	id <J5SXN9B0>; Mon, 29 Apr 2002 08:05:00 -0400
Message-ID: <2415C206C515244DBFB12EC0C064A448404D56@wench>
From: Carl Rutter <crutter@telica.com>
To: "'Fernando Vallejo Lazaro'" <Fernando.Vallejo_Lazaro@alcatel.es>,
        Megaco
	 <megaco@ietf.org>
Subject: RE: [Megaco] Version 1 and 1.0
Date: Mon, 29 Apr 2002 08:04:59 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1EF76.160E4D60"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1EF76.160E4D60
Content-Type: text/plain;
	charset="iso-8859-1"

Actually the older V12 version used "/1.0" where V1  uses "/1"
 
Carl

-----Original Message-----
From: Fernando Vallejo Lazaro [mailto:Fernando.Vallejo_Lazaro@alcatel.es]
Sent: Monday, April 29, 2002 3:09 AM
To: Megaco
Subject: [Megaco] Version 1 and 1.0


Hi all, 

Can we consider that version 1 is the same that version 1.0? 
(for the negotiation in the ServiceChange) 


Regards 
Fernando 
  

-- 

Fernando Vallejo Lazaro

Phone:  +34 91 330 8279

SW  Wireline ASD-Madrid

       ALCATEL
  


------_=_NextPart_001_01C1EF76.160E4D60
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">


<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=517300412-29042002><FONT face=Arial color=#0000ff 
size=2>Actually the older V12 version used "/1.0" where V1&nbsp; uses 
"/1"</FONT></SPAN></DIV>
<DIV><SPAN class=517300412-29042002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=517300412-29042002><FONT face=Arial color=#0000ff 
size=2>Carl</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Fernando Vallejo Lazaro 
  [mailto:Fernando.Vallejo_Lazaro@alcatel.es]<BR><B>Sent:</B> Monday, April 29, 
  2002 3:09 AM<BR><B>To:</B> Megaco<BR><B>Subject:</B> [Megaco] Version 1 and 
  1.0<BR><BR></FONT></DIV>Hi all, 
  <P>Can we consider that version 1 is the same that version 1.0? <BR>(for the 
  negotiation in the ServiceChange) 
  <P>Regards <BR>Fernando <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; 
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1EF76.160E4D60--

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



From megaco-admin@ietf.org  Mon Apr 29 10:28: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 KAA12300
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 10:28:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23440;
	Mon, 29 Apr 2002 10:09:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23411
	for <megaco@optimus.ietf.org>; Mon, 29 Apr 2002 10:09:33 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10007
	for <megaco@ietf.org>; Mon, 29 Apr 2002 10:09:30 -0400 (EDT)
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 g3TE8sk23074
	for <megaco@ietf.org>; Mon, 29 Apr 2002 10:08:55 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN772TW>; Mon, 29 Apr 2002 10:08:57 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3A2@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Raphael Tryster'" <raphael@tdsoft.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] reply to sender of command
Date: Mon, 29 Apr 2002 10:08:53 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

The MG sends 505 to the MGC to which it has sent a ServiceChange
registration.  To any other MGC it would send 402 Unauthorized, if it sends
anything at all.  I'm not sure it should send anything, because rogue
commands could constitute a Denial of Service attack.  Remember that we
expect Megaco commands to pass over an established security association
(which brings to mind that some day we should add security considerations to
the ATM transport annex, Annex I).

-----Original Message-----
From: Raphael Tryster [mailto:raphael@tdsoft.com]
Sent: Monday, April 29, 2002 4:50 AM
To: 'megaco@ietf.org'
Subject: [Megaco] reply to sender of command


I have seen a number of discussions in the archive about the following
statement: 
"Responses must be sent to the address and port from which the corresponding
commands were sent". 
The discussions relate mostly to failover and handover situations, but I
could not find any discussion of what happens when a rogue MGC sends a
command to an MG with which it has not established a control association.
One rule that may be relevant here is:
"It is possible that the reply to a ServiceChange with Restart will be lost,
and a command will be received by the MG prior to the receipt of the
ServiceChange response.  The MG shall issue error 505 - Command Received
before Restart Response".
Does the MG send error 505 if it has not received a restart response from
the SENDING MGC, or from ANY MGC?  If the answer is ANY MGC, how does the MG
protect itself from being sent commands by unauthorized entities?


Raphael Tryster 

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


From daemon@optimus.ietf.org  Mon Apr 29 10:28: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 KAA12312
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 10:28:23 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA24533
	for megaco-archive@odin.ietf.org; Mon, 29 Apr 2002 10:28:25 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23440;
	Mon, 29 Apr 2002 10:09:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23411
	for <megaco@optimus.ietf.org>; Mon, 29 Apr 2002 10:09:33 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10007
	for <megaco@ietf.org>; Mon, 29 Apr 2002 10:09:30 -0400 (EDT)
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 g3TE8sk23074
	for <megaco@ietf.org>; Mon, 29 Apr 2002 10:08:55 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN772TW>; Mon, 29 Apr 2002 10:08:57 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3A2@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Raphael Tryster'" <raphael@tdsoft.com>,
        "'megaco@ietf.org'"
	 <megaco@ietf.org>
Subject: RE: [Megaco] reply to sender of command
Date: Mon, 29 Apr 2002 10:08:53 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

The MG sends 505 to the MGC to which it has sent a ServiceChange
registration.  To any other MGC it would send 402 Unauthorized, if it sends
anything at all.  I'm not sure it should send anything, because rogue
commands could constitute a Denial of Service attack.  Remember that we
expect Megaco commands to pass over an established security association
(which brings to mind that some day we should add security considerations to
the ATM transport annex, Annex I).

-----Original Message-----
From: Raphael Tryster [mailto:raphael@tdsoft.com]
Sent: Monday, April 29, 2002 4:50 AM
To: 'megaco@ietf.org'
Subject: [Megaco] reply to sender of command


I have seen a number of discussions in the archive about the following
statement: 
"Responses must be sent to the address and port from which the corresponding
commands were sent". 
The discussions relate mostly to failover and handover situations, but I
could not find any discussion of what happens when a rogue MGC sends a
command to an MG with which it has not established a control association.
One rule that may be relevant here is:
"It is possible that the reply to a ServiceChange with Restart will be lost,
and a command will be received by the MG prior to the receipt of the
ServiceChange response.  The MG shall issue error 505 - Command Received
before Restart Response".
Does the MG send error 505 if it has not received a restart response from
the SENDING MGC, or from ANY MGC?  If the answer is ANY MGC, how does the MG
protect itself from being sent commands by unauthorized entities?


Raphael Tryster 

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



From megaco-admin@ietf.org  Mon Apr 29 10:32: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 KAA12714
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 10:32:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23550;
	Mon, 29 Apr 2002 10:12:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23525
	for <megaco@optimus.ietf.org>; Mon, 29 Apr 2002 10:12:05 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10388
	for <megaco@ietf.org>; Mon, 29 Apr 2002 10:12:01 -0400 (EDT)
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 g3TEBVk23219
	for <megaco@ietf.org>; Mon, 29 Apr 2002 10:11:32 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN772W2>; Mon, 29 Apr 2002 10:11:34 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3A3@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Carl Rutter'" <crutter@telica.com>,
        "'Fernando Vallejo Lazaro'"
	 <Fernando.Vallejo_Lazaro@alcatel.es>,
        Megaco <megaco@ietf.org>
Subject: RE: [Megaco] Version 1 and 1.0
Date: Mon, 29 Apr 2002 10:11:31 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Yes, we dropped fractional versions on the grounds that new versions were
bound to have features older versions wouldn't recognize, so we should use
whole numbers.  Given our succession of Implementor's Guide corrections, I'm
starting to wonder if I, for one, was mistaken.

-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Monday, April 29, 2002 8:05 AM
To: 'Fernando Vallejo Lazaro'; Megaco
Subject: RE: [Megaco] Version 1 and 1.0


Actually the older V12 version used "/1.0" where V1  uses "/1"
 
Carl
-----Original Message-----
From: Fernando Vallejo Lazaro [mailto:Fernando.Vallejo_Lazaro@alcatel.es]
Sent: Monday, April 29, 2002 3:09 AM
To: Megaco
Subject: [Megaco] Version 1 and 1.0


Hi all, 
Can we consider that version 1 is the same that version 1.0? 
(for the negotiation in the ServiceChange) 
Regards 
Fernando 
  
-- 
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL
  

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


From daemon@optimus.ietf.org  Mon Apr 29 10:32: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 KAA12737
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 10:32:05 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA25069
	for megaco-archive@odin.ietf.org; Mon, 29 Apr 2002 10:32:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23550;
	Mon, 29 Apr 2002 10:12:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23525
	for <megaco@optimus.ietf.org>; Mon, 29 Apr 2002 10:12:05 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10388
	for <megaco@ietf.org>; Mon, 29 Apr 2002 10:12:01 -0400 (EDT)
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 g3TEBVk23219
	for <megaco@ietf.org>; Mon, 29 Apr 2002 10:11:32 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN772W2>; Mon, 29 Apr 2002 10:11:34 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3A3@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Carl Rutter'" <crutter@telica.com>,
        "'Fernando Vallejo Lazaro'"
	 <Fernando.Vallejo_Lazaro@alcatel.es>,
        Megaco <megaco@ietf.org>
Subject: RE: [Megaco] Version 1 and 1.0
Date: Mon, 29 Apr 2002 10:11:31 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Yes, we dropped fractional versions on the grounds that new versions were
bound to have features older versions wouldn't recognize, so we should use
whole numbers.  Given our succession of Implementor's Guide corrections, I'm
starting to wonder if I, for one, was mistaken.

-----Original Message-----
From: Carl Rutter [mailto:crutter@telica.com]
Sent: Monday, April 29, 2002 8:05 AM
To: 'Fernando Vallejo Lazaro'; Megaco
Subject: RE: [Megaco] Version 1 and 1.0


Actually the older V12 version used "/1.0" where V1  uses "/1"
 
Carl
-----Original Message-----
From: Fernando Vallejo Lazaro [mailto:Fernando.Vallejo_Lazaro@alcatel.es]
Sent: Monday, April 29, 2002 3:09 AM
To: Megaco
Subject: [Megaco] Version 1 and 1.0


Hi all, 
Can we consider that version 1 is the same that version 1.0? 
(for the negotiation in the ServiceChange) 
Regards 
Fernando 
  
-- 
Fernando Vallejo Lazaro
Phone:  +34 91 330 8279
SW  Wireline ASD-Madrid
       ALCATEL
  

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



From megaco-admin@ietf.org  Mon Apr 29 11: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 LAA16926
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 11:11:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA26088;
	Mon, 29 Apr 2002 10:49:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA25604
	for <megaco@optimus.ietf.org>; Mon, 29 Apr 2002 10:40:46 -0400 (EDT)
Received: from mail-sweeper.msw (clnt-21138.bezeqint.net [212.179.22.138] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13738
	for <megaco@ietf.org>; Mon, 29 Apr 2002 10:40:41 -0400 (EDT)
Received: from Yehmsg01.corp.audiocodes.com (unverified) by mail-sweeper.msw
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T5a8f3c3c81d4b3168a49c@mail-sweeper.msw>;
 Mon, 29 Apr 2002 17:42:26 +0200
Received: from lodmsg01.corp.audiocodes.com ([10.2.0.2]) by Yehmsg01.corp.audiocodes.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Mon, 29 Apr 2002 17:39:19 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Subject: RE: [Megaco] Deleting termination from the Context
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1EF94.06574A3C"
Date: Mon, 29 Apr 2002 17:39:18 +0200
Message-ID: <14B7C5B03853404495D29CFA4A54B21C01C098@lodmsg01.corp.audiocodes.com>
Thread-Topic: [Megaco] Deleting termination from the Context
Thread-Index: AcHrmdFrbBxdimhxRyW1IKHnuXvqEQD+ZhPw
From: "Nurit Shenhar" <NuritS@audiocodes.com>
To: <megaco@ietf.org>, <taylor@nortelnetworks.com>
X-OriginalArrivalTime: 29 Apr 2002 15:39:19.0642 (UTC) FILETIME=[0719E3A0:01C1EF94]
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1EF94.06574A3C
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi
=20
I have always thought that using the format of Context=3D* and termination=
=3Dspecific should be limited to the audit command. The MGC id supposed to =
have the picture at all times, and if there is a loss of synchronization, i=
t should audit to get the current status. So how come that the MGC doesn't =
know the context's termination? And if the context is known, why using the =
ALL wildcard?
=20
Nurit
=20
-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 24, 2002 2:56 PM
To: 'Anil Jangam'; 'megaco@ietf.org'
Subject: RE: [Megaco] Deleting termination from the Context
=20
Following the precedent set with the Audit commands, I think this should be=
 possible.=20
-----Original Message-----=20
From: Anil Jangam [ mailto:anilj@indts.com]=20
Sent: Wednesday, April 24, 2002 2:40 AM=20
To: 'megaco@ietf.org'=20
Subject: [Megaco] Deleting termination from the Context=20
=20
Hi,=20
Is it possible to issue a 'Subtract' command to delete a Termination with=
 'Context' as a '*'.=20
I am looking at subtract command which essentially deletes a Termination=20
from the context, when I don't have the information about the context, in=
 which the Termination is present. Thus with 'Context' as '*', it would try=
 to find out the TerminastionId in all the contexts present and delete it.=
 regds,=20
/anil.=20
_______________________________________________=20
Megaco mailing list=20
Megaco@ietf.org=20
https://www1.ietf.org/mailman/listinfo/megaco=20


=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C1EFA4.C9D41900">
<title>RE: [Megaco] Deleting termination from the Context</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h1
	{mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:0in;
	text-indent:0in;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	tab-stops:list .25in;
	font-size:16.0pt;
	font-family:Arial;
	mso-font-kerning:16.0pt;
	font-weight:bold;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.Appendix, li.Appendix, div.Appendix
	{mso-style-name:Appendix;
	mso-style-parent:"Heading 1";
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:0in;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	tab-stops:list .25in;
	font-size:16.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	font-weight:bold;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;
	mso-gutter-direction:rtl;}
div.Section1
	{page:Section1;}
 /* List Definitions */
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue style=3D'tab-interval:.5in'>

<div class=3DSection1 dir=3DRTL>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'>Hi<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font><=
/span></p>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'>I have always thought that using the format of Context=3D* and
termination=3Dspecific should be limited to the audit command. The MGC id
supposed to have the picture at all times, and if there is a loss of
synchronization, it should audit to get the current status. So how come that
the MGC doesn&#8217;t know the context&#8217;s termination? And if the cont=
ext is known,
why using the ALL wildcard?<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font><=
/span></p>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'>Nurit<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font><=
/span></p>

<p class=3DMsoNormal dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 co=
lor=3Dblack
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma;color:blac=
k'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Tom-PT Taylor
[mailto:taylor@nortelnetworks.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, April 24, 2=
002
2:56 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Anil Jangam';
'megaco@ietf.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Megaco] Deleti=
ng
termination from the Context</span></font></p>

<p class=3DMsoNormal dir=3DLTR style=3D'margin-left:.5in'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'><![if !supportEmp=
tyParas]>&nbsp;<![endif]><o:p></o:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>Follo=
wing the
precedent set with the Audit commands, I think this should be possible.</sp=
an></font><font
color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblac=
k><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>-----=
Original
Message-----</span></font><font color=3Dblack><span style=3D'color:black'> =
<br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>From: Anil Jangam [<a href=3D"mailto:anilj@indts.com">mailto:a=
nilj@indts.com</a>]</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>Sent: Wednesday, April 24, 2002 2:40 AM</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>To: 'megaco@ietf.org'</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>Subject: [Megaco] Deleting termination from the Context</span>=
</font><font
color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblac=
k><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR style=3D'margin-left:.5in'><font size=3D3 co=
lor=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;color:black'><![if=
 !supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span style=3D'color:black;mso-color-alt:windowtext'><o:p></o=
:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>Hi,</=
span></font><font
color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblac=
k><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>Is it
possible to issue a 'Subtract' command to delete a Termination with</span><=
/font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>'Context' as a '*'.</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>I am looking at subtract command which essentially deletes a
Termination</span></font><font color=3Dblack><span style=3D'color:black'> <=
br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>from the context, when I don't have the information about the
context, in</span></font><font color=3Dblack><span style=3D'color:black'> <=
br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>which the Termination is present. Thus with 'Context' as '*', =
it
would try</span></font><font color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>to find out the TerminastionId in all the contexts present and
delete it. </span></font><font color=3Dblack><span style=3D'color:black;mso=
-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>regds=
,</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>/anil.</span></font><font color=3Dblack><span style=3D'color:b=
lack'> </span></font><font
color=3Dblack><span style=3D'color:black;mso-color-alt:windowtext'><o:p></o=
:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>_____=
__________________________________________</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>Megaco mailing list</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>Megaco@ietf.org</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'><a href=3D"https://www1.ietf.org/mailman/listinfo/megaco"
target=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</a></span><=
/font><font
color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblac=
k><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

</div>

<CODE><FONT SIZE=3D3><BR>
<BR>
 <BR>
</FONT></CODE>
</body>

</html>

------_=_NextPart_001_01C1EF94.06574A3C--


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


From daemon@optimus.ietf.org  Mon Apr 29 11:11: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 LAA16942
	for <megaco-archive@odin.ietf.org>; Mon, 29 Apr 2002 11:11:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA27798
	for megaco-archive@odin.ietf.org; Mon, 29 Apr 2002 11:11:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA26088;
	Mon, 29 Apr 2002 10:49:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA25604
	for <megaco@optimus.ietf.org>; Mon, 29 Apr 2002 10:40:46 -0400 (EDT)
Received: from mail-sweeper.msw (clnt-21138.bezeqint.net [212.179.22.138] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13738
	for <megaco@ietf.org>; Mon, 29 Apr 2002 10:40:41 -0400 (EDT)
Received: from Yehmsg01.corp.audiocodes.com (unverified) by mail-sweeper.msw
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T5a8f3c3c81d4b3168a49c@mail-sweeper.msw>;
 Mon, 29 Apr 2002 17:42:26 +0200
Received: from lodmsg01.corp.audiocodes.com ([10.2.0.2]) by Yehmsg01.corp.audiocodes.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Mon, 29 Apr 2002 17:39:19 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Subject: RE: [Megaco] Deleting termination from the Context
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1EF94.06574A3C"
Date: Mon, 29 Apr 2002 17:39:18 +0200
Message-ID: <14B7C5B03853404495D29CFA4A54B21C01C098@lodmsg01.corp.audiocodes.com>
Thread-Topic: [Megaco] Deleting termination from the Context
Thread-Index: AcHrmdFrbBxdimhxRyW1IKHnuXvqEQD+ZhPw
From: "Nurit Shenhar" <NuritS@audiocodes.com>
To: <megaco@ietf.org>, <taylor@nortelnetworks.com>
X-OriginalArrivalTime: 29 Apr 2002 15:39:19.0642 (UTC) FILETIME=[0719E3A0:01C1EF94]
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1EF94.06574A3C
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi
=20
I have always thought that using the format of Context=3D* and termination=
=3Dspecific should be limited to the audit command. The MGC id supposed to =
have the picture at all times, and if there is a loss of synchronization, i=
t should audit to get the current status. So how come that the MGC doesn't =
know the context's termination? And if the context is known, why using the =
ALL wildcard?
=20
Nurit
=20
-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Wednesday, April 24, 2002 2:56 PM
To: 'Anil Jangam'; 'megaco@ietf.org'
Subject: RE: [Megaco] Deleting termination from the Context
=20
Following the precedent set with the Audit commands, I think this should be=
 possible.=20
-----Original Message-----=20
From: Anil Jangam [ mailto:anilj@indts.com]=20
Sent: Wednesday, April 24, 2002 2:40 AM=20
To: 'megaco@ietf.org'=20
Subject: [Megaco] Deleting termination from the Context=20
=20
Hi,=20
Is it possible to issue a 'Subtract' command to delete a Termination with=
 'Context' as a '*'.=20
I am looking at subtract command which essentially deletes a Termination=20
from the context, when I don't have the information about the context, in=
 which the Termination is present. Thus with 'Context' as '*', it would try=
 to find out the TerminastionId in all the contexts present and delete it.=
 regds,=20
/anil.=20
_______________________________________________=20
Megaco mailing list=20
Megaco@ietf.org=20
https://www1.ietf.org/mailman/listinfo/megaco=20


=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C1EFA4.C9D41900">
<title>RE: [Megaco] Deleting termination from the Context</title>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h1
	{mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:0in;
	text-indent:0in;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	tab-stops:list .25in;
	font-size:16.0pt;
	font-family:Arial;
	mso-font-kerning:16.0pt;
	font-weight:bold;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.Appendix, li.Appendix, div.Appendix
	{mso-style-name:Appendix;
	mso-style-parent:"Heading 1";
	margin:0in;
	margin-bottom:.0001pt;
	text-indent:0in;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	tab-stops:list .25in;
	font-size:16.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	font-weight:bold;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;
	mso-gutter-direction:rtl;}
div.Section1
	{page:Section1;}
 /* List Definitions */
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue style=3D'tab-interval:.5in'>

<div class=3DSection1 dir=3DRTL>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'>Hi<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font><=
/span></p>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'>I have always thought that using the format of Context=3D* and
termination=3Dspecific should be limited to the audit command. The MGC id
supposed to have the picture at all times, and if there is a loss of
synchronization, it should audit to get the current status. So how come that
the MGC doesn&#8217;t know the context&#8217;s termination? And if the cont=
ext is known,
why using the ALL wildcard?<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font><=
/span></p>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'>Nurit<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal dir=3DLTR><span class=3DEmailStyle19><font size=3D2 co=
lor=3Dnavy
face=3DArial><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font=
-family:
Arial'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font><=
/span></p>

<p class=3DMsoNormal dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 co=
lor=3Dblack
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma;color:blac=
k'>-----Original
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Tom-PT Taylor
[mailto:taylor@nortelnetworks.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, April 24, 2=
002
2:56 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> 'Anil Jangam';
'megaco@ietf.org'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Megaco] Deleti=
ng
termination from the Context</span></font></p>

<p class=3DMsoNormal dir=3DLTR style=3D'margin-left:.5in'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'><![if !supportEmp=
tyParas]>&nbsp;<![endif]><o:p></o:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>Follo=
wing the
precedent set with the Audit commands, I think this should be possible.</sp=
an></font><font
color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblac=
k><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>-----=
Original
Message-----</span></font><font color=3Dblack><span style=3D'color:black'> =
<br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>From: Anil Jangam [<a href=3D"mailto:anilj@indts.com">mailto:a=
nilj@indts.com</a>]</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>Sent: Wednesday, April 24, 2002 2:40 AM</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>To: 'megaco@ietf.org'</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>Subject: [Megaco] Deleting termination from the Context</span>=
</font><font
color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblac=
k><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal dir=3DLTR style=3D'margin-left:.5in'><font size=3D3 co=
lor=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;color:black'><![if=
 !supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span style=3D'color:black;mso-color-alt:windowtext'><o:p></o=
:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>Hi,</=
span></font><font
color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblac=
k><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>Is it
possible to issue a 'Subtract' command to delete a Termination with</span><=
/font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>'Context' as a '*'.</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>I am looking at subtract command which essentially deletes a
Termination</span></font><font color=3Dblack><span style=3D'color:black'> <=
br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>from the context, when I don't have the information about the
context, in</span></font><font color=3Dblack><span style=3D'color:black'> <=
br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>which the Termination is present. Thus with 'Context' as '*', =
it
would try</span></font><font color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>to find out the TerminastionId in all the contexts present and
delete it. </span></font><font color=3Dblack><span style=3D'color:black;mso=
-color-alt:
windowtext'><o:p></o:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>regds=
,</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>/anil.</span></font><font color=3Dblack><span style=3D'color:b=
lack'> </span></font><font
color=3Dblack><span style=3D'color:black;mso-color-alt:windowtext'><o:p></o=
:p></span></font></p>

<p dir=3DLTR style=3D'margin-left:.5in'><font size=3D2 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:10.0pt;color:black'>_____=
__________________________________________</span></font><font
color=3Dblack><span style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>Megaco mailing list</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'>Megaco@ietf.org</span></font><font color=3Dblack><span
style=3D'color:black'> <br>
</span></font><font size=3D2 color=3Dblack><span style=3D'font-size:10.0pt;
color:black'><a href=3D"https://www1.ietf.org/mailman/listinfo/megaco"
target=3D"_blank">https://www1.ietf.org/mailman/listinfo/megaco</a></span><=
/font><font
color=3Dblack><span style=3D'color:black'> </span></font><font color=3Dblac=
k><span
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

</div>

<CODE><FONT SIZE=3D3><BR>
<BR>
 <BR>
</FONT></CODE>
</body>

</html>

------_=_NextPart_001_01C1EF94.06574A3C--


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



From megaco-admin@ietf.org  Tue Apr 30 00: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 AAA29870
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 00:49:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA17367;
	Tue, 30 Apr 2002 00:30:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA17236
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 00:30:05 -0400 (EDT)
Received: from ish7.ericsson.com.au (ish7.ericsson.com.au [203.61.155.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29689;
	Tue, 30 Apr 2002 00:30:00 -0400 (EDT)
Received: from brsf10.epa.ericsson.se (brsf10 [146.11.8.4])
	by ish7.ericsson.com.au (8.11.6+Sun/8.11.6) with ESMTP id g3U4SN019079;
	Tue, 30 Apr 2002 14:28:23 +1000 (EST)
Received: from ericsson.com.au (dhcp-239-110.epa.ericsson.se [146.11.239.110])
	by brsf10.epa.ericsson.se (8.11.6+Sun/8.9.3) with ESMTP id g3U4TxN12869;
	Tue, 30 Apr 2002 14:29:59 +1000 (EST)
Message-ID: <3CCDF743.3682E0EA@ericsson.com.au>
Date: Tue, 30 Apr 2002 11:45:39 +1000
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>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>
References: <4D79C746863DD51197690002A52CDA0001E8A2A2@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Megaco] Re: [MMUSIC] FW: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.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
Content-Transfer-Encoding: 8bit

G'Day Tom,

I've been having a look at the TDM draft and my main comment is regarding mainly
section 4 TDM attributes although it may have some flow on effects. Whilst the
list of attributes is rather comprehensive it seems to me that this is a
duplication of already defined values. All of the values can be represented by
the User Service Information (USI) Q.763 / Bearer Capability information element
Q.931. Given that TDM terminations will most likely be used in scenarios where
the Call control will be BICC/ISUP/Q.931 the USI will be available in the MGC in
the native USI format. It seems pointless to translate the values from native
USI format to a SDP format where each sub-value of the USI is defined as
seperate attributes. An attribute to carry USI has already been defined in the
SG11 work for BICC ie.
a=isup_usi: <value of USI in hex digits as specified in ITU-T Q.1902.3/§ 6.102
[5]>
The left most hex digit pair (e.g. EF in the following sequence EF 23 12 13)
represents the first binary octet that would be transmitted as per Q.1902.3 §
5.10.)

By specifying that a=isup_usi be used instead of the values in section it will
mean that currently defined vertical protocol for ISUP and BICC will be
consistant with your draft.

Regards, Christian

Tom-PT Taylor wrote:
> 
> I have recycled this document at last.  Material relating to Nx64 kbit/s or
> multilink operation has been stripped out, and material relating to H.320
> and H.324 sessions has been modified to conform to the latest views of how
> Megaco operates.  I forgot to put in the MIME registrations for audio/PCMU,
> audio/PCMA, audio/G726xx, and application/octet-stream all over TDM
> transport, but I'll do that on the next pass.
> 
> I sent a copy to Jim Renkel, who had urged that requirements for
> CAS-signalled TDM be taken into account when I first presented this to
> MMUSIC.  I have no idea what additional requirements he has in mind, but
> I'll see.  In the meantime, does anyone else have comments?  We need this
> for NAS operation.
> 
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Tuesday, April 09, 2002 8:41 AM
> Subject: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
>         Title           : Conventions for the use of the Session Description
> 
>                           Protocol (SDP)for Digital Circuit Connections
>         Author(s)       : T. Taylor
>         Filename        : draft-taylor-mmusic-sdp-tdm-01.txt
>         Pages           : 14
>         Date            : 08-Apr-02
> 
> This document describes conventions for using the Session
> Description Protocol (SDP) for controlling digital circuits.  These
> conventions describe
> - circuit addressing conventions for use on the SDP 'c=' line
> - content of the 'm=' line(s) for digital circuits
> - attributes to convey the parameters contained within the Bearer
> Capability, Low Layer Compatibility, and High Layer Compatibility
> Information Elements of ITU-T Recommendation Q.931.
> These conventions have been defined for use in media gateway
> control, particularly in support of NAS operation, but may also be
> used by IP-based call signalling schemes (SIP, BICC) to control
> media exchange over digital circuits.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt
> 
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-taylor-mmusic-sdp-tdm-01.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
>         mailserv@ietf.org.
> In the body type:
>         "FILE /internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt".
> 
> NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
> 
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> -----
> To:
> Subject:
> Date: Tue, 9 Apr 2002 09:51:14 -0400
> X-Mailer: Internet Mail Service (5.5.2653.19)
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 
>                Name: ATT64470
>    ATT64470    Type: unspecified type (application/octet-stream)
>            Encoding: x-uuencode
> 
>                                          Name: draft-taylor-mmusic-sdp-tdm-01.url
>    draft-taylor-mmusic-sdp-tdm-01.url    Type: Internet Shortcut (application/x-unknown-content-type-InternetShortcut)
>                                      Encoding: x-uuencode



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


From daemon@optimus.ietf.org  Tue Apr 30 00: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 AAA29885
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 00:49:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA18567
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 00:49:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA17367;
	Tue, 30 Apr 2002 00:30:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA17236
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 00:30:05 -0400 (EDT)
Received: from ish7.ericsson.com.au (ish7.ericsson.com.au [203.61.155.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29689;
	Tue, 30 Apr 2002 00:30:00 -0400 (EDT)
Received: from brsf10.epa.ericsson.se (brsf10 [146.11.8.4])
	by ish7.ericsson.com.au (8.11.6+Sun/8.11.6) with ESMTP id g3U4SN019079;
	Tue, 30 Apr 2002 14:28:23 +1000 (EST)
Received: from ericsson.com.au (dhcp-239-110.epa.ericsson.se [146.11.239.110])
	by brsf10.epa.ericsson.se (8.11.6+Sun/8.9.3) with ESMTP id g3U4TxN12869;
	Tue, 30 Apr 2002 14:29:59 +1000 (EST)
Message-ID: <3CCDF743.3682E0EA@ericsson.com.au>
Date: Tue, 30 Apr 2002 11:45:39 +1000
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>,
        "'mmusic@ietf.org'" <mmusic@ietf.org>
References: <4D79C746863DD51197690002A52CDA0001E8A2A2@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Megaco] Re: [MMUSIC] FW: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.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
Content-Transfer-Encoding: 8bit

G'Day Tom,

I've been having a look at the TDM draft and my main comment is regarding mainly
section 4 TDM attributes although it may have some flow on effects. Whilst the
list of attributes is rather comprehensive it seems to me that this is a
duplication of already defined values. All of the values can be represented by
the User Service Information (USI) Q.763 / Bearer Capability information element
Q.931. Given that TDM terminations will most likely be used in scenarios where
the Call control will be BICC/ISUP/Q.931 the USI will be available in the MGC in
the native USI format. It seems pointless to translate the values from native
USI format to a SDP format where each sub-value of the USI is defined as
seperate attributes. An attribute to carry USI has already been defined in the
SG11 work for BICC ie.
a=isup_usi: <value of USI in hex digits as specified in ITU-T Q.1902.3/§ 6.102
[5]>
The left most hex digit pair (e.g. EF in the following sequence EF 23 12 13)
represents the first binary octet that would be transmitted as per Q.1902.3 §
5.10.)

By specifying that a=isup_usi be used instead of the values in section it will
mean that currently defined vertical protocol for ISUP and BICC will be
consistant with your draft.

Regards, Christian

Tom-PT Taylor wrote:
> 
> I have recycled this document at last.  Material relating to Nx64 kbit/s or
> multilink operation has been stripped out, and material relating to H.320
> and H.324 sessions has been modified to conform to the latest views of how
> Megaco operates.  I forgot to put in the MIME registrations for audio/PCMU,
> audio/PCMA, audio/G726xx, and application/octet-stream all over TDM
> transport, but I'll do that on the next pass.
> 
> I sent a copy to Jim Renkel, who had urged that requirements for
> CAS-signalled TDM be taken into account when I first presented this to
> MMUSIC.  I have no idea what additional requirements he has in mind, but
> I'll see.  In the meantime, does anyone else have comments?  We need this
> for NAS operation.
> 
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Tuesday, April 09, 2002 8:41 AM
> Subject: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
>         Title           : Conventions for the use of the Session Description
> 
>                           Protocol (SDP)for Digital Circuit Connections
>         Author(s)       : T. Taylor
>         Filename        : draft-taylor-mmusic-sdp-tdm-01.txt
>         Pages           : 14
>         Date            : 08-Apr-02
> 
> This document describes conventions for using the Session
> Description Protocol (SDP) for controlling digital circuits.  These
> conventions describe
> - circuit addressing conventions for use on the SDP 'c=' line
> - content of the 'm=' line(s) for digital circuits
> - attributes to convey the parameters contained within the Bearer
> Capability, Low Layer Compatibility, and High Layer Compatibility
> Information Elements of ITU-T Recommendation Q.931.
> These conventions have been defined for use in media gateway
> control, particularly in support of NAS operation, but may also be
> used by IP-based call signalling schemes (SIP, BICC) to control
> media exchange over digital circuits.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt
> 
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-taylor-mmusic-sdp-tdm-01.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
>         mailserv@ietf.org.
> In the body type:
>         "FILE /internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt".
> 
> NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
> 
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> -----
> To:
> Subject:
> Date: Tue, 9 Apr 2002 09:51:14 -0400
> X-Mailer: Internet Mail Service (5.5.2653.19)
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 
>                Name: ATT64470
>    ATT64470    Type: unspecified type (application/octet-stream)
>            Encoding: x-uuencode
> 
>                                          Name: draft-taylor-mmusic-sdp-tdm-01.url
>    draft-taylor-mmusic-sdp-tdm-01.url    Type: Internet Shortcut (application/x-unknown-content-type-InternetShortcut)
>                                      Encoding: x-uuencode



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



From megaco-admin@ietf.org  Tue Apr 30 05:30: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 FAA11424
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 05:30:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA07787;
	Tue, 30 Apr 2002 04:50:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA07758
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 04:50:05 -0400 (EDT)
Received: from mailgate.sbell.com.cn (mailgate.sbell.com.cn [202.96.203.173])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10932
	for <megaco@ietf.org>; Tue, 30 Apr 2002 04:49:56 -0400 (EDT)
Received: from bellnet-mail4.sbell.com.cn (bellnet-mail4.sbell.com.cn [202.96.203.174])
	by mailgate.sbell.com.cn (8.9.2/8.9.2) with ESMTP id QAA07030;
	Tue, 30 Apr 2002 16:36:04 +0800 (CST)
Received: from bellnet-mail1.sbell.com.cn ([202.96.203.171]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 30 Apr 2002 16:48:05 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1F023.BE24A1BF"
Date: Tue, 30 Apr 2002 16:48:04 +0800
Message-ID: <C65F869D22451348A9970B1670ED366301A701AE@bellnet-mail1.sbell.com.cn>
Thread-Topic: Latest SW version ?
Thread-Index: AcHvjA8qQeKXIivPS061mC+D6gX5TwAk6qtQ
From: "SRD Wang JuLin" <WangJL2@sbell.com.cn>
To: "An Leurs" <ALeurs@alcatel.de>, "Megaco (E-mail)" <megaco@ietf.org>,
        "MadhuBabu Brahmanapally (E-mail)" <madhubabu@kenetec.com>
Cc: "Albrecht Schwarz" <Albrecht.Schwarz@alcatel.de>,
        "Patrick Villarin" <Patrick.Villarin@alcatel.be>,
        "Van Opstal Jan" <jan.van_opstal@alcatel.be>
X-OriginalArrivalTime: 30 Apr 2002 08:48:05.0229 (UTC) FILETIME=[BE6B01D0:01C1F023]
Subject: [Megaco] About RGW PBX application
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1F023.BE24A1BF
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
Currently,we are take consideration of RGW (FXS type)PBX application.I =
have a question to consult:
Suppose that the caller located in one RGW firstly dial a number to =
connect to the PBX which are lined to another RGW. After call connected =
and establish rtp stream,the  PBX will send dialtone directly to the =
caller  indicating the caller  to dial the ext(callee's) number (callee =
lined to the PBX).So the caller can send the  ext number to Softswtich =
in Notify message.(use dtmf inband transfer is another case)But i wonder =
how can the Softswtich send the ext number to the callee side?Use dg =
package???
Pls clear my mind about it!
Thanks a lot!=20
=20

best  regards=20
:-)Jerry Wang=20
tel:(8621)58541240 ext 9615=20
mailto:wangjl2@sbell.com.cn=20
Shanghai Bell Co.LTD=20

=20


------_=_NextPart_001_01C1F023.BE24A1BF
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 6.00.2712.300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff=20
size=3D2>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff=20
size=3D2>Currently,we are take consideration of RGW (FXS type)PBX =
application.I=20
have a question to consult:</FONT></SPAN></DIV>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff size=3D2>Suppose=20
that the caller located in one RGW&nbsp;firstly dial a number to connect =
to the=20
PBX which are&nbsp;lined to another RGW. After call connected and =
establish rtp=20
stream,the&nbsp; PBX will send dialtone directly to the caller&nbsp;=20
indicating&nbsp;the caller &nbsp;to dial the ext(callee's) =
number&nbsp;(callee=20
lined to the PBX).So the caller&nbsp;can send the &nbsp;ext number to =
Softswtich=20
in Notify message.(use dtmf inband transfer is another case)But i wonder =

h</FONT></SPAN><SPAN class=3D570191908-30042002><FONT =
face=3D&#23435;&#20307; color=3D#0000ff=20
size=3D2>ow can the Softswtich&nbsp;send the ext number to the callee =
side?Use dg=20
package???</FONT></SPAN></DIV>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff size=3D2>Pls clear=20
my mind about it!</FONT></SPAN></DIV>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff size=3D2>Thanks a=20
lot!</FONT>&nbsp;</SPAN></DIV>
<DIV><FONT face=3D&#23435;&#20307; color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV>
<P><I><FONT face=3DArial color=3D#0000ff>best&nbsp; =
regards</FONT><B></B></I>=20
<BR><FONT face=3DWingdings=20
size=3D4>J</FONT><B></B><B><I></I></B><B><I></I></B><B><I><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Jerry Wang</FONT></I></B> <BR><B><FONT =
face=3DArial=20
color=3D#008080 size=3D1>tel:</FONT><FONT face=3D&#23435;&#20307; =
color=3D#008080=20
size=3D1>(8621)</FONT><FONT face=3DArial color=3D#008080 =
size=3D1>58541240 ext=20
9615</FONT></B> <BR><B><FONT face=3DArial color=3D#008080 size=3D1><A=20
href=3D"mailto:wangjl2@sbell.com.cn">mailto:wangjl2@sbell.com.cn</A></FON=
T></B>=20
<BR><B><FONT face=3DArial color=3D#008080 size=3D1>Shanghai Bell =
Co.LTD</FONT></B>=20
</P>
<BLOCKQUOTE dir=3Dltr=20
style=3D"MARGIN-RIGHT: 0px"><TT></TT>&nbsp;</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1F023.BE24A1BF--

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


From daemon@optimus.ietf.org  Tue Apr 30 05:30: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 FAA11434
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 05:30:17 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA09691
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 05:30:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA07787;
	Tue, 30 Apr 2002 04:50:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA07758
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 04:50:05 -0400 (EDT)
Received: from mailgate.sbell.com.cn (mailgate.sbell.com.cn [202.96.203.173])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10932
	for <megaco@ietf.org>; Tue, 30 Apr 2002 04:49:56 -0400 (EDT)
Received: from bellnet-mail4.sbell.com.cn (bellnet-mail4.sbell.com.cn [202.96.203.174])
	by mailgate.sbell.com.cn (8.9.2/8.9.2) with ESMTP id QAA07030;
	Tue, 30 Apr 2002 16:36:04 +0800 (CST)
Received: from bellnet-mail1.sbell.com.cn ([202.96.203.171]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 30 Apr 2002 16:48:05 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1F023.BE24A1BF"
Date: Tue, 30 Apr 2002 16:48:04 +0800
Message-ID: <C65F869D22451348A9970B1670ED366301A701AE@bellnet-mail1.sbell.com.cn>
Thread-Topic: Latest SW version ?
Thread-Index: AcHvjA8qQeKXIivPS061mC+D6gX5TwAk6qtQ
From: "SRD Wang JuLin" <WangJL2@sbell.com.cn>
To: "An Leurs" <ALeurs@alcatel.de>, "Megaco (E-mail)" <megaco@ietf.org>,
        "MadhuBabu Brahmanapally (E-mail)" <madhubabu@kenetec.com>
Cc: "Albrecht Schwarz" <Albrecht.Schwarz@alcatel.de>,
        "Patrick Villarin" <Patrick.Villarin@alcatel.be>,
        "Van Opstal Jan" <jan.van_opstal@alcatel.be>
X-OriginalArrivalTime: 30 Apr 2002 08:48:05.0229 (UTC) FILETIME=[BE6B01D0:01C1F023]
Subject: [Megaco] About RGW PBX application
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1F023.BE24A1BF
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
Currently,we are take consideration of RGW (FXS type)PBX application.I =
have a question to consult:
Suppose that the caller located in one RGW firstly dial a number to =
connect to the PBX which are lined to another RGW. After call connected =
and establish rtp stream,the  PBX will send dialtone directly to the =
caller  indicating the caller  to dial the ext(callee's) number (callee =
lined to the PBX).So the caller can send the  ext number to Softswtich =
in Notify message.(use dtmf inband transfer is another case)But i wonder =
how can the Softswtich send the ext number to the callee side?Use dg =
package???
Pls clear my mind about it!
Thanks a lot!=20
=20

best  regards=20
:-)Jerry Wang=20
tel:(8621)58541240 ext 9615=20
mailto:wangjl2@sbell.com.cn=20
Shanghai Bell Co.LTD=20

=20


------_=_NextPart_001_01C1F023.BE24A1BF
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 6.00.2712.300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff=20
size=3D2>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff=20
size=3D2>Currently,we are take consideration of RGW (FXS type)PBX =
application.I=20
have a question to consult:</FONT></SPAN></DIV>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff size=3D2>Suppose=20
that the caller located in one RGW&nbsp;firstly dial a number to connect =
to the=20
PBX which are&nbsp;lined to another RGW. After call connected and =
establish rtp=20
stream,the&nbsp; PBX will send dialtone directly to the caller&nbsp;=20
indicating&nbsp;the caller &nbsp;to dial the ext(callee's) =
number&nbsp;(callee=20
lined to the PBX).So the caller&nbsp;can send the &nbsp;ext number to =
Softswtich=20
in Notify message.(use dtmf inband transfer is another case)But i wonder =

h</FONT></SPAN><SPAN class=3D570191908-30042002><FONT =
face=3D&#23435;&#20307; color=3D#0000ff=20
size=3D2>ow can the Softswtich&nbsp;send the ext number to the callee =
side?Use dg=20
package???</FONT></SPAN></DIV>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff size=3D2>Pls clear=20
my mind about it!</FONT></SPAN></DIV>
<DIV><SPAN class=3D570191908-30042002><FONT face=3D&#23435;&#20307; =
color=3D#0000ff size=3D2>Thanks a=20
lot!</FONT>&nbsp;</SPAN></DIV>
<DIV><FONT face=3D&#23435;&#20307; color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV>
<P><I><FONT face=3DArial color=3D#0000ff>best&nbsp; =
regards</FONT><B></B></I>=20
<BR><FONT face=3DWingdings=20
size=3D4>J</FONT><B></B><B><I></I></B><B><I></I></B><B><I><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Jerry Wang</FONT></I></B> <BR><B><FONT =
face=3DArial=20
color=3D#008080 size=3D1>tel:</FONT><FONT face=3D&#23435;&#20307; =
color=3D#008080=20
size=3D1>(8621)</FONT><FONT face=3DArial color=3D#008080 =
size=3D1>58541240 ext=20
9615</FONT></B> <BR><B><FONT face=3DArial color=3D#008080 size=3D1><A=20
href=3D"mailto:wangjl2@sbell.com.cn">mailto:wangjl2@sbell.com.cn</A></FON=
T></B>=20
<BR><B><FONT face=3DArial color=3D#008080 size=3D1>Shanghai Bell =
Co.LTD</FONT></B>=20
</P>
<BLOCKQUOTE dir=3Dltr=20
style=3D"MARGIN-RIGHT: 0px"><TT></TT>&nbsp;</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1F023.BE24A1BF--

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



From megaco-admin@ietf.org  Tue Apr 30 08:33: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 IAA16645
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 08:33:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18569;
	Tue, 30 Apr 2002 08:13:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18499
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 08:13:22 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15362;
	Tue, 30 Apr 2002 08:13:15 -0400 (EDT)
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 g3UCCjd07313;
	Tue, 30 Apr 2002 08:12:45 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78A24>; Tue, 30 Apr 2002 08:12:49 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3B2@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>,
        "'mmusic@ietf.org'"
	 <mmusic@ietf.org>
Date: Tue, 30 Apr 2002 08:12:48 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: [MMUSIC] FW: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.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

The whole point of the draft is to relieve MGs of the necessity to
understand legacy telephony signalling protocols.  I will allow the WGs to
comment on whether this is the right approach, since your proposal is
obviously a workable alternative.

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Monday, April 29, 2002 9:46 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'; 'mmusic@ietf.org'
Subject: Re: [MMUSIC] FW: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.txt


G'Day Tom,

I've been having a look at the TDM draft and my main comment is regarding
mainly
section 4 TDM attributes although it may have some flow on effects. Whilst
the
list of attributes is rather comprehensive it seems to me that this is a
duplication of already defined values. All of the values can be represented
by
the User Service Information (USI) Q.763 / Bearer Capability information
element
Q.931. Given that TDM terminations will most likely be used in scenarios
where
the Call control will be BICC/ISUP/Q.931 the USI will be available in the
MGC in
the native USI format. It seems pointless to translate the values from
native
USI format to a SDP format where each sub-value of the USI is defined as
seperate attributes. An attribute to carry USI has already been defined in
the
SG11 work for BICC ie.
a=isup_usi: <value of USI in hex digits as specified in ITU-T Q.1902.3/§
6.102
[5]>
The left most hex digit pair (e.g. EF in the following sequence EF 23 12 13)
represents the first binary octet that would be transmitted as per Q.1902.3
§
5.10.)

By specifying that a=isup_usi be used instead of the values in section it
will
mean that currently defined vertical protocol for ISUP and BICC will be
consistant with your draft.

Regards, Christian

Tom-PT Taylor wrote:
> 
> I have recycled this document at last.  Material relating to Nx64 kbit/s
or
> multilink operation has been stripped out, and material relating to H.320
> and H.324 sessions has been modified to conform to the latest views of how
> Megaco operates.  I forgot to put in the MIME registrations for
audio/PCMU,
> audio/PCMA, audio/G726xx, and application/octet-stream all over TDM
> transport, but I'll do that on the next pass.
> 
> I sent a copy to Jim Renkel, who had urged that requirements for
> CAS-signalled TDM be taken into account when I first presented this to
> MMUSIC.  I have no idea what additional requirements he has in mind, but
> I'll see.  In the meantime, does anyone else have comments?  We need this
> for NAS operation.
> 
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Tuesday, April 09, 2002 8:41 AM
> Subject: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
>         Title           : Conventions for the use of the Session
Description
> 
>                           Protocol (SDP)for Digital Circuit Connections
>         Author(s)       : T. Taylor
>         Filename        : draft-taylor-mmusic-sdp-tdm-01.txt
>         Pages           : 14
>         Date            : 08-Apr-02
> 
> This document describes conventions for using the Session
> Description Protocol (SDP) for controlling digital circuits.  These
> conventions describe
> - circuit addressing conventions for use on the SDP 'c=' line
> - content of the 'm=' line(s) for digital circuits
> - attributes to convey the parameters contained within the Bearer
> Capability, Low Layer Compatibility, and High Layer Compatibility
> Information Elements of ITU-T Recommendation Q.931.
> These conventions have been defined for use in media gateway
> control, particularly in support of NAS operation, but may also be
> used by IP-based call signalling schemes (SIP, BICC) to control
> media exchange over digital circuits.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt
> 
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the
message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the
username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-taylor-mmusic-sdp-tdm-01.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
>         mailserv@ietf.org.
> In the body type:
>         "FILE /internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt".
> 
> NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail
readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
> 
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> -----
> To:
> Subject:
> Date: Tue, 9 Apr 2002 09:51:14 -0400
> X-Mailer: Internet Mail Service (5.5.2653.19)
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 
>                Name: ATT64470
>    ATT64470    Type: unspecified type (application/octet-stream)
>            Encoding: x-uuencode
> 
>                                          Name:
draft-taylor-mmusic-sdp-tdm-01.url
>    draft-taylor-mmusic-sdp-tdm-01.url    Type: Internet Shortcut
(application/x-unknown-content-type-InternetShortcut)
>                                      Encoding: x-uuencode


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


From daemon@optimus.ietf.org  Tue Apr 30 08:34: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 IAA16660
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 08:34:00 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA20376
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 08:34:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18569;
	Tue, 30 Apr 2002 08:13:28 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA18499
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 08:13:22 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15362;
	Tue, 30 Apr 2002 08:13:15 -0400 (EDT)
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 g3UCCjd07313;
	Tue, 30 Apr 2002 08:12:45 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78A24>; Tue, 30 Apr 2002 08:12:49 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3B2@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>,
        "'mmusic@ietf.org'"
	 <mmusic@ietf.org>
Date: Tue, 30 Apr 2002 08:12:48 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] RE: [MMUSIC] FW: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.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

The whole point of the draft is to relieve MGs of the necessity to
understand legacy telephony signalling protocols.  I will allow the WGs to
comment on whether this is the right approach, since your proposal is
obviously a workable alternative.

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Monday, April 29, 2002 9:46 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]
Cc: 'megaco@ietf.org'; 'mmusic@ietf.org'
Subject: Re: [MMUSIC] FW: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.txt


G'Day Tom,

I've been having a look at the TDM draft and my main comment is regarding
mainly
section 4 TDM attributes although it may have some flow on effects. Whilst
the
list of attributes is rather comprehensive it seems to me that this is a
duplication of already defined values. All of the values can be represented
by
the User Service Information (USI) Q.763 / Bearer Capability information
element
Q.931. Given that TDM terminations will most likely be used in scenarios
where
the Call control will be BICC/ISUP/Q.931 the USI will be available in the
MGC in
the native USI format. It seems pointless to translate the values from
native
USI format to a SDP format where each sub-value of the USI is defined as
seperate attributes. An attribute to carry USI has already been defined in
the
SG11 work for BICC ie.
a=isup_usi: <value of USI in hex digits as specified in ITU-T Q.1902.3/§
6.102
[5]>
The left most hex digit pair (e.g. EF in the following sequence EF 23 12 13)
represents the first binary octet that would be transmitted as per Q.1902.3
§
5.10.)

By specifying that a=isup_usi be used instead of the values in section it
will
mean that currently defined vertical protocol for ISUP and BICC will be
consistant with your draft.

Regards, Christian

Tom-PT Taylor wrote:
> 
> I have recycled this document at last.  Material relating to Nx64 kbit/s
or
> multilink operation has been stripped out, and material relating to H.320
> and H.324 sessions has been modified to conform to the latest views of how
> Megaco operates.  I forgot to put in the MIME registrations for
audio/PCMU,
> audio/PCMA, audio/G726xx, and application/octet-stream all over TDM
> transport, but I'll do that on the next pass.
> 
> I sent a copy to Jim Renkel, who had urged that requirements for
> CAS-signalled TDM be taken into account when I first presented this to
> MMUSIC.  I have no idea what additional requirements he has in mind, but
> I'll see.  In the meantime, does anyone else have comments?  We need this
> for NAS operation.
> 
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Tuesday, April 09, 2002 8:41 AM
> Subject: I-D ACTION:draft-taylor-mmusic-sdp-tdm-01.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
>         Title           : Conventions for the use of the Session
Description
> 
>                           Protocol (SDP)for Digital Circuit Connections
>         Author(s)       : T. Taylor
>         Filename        : draft-taylor-mmusic-sdp-tdm-01.txt
>         Pages           : 14
>         Date            : 08-Apr-02
> 
> This document describes conventions for using the Session
> Description Protocol (SDP) for controlling digital circuits.  These
> conventions describe
> - circuit addressing conventions for use on the SDP 'c=' line
> - content of the 'm=' line(s) for digital circuits
> - attributes to convey the parameters contained within the Bearer
> Capability, Low Layer Compatibility, and High Layer Compatibility
> Information Elements of ITU-T Recommendation Q.931.
> These conventions have been defined for use in media gateway
> control, particularly in support of NAS operation, but may also be
> used by IP-based call signalling schemes (SIP, BICC) to control
> media exchange over digital circuits.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt
> 
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the
message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the
username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-taylor-mmusic-sdp-tdm-01.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
>         mailserv@ietf.org.
> In the body type:
>         "FILE /internet-drafts/draft-taylor-mmusic-sdp-tdm-01.txt".
> 
> NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail
readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
> 
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> -----
> To:
> Subject:
> Date: Tue, 9 Apr 2002 09:51:14 -0400
> X-Mailer: Internet Mail Service (5.5.2653.19)
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www1.ietf.org/mailman/listinfo/mmusic
> 
>                Name: ATT64470
>    ATT64470    Type: unspecified type (application/octet-stream)
>            Encoding: x-uuencode
> 
>                                          Name:
draft-taylor-mmusic-sdp-tdm-01.url
>    draft-taylor-mmusic-sdp-tdm-01.url    Type: Internet Shortcut
(application/x-unknown-content-type-InternetShortcut)
>                                      Encoding: x-uuencode


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



From megaco-admin@ietf.org  Tue Apr 30 09:13: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 JAA18870
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 09:13:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21087;
	Tue, 30 Apr 2002 08:43:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21061
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 08:43:56 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17576
	for <megaco@ietf.org>; Tue, 30 Apr 2002 08:43:53 -0400 (EDT)
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 g3UChNd08774
	for <megaco@ietf.org>; Tue, 30 Apr 2002 08:43:23 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78BA6>; Tue, 30 Apr 2002 08:43:27 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3B6@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'SRD Wang JuLin'" <WangJL2@sbell.com.cn>, An Leurs <ALeurs@alcatel.de>,
        "Megaco (E-mail)" <megaco@ietf.org>,
        "MadhuBabu Brahmanapally (E-mail)"
	 <madhubabu@kenetec.com>
Cc: Albrecht Schwarz <Albrecht.Schwarz@alcatel.de>,
        Patrick Villarin
	 <Patrick.Villarin@alcatel.be>,
        Van Opstal Jan
	 <jan.van_opstal@alcatel.be>
Subject: RE: [Megaco] About RGW PBX application
Date: Tue, 30 Apr 2002 08:43:27 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Why does the callee side need the ext number?  Normally it is up to the MGC
to translate between the called number and a terminationID representing the
called party in the destination RGW.

-----Original Message-----
From: SRD Wang JuLin [mailto:WangJL2@sbell.com.cn]
Sent: Tuesday, April 30, 2002 4:48 AM
To: An Leurs; Megaco (E-mail); MadhuBabu Brahmanapally (E-mail)
Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
Subject: [Megaco] About RGW PBX application


Hi,
 
Currently,we are take consideration of RGW (FXS type)PBX application.I have
a question to consult:
Suppose that the caller located in one RGW firstly dial a number to connect
to the PBX which are lined to another RGW. After call connected and
establish rtp stream,the  PBX will send dialtone directly to the caller
indicating the caller  to dial the ext(callee's) number (callee lined to the
PBX).So the caller can send the  ext number to Softswtich in Notify
message.(use dtmf inband transfer is another case)But i wonder how can the
Softswtich send the ext number to the callee side?Use dg package???
Pls clear my mind about it!
Thanks a lot! 
 
best  regards 
JJerry Wang 
tel:(8621)58541240 ext 9615 
mailto:wangjl2@sbell.com.cn 
Shanghai Bell Co.LTD 
 

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


From daemon@optimus.ietf.org  Tue Apr 30 09:13: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 JAA18884
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 09:13:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA22722
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 09:13:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21087;
	Tue, 30 Apr 2002 08:43:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21061
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 08:43:56 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17576
	for <megaco@ietf.org>; Tue, 30 Apr 2002 08:43:53 -0400 (EDT)
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 g3UChNd08774
	for <megaco@ietf.org>; Tue, 30 Apr 2002 08:43:23 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78BA6>; Tue, 30 Apr 2002 08:43:27 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3B6@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'SRD Wang JuLin'" <WangJL2@sbell.com.cn>, An Leurs <ALeurs@alcatel.de>,
        "Megaco (E-mail)" <megaco@ietf.org>,
        "MadhuBabu Brahmanapally (E-mail)"
	 <madhubabu@kenetec.com>
Cc: Albrecht Schwarz <Albrecht.Schwarz@alcatel.de>,
        Patrick Villarin
	 <Patrick.Villarin@alcatel.be>,
        Van Opstal Jan
	 <jan.van_opstal@alcatel.be>
Subject: RE: [Megaco] About RGW PBX application
Date: Tue, 30 Apr 2002 08:43:27 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Why does the callee side need the ext number?  Normally it is up to the MGC
to translate between the called number and a terminationID representing the
called party in the destination RGW.

-----Original Message-----
From: SRD Wang JuLin [mailto:WangJL2@sbell.com.cn]
Sent: Tuesday, April 30, 2002 4:48 AM
To: An Leurs; Megaco (E-mail); MadhuBabu Brahmanapally (E-mail)
Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
Subject: [Megaco] About RGW PBX application


Hi,
 
Currently,we are take consideration of RGW (FXS type)PBX application.I have
a question to consult:
Suppose that the caller located in one RGW firstly dial a number to connect
to the PBX which are lined to another RGW. After call connected and
establish rtp stream,the  PBX will send dialtone directly to the caller
indicating the caller  to dial the ext(callee's) number (callee lined to the
PBX).So the caller can send the  ext number to Softswtich in Notify
message.(use dtmf inband transfer is another case)But i wonder how can the
Softswtich send the ext number to the callee side?Use dg package???
Pls clear my mind about it!
Thanks a lot! 
 
best  regards 
JJerry Wang 
tel:(8621)58541240 ext 9615 
mailto:wangjl2@sbell.com.cn 
Shanghai Bell Co.LTD 
 

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



From megaco-admin@ietf.org  Tue Apr 30 09:31: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 JAA19590
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 09:31:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA22512;
	Tue, 30 Apr 2002 09:08:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA22482
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 09:08:42 -0400 (EDT)
Received: from telesoft.indts.com (IDENT:root@[164.164.71.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18649
	for <megaco@ietf.org>; Tue, 30 Apr 2002 09:08:34 -0400 (EDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id SAA27490;
	Tue, 30 Apr 2002 18:37:08 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <GWSJC41P>; Tue, 30 Apr 2002 18:41:59 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337263B3CE@INDTS_FS>
From: Anil Jangam <anilj@indts.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'SRD Wang JuLin'"
	 <WangJL2@sbell.com.cn>,
        An Leurs <ALeurs@alcatel.de>, "Megaco (E-mail)"
	 <megaco@ietf.org>,
        "MadhuBabu Brahmanapally (E-mail)"
	 <madhubabu@kenetec.com>
Cc: Albrecht Schwarz <Albrecht.Schwarz@alcatel.de>,
        Patrick Villarin
	 <Patrick.Villarin@alcatel.be>,
        Van Opstal Jan
	 <jan.van_opstal@alcatel.be>
Subject: RE: [Megaco] About RGW PBX application
Date: Tue, 30 Apr 2002 18:41:59 +0530
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

Hi PTT,

this is a typical scenario as follows.
Tel1 --> RGW1 --> Softswitch ---> RGW2 ---> PBX ---> Tel2.
In this case, the PBX is one of the endpoints configured on the RGW2, and
also would have been configured as one of the route in softswitch (I assume
that both the gateways are configured in the same softswitch). Now the call
is assumed to be established between the caller and the callee (in this set
up case, it is PBX), and then once the media is established, PBX would play
a file asking to dial the ext number. Once the PBX receives the digits, it
will send an alert to the ext inside its own network.

The question, here is in the context... how the dialed digits (after the
media is established) are being passed to the PBX. One method is to send the
inband DTMF, which has inherent problems of low frequency signal
transmission (I took the reference of the link:
http://www.cs.columbia.edu/sip/drafts/draft-sinnreich-sigdevctrl-00.txt see
6.2. DTMF Signaling Issues). 

In case of out of band digit transmission, the RGW1 can be programmed to
send NTFY (in case of MGCP) to the softswitch. But I couldn't find out how
the softswitch would inform it to the RGW2, and ultimately to the PBX.

/anil.

> -----Original Message-----
> From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Tuesday, April 30, 2002 6:13 PM
> To: 'SRD Wang JuLin'; An Leurs; Megaco (E-mail); MadhuBabu 
> Brahmanapally
> (E-mail)
> Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
> Subject: RE: [Megaco] About RGW PBX application
> 
> 
> Why does the callee side need the ext number?  Normally it is 
> up to the MGC
> to translate between the called number and a terminationID 
> representing the
> called party in the destination RGW.
> 
> -----Original Message-----
> From: SRD Wang JuLin [mailto:WangJL2@sbell.com.cn]
> Sent: Tuesday, April 30, 2002 4:48 AM
> To: An Leurs; Megaco (E-mail); MadhuBabu Brahmanapally (E-mail)
> Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
> Subject: [Megaco] About RGW PBX application
> 
> 
> Hi,
>  
> Currently,we are take consideration of RGW (FXS type)PBX 
> application.I have
> a question to consult:
> Suppose that the caller located in one RGW firstly dial a 
> number to connect
> to the PBX which are lined to another RGW. After call connected and
> establish rtp stream,the  PBX will send dialtone directly to 
> the caller
> indicating the caller  to dial the ext(callee's) number 
> (callee lined to the
> PBX).So the caller can send the  ext number to Softswtich in Notify
> message.(use dtmf inband transfer is another case)But i 
> wonder how can the
> Softswtich send the ext number to the callee side?Use dg package???
> Pls clear my mind about it!
> Thanks a lot! 
>  
> best  regards 
> JJerry Wang 
> tel:(8621)58541240 ext 9615 
> mailto:wangjl2@sbell.com.cn 
> Shanghai Bell Co.LTD 
>  
> 
> _______________________________________________
> Megaco mailing list
> 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 Apr 30 09:31: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 JAA19601
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 09:31:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA23816
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 09:31:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA22512;
	Tue, 30 Apr 2002 09:08:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA22482
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 09:08:42 -0400 (EDT)
Received: from telesoft.indts.com (IDENT:root@[164.164.71.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18649
	for <megaco@ietf.org>; Tue, 30 Apr 2002 09:08:34 -0400 (EDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id SAA27490;
	Tue, 30 Apr 2002 18:37:08 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <GWSJC41P>; Tue, 30 Apr 2002 18:41:59 +0530
Message-ID: <F73B646FCC01D5118F530002B32C337263B3CE@INDTS_FS>
From: Anil Jangam <anilj@indts.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        "'SRD Wang JuLin'"
	 <WangJL2@sbell.com.cn>,
        An Leurs <ALeurs@alcatel.de>, "Megaco (E-mail)"
	 <megaco@ietf.org>,
        "MadhuBabu Brahmanapally (E-mail)"
	 <madhubabu@kenetec.com>
Cc: Albrecht Schwarz <Albrecht.Schwarz@alcatel.de>,
        Patrick Villarin
	 <Patrick.Villarin@alcatel.be>,
        Van Opstal Jan
	 <jan.van_opstal@alcatel.be>
Subject: RE: [Megaco] About RGW PBX application
Date: Tue, 30 Apr 2002 18:41:59 +0530
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

Hi PTT,

this is a typical scenario as follows.
Tel1 --> RGW1 --> Softswitch ---> RGW2 ---> PBX ---> Tel2.
In this case, the PBX is one of the endpoints configured on the RGW2, and
also would have been configured as one of the route in softswitch (I assume
that both the gateways are configured in the same softswitch). Now the call
is assumed to be established between the caller and the callee (in this set
up case, it is PBX), and then once the media is established, PBX would play
a file asking to dial the ext number. Once the PBX receives the digits, it
will send an alert to the ext inside its own network.

The question, here is in the context... how the dialed digits (after the
media is established) are being passed to the PBX. One method is to send the
inband DTMF, which has inherent problems of low frequency signal
transmission (I took the reference of the link:
http://www.cs.columbia.edu/sip/drafts/draft-sinnreich-sigdevctrl-00.txt see
6.2. DTMF Signaling Issues). 

In case of out of band digit transmission, the RGW1 can be programmed to
send NTFY (in case of MGCP) to the softswitch. But I couldn't find out how
the softswitch would inform it to the RGW2, and ultimately to the PBX.

/anil.

> -----Original Message-----
> From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Tuesday, April 30, 2002 6:13 PM
> To: 'SRD Wang JuLin'; An Leurs; Megaco (E-mail); MadhuBabu 
> Brahmanapally
> (E-mail)
> Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
> Subject: RE: [Megaco] About RGW PBX application
> 
> 
> Why does the callee side need the ext number?  Normally it is 
> up to the MGC
> to translate between the called number and a terminationID 
> representing the
> called party in the destination RGW.
> 
> -----Original Message-----
> From: SRD Wang JuLin [mailto:WangJL2@sbell.com.cn]
> Sent: Tuesday, April 30, 2002 4:48 AM
> To: An Leurs; Megaco (E-mail); MadhuBabu Brahmanapally (E-mail)
> Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
> Subject: [Megaco] About RGW PBX application
> 
> 
> Hi,
>  
> Currently,we are take consideration of RGW (FXS type)PBX 
> application.I have
> a question to consult:
> Suppose that the caller located in one RGW firstly dial a 
> number to connect
> to the PBX which are lined to another RGW. After call connected and
> establish rtp stream,the  PBX will send dialtone directly to 
> the caller
> indicating the caller  to dial the ext(callee's) number 
> (callee lined to the
> PBX).So the caller can send the  ext number to Softswtich in Notify
> message.(use dtmf inband transfer is another case)But i 
> wonder how can the
> Softswtich send the ext number to the callee side?Use dg package???
> Pls clear my mind about it!
> Thanks a lot! 
>  
> best  regards 
> JJerry Wang 
> tel:(8621)58541240 ext 9615 
> mailto:wangjl2@sbell.com.cn 
> Shanghai Bell Co.LTD 
>  
> 
> _______________________________________________
> Megaco mailing list
> 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 Apr 30 09: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 JAA20104
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 09:45:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA23139;
	Tue, 30 Apr 2002 09:24:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA23110
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 09:24:02 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19261
	for <megaco@ietf.org>; Tue, 30 Apr 2002 09:23:58 -0400 (EDT)
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 g3UDMqd14132;
	Tue, 30 Apr 2002 09:22:52 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78CQY>; Tue, 30 Apr 2002 09:22:56 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3BA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Anil Jangam'" <anilj@indts.com>,
        "'SRD Wang JuLin'"
	 <WangJL2@sbell.com.cn>,
        An Leurs <ALeurs@alcatel.de>, "Megaco (E-mail)"
	 <megaco@ietf.org>,
        "MadhuBabu Brahmanapally (E-mail)"
	 <madhubabu@kenetec.com>
Cc: Albrecht Schwarz <Albrecht.Schwarz@alcatel.de>,
        Patrick Villarin
	 <Patrick.Villarin@alcatel.be>,
        Van Opstal Jan
	 <jan.van_opstal@alcatel.be>
Subject: RE: [Megaco] About RGW PBX application
Date: Tue, 30 Apr 2002 09:22:55 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Occasionally one encounters PBXs where DTMF signalling is used over the
trunks.  I would think it more common these days for the PBX to use PRI,
H.323, or SIP for call signalling.  That means that the linear diagram you
show below looks more like this (in the PRI case):

            Softswitch
            /     \  \
           /Megaco \  \Q.931/IUA/SCTP/IP
          /         \  \
     ----------   ----------
     |  MG1   |   |  MG2   |
     |        |   |        |
     ----------   ----------
         |            |  T1 or E1      --------
        Tel           -----------------|  PBX |
                                       --------

That rightmost line up to the Softswitch is a Sigtran connection carrying
the PRI signalling from the PBX.  The box containing MG2 also incorporates
Signalling Gateway (SG) functionality as defined by RFC 2719.

-----Original Message-----
From: Anil Jangam [mailto:anilj@indts.com]
Sent: Tuesday, April 30, 2002 9:12 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; 'SRD Wang JuLin'; An Leurs; Megaco
(E-mail); MadhuBabu Brahmanapally (E-mail)
Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
Subject: RE: [Megaco] About RGW PBX application


Hi PTT,

this is a typical scenario as follows.
Tel1 --> RGW1 --> Softswitch ---> RGW2 ---> PBX ---> Tel2.
In this case, the PBX is one of the endpoints configured on the RGW2, and
also would have been configured as one of the route in softswitch (I assume
that both the gateways are configured in the same softswitch). Now the call
is assumed to be established between the caller and the callee (in this set
up case, it is PBX), and then once the media is established, PBX would play
a file asking to dial the ext number. Once the PBX receives the digits, it
will send an alert to the ext inside its own network.

The question, here is in the context... how the dialed digits (after the
media is established) are being passed to the PBX. One method is to send the
inband DTMF, which has inherent problems of low frequency signal
transmission (I took the reference of the link:
http://www.cs.columbia.edu/sip/drafts/draft-sinnreich-sigdevctrl-00.txt see
6.2. DTMF Signaling Issues). 

In case of out of band digit transmission, the RGW1 can be programmed to
send NTFY (in case of MGCP) to the softswitch. But I couldn't find out how
the softswitch would inform it to the RGW2, and ultimately to the PBX.

/anil.

> -----Original Message-----
> From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Tuesday, April 30, 2002 6:13 PM
> To: 'SRD Wang JuLin'; An Leurs; Megaco (E-mail); MadhuBabu 
> Brahmanapally
> (E-mail)
> Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
> Subject: RE: [Megaco] About RGW PBX application
> 
> 
> Why does the callee side need the ext number?  Normally it is 
> up to the MGC
> to translate between the called number and a terminationID 
> representing the
> called party in the destination RGW.
> 
> -----Original Message-----
> From: SRD Wang JuLin [mailto:WangJL2@sbell.com.cn]
> Sent: Tuesday, April 30, 2002 4:48 AM
> To: An Leurs; Megaco (E-mail); MadhuBabu Brahmanapally (E-mail)
> Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
> Subject: [Megaco] About RGW PBX application
> 
> 
> Hi,
>  
> Currently,we are take consideration of RGW (FXS type)PBX 
> application.I have
> a question to consult:
> Suppose that the caller located in one RGW firstly dial a 
> number to connect
> to the PBX which are lined to another RGW. After call connected and
> establish rtp stream,the  PBX will send dialtone directly to 
> the caller
> indicating the caller  to dial the ext(callee's) number 
> (callee lined to the
> PBX).So the caller can send the  ext number to Softswtich in Notify
> message.(use dtmf inband transfer is another case)But i 
> wonder how can the
> Softswtich send the ext number to the callee side?Use dg package???
> Pls clear my mind about it!
> Thanks a lot! 
>  
> best  regards 
> JJerry Wang 
> tel:(8621)58541240 ext 9615 
> mailto:wangjl2@sbell.com.cn 
> Shanghai Bell Co.LTD 
>  
> 
> _______________________________________________
> Megaco mailing list
> 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 Apr 30 09: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 JAA20120
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 09:45:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA24705
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 09:45:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA23139;
	Tue, 30 Apr 2002 09:24:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA23110
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 09:24:02 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19261
	for <megaco@ietf.org>; Tue, 30 Apr 2002 09:23:58 -0400 (EDT)
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 g3UDMqd14132;
	Tue, 30 Apr 2002 09:22:52 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78CQY>; Tue, 30 Apr 2002 09:22:56 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3BA@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Anil Jangam'" <anilj@indts.com>,
        "'SRD Wang JuLin'"
	 <WangJL2@sbell.com.cn>,
        An Leurs <ALeurs@alcatel.de>, "Megaco (E-mail)"
	 <megaco@ietf.org>,
        "MadhuBabu Brahmanapally (E-mail)"
	 <madhubabu@kenetec.com>
Cc: Albrecht Schwarz <Albrecht.Schwarz@alcatel.de>,
        Patrick Villarin
	 <Patrick.Villarin@alcatel.be>,
        Van Opstal Jan
	 <jan.van_opstal@alcatel.be>
Subject: RE: [Megaco] About RGW PBX application
Date: Tue, 30 Apr 2002 09:22:55 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Occasionally one encounters PBXs where DTMF signalling is used over the
trunks.  I would think it more common these days for the PBX to use PRI,
H.323, or SIP for call signalling.  That means that the linear diagram you
show below looks more like this (in the PRI case):

            Softswitch
            /     \  \
           /Megaco \  \Q.931/IUA/SCTP/IP
          /         \  \
     ----------   ----------
     |  MG1   |   |  MG2   |
     |        |   |        |
     ----------   ----------
         |            |  T1 or E1      --------
        Tel           -----------------|  PBX |
                                       --------

That rightmost line up to the Softswitch is a Sigtran connection carrying
the PRI signalling from the PBX.  The box containing MG2 also incorporates
Signalling Gateway (SG) functionality as defined by RFC 2719.

-----Original Message-----
From: Anil Jangam [mailto:anilj@indts.com]
Sent: Tuesday, April 30, 2002 9:12 AM
To: Taylor, Tom-PT [CAR:B800:EXCH]; 'SRD Wang JuLin'; An Leurs; Megaco
(E-mail); MadhuBabu Brahmanapally (E-mail)
Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
Subject: RE: [Megaco] About RGW PBX application


Hi PTT,

this is a typical scenario as follows.
Tel1 --> RGW1 --> Softswitch ---> RGW2 ---> PBX ---> Tel2.
In this case, the PBX is one of the endpoints configured on the RGW2, and
also would have been configured as one of the route in softswitch (I assume
that both the gateways are configured in the same softswitch). Now the call
is assumed to be established between the caller and the callee (in this set
up case, it is PBX), and then once the media is established, PBX would play
a file asking to dial the ext number. Once the PBX receives the digits, it
will send an alert to the ext inside its own network.

The question, here is in the context... how the dialed digits (after the
media is established) are being passed to the PBX. One method is to send the
inband DTMF, which has inherent problems of low frequency signal
transmission (I took the reference of the link:
http://www.cs.columbia.edu/sip/drafts/draft-sinnreich-sigdevctrl-00.txt see
6.2. DTMF Signaling Issues). 

In case of out of band digit transmission, the RGW1 can be programmed to
send NTFY (in case of MGCP) to the softswitch. But I couldn't find out how
the softswitch would inform it to the RGW2, and ultimately to the PBX.

/anil.

> -----Original Message-----
> From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Tuesday, April 30, 2002 6:13 PM
> To: 'SRD Wang JuLin'; An Leurs; Megaco (E-mail); MadhuBabu 
> Brahmanapally
> (E-mail)
> Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
> Subject: RE: [Megaco] About RGW PBX application
> 
> 
> Why does the callee side need the ext number?  Normally it is 
> up to the MGC
> to translate between the called number and a terminationID 
> representing the
> called party in the destination RGW.
> 
> -----Original Message-----
> From: SRD Wang JuLin [mailto:WangJL2@sbell.com.cn]
> Sent: Tuesday, April 30, 2002 4:48 AM
> To: An Leurs; Megaco (E-mail); MadhuBabu Brahmanapally (E-mail)
> Cc: Albrecht Schwarz; Patrick Villarin; Van Opstal Jan
> Subject: [Megaco] About RGW PBX application
> 
> 
> Hi,
>  
> Currently,we are take consideration of RGW (FXS type)PBX 
> application.I have
> a question to consult:
> Suppose that the caller located in one RGW firstly dial a 
> number to connect
> to the PBX which are lined to another RGW. After call connected and
> establish rtp stream,the  PBX will send dialtone directly to 
> the caller
> indicating the caller  to dial the ext(callee's) number 
> (callee lined to the
> PBX).So the caller can send the  ext number to Softswtich in Notify
> message.(use dtmf inband transfer is another case)But i 
> wonder how can the
> Softswtich send the ext number to the callee side?Use dg package???
> Pls clear my mind about it!
> Thanks a lot! 
>  
> best  regards 
> JJerry Wang 
> tel:(8621)58541240 ext 9615 
> mailto:wangjl2@sbell.com.cn 
> Shanghai Bell Co.LTD 
>  
> 
> _______________________________________________
> Megaco mailing list
> 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 Apr 30 10:15: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 KAA21452
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 10:15:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24767;
	Tue, 30 Apr 2002 09:45:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24738
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 09:45:54 -0400 (EDT)
Received: from mxout1.netvision.net.il (mxout1.netvision.net.il [194.90.9.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20161
	for <megaco@ietf.org>; Tue, 30 Apr 2002 09:45:50 -0400 (EDT)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout1.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GVD002I0VJFHN@mxout1.netvision.net.il> for megaco@ietf.org;
 Tue, 30 Apr 2002 16:45:16 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <2VF08613>; Tue, 30 Apr 2002 16:43:48 +0300
Content-return: allowed
Date: Tue, 30 Apr 2002 16:43:47 +0300
From: Dan Elbert <delbert@radvision.com>
To: "Megaco (E-mail)" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B01FCF320@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
Subject: [Megaco] ServiceChangeAddress 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 All
Do we have anywhere a strict definition saying that the ServiceChangeAddress
parameter MUST be a port number for IP transport?
Leaving this so loosely defined can open the door to compatibility problems
if use of this feature is intended.

Dan Elbert
RADVISION

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


From daemon@optimus.ietf.org  Tue Apr 30 10:15: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 KAA21462
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 10:15:19 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA27260
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 10:15:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24767;
	Tue, 30 Apr 2002 09:45:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA24738
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 09:45:54 -0400 (EDT)
Received: from mxout1.netvision.net.il (mxout1.netvision.net.il [194.90.9.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20161
	for <megaco@ietf.org>; Tue, 30 Apr 2002 09:45:50 -0400 (EDT)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout1.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GVD002I0VJFHN@mxout1.netvision.net.il> for megaco@ietf.org;
 Tue, 30 Apr 2002 16:45:16 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <2VF08613>; Tue, 30 Apr 2002 16:43:48 +0300
Content-return: allowed
Date: Tue, 30 Apr 2002 16:43:47 +0300
From: Dan Elbert <delbert@radvision.com>
To: "Megaco (E-mail)" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B01FCF320@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
Subject: [Megaco] ServiceChangeAddress 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 All
Do we have anywhere a strict definition saying that the ServiceChangeAddress
parameter MUST be a port number for IP transport?
Leaving this so loosely defined can open the door to compatibility problems
if use of this feature is intended.

Dan Elbert
RADVISION

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



From megaco-admin@ietf.org  Tue Apr 30 14:04: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 OAA01743
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:04:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11139;
	Tue, 30 Apr 2002 13:34:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11101
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 13:33:59 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00131
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:33:56 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3UHXRL27986
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:33:27 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78K0Z>; Tue, 30 Apr 2002 13:33:27 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3C3@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Dan Elbert'" <delbert@radvision.com>,
        "Megaco (E-mail)"
	 <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChangeAddress parameter
Date: Tue, 30 Apr 2002 13:33:25 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Must we have this restriction?  I can see instances where an MGC is
multi-homed (or is in fact two separate physical devices tied together in
close synchronism), and the listening address happens to differ from the
working address the MGC wants to assign to the control session.

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Tuesday, April 30, 2002 9:44 AM
To: Megaco (E-mail)
Subject: [Megaco] ServiceChangeAddress parameter


Hi All
Do we have anywhere a strict definition saying that the ServiceChangeAddress
parameter MUST be a port number for IP transport?
Leaving this so loosely defined can open the door to compatibility problems
if use of this feature is intended.

Dan Elbert
RADVISION

_______________________________________________
Megaco mailing list
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 Apr 30 14:04: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 OAA01756
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:04:04 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA14019
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 14:04:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11139;
	Tue, 30 Apr 2002 13:34:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11101
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 13:33:59 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00131
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:33:56 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3UHXRL27986
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:33:27 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78K0Z>; Tue, 30 Apr 2002 13:33:27 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3C3@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Dan Elbert'" <delbert@radvision.com>,
        "Megaco (E-mail)"
	 <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChangeAddress parameter
Date: Tue, 30 Apr 2002 13:33:25 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

Must we have this restriction?  I can see instances where an MGC is
multi-homed (or is in fact two separate physical devices tied together in
close synchronism), and the listening address happens to differ from the
working address the MGC wants to assign to the control session.

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Tuesday, April 30, 2002 9:44 AM
To: Megaco (E-mail)
Subject: [Megaco] ServiceChangeAddress parameter


Hi All
Do we have anywhere a strict definition saying that the ServiceChangeAddress
parameter MUST be a port number for IP transport?
Leaving this so loosely defined can open the door to compatibility problems
if use of this feature is intended.

Dan Elbert
RADVISION

_______________________________________________
Megaco mailing list
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 Apr 30 14:04: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 OAA01777
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:04:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10360;
	Tue, 30 Apr 2002 13:29:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10326
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 13:29:16 -0400 (EDT)
Received: from zrc2s0jx.us.nortel.com (zrc2s0jx.nortelnetworks.com [47.103.122.112])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29950
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:29:13 -0400 (EDT)
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.us.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3UHSnN05788
	for <megaco@ietf.org>; Tue, 30 Apr 2002 12:28:49 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <J4QHSJB7>; Tue, 30 Apr 2002 12:28:44 -0500
Message-ID: <A19D67E3240DD511960200508BF93BF20582CC1F@zrc2c002.us.nortel.com>
From: "Mark Sellers"<sellers@nortelnetworks.com>
To: megaco@ietf.org
Date: Tue, 30 Apr 2002 12:28:44 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1F06C.7A5A0A60"
Subject: [Megaco] unsubscribe 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

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_01C1F06C.7A5A0A60
Content-Type: text/plain;
	charset="iso-8859-1"



------_=_NextPart_001_01C1F06C.7A5A0A60
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.2654.89">
<TITLE>unsubscribe megaco</TITLE>
</HEAD>
<BODY>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1F06C.7A5A0A60--

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


From daemon@optimus.ietf.org  Tue Apr 30 14:04: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 OAA01790
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:04:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA14054
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 14:04:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10360;
	Tue, 30 Apr 2002 13:29:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10326
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 13:29:16 -0400 (EDT)
Received: from zrc2s0jx.us.nortel.com (zrc2s0jx.nortelnetworks.com [47.103.122.112])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29950
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:29:13 -0400 (EDT)
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.us.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3UHSnN05788
	for <megaco@ietf.org>; Tue, 30 Apr 2002 12:28:49 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <J4QHSJB7>; Tue, 30 Apr 2002 12:28:44 -0500
Message-ID: <A19D67E3240DD511960200508BF93BF20582CC1F@zrc2c002.us.nortel.com>
From: "Mark Sellers"<sellers@nortelnetworks.com>
To: megaco@ietf.org
Date: Tue, 30 Apr 2002 12:28:44 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1F06C.7A5A0A60"
Subject: [Megaco] unsubscribe 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

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_01C1F06C.7A5A0A60
Content-Type: text/plain;
	charset="iso-8859-1"



------_=_NextPart_001_01C1F06C.7A5A0A60
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.2654.89">
<TITLE>unsubscribe megaco</TITLE>
</HEAD>
<BODY>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C1F06C.7A5A0A60--

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



From megaco-admin@ietf.org  Tue Apr 30 14:08: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 OAA01985
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:08:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11734;
	Tue, 30 Apr 2002 13:43:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11700
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 13:43:30 -0400 (EDT)
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 NAA00523
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:43:27 -0400 (EDT)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.42 2002/04/26 23:25:13 root Exp $) with ESMTP id g3UHiG900433
	for <megaco@ietf.org>; Tue, 30 Apr 2002 17:44:16 GMT
Received: from fmsmsxvs043.fm.intel.com (fmsmsxv043-1.fm.intel.com [132.233.48.128])
	by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.17 2002/04/27 00:24:04 root Exp $) with SMTP id g3UHjf418365
	for <megaco@ietf.org>; Tue, 30 Apr 2002 17:45:41 GMT
Received: from FMSMSX017.fm.intel.com ([132.233.42.196])
 by fmsmsxvs043.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002043010422232035
 ; Tue, 30 Apr 2002 10:42:23 -0700
Received: by fmsmsx017.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <J8W6409Y>; Tue, 30 Apr 2002 10:43:18 -0700
Message-ID: <F1CE15E08172D4119247009027AE9D50187481E0@FMSMSX37>
From: "Kaul, Bharat" <bharat@trillium.com>
To: "'Dan Elbert'" <delbert@radvision.com>,
        "'Tom-PT Taylor'"<taylor@nortelnetworks.com>,
        "Megaco (E-mail)" <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChangeAddress parameter
Date: Tue, 30 Apr 2002 10:43:10 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1F06E.7ECFF030"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1F06E.7ECFF030
Content-Type: text/plain;
	charset="iso-8859-1"

I think what Tom meant was that for multi-homed MGC case, one MID will map
to multiple physical IP addresses. New mgcId would mean a different MID
altogether and hence a different device from a concept point of view.

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Tuesday, April 30, 2002 10:34 AM
To: 'Tom-PT Taylor'; Dan Elbert; Megaco (E-mail)
Subject: RE: [Megaco] ServiceChangeAddress parameter



Wouldn't in that case a new mgcId be more appropiated ?

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Tuesday, April 30, 2002 8:33 PM
To: 'Dan Elbert'; Megaco (E-mail)
Subject: RE: [Megaco] ServiceChangeAddress parameter



Must we have this restriction?  I can see instances where an MGC is
multi-homed (or is in fact two separate physical devices tied together in
close synchronism), and the listening address happens to differ from the
working address the MGC wants to assign to the control session.

-----Original Message----- 
From: Dan Elbert [ mailto:delbert@radvision.com
<mailto:delbert@radvision.com> ] 
Sent: Tuesday, April 30, 2002 9:44 AM 
To: Megaco (E-mail) 
Subject: [Megaco] ServiceChangeAddress parameter 


Hi All 
Do we have anywhere a strict definition saying that the ServiceChangeAddress

parameter MUST be a port number for IP transport? 
Leaving this so loosely defined can open the door to compatibility problems 
if use of this feature is intended. 

Dan Elbert 
RADVISION 

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


------_=_NextPart_001_01C1F06E.7ECFF030
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] ServiceChangeAddress parameter</TITLE>

<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=450434017-30042002><FONT face=Arial color=#008080><STRONG>I 
think what Tom meant was that for multi-homed MGC case, one MID will map to 
multiple physical IP addresses. New mgcId would mean a different MID altogether 
and hence a different device from a concept point of 
view.</STRONG></FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Dan Elbert 
  [mailto:delbert@radvision.com]<BR><B>Sent:</B> Tuesday, April 30, 2002 10:34 
  AM<BR><B>To:</B> 'Tom-PT Taylor'; Dan Elbert; Megaco 
  (E-mail)<BR><B>Subject:</B> RE: [Megaco] ServiceChangeAddress 
  parameter<BR><BR></FONT></DIV>
  <DIV><SPAN class=919143417-30042002><FONT face=Arial color=#0000ff size=2>
  <DIV><SPAN class=780173317-30042002><FONT face=Arial color=#0000ff 
  size=2>Wouldn't in that case a new mgcId be more appropiated 
  ?</FONT></SPAN></DIV></FONT></SPAN></DIV>
  <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
    <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Tom-PT Taylor 
    [mailto:taylor@nortelnetworks.com]<BR><B>Sent:</B> Tuesday, April 30, 2002 
    8:33 PM<BR><B>To:</B> 'Dan Elbert'; Megaco (E-mail)<BR><B>Subject:</B> RE: 
    [Megaco] ServiceChangeAddress parameter<BR><BR></FONT></DIV>
    <P><FONT size=2>Must we have this restriction?&nbsp; I can see instances 
    where an MGC is multi-homed (or is in fact two separate physical devices 
    tied together in close synchronism), and the listening address happens to 
    differ from the working address the MGC wants to assign to the control 
    session.</FONT></P>
    <P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From: Dan 
    Elbert [<A 
    href="mailto:delbert@radvision.com">mailto:delbert@radvision.com</A>]</FONT> 
    <BR><FONT size=2>Sent: Tuesday, April 30, 2002 9:44 AM</FONT> <BR><FONT 
    size=2>To: Megaco (E-mail)</FONT> <BR><FONT size=2>Subject: [Megaco] 
    ServiceChangeAddress parameter</FONT> </P><BR>
    <P><FONT size=2>Hi All</FONT> <BR><FONT size=2>Do we have anywhere a strict 
    definition saying that the ServiceChangeAddress</FONT> <BR><FONT 
    size=2>parameter MUST be a port number for IP transport?</FONT> <BR><FONT 
    size=2>Leaving this so loosely defined can open the door to compatibility 
    problems</FONT> <BR><FONT size=2>if use of this feature is intended.</FONT> 
    </P>
    <P><FONT size=2>Dan Elbert</FONT> <BR><FONT size=2>RADVISION</FONT> </P>
    <P><FONT size=2>_______________________________________________</FONT> 
    <BR><FONT size=2>Megaco mailing list</FONT> <BR><FONT 
    size=2>Megaco@ietf.org</FONT> <BR><FONT size=2><A target=_blank 
    href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</A></FONT> 
    </P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1F06E.7ECFF030--

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


From daemon@optimus.ietf.org  Tue Apr 30 14:08: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 OAA01995
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:08:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA14200
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 14:08:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11734;
	Tue, 30 Apr 2002 13:43:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11700
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 13:43:30 -0400 (EDT)
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 NAA00523
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:43:27 -0400 (EDT)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39])
	by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.42 2002/04/26 23:25:13 root Exp $) with ESMTP id g3UHiG900433
	for <megaco@ietf.org>; Tue, 30 Apr 2002 17:44:16 GMT
Received: from fmsmsxvs043.fm.intel.com (fmsmsxv043-1.fm.intel.com [132.233.48.128])
	by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.17 2002/04/27 00:24:04 root Exp $) with SMTP id g3UHjf418365
	for <megaco@ietf.org>; Tue, 30 Apr 2002 17:45:41 GMT
Received: from FMSMSX017.fm.intel.com ([132.233.42.196])
 by fmsmsxvs043.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002043010422232035
 ; Tue, 30 Apr 2002 10:42:23 -0700
Received: by fmsmsx017.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <J8W6409Y>; Tue, 30 Apr 2002 10:43:18 -0700
Message-ID: <F1CE15E08172D4119247009027AE9D50187481E0@FMSMSX37>
From: "Kaul, Bharat" <bharat@trillium.com>
To: "'Dan Elbert'" <delbert@radvision.com>,
        "'Tom-PT Taylor'"<taylor@nortelnetworks.com>,
        "Megaco (E-mail)" <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChangeAddress parameter
Date: Tue, 30 Apr 2002 10:43:10 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1F06E.7ECFF030"
Sender: megaco-admin@ietf.org
Errors-To: 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_01C1F06E.7ECFF030
Content-Type: text/plain;
	charset="iso-8859-1"

I think what Tom meant was that for multi-homed MGC case, one MID will map
to multiple physical IP addresses. New mgcId would mean a different MID
altogether and hence a different device from a concept point of view.

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Tuesday, April 30, 2002 10:34 AM
To: 'Tom-PT Taylor'; Dan Elbert; Megaco (E-mail)
Subject: RE: [Megaco] ServiceChangeAddress parameter



Wouldn't in that case a new mgcId be more appropiated ?

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Tuesday, April 30, 2002 8:33 PM
To: 'Dan Elbert'; Megaco (E-mail)
Subject: RE: [Megaco] ServiceChangeAddress parameter



Must we have this restriction?  I can see instances where an MGC is
multi-homed (or is in fact two separate physical devices tied together in
close synchronism), and the listening address happens to differ from the
working address the MGC wants to assign to the control session.

-----Original Message----- 
From: Dan Elbert [ mailto:delbert@radvision.com
<mailto:delbert@radvision.com> ] 
Sent: Tuesday, April 30, 2002 9:44 AM 
To: Megaco (E-mail) 
Subject: [Megaco] ServiceChangeAddress parameter 


Hi All 
Do we have anywhere a strict definition saying that the ServiceChangeAddress

parameter MUST be a port number for IP transport? 
Leaving this so loosely defined can open the door to compatibility problems 
if use of this feature is intended. 

Dan Elbert 
RADVISION 

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


------_=_NextPart_001_01C1F06E.7ECFF030
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] ServiceChangeAddress parameter</TITLE>

<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=450434017-30042002><FONT face=Arial color=#008080><STRONG>I 
think what Tom meant was that for multi-homed MGC case, one MID will map to 
multiple physical IP addresses. New mgcId would mean a different MID altogether 
and hence a different device from a concept point of 
view.</STRONG></FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Dan Elbert 
  [mailto:delbert@radvision.com]<BR><B>Sent:</B> Tuesday, April 30, 2002 10:34 
  AM<BR><B>To:</B> 'Tom-PT Taylor'; Dan Elbert; Megaco 
  (E-mail)<BR><B>Subject:</B> RE: [Megaco] ServiceChangeAddress 
  parameter<BR><BR></FONT></DIV>
  <DIV><SPAN class=919143417-30042002><FONT face=Arial color=#0000ff size=2>
  <DIV><SPAN class=780173317-30042002><FONT face=Arial color=#0000ff 
  size=2>Wouldn't in that case a new mgcId be more appropiated 
  ?</FONT></SPAN></DIV></FONT></SPAN></DIV>
  <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
    <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
    size=2>-----Original Message-----<BR><B>From:</B> Tom-PT Taylor 
    [mailto:taylor@nortelnetworks.com]<BR><B>Sent:</B> Tuesday, April 30, 2002 
    8:33 PM<BR><B>To:</B> 'Dan Elbert'; Megaco (E-mail)<BR><B>Subject:</B> RE: 
    [Megaco] ServiceChangeAddress parameter<BR><BR></FONT></DIV>
    <P><FONT size=2>Must we have this restriction?&nbsp; I can see instances 
    where an MGC is multi-homed (or is in fact two separate physical devices 
    tied together in close synchronism), and the listening address happens to 
    differ from the working address the MGC wants to assign to the control 
    session.</FONT></P>
    <P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From: Dan 
    Elbert [<A 
    href="mailto:delbert@radvision.com">mailto:delbert@radvision.com</A>]</FONT> 
    <BR><FONT size=2>Sent: Tuesday, April 30, 2002 9:44 AM</FONT> <BR><FONT 
    size=2>To: Megaco (E-mail)</FONT> <BR><FONT size=2>Subject: [Megaco] 
    ServiceChangeAddress parameter</FONT> </P><BR>
    <P><FONT size=2>Hi All</FONT> <BR><FONT size=2>Do we have anywhere a strict 
    definition saying that the ServiceChangeAddress</FONT> <BR><FONT 
    size=2>parameter MUST be a port number for IP transport?</FONT> <BR><FONT 
    size=2>Leaving this so loosely defined can open the door to compatibility 
    problems</FONT> <BR><FONT size=2>if use of this feature is intended.</FONT> 
    </P>
    <P><FONT size=2>Dan Elbert</FONT> <BR><FONT size=2>RADVISION</FONT> </P>
    <P><FONT size=2>_______________________________________________</FONT> 
    <BR><FONT size=2>Megaco mailing list</FONT> <BR><FONT 
    size=2>Megaco@ietf.org</FONT> <BR><FONT size=2><A target=_blank 
    href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</A></FONT> 
    </P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1F06E.7ECFF030--

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



From megaco-admin@ietf.org  Tue Apr 30 14:13: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 OAA02197
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:13:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11294;
	Tue, 30 Apr 2002 13:36:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11253
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 13:36:27 -0400 (EDT)
Received: from mxout1.netvision.net.il (mxout1.netvision.net.il [194.90.9.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00204
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:36:23 -0400 (EDT)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout1.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GVE0032667OO8@mxout1.netvision.net.il> for megaco@ietf.org;
 Tue, 30 Apr 2002 20:35:48 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <2VF086YZ>; Tue, 30 Apr 2002 20:34:21 +0300
Content-return: allowed
Date: Tue, 30 Apr 2002 20:34:20 +0300
From: Dan Elbert <delbert@radvision.com>
Subject: RE: [Megaco] ServiceChangeAddress parameter
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        Dan Elbert <delbert@radvision.com>,
        "Megaco (E-mail)" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B01FCF32F@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_FwKIjtNmkhPHs4FKz2E4LQ)"
Sender: megaco-admin@ietf.org
Errors-To: 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.

--Boundary_(ID_FwKIjtNmkhPHs4FKz2E4LQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Wouldn't in that case a new mgcId be more appropiated ?

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Tuesday, April 30, 2002 8:33 PM
To: 'Dan Elbert'; Megaco (E-mail)
Subject: RE: [Megaco] ServiceChangeAddress parameter



Must we have this restriction?  I can see instances where an MGC is
multi-homed (or is in fact two separate physical devices tied together in
close synchronism), and the listening address happens to differ from the
working address the MGC wants to assign to the control session.

-----Original Message----- 
From: Dan Elbert [ mailto:delbert@radvision.com
<mailto:delbert@radvision.com> ] 
Sent: Tuesday, April 30, 2002 9:44 AM 
To: Megaco (E-mail) 
Subject: [Megaco] ServiceChangeAddress parameter 


Hi All 
Do we have anywhere a strict definition saying that the ServiceChangeAddress

parameter MUST be a port number for IP transport? 
Leaving this so loosely defined can open the door to compatibility problems 
if use of this feature is intended. 

Dan Elbert 
RADVISION 

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


--Boundary_(ID_FwKIjtNmkhPHs4FKz2E4LQ)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!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] ServiceChangeAddress parameter</TITLE>

<META content="MSHTML 5.50.4613.1700" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=919143417-30042002><FONT face=Arial color=#0000ff size=2>
<DIV><SPAN class=780173317-30042002><FONT face=Arial color=#0000ff 
size=2>Wouldn't in that case a new mgcId be more appropiated 
?</FONT></SPAN></DIV></FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Tom-PT Taylor 
  [mailto:taylor@nortelnetworks.com]<BR><B>Sent:</B> Tuesday, April 30, 2002 
  8:33 PM<BR><B>To:</B> 'Dan Elbert'; Megaco (E-mail)<BR><B>Subject:</B> RE: 
  [Megaco] ServiceChangeAddress parameter<BR><BR></FONT></DIV>
  <P><FONT size=2>Must we have this restriction?&nbsp; I can see instances where 
  an MGC is multi-homed (or is in fact two separate physical devices tied 
  together in close synchronism), and the listening address happens to differ 
  from the working address the MGC wants to assign to the control 
  session.</FONT></P>
  <P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From: Dan 
  Elbert [<A 
  href="mailto:delbert@radvision.com">mailto:delbert@radvision.com</A>]</FONT> 
  <BR><FONT size=2>Sent: Tuesday, April 30, 2002 9:44 AM</FONT> <BR><FONT 
  size=2>To: Megaco (E-mail)</FONT> <BR><FONT size=2>Subject: [Megaco] 
  ServiceChangeAddress parameter</FONT> </P><BR>
  <P><FONT size=2>Hi All</FONT> <BR><FONT size=2>Do we have anywhere a strict 
  definition saying that the ServiceChangeAddress</FONT> <BR><FONT 
  size=2>parameter MUST be a port number for IP transport?</FONT> <BR><FONT 
  size=2>Leaving this so loosely defined can open the door to compatibility 
  problems</FONT> <BR><FONT size=2>if use of this feature is intended.</FONT> 
  </P>
  <P><FONT size=2>Dan Elbert</FONT> <BR><FONT size=2>RADVISION</FONT> </P>
  <P><FONT size=2>_______________________________________________</FONT> 
  <BR><FONT size=2>Megaco mailing list</FONT> <BR><FONT 
  size=2>Megaco@ietf.org</FONT> <BR><FONT size=2><A target=_blank 
  href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</A></FONT> 
  </P></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_FwKIjtNmkhPHs4FKz2E4LQ)--

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


From daemon@optimus.ietf.org  Tue Apr 30 14:13: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 OAA02208
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:13:23 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA14784
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 14:13:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11294;
	Tue, 30 Apr 2002 13:36:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11253
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 13:36:27 -0400 (EDT)
Received: from mxout1.netvision.net.il (mxout1.netvision.net.il [194.90.9.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00204
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:36:23 -0400 (EDT)
Received: from nt-mail.radvision.com ([212.143.185.30])
 by mxout1.netvision.net.il (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0GVE0032667OO8@mxout1.netvision.net.il> for megaco@ietf.org;
 Tue, 30 Apr 2002 20:35:48 +0300 (IDT)
Received: by nt-mail.radvision.com with Internet Mail Service (5.5.2650.21)
	id <2VF086YZ>; Tue, 30 Apr 2002 20:34:21 +0300
Content-return: allowed
Date: Tue, 30 Apr 2002 20:34:20 +0300
From: Dan Elbert <delbert@radvision.com>
Subject: RE: [Megaco] ServiceChangeAddress parameter
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>,
        Dan Elbert <delbert@radvision.com>,
        "Megaco (E-mail)" <megaco@ietf.org>
Message-id: <EE5AF23B5764D511A6B900508BB82A0B01FCF32F@nt-mail.radvision.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_FwKIjtNmkhPHs4FKz2E4LQ)"
Sender: megaco-admin@ietf.org
Errors-To: 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.

--Boundary_(ID_FwKIjtNmkhPHs4FKz2E4LQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Wouldn't in that case a new mgcId be more appropiated ?

-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Tuesday, April 30, 2002 8:33 PM
To: 'Dan Elbert'; Megaco (E-mail)
Subject: RE: [Megaco] ServiceChangeAddress parameter



Must we have this restriction?  I can see instances where an MGC is
multi-homed (or is in fact two separate physical devices tied together in
close synchronism), and the listening address happens to differ from the
working address the MGC wants to assign to the control session.

-----Original Message----- 
From: Dan Elbert [ mailto:delbert@radvision.com
<mailto:delbert@radvision.com> ] 
Sent: Tuesday, April 30, 2002 9:44 AM 
To: Megaco (E-mail) 
Subject: [Megaco] ServiceChangeAddress parameter 


Hi All 
Do we have anywhere a strict definition saying that the ServiceChangeAddress

parameter MUST be a port number for IP transport? 
Leaving this so loosely defined can open the door to compatibility problems 
if use of this feature is intended. 

Dan Elbert 
RADVISION 

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


--Boundary_(ID_FwKIjtNmkhPHs4FKz2E4LQ)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!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] ServiceChangeAddress parameter</TITLE>

<META content="MSHTML 5.50.4613.1700" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=919143417-30042002><FONT face=Arial color=#0000ff size=2>
<DIV><SPAN class=780173317-30042002><FONT face=Arial color=#0000ff 
size=2>Wouldn't in that case a new mgcId be more appropiated 
?</FONT></SPAN></DIV></FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Tom-PT Taylor 
  [mailto:taylor@nortelnetworks.com]<BR><B>Sent:</B> Tuesday, April 30, 2002 
  8:33 PM<BR><B>To:</B> 'Dan Elbert'; Megaco (E-mail)<BR><B>Subject:</B> RE: 
  [Megaco] ServiceChangeAddress parameter<BR><BR></FONT></DIV>
  <P><FONT size=2>Must we have this restriction?&nbsp; I can see instances where 
  an MGC is multi-homed (or is in fact two separate physical devices tied 
  together in close synchronism), and the listening address happens to differ 
  from the working address the MGC wants to assign to the control 
  session.</FONT></P>
  <P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From: Dan 
  Elbert [<A 
  href="mailto:delbert@radvision.com">mailto:delbert@radvision.com</A>]</FONT> 
  <BR><FONT size=2>Sent: Tuesday, April 30, 2002 9:44 AM</FONT> <BR><FONT 
  size=2>To: Megaco (E-mail)</FONT> <BR><FONT size=2>Subject: [Megaco] 
  ServiceChangeAddress parameter</FONT> </P><BR>
  <P><FONT size=2>Hi All</FONT> <BR><FONT size=2>Do we have anywhere a strict 
  definition saying that the ServiceChangeAddress</FONT> <BR><FONT 
  size=2>parameter MUST be a port number for IP transport?</FONT> <BR><FONT 
  size=2>Leaving this so loosely defined can open the door to compatibility 
  problems</FONT> <BR><FONT size=2>if use of this feature is intended.</FONT> 
  </P>
  <P><FONT size=2>Dan Elbert</FONT> <BR><FONT size=2>RADVISION</FONT> </P>
  <P><FONT size=2>_______________________________________________</FONT> 
  <BR><FONT size=2>Megaco mailing list</FONT> <BR><FONT 
  size=2>Megaco@ietf.org</FONT> <BR><FONT size=2><A target=_blank 
  href="https://www1.ietf.org/mailman/listinfo/megaco">https://www1.ietf.org/mailman/listinfo/megaco</A></FONT> 
  </P></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_FwKIjtNmkhPHs4FKz2E4LQ)--

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



From megaco-admin@ietf.org  Tue Apr 30 14:29: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 OAA02966
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:29:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11611;
	Tue, 30 Apr 2002 13:41:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11572
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 13:41:39 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00434
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:41:36 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3UHf7L28609
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:41:07 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78L22>; Tue, 30 Apr 2002 13:41:07 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3C5@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Dan Elbert'" <delbert@radvision.com>,
        "Megaco (E-mail)"
	 <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChangeAddress parameter
Date: Tue, 30 Apr 2002 13:41:04 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


I'll leave this to implementors to argue out.  Your convention of a separate
mgcId might seem artificial to some people, but if it is generally
acceptable I can see that it would simplify implementations.

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Tuesday, April 30, 2002 1:34 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]; Dan Elbert; Megaco (E-mail)
Subject: RE: [Megaco] ServiceChangeAddress parameter


Wouldn't in that case a new mgcId be more appropiated ?
-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Tuesday, April 30, 2002 8:33 PM
To: 'Dan Elbert'; Megaco (E-mail)
Subject: RE: [Megaco] ServiceChangeAddress parameter


Must we have this restriction?  I can see instances where an MGC is
multi-homed (or is in fact two separate physical devices tied together in
close synchronism), and the listening address happens to differ from the
working address the MGC wants to assign to the control session.
-----Original Message----- 
From: Dan Elbert [mailto:delbert@radvision.com] 
Sent: Tuesday, April 30, 2002 9:44 AM 
To: Megaco (E-mail) 
Subject: [Megaco] ServiceChangeAddress parameter 


Hi All 
Do we have anywhere a strict definition saying that the ServiceChangeAddress

parameter MUST be a port number for IP transport? 
Leaving this so loosely defined can open the door to compatibility problems 
if use of this feature is intended. 
Dan Elbert 
RADVISION 
_______________________________________________ 
Megaco mailing list 
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 Apr 30 14:29: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 OAA02978
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:29:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA15910
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 14:30:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11611;
	Tue, 30 Apr 2002 13:41:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11572
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 13:41:39 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00434
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:41:36 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3UHf7L28609
	for <megaco@ietf.org>; Tue, 30 Apr 2002 13:41:07 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78L22>; Tue, 30 Apr 2002 13:41:07 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3C5@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Dan Elbert'" <delbert@radvision.com>,
        "Megaco (E-mail)"
	 <megaco@ietf.org>
Subject: RE: [Megaco] ServiceChangeAddress parameter
Date: Tue, 30 Apr 2002 13:41:04 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org


I'll leave this to implementors to argue out.  Your convention of a separate
mgcId might seem artificial to some people, but if it is generally
acceptable I can see that it would simplify implementations.

-----Original Message-----
From: Dan Elbert [mailto:delbert@radvision.com]
Sent: Tuesday, April 30, 2002 1:34 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]; Dan Elbert; Megaco (E-mail)
Subject: RE: [Megaco] ServiceChangeAddress parameter


Wouldn't in that case a new mgcId be more appropiated ?
-----Original Message-----
From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com]
Sent: Tuesday, April 30, 2002 8:33 PM
To: 'Dan Elbert'; Megaco (E-mail)
Subject: RE: [Megaco] ServiceChangeAddress parameter


Must we have this restriction?  I can see instances where an MGC is
multi-homed (or is in fact two separate physical devices tied together in
close synchronism), and the listening address happens to differ from the
working address the MGC wants to assign to the control session.
-----Original Message----- 
From: Dan Elbert [mailto:delbert@radvision.com] 
Sent: Tuesday, April 30, 2002 9:44 AM 
To: Megaco (E-mail) 
Subject: [Megaco] ServiceChangeAddress parameter 


Hi All 
Do we have anywhere a strict definition saying that the ServiceChangeAddress

parameter MUST be a port number for IP transport? 
Leaving this so loosely defined can open the door to compatibility problems 
if use of this feature is intended. 
Dan Elbert 
RADVISION 
_______________________________________________ 
Megaco mailing list 
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 Apr 30 19:17: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 TAA12257
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 19:17:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA01498;
	Tue, 30 Apr 2002 18:48:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA01469
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 18:48:49 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11567
	for <megaco@ietf.org>; Tue, 30 Apr 2002 18:48:44 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3UMmGL01771
	for <megaco@ietf.org>; Tue, 30 Apr 2002 18:48:17 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78TNP>; Tue, 30 Apr 2002 18:48:17 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3CE@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Cc: "'Seong-Ho Jeong'" <shojeong@hotmail.com>,
        "'Blatherwick, Peter'" <Peter_Blatherwick@Mitel.COM>,
        "'Marcello Pantaleo (EED)'" <Marcello.Pantaleo@eed.ericsson.se>,
        "John Pugh"<johnpugh@nortelnetworks.com>
Date: Tue, 30 Apr 2002 18:48:15 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Access To Megaco 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

I found a formula that works, though I don't like it.  To get at the Megaco
documents via your browser, go to
ftp://ftp@standards.nortelnetworks.com/megaco/docs/.  When asked for your
password, user@host.com will work.  I'm not sure why we need a password now.

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 Apr 30 19:17: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 TAA12270
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 19:17:01 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA03233
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 19:17:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA01498;
	Tue, 30 Apr 2002 18:48:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA01469
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 18:48:49 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11567
	for <megaco@ietf.org>; Tue, 30 Apr 2002 18:48:44 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3UMmGL01771
	for <megaco@ietf.org>; Tue, 30 Apr 2002 18:48:17 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78TNP>; Tue, 30 Apr 2002 18:48:17 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3CE@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Cc: "'Seong-Ho Jeong'" <shojeong@hotmail.com>,
        "'Blatherwick, Peter'" <Peter_Blatherwick@Mitel.COM>,
        "'Marcello Pantaleo (EED)'" <Marcello.Pantaleo@eed.ericsson.se>,
        "John Pugh"<johnpugh@nortelnetworks.com>
Date: Tue, 30 Apr 2002 18:48:15 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Megaco] Access To Megaco 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

I found a formula that works, though I don't like it.  To get at the Megaco
documents via your browser, go to
ftp://ftp@standards.nortelnetworks.com/megaco/docs/.  When asked for your
password, user@host.com will work.  I'm not sure why we need a password now.

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 Apr 30 19:17: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 TAA12297
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 19:17:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA01735;
	Tue, 30 Apr 2002 18:55:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA01704
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 18:55:05 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11683
	for <megaco@ietf.org>; Tue, 30 Apr 2002 18:55:00 -0400 (EDT)
Received: from balanew ([172.16.137.131])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3UMsVK00450;
	Tue, 30 Apr 2002 18:54:31 -0400 (EDT)
Reply-To: <bs@utstar.com>
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
Cc: "'Seong-Ho Jeong'" <shojeong@hotmail.com>,
        "'Blatherwick, Peter'" <Peter_Blatherwick@mitel.com>,
        "'Marcello Pantaleo \(EED\)'" <Marcello.Pantaleo@eed.ericsson.se>,
        "'John Pugh'" <johnpugh@nortelnetworks.com>
Subject: RE: [Megaco] Access To Megaco Documents
Date: Tue, 30 Apr 2002 18:54:55 -0400
Organization: UTStarcom Inc
Message-ID: <002001c1f09a$0bd43150$838910ac@balanew>
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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <4D79C746863DD51197690002A52CDA0001E8A3CE@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

Tom,

The URL does not seem to work. Is this a new server? 

Because the URL used to be:

ftp://standards.nortelnetworks.com/megaco/docs/

You have mentioned below that the URL is

ftp://ftp@stadards.nortelnetworks.com/megaco/docs/

Anyways, I have tried both. No luck.


Thanks,
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Tom-PT Taylor
Sent: Tuesday, April 30, 2002 6:48 PM
To: 'megaco@ietf.org'
Cc: 'Seong-Ho Jeong'; 'Blatherwick, Peter'; 'Marcello Pantaleo (EED)';
John Pugh
Subject: [Megaco] Access To Megaco Documents

I found a formula that works, though I don't like it.  To get at the
Megaco
documents via your browser, go to
ftp://ftp@standards.nortelnetworks.com/megaco/docs/.  When asked for
your
password, user@host.com will work.  I'm not sure why we need a password
now.

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 Apr 30 19:17: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 TAA12308
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 19:17:40 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA03268
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 19:17:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA01735;
	Tue, 30 Apr 2002 18:55:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA01704
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 18:55:05 -0400 (EDT)
Received: from mail.utstar.com ([65.200.123.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11683
	for <megaco@ietf.org>; Tue, 30 Apr 2002 18:55:00 -0400 (EDT)
Received: from balanew ([172.16.137.131])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id g3UMsVK00450;
	Tue, 30 Apr 2002 18:54:31 -0400 (EDT)
Reply-To: <bs@utstar.com>
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>, <megaco@ietf.org>
Cc: "'Seong-Ho Jeong'" <shojeong@hotmail.com>,
        "'Blatherwick, Peter'" <Peter_Blatherwick@mitel.com>,
        "'Marcello Pantaleo \(EED\)'" <Marcello.Pantaleo@eed.ericsson.se>,
        "'John Pugh'" <johnpugh@nortelnetworks.com>
Subject: RE: [Megaco] Access To Megaco Documents
Date: Tue, 30 Apr 2002 18:54:55 -0400
Organization: UTStarcom Inc
Message-ID: <002001c1f09a$0bd43150$838910ac@balanew>
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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <4D79C746863DD51197690002A52CDA0001E8A3CE@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

Tom,

The URL does not seem to work. Is this a new server? 

Because the URL used to be:

ftp://standards.nortelnetworks.com/megaco/docs/

You have mentioned below that the URL is

ftp://ftp@stadards.nortelnetworks.com/megaco/docs/

Anyways, I have tried both. No luck.


Thanks,
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Tom-PT Taylor
Sent: Tuesday, April 30, 2002 6:48 PM
To: 'megaco@ietf.org'
Cc: 'Seong-Ho Jeong'; 'Blatherwick, Peter'; 'Marcello Pantaleo (EED)';
John Pugh
Subject: [Megaco] Access To Megaco Documents

I found a formula that works, though I don't like it.  To get at the
Megaco
documents via your browser, go to
ftp://ftp@standards.nortelnetworks.com/megaco/docs/.  When asked for
your
password, user@host.com will work.  I'm not sure why we need a password
now.

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 Apr 30 19:27: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 TAA12576
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 19:27:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA02631;
	Tue, 30 Apr 2002 19:02:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA02601
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 19:02:21 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11887
	for <megaco@ietf.org>; Tue, 30 Apr 2002 19:02:16 -0400 (EDT)
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 g3UN1md13488
	for <megaco@ietf.org>; Tue, 30 Apr 2002 19:01:48 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78TQ4>; Tue, 30 Apr 2002 19:01:49 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3CF@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'bs@utstar.com'" <bs@utstar.com>, megaco@ietf.org
Cc: "'Seong-Ho Jeong'" <shojeong@hotmail.com>,
        "'Blatherwick, Peter'" <Peter_Blatherwick@mitel.com>,
        "'Marcello Pantaleo (EED)'" <Marcello.Pantaleo@eed.ericsson.se>,
        "John Pugh"<johnpugh@nortelnetworks.com>
Subject: RE: [Megaco] Access To Megaco Documents
Date: Tue, 30 Apr 2002 19:01:49 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

I see a typo in the URL I gave -- not sure how, since it was a
cut-and-paste.  Anyway, the right URL is
ftp://ftp@standards.nortelnetworks.com/megaco/docs/

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Tuesday, April 30, 2002 6:55 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Cc: 'Seong-Ho Jeong'; 'Blatherwick, Peter'; 'Marcello Pantaleo (EED)';
Pugh, John [NC1:6L24:EXCH]
Subject: RE: [Megaco] Access To Megaco Documents


Tom,

The URL does not seem to work. Is this a new server? 

Because the URL used to be:

ftp://standards.nortelnetworks.com/megaco/docs/

You have mentioned below that the URL is

ftp://ftp@stadards.nortelnetworks.com/megaco/docs/

Anyways, I have tried both. No luck.


Thanks,
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Tom-PT Taylor
Sent: Tuesday, April 30, 2002 6:48 PM
To: 'megaco@ietf.org'
Cc: 'Seong-Ho Jeong'; 'Blatherwick, Peter'; 'Marcello Pantaleo (EED)';
John Pugh
Subject: [Megaco] Access To Megaco Documents

I found a formula that works, though I don't like it.  To get at the
Megaco
documents via your browser, go to
ftp://ftp@standards.nortelnetworks.com/megaco/docs/.  When asked for
your
password, user@host.com will work.  I'm not sure why we need a password
now.

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 Apr 30 20: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 TAA12588
	for <megaco-archive@odin.ietf.org>; Tue, 30 Apr 2002 19:27:37 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA03517
	for megaco-archive@odin.ietf.org; Tue, 30 Apr 2002 19:27:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA02631;
	Tue, 30 Apr 2002 19:02:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA02601
	for <megaco@optimus.ietf.org>; Tue, 30 Apr 2002 19:02:21 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11887
	for <megaco@ietf.org>; Tue, 30 Apr 2002 19:02:16 -0400 (EDT)
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 g3UN1md13488
	for <megaco@ietf.org>; Tue, 30 Apr 2002 19:01:48 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78TQ4>; Tue, 30 Apr 2002 19:01:49 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3CF@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'bs@utstar.com'" <bs@utstar.com>, megaco@ietf.org
Cc: "'Seong-Ho Jeong'" <shojeong@hotmail.com>,
        "'Blatherwick, Peter'" <Peter_Blatherwick@mitel.com>,
        "'Marcello Pantaleo (EED)'" <Marcello.Pantaleo@eed.ericsson.se>,
        "John Pugh"<johnpugh@nortelnetworks.com>
Subject: RE: [Megaco] Access To Megaco Documents
Date: Tue, 30 Apr 2002 19:01:49 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org

I see a typo in the URL I gave -- not sure how, since it was a
cut-and-paste.  Anyway, the right URL is
ftp://ftp@standards.nortelnetworks.com/megaco/docs/

-----Original Message-----
From: Balasubramanian Pitchandi [mailto:bs@utstar.com]
Sent: Tuesday, April 30, 2002 6:55 PM
To: Taylor, Tom-PT [CAR:B800:EXCH]; megaco@ietf.org
Cc: 'Seong-Ho Jeong'; 'Blatherwick, Peter'; 'Marcello Pantaleo (EED)';
Pugh, John [NC1:6L24:EXCH]
Subject: RE: [Megaco] Access To Megaco Documents


Tom,

The URL does not seem to work. Is this a new server? 

Because the URL used to be:

ftp://standards.nortelnetworks.com/megaco/docs/

You have mentioned below that the URL is

ftp://ftp@stadards.nortelnetworks.com/megaco/docs/

Anyways, I have tried both. No luck.


Thanks,
Bala


-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Tom-PT Taylor
Sent: Tuesday, April 30, 2002 6:48 PM
To: 'megaco@ietf.org'
Cc: 'Seong-Ho Jeong'; 'Blatherwick, Peter'; 'Marcello Pantaleo (EED)';
John Pugh
Subject: [Megaco] Access To Megaco Documents

I found a formula that works, though I don't like it.  To get at the
Megaco
documents via your browser, go to
ftp://ftp@standards.nortelnetworks.com/megaco/docs/.  When asked for
your
password, user@host.com will work.  I'm not sure why we need a password
now.

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



