From mailman-bounces@ietf.org  Mon Nov  1 08:00:06 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27978
	for <megaco-archive@lists.ietf.org>; Mon, 1 Nov 2004 08:00:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COZbQ-0001UM-7O
	for megaco-archive@lists.ietf.org; Mon, 01 Nov 2004 05:39:56 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: megaco-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.22482.1099304174.20557.mailman@lists.ietf.org>
Date: Mon, 01 Nov 2004 05:16:14 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

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, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


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%40lists.ietf.org


From megaco-bounces@ietf.org  Wed Nov  3 07:37:27 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02582
	for <megaco-archive@lists.ietf.org>; Wed, 3 Nov 2004 07:37:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPKDT-000775-Ht; Wed, 03 Nov 2004 07:26:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPK6M-0005Yy-4H
	for megaco@megatron.ietf.org; Wed, 03 Nov 2004 07:18:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00898
	for <megaco@ietf.org>; Wed, 3 Nov 2004 07:18:55 -0500 (EST)
Received: from mailserv.intranet.gr ([146.124.14.106])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPKLe-0002jR-9O
	for megaco@ietf.org; Wed, 03 Nov 2004 07:34:48 -0500
Received: from mailserv.intranet.gr (localhost [127.0.0.1])
	by mailserv.intranet.gr (8.13.1/8.13.1) with ESMTP id iA3CJVPb018741
	for <megaco@ietf.org>; Wed, 3 Nov 2004 14:19:31 +0200 (EET)
Received: from pella.intranet.gr (pella.intranet.GR [146.124.173.10])
	by mailserv.intranet.gr (8.13.1/8.13.1) with ESMTP id iA3CJKOu018514
	for <megaco@ietf.org>; Wed, 3 Nov 2004 14:19:24 +0200 (EET)
Received: from thespcrh1.intranet.gr (thespcrh1.intranet.GR [146.124.173.131])
	by pella.intranet.gr (8.11.7p1+Sun/8.11.7) with ESMTP id iA3CGXJ29210
	for <megaco@ietf.org>; Wed, 3 Nov 2004 14:16:33 +0200 (EET)
To: megaco@ietf.org
Date: Wed, 03 Nov 2004 14:20:22 +0200
From: "Tintikakis Giorgos" <gtin@intracom.gr>
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-7
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-ID: <opsgv1v8td773hoi@thespcrh1.intranet.gr>
User-Agent: Opera M2/7.54 (Win32, build 3865)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 8bit
Subject: [Megaco] Number of MG's IP addresses
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 8bit


Hello,

A very simple question but the confirmation is critical for us.

Could the MG have a different IP address (from the MG-MGC transport  
address)
for the RTP streams ?

We can see from the 'Call flow examples' example 2.1 that this  
configuration is
possible.

Those IP addresses could belong to two different subnets?

Does any document exists where is specified how many IP addresses
an MG could use for the control association and for the RTP streams?

Thank you in advance,
Giorgos

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


From megaco-bounces@ietf.org  Wed Nov  3 08:15:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06599
	for <megaco-archive@lists.ietf.org>; Wed, 3 Nov 2004 08:15:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPKoT-0007k4-PY; Wed, 03 Nov 2004 08:04:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPKiT-0005Qh-RC
	for megaco@megatron.ietf.org; Wed, 03 Nov 2004 07:58:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04408
	for <megaco@ietf.org>; Wed, 3 Nov 2004 07:58:20 -0500 (EST)
Received: from mail.tdsoft.com ([212.143.64.34] helo=TdSoft.Esafe.com)
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CPKxl-0003oB-BN
	for megaco@ietf.org; Wed, 03 Nov 2004 08:14:12 -0500
Received: from mailserver.td-soft.co.il ([IP=172.16.1.203]) by eSafe SMTP
	Relay 1099233645; Wed Nov 03 14:56:41 2004
Received: by MAILSERVER with Internet Mail Service (5.5.2657.72) id <45L47RDK>;
	Wed, 3 Nov 2004 14:57:26 +0200
Message-ID: <9A64A99CD3F2BD4582BE4FB63FC1F381010D2D30@MAILSERVER>
From: Raphael Tryster <raphael@tdsoft.com>
To: "'Tintikakis Giorgos'" <gtin@intracom.gr>, megaco@ietf.org
Subject: RE: [Megaco] Number of MG's IP addresses
Date: Wed, 3 Nov 2004 14:57:26 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-ESAFE-STATUS: Mail clean
X-ESAFE-DETAILS: Clean
X-Spam-Score: 0.5 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1388956182=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@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.

--===============1388956182==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C1A4.AAF6B9F0"

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_01C4C1A4.AAF6B9F0
Content-Type: text/plain

Yes, there is no restriction.  The signaling and voice handling parts of an
MG could reside on different hardware entities.

Raphael Tryster


	-----Original Message-----
	From:	Tintikakis Giorgos [SMTP:gtin@intracom.gr]
	Sent:	Wednesday, 3 November 2004 14:20
	To:	megaco@ietf.org
	Subject:	[Megaco] Number of MG's IP addresses


	Hello,

	A very simple question but the confirmation is critical for us.

	Could the MG have a different IP address (from the MG-MGC transport

	address)
	for the RTP streams ?

	We can see from the 'Call flow examples' example 2.1 that this  
	configuration is
	possible.

	Those IP addresses could belong to two different subnets?

	Does any document exists where is specified how many IP addresses
	an MG could use for the control association and for the RTP streams?

	Thank you in advance,
	Giorgos

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

------_=_NextPart_001_01C4C1A4.AAF6B9F0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-asci=
i">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2654.4=
5">
<TITLE>RE: [Megaco] Number of MG's IP addresses</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Yes, there is no restriction.&nbsp; The =
signaling and voice handling parts of an MG could reside on different har=
dware entities.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Tahoma">Raphael Tryster</FONT>
</P>
<BR>
<UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original Mess=
age-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:&nbsp;&nbsp; Tintikakis Giorgos=
 [SMTP:gtin@intracom.gr]</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT S=
IZE=3D2 FACE=3D"Arial">Wednesday, 3 November 2004 14:20</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></=
B> <FONT SIZE=3D2 FACE=3D"Arial">megaco@ietf.org</FONT>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D2 FACE=3D"Arial">[Megaco] Number o=
f MG's IP addresses</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Hello,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">A very simple question but the con=
firmation is critical for us.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Could the MG have a different IP a=
ddress (from the MG-MGC transport&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">address)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">for the RTP streams ?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">We can see from the 'Call flow exa=
mples' example 2.1 that this&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">configuration is</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">possible.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Those IP addresses could belong to=
 two different subnets?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Does any document exists where is =
specified how many IP addresses</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">an MG could use for the control a=
ssociation and for the RTP streams?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Thank you in advance,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Giorgos</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">__________________________________=
_____________</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Megaco mailing list</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Megaco@ietf.org</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New"><A HREF=3D"https://www1.ietf.org/=
mailman/listinfo/megaco" TARGET=3D"_blank">https://www1.ietf.org/mailman/=
listinfo/megaco</A></FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C4C1A4.AAF6B9F0--


--===============1388956182==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1388956182==--



From megaco-bounces@ietf.org  Wed Nov  3 09:13:50 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11512
	for <megaco-archive@lists.ietf.org>; Wed, 3 Nov 2004 09:13:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPLoa-0004ul-5F; Wed, 03 Nov 2004 09:08:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPLh8-0003zf-On
	for megaco@megatron.ietf.org; Wed, 03 Nov 2004 09:01:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10402
	for <megaco@ietf.org>; Wed, 3 Nov 2004 09:01:01 -0500 (EST)
From: Albrecht.Schwarz@alcatel.de
Received: from mailrelay1.alcatel.de ([194.113.59.55]
	helo=mailrelay2.alcatel.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPLwS-0005YM-T8
	for megaco@ietf.org; Wed, 03 Nov 2004 09:16:53 -0500
Received: from demail05.netfr.alcatel.fr (demail05.netfr.alcatel.fr
	[155.132.182.205])
	by mailrelay2.alcatel.de (8.12.11/8.12.10) with ESMTP id iA3E0KR1015453;
	Wed, 3 Nov 2004 15:00:21 +0100 (MET)
In-Reply-To: <4158A898.1070206@ericsson.com>
To: Christian Groves <christian.groves@ericsson.com>
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF76F84E15.A4CF17B8-ONC1256F41.004C2618-C1256F41.004CEF34@netfr.alcatel.fr>
Date: Wed, 3 Nov 2004 15:00:19 +0100
X-MIMETrack: Serialize by Router on DEMAIL05/DE/ALCATEL(Release 5.0.11 |July
	24, 2002) at 11/03/2004 15:00:20
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-AES-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: megaco@ietf.org
Subject: [Megaco] H.248.1 V3 Appendix II "H.248 Package Template": Error
	Codes
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org


Hello Christian,

got a basic question to the Error Code section
(H.248.1 V3, Appendix II, cl. 5.5,
http://ftp3.itu.int/av-arch/avc-site/2001-2004/0408_San/TD-33.zip)
in the V3 template.

Package specific error codes shall be defined in form of


<Error Code Title>

       Error Code #:    <number>

       Name:                  <name>

       Definition:            <definition>

       Error Text in the Error Descriptor:

          <error text to return>

       Comment:   <comment>


Question: how are local (i.e, package specific error codes) distinguished
from global ones (= H.248.8)?
How may the MGC distinguish between local & global?

Background: I'm currently drafting the H.248.33 local error code.

Thanks
Albrecht





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


From megaco-bounces@ietf.org  Wed Nov  3 09:22:55 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12112
	for <megaco-archive@lists.ietf.org>; Wed, 3 Nov 2004 09:22:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPLuh-0006Ok-KQ; Wed, 03 Nov 2004 09:15:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPLpq-00056a-8T
	for megaco@megatron.ietf.org; Wed, 03 Nov 2004 09:10:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11179
	for <megaco@ietf.org>; Wed, 3 Nov 2004 09:10:00 -0500 (EST)
From: Albrecht.Schwarz@alcatel.de
Received: from mailrelay1.alcatel.de ([194.113.59.55]
	helo=mailrelay2.alcatel.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPM5A-0005jI-Pa
	for megaco@ietf.org; Wed, 03 Nov 2004 09:25:53 -0500
Received: from demail05.netfr.alcatel.fr (demail05.netfr.alcatel.fr
	[155.132.182.205])
	by mailrelay2.alcatel.de (8.12.11/8.12.10) with ESMTP id iA3E9SYn017452;
	Wed, 3 Nov 2004 15:09:28 +0100 (MET)
In-Reply-To: <opsgv1v8td773hoi@thespcrh1.intranet.gr>
Subject: Re: [Megaco] Number of MG's IP addresses
To: "Tintikakis Giorgos" <gtin@intracom.gr>
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF3D7E8C32.0A4E4579-ONC1256F41.004D27FB-C1256F41.004DC4F3@netfr.alcatel.fr>
Date: Wed, 3 Nov 2004 15:09:26 +0100
X-MIMETrack: Serialize by Router on DEMAIL05/DE/ALCATEL(Release 5.0.11 |July
	24, 2002) at 11/03/2004 15:09:27
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-AES-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org


Sure Giorgos.
IP addressing is independent of H.248. Practically it's an implementation
issue, dependent for instance of MG size, interface capacities, address
realm(s) requirement, etc.

For instance, if a network operator wants to separate H.248-over-IP traffic
from RTP-over-IP traffic, then this is typically starting on IP@ level.
Further: high capacity MGs providing typically at least one IP@ per
physical IP interface, etc.

regards
Albrecht




                                                                                                                                
                      "Tintikakis                                                                                               
                      Giorgos"                 To:      megaco@ietf.org                                                         
                      <gtin@intracom.g         cc:                                                                              
                      r>                       Subject: [Megaco] Number of MG's IP addresses                                    
                      Sent by:                                                                                                  
                      megaco-bounces@i                                                                                          
                      etf.org                                                                                                   
                                                                                                                                
                                                                                                                                
                      03.11.2004 13:20                                                                                          
                                                                                                                                





Hello,

A very simple question but the confirmation is critical for us.

Could the MG have a different IP address (from the MG-MGC transport
address)
for the RTP streams ?

We can see from the 'Call flow examples' example 2.1 that this
configuration is
possible.

Those IP addresses could belong to two different subnets?

Does any document exists where is specified how many IP addresses
an MG could use for the control association and for the RTP streams?

Thank you in advance,
Giorgos

_______________________________________________
Megaco mailing list
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-bounces@ietf.org  Wed Nov  3 10:02:37 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15666
	for <megaco-archive@lists.ietf.org>; Wed, 3 Nov 2004 10:02:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPMTY-0005KI-EK; Wed, 03 Nov 2004 09:51:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPMJV-0003FQ-3h
	for megaco@megatron.ietf.org; Wed, 03 Nov 2004 09:40:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13765
	for <megaco@ietf.org>; Wed, 3 Nov 2004 09:40:39 -0500 (EST)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPMYq-0006UA-09
	for megaco@ietf.org; Wed, 03 Nov 2004 09:56:32 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iA3Eboo28223; Wed, 3 Nov 2004 09:37:50 -0500 (EST)
Received: from [47.130.17.132] (acart263.ca.nortel.com [47.130.17.132]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14F3B4F; Wed, 3 Nov 2004 09:37:50 -0500
Message-ID: <4188ED3D.8060104@nortelnetworks.com>
Date: Wed, 03 Nov 2004 09:37:49 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Albrecht.Schwarz@alcatel.de
Subject: Re: [Megaco] H.248.1 V3 Appendix II "H.248 Package Template": Error
	Codes
References: <OF76F84E15.A4CF17B8-ONC1256F41.004C2618-C1256F41.004CEF34@netfr.alcatel.fr>
In-Reply-To: <OF76F84E15.A4CF17B8-ONC1256F41.004C2618-C1256F41.004CEF34@netfr.alcatel.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
Cc: Christian Groves <christian.groves@ericsson.com>, megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Error codes may be defined in packages, but in fact they are generally applicable. 
  The package just happens to be where they are documented.

Of course, by its nature the error may be something that can't possibly occur 
unless you are using a particular package.  When defining an error, you need to 
come up with a balance between the amount of information it provides (which should 
be enough to point corrective action in the right direction, but not enough to be 
a debugging tool on its own) and the possibility of its more general application 
(which is desirable).

Albrecht.Schwarz@alcatel.de wrote:
> Hello Christian,
> 
> got a basic question to the Error Code section
> (H.248.1 V3, Appendix II, cl. 5.5,
> http://ftp3.itu.int/av-arch/avc-site/2001-2004/0408_San/TD-33.zip)
> in the V3 template.
> 
> Package specific error codes shall be defined in form of
> 
> 
> <Error Code Title>
> 
>        Error Code #:    <number>
> 
>        Name:                  <name>
> 
>        Definition:            <definition>
> 
>        Error Text in the Error Descriptor:
> 
>           <error text to return>
> 
>        Comment:   <comment>
> 
> 
> Question: how are local (i.e, package specific error codes) distinguished
> from global ones (= H.248.8)?
> How may the MGC distinguish between local & global?
> 
> Background: I'm currently drafting the H.248.33 local error code.
> 
> Thanks
> Albrecht
> 
> 
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 

-- 
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com

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


From megaco-bounces@ietf.org  Wed Nov  3 10:32:23 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19809
	for <megaco-archive@lists.ietf.org>; Wed, 3 Nov 2004 10:32:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPN4w-0001mS-U8; Wed, 03 Nov 2004 10:29:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPN1x-0000fa-8N
	for megaco@megatron.ietf.org; Wed, 03 Nov 2004 10:26:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19110
	for <megaco@ietf.org>; Wed, 3 Nov 2004 10:26:34 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPNHE-0007iJ-88
	for megaco@ietf.org; Wed, 03 Nov 2004 10:42:27 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iA3FPxv10098
	for <megaco@ietf.org>; Wed, 3 Nov 2004 10:26:00 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WFB8HDHS>; Wed, 3 Nov 2004 10:26:00 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5366BA7E4@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "Tom-PT Taylor" <taylor@nortelnetworks.com>, Albrecht.Schwarz@alcatel.de
Subject: RE: [Megaco] H.248.1 V3 Appendix II "H.248 Package Template": Err
	orCodes
Date: Wed, 3 Nov 2004 10:25:42 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: Christian Groves <christian.groves@ericsson.com>, megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

To date, error codes which are specifically related to a particular
package's function are defined by the package and those independent of
package function get put in H.248.8.

Kevin

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Taylor, Tom-PT [CAR:5N00:EXCH]
Sent: Wednesday, November 03, 2004 9:38 AM
To: Albrecht.Schwarz@alcatel.de
Cc: Christian Groves; megaco@ietf.org
Subject: Re: [Megaco] H.248.1 V3 Appendix II "H.248 Package Template":
ErrorCodes

Error codes may be defined in packages, but in fact they are generally
applicable. 
  The package just happens to be where they are documented.

Of course, by its nature the error may be something that can't possibly
occur unless you are using a particular package.  When defining an error,
you need to come up with a balance between the amount of information it
provides (which should be enough to point corrective action in the right
direction, but not enough to be a debugging tool on its own) and the
possibility of its more general application (which is desirable).

Albrecht.Schwarz@alcatel.de wrote:
> Hello Christian,
> 
> got a basic question to the Error Code section
> (H.248.1 V3, Appendix II, cl. 5.5,
> http://ftp3.itu.int/av-arch/avc-site/2001-2004/0408_San/TD-33.zip)
> in the V3 template.
> 
> Package specific error codes shall be defined in form of
> 
> 
> <Error Code Title>
> 
>        Error Code #:    <number>
> 
>        Name:                  <name>
> 
>        Definition:            <definition>
> 
>        Error Text in the Error Descriptor:
> 
>           <error text to return>
> 
>        Comment:   <comment>
> 
> 
> Question: how are local (i.e, package specific error codes) 
> distinguished from global ones (= H.248.8)?
> How may the MGC distinguish between local & global?
> 
> Background: I'm currently drafting the H.248.33 local error code.
> 
> Thanks
> Albrecht
> 
> 
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 

--
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.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-bounces@ietf.org  Wed Nov  3 11:20:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23210
	for <megaco-archive@lists.ietf.org>; Wed, 3 Nov 2004 11:20:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPNol-0001yo-Su; Wed, 03 Nov 2004 11:17:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPNjA-0000in-8J
	for megaco@megatron.ietf.org; Wed, 03 Nov 2004 11:11:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22452
	for <megaco@ietf.org>; Wed, 3 Nov 2004 11:11:14 -0500 (EST)
Received: from [200.51.236.11] (helo=mail4.telefonica.com.ar)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPNyV-0000FJ-ET
	for megaco@ietf.org; Wed, 03 Nov 2004 11:27:08 -0500
Received: by mailhub2.telefonica.com.ar with Internet Mail Service
	(5.5.2653.19) id <4R81T4GY>; Wed, 3 Nov 2004 13:11:06 -0300
Message-ID: <6BB2DEB822D3D111817B00805FBE5F021518276C@mstelefonica6.telefonica.com.ar>
From: Pellegrino Jose Luis <pellegrj@TELEFONICA.COM.AR>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 3 Nov 2004 13:12:21 -0300 
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Subject: [Megaco] (no subject)
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0638570932=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@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.

--===============0638570932==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C1BF.E6086280"

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_01C4C1BF.E6086280
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi, I have some questions about NGN (trunking) architecture using H.248 =
and
the interworking with ISUP.

Suppose two MGCs which controlate N MGs in a trunking network. Each MG =
is
conected to a tradicional TDM switch and the ISUP messages sent by the
switches are received by the signalling gateway via STP. There's no =
class
five services.


RFC 3525, point 11.5 "failure of an MGC" describe the procedures for =
the MG
in order to switch to another MGC in case of failure of the primary =
MGC.
This is in  my opinion one of the facilities that make MEGACO better =
than
MGCP.

-In my understanding, the mechanism described above is possible only if =
the
MGC's are working in the "Hot/Stand by" modality. =BFAm I right?
-The Signalling Gateways have an unique DPC (destination point code).
Having different DPC is not possible =BFIs this correct?.

Now, Suppose that you have the same  two MGCs, but  working in the =
"Sharing
load" modality, each of them controlling a group of MG's.

-In this architecture each MGC have a DPC different from the =
other.=BFIs this
correct?
-In this case, switching to another MGC is not possible because the =
vocals
trunks (wich are asociated with the fisical terminations), are related =
to
ONE DPC. =BFIs this correct?

However, in a sharing load scenario, it's possible to use Virtual MGs =
in
order give redundance to NGN - TDM conection (point 11.1 "Multiple =
Virtual
MGs").

So, making a summary, if I'm not wrong, depending on the Architecture,
"Hot/Stand by" or in the other hand "Sharing load", you can take =
advantage
of using switching mechanism or virtual MGs.

I will appreciate all the comments,=20

Thanks in advance,

Jos=E9 Luis




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

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

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi, I have some questions about NGN =
(trunking) architecture using H.248 and the interworking with =
ISUP.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Suppose two MGCs which controlate N =
MGs in a trunking network. Each MG is conected to a tradicional TDM =
switch and the ISUP messages sent by the switches are received by the =
signalling gateway via STP. There's no class five services.</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">RFC 3525, point 11.5 &quot;failure of =
an MGC&quot; describe the procedures for the MG in order to switch to =
another MGC in case of failure of the primary MGC. This is in&nbsp; my =
opinion one of the facilities that make MEGACO better than =
MGCP.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">-In my understanding, the mechanism =
described above is possible only if the MGC's are working in the =
&quot;Hot/Stand by&quot; modality. =BFAm I right?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">-The Signalling Gateways have an =
unique DPC (destination point code).&nbsp; Having different DPC is not =
possible =BFIs this correct?.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Now, Suppose that you have the =
same&nbsp; two MGCs, but&nbsp; working in the &quot;Sharing load&quot; =
modality, each of them controlling a group of MG's.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">-In this architecture each MGC have a =
DPC different from the other.=BFIs this correct?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">-In this case, switching to another =
MGC is not possible because the vocals trunks (wich are asociated with =
the fisical terminations), are related to ONE DPC. =BFIs this =
correct?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">However, in a sharing load scenario, =
it's possible to use Virtual MGs in order give redundance to NGN - TDM =
conection (point 11.1 &quot;Multiple Virtual MGs&quot;).</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">So, making a summary, if I'm not =
wrong, depending on the Architecture, &quot;Hot/Stand by&quot; or in =
the other hand &quot;Sharing load&quot;, you can take advantage of =
using switching mechanism or virtual MGs.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I will appreciate all the comments, =
</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks in advance,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Jos=E9 Luis</FONT>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4C1BF.E6086280--


--===============0638570932==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0638570932==--



From megaco-bounces@ietf.org  Wed Nov  3 11:24:33 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23557
	for <megaco-archive@lists.ietf.org>; Wed, 3 Nov 2004 11:24:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPNqb-0002TZ-CR; Wed, 03 Nov 2004 11:18:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPNoB-0001ls-JE; Wed, 03 Nov 2004 11:16:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22899;
	Wed, 3 Nov 2004 11:16:25 -0500 (EST)
From: Albrecht.Schwarz@alcatel.de
Received: from mailrelay1.alcatel.de ([194.113.59.55]
	helo=mailrelay2.alcatel.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPO3V-0000MQ-0s; Wed, 03 Nov 2004 11:32:19 -0500
Received: from demail05.netfr.alcatel.fr (demail05.netfr.alcatel.fr
	[155.132.182.205])
	by mailrelay2.alcatel.de (8.12.11/8.12.10) with ESMTP id iA3GFnhH015859;
	Wed, 3 Nov 2004 17:15:49 +0100 (MET)
In-Reply-To: <B258A372CEA20246A363BB86753DB5366BA7E4@zrtphxm2>
Subject: RE: [Megaco] H.248.1 V3 Appendix II "H.248 Package Template":
	Err	orCodes
To: "Kevin Boyle" <kboyle@nortelnetworks.com>
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFAFCF50E0.1C8C18BF-ONC1256F41.0058C0C2-C1256F41.005955ED@netfr.alcatel.fr>
Date: Wed, 3 Nov 2004 17:15:46 +0100
X-MIMETrack: Serialize by Router on DEMAIL05/DE/ALCATEL(Release 5.0.11 |July
	24, 2002) at 11/03/2004 17:15:49
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-AES-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: Tom-PT Taylor <taylor@nortelnetworks.com>,
        Christian Groves <christian.groves@ericsson.com>, megaco@ietf.org,
        megaco-bounces@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org


Thanks Tom & Kevin!
This means that there's a common codepoint space for package independent
and package specific error codes, meaning, I need an IANA registration for
package specific error codes as well. Right?

If yes, perhaps a corresponding note in H.248.1 V3, Appendix II, cl. 5.5
might be helpful.
E.g.: "Error code assignment shall follow the same rules as described in
H.248.4, clause 4.1 'Assigning Error Codes'".

What do you think about such a note?
Shall I write a contribution?

Regards
Albrecht




                                                                                                                                
                      "Kevin Boyle"                                                                                             
                      <kboyle@nortelne         To:      "Tom-PT Taylor" <taylor@nortelnetworks.com>, Albrecht                   
                      tworks.com>              SCHWARZ/DE/ALCATEL@ALCATEL                                                       
                      Sent by:                 cc:      Christian Groves <christian.groves@ericsson.com>, megaco@ietf.org       
                      megaco-bounces@i         Subject: RE: [Megaco] H.248.1 V3 Appendix II "H.248 Package Template": Err       
                      etf.org                  orCodes                                                                          
                                                                                                                                
                                                                                                                                
                      03.11.2004 16:25                                                                                          
                                                                                                                                




To date, error codes which are specifically related to a particular
package's function are defined by the package and those independent of
package function get put in H.248.8.

Kevin

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Taylor, Tom-PT [CAR:5N00:EXCH]
Sent: Wednesday, November 03, 2004 9:38 AM
To: Albrecht.Schwarz@alcatel.de
Cc: Christian Groves; megaco@ietf.org
Subject: Re: [Megaco] H.248.1 V3 Appendix II "H.248 Package Template":
ErrorCodes

Error codes may be defined in packages, but in fact they are generally
applicable.
  The package just happens to be where they are documented.

Of course, by its nature the error may be something that can't possibly
occur unless you are using a particular package.  When defining an error,
you need to come up with a balance between the amount of information it
provides (which should be enough to point corrective action in the right
direction, but not enough to be a debugging tool on its own) and the
possibility of its more general application (which is desirable).

Albrecht.Schwarz@alcatel.de wrote:
> Hello Christian,
>
> got a basic question to the Error Code section
> (H.248.1 V3, Appendix II, cl. 5.5,
> http://ftp3.itu.int/av-arch/avc-site/2001-2004/0408_San/TD-33.zip)
> in the V3 template.
>
> Package specific error codes shall be defined in form of
>
>
> <Error Code Title>
>
>        Error Code #:    <number>
>
>        Name:                  <name>
>
>        Definition:            <definition>
>
>        Error Text in the Error Descriptor:
>
>           <error text to return>
>
>        Comment:   <comment>
>
>
> Question: how are local (i.e, package specific error codes)
> distinguished from global ones (= H.248.8)?
> How may the MGC distinguish between local & global?
>
> Background: I'm currently drafting the H.248.33 local error code.
>
> Thanks
> Albrecht
>
>
>
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>
>

--
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.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-bounces@ietf.org  Wed Nov  3 19:53:23 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08537
	for <megaco-archive@lists.ietf.org>; Wed, 3 Nov 2004 19:53:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPVq4-0002VA-As; Wed, 03 Nov 2004 19:50:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPVmV-0001fh-0u; Wed, 03 Nov 2004 19:47:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08152;
	Wed, 3 Nov 2004 19:47:11 -0500 (EST)
Received: from eagle.ericsson.se ([193.180.251.53])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CPW1k-0004Dz-Lr; Wed, 03 Nov 2004 20:03:11 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iA40l2R2025078; Thu, 4 Nov 2004 01:47:02 +0100
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 4 Nov 2004 01:47:02 +0100
Received: from eaubrnt019.epa.ericsson.se ([146.11.9.165]) by
	esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id VJSNWNNW; Thu, 4 Nov 2004 01:47:01 +0100
Received: from ericsson.com (EG2E500202DSEGL [146.11.22.6]) by
	eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WDN9XHG2; Thu, 4 Nov 2004 11:46:57 +1100
Message-ID: <41897541.7050702@ericsson.com>
Date: Thu, 04 Nov 2004 11:18:09 +1100
X-Sybari-Trust: f8182d0f bfd556f1 5d79371e 00000139
From: Christian Groves <christian.groves@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Albrecht.Schwarz@alcatel.de
Subject: Re: [Megaco] H.248.1 V3 Appendix II "H.248 Package Template": Err
	orCodes
References: <OFAFCF50E0.1C8C18BF-ONC1256F41.0058C0C2-C1256F41.005955ED@netfr.alcatel.fr>
In-Reply-To: <OFAFCF50E0.1C8C18BF-ONC1256F41.0058C0C2-C1256F41.005955ED@netfr.alcatel.fr>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Nov 2004 00:47:02.0371 (UTC)
	FILETIME=[CC70A330:01C4C207]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Content-Transfer-Encoding: 7bit
Cc: megaco-bounces@ietf.org, Tom-PT Taylor <taylor@nortelnetworks.com>,
        megaco@ietf.org, Kevin Boyle <kboyle@nortelnetworks.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hello Albrecht,

Yes you are correct that even for package specific error codes you need to 
register them with IANA. The note you propose would be beneficial. Rather than 
writing a new contribution you could add this to the proposal section of the 
contribution that introduces the error codes.

Regards, Christian

Albrecht.Schwarz@alcatel.de wrote:

> Thanks Tom & Kevin!
> This means that there's a common codepoint space for package independent
> and package specific error codes, meaning, I need an IANA registration for
> package specific error codes as well. Right?
> 
> If yes, perhaps a corresponding note in H.248.1 V3, Appendix II, cl. 5.5
> might be helpful.
> E.g.: "Error code assignment shall follow the same rules as described in
> H.248.4, clause 4.1 'Assigning Error Codes'".
> 
> What do you think about such a note?
> Shall I write a contribution?
> 
> Regards
> Albrecht
> 
> 
> 
> 
>                                                                                                                                 
>                       "Kevin Boyle"                                                                                             
>                       <kboyle@nortelne         To:      "Tom-PT Taylor" <taylor@nortelnetworks.com>, Albrecht                   
>                       tworks.com>              SCHWARZ/DE/ALCATEL@ALCATEL                                                       
>                       Sent by:                 cc:      Christian Groves <christian.groves@ericsson.com>, megaco@ietf.org       
>                       megaco-bounces@i         Subject: RE: [Megaco] H.248.1 V3 Appendix II "H.248 Package Template": Err       
>                       etf.org                  orCodes                                                                          
>                                                                                                                                 
>                                                                                                                                 
>                       03.11.2004 16:25                                                                                          
>                                                                                                                                 
> 
> 
> 
> 
> To date, error codes which are specifically related to a particular
> package's function are defined by the package and those independent of
> package function get put in H.248.8.
> 
> Kevin
> 
> -----Original Message-----
> From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
> Taylor, Tom-PT [CAR:5N00:EXCH]
> Sent: Wednesday, November 03, 2004 9:38 AM
> To: Albrecht.Schwarz@alcatel.de
> Cc: Christian Groves; megaco@ietf.org
> Subject: Re: [Megaco] H.248.1 V3 Appendix II "H.248 Package Template":
> ErrorCodes
> 
> Error codes may be defined in packages, but in fact they are generally
> applicable.
>   The package just happens to be where they are documented.
> 
> Of course, by its nature the error may be something that can't possibly
> occur unless you are using a particular package.  When defining an error,
> you need to come up with a balance between the amount of information it
> provides (which should be enough to point corrective action in the right
> direction, but not enough to be a debugging tool on its own) and the
> possibility of its more general application (which is desirable).
> 
> Albrecht.Schwarz@alcatel.de wrote:
> 
>>Hello Christian,
>>
>>got a basic question to the Error Code section
>>(H.248.1 V3, Appendix II, cl. 5.5,
>>http://ftp3.itu.int/av-arch/avc-site/2001-2004/0408_San/TD-33.zip)
>>in the V3 template.
>>
>>Package specific error codes shall be defined in form of
>>
>>
>><Error Code Title>
>>
>>       Error Code #:    <number>
>>
>>       Name:                  <name>
>>
>>       Definition:            <definition>
>>
>>       Error Text in the Error Descriptor:
>>
>>          <error text to return>
>>
>>       Comment:   <comment>
>>
>>
>>Question: how are local (i.e, package specific error codes)
>>distinguished from global ones (= H.248.8)?
>>How may the MGC distinguish between local & global?
>>
>>Background: I'm currently drafting the H.248.33 local error code.
>>
>>Thanks
>>Albrecht
>>
>>
>>
>>
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>>
> 
> 
> --
> Tom Taylor
> Carrier VoIP Standards Development
> Nortel Networks
> Phone +1 613 763 1496  (ESN 393-1496)
> E-mail: taylor@nortelnetworks.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-bounces@ietf.org  Fri Nov  5 02:18:37 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10563
	for <megaco-archive@lists.ietf.org>; Fri, 5 Nov 2004 02:18:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CPyLB-0000cM-0b; Fri, 05 Nov 2004 02:16:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CPyCF-0005ii-Ly
	for megaco@megatron.ietf.org; Fri, 05 Nov 2004 02:07:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02822
	for <megaco@ietf.org>; Fri, 5 Nov 2004 02:07:41 -0500 (EST)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPyRv-0003Hf-9g
	for megaco@ietf.org; Fri, 05 Nov 2004 02:23:55 -0500
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I6P006DA2FX0O@mailout3.samsung.com> for megaco@ietf.org; Fri,
	05 Nov 2004 16:07:09 +0900 (KST)
Received: from ep_ms7_bk (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I6P00LRL2EYRQ@mailout3.samsung.com> for megaco@ietf.org;
	Fri, 05 Nov 2004 16:06:34 +0900 (KST)
Received: from ep_spt04 (ms7.samsung.com [203.254.225.101])
	by ms7.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTP id <0I6P005Z92EYNG@ms7.samsung.com> for megaco@ietf.org; Fri,
	05 Nov 2004 16:06:34 +0900 (KST)
Content-return: prohibited
Date: Fri, 05 Nov 2004 07:06:34 +0000 (GMT)
From: =?euc-kr?B?seiw6L/P?= <kkyewan@samsung.com>
Subject: [MEGACO] Number of Call Processing Blocks in VMG ?
X-Sender: =?euc-kr?B?u++8usD8wNqh501HVyBMYWIuMihDb3JlKaHnRTUow6XA0ykvw6XA0w==?=
To: megaco@ietf.org
Message-id: <0I6P005ZA2EYNG@ms7.samsung.com>
MIME-version: 1.0
X-Priority: 3
Msgkey: 20041105070633073@kkyewan
X-MTR: 20041105070633073@kkyewan
X-EPLocale: ko_KR.euc-kr
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-Generator: NamoMIME 1.1.0.17
X-Spam-Score: 2.8 (++)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: kkyewan@samsung.com
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1747992929=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

--===============1747992929==
Content-return: prohibited
Content-type: text/html; charset=euc-kr
Content-Transfer-Encoding: base64

PEhUTUw+PEhFQUQ+PE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVudD0ndGV4dC9o
dG1sOyBjaGFyc2V0PWV1Yy1rcic+Cjx0aXRsZT5TYW1zdW5nIEVudGVycHJpc2UgUG9ydGFsIG15
U2luZ2xlPC90aXRsZT4KPHN0eWxlPiBQLCB0ZCwgbGkge2ZvbnQtZmFtaWx5OrG8uLLDvCwgYXJp
YWw7IGZvbnQtc2l6ZTo5cHQ7IG1hcmdpbi10b3A6NXB4O21hcmdpbi1ib3R0b206NXB4O308L3N0
eWxlPgo8L0hFQUQ+CjxCT0RZPg0KPHA+SGVsbG8uPC9wPg0KPHA+Jm5ic3A7PC9wPg0KPFBSRSBz
dHlsZT0iTUFSR0lOOiAwZW0iPkkgd29uZGVyIGFib3V0IHRoZSBudW1iZXIgb2YgY2FsbCBwcm9j
ZXNzaW5nIGJsb2NrIChDUCkgaW4gVk1HLjwvUFJFPg0KPHA+SW4mbmJzcDtWTUcsIEkgdGhpbmsg
dGhlIGJlbG93IDIgc3cgYXJjaGl0ZWN0dXJlIGNhbiBiZSBwb3NzaWJsZS4gKGlzIGNvcnJlY3Qg
DQpteSB0aGlua2luZz8pPC9wPg0KPHA+SWYgbXkgdGhpbmtpbmcgaXMgY29ycmVjdCwgd2hpY2gg
YXJjaGl0ZWN0dXJlIGlzIG1vcmUgZ2VuZXJhbCA/PC9wPg0KPHA+Jm5ic3A7PC9wPg0KPHA+MS4g
bW9kZWwgMSAoQ1AxPSZndDtWTUcxLENQMj0mZ3Q7TUcyKTwvcD4NCjxwPlByb2Nlc3MgQ1AxIGNv
bnRyb2xzIFZNRzEgY2FsbCBjb250cm9sLCBBbm90aGVyIHByb2Nlc3MgQ1AyIGNvbnRyb2xzIFZN
RzIgDQpjYWxsIGNvbnRyb2wuPC9wPg0KPHA+aWYgTiBWTUdzLCB0aGUgbnVtYmVyIE4gY2FsbCBw
cm9jZXNzaW5nIGJsb2NrcyBpcyBydW5uaW5nIHNpbXVsdGFuZW91c2x5PC9wPg0KPHA+Jm5ic3A7
PC9wPg0KPHA+Mi4gbW9kZWwgMiAoQ29tbW9uIENQPSZndDtWTUcxLFZNRzIpPC9wPg0KPHA+Q29t
bW9uIHByb2Nlc3MgQ1AgY29udHJvbHMgVk1HMSwgVk1HMi4gJm5ic3A7VGhlIENQIGNhbiBtYW5h
Z2UgVk1HMSxWTUcyIA0KaW50ZXJuYWxseS48L3A+DQo8cD5pbiBOIFZNR3MsIG9ubHkgb25lIGNh
bGwgcHJvY2Vzc2luZyBibG9jayBpcyBydW5uaW5nLjwvcD4NCjxwPiZuYnNwOzwvcD48L0JPRFk+
PC9IVE1MPg==




--===============1747992929==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1747992929==--


From megaco-bounces@ietf.org  Fri Nov  5 08:06:51 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09424
	for <megaco-archive@lists.ietf.org>; Fri, 5 Nov 2004 08:06:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ3gP-0001bZ-Kh; Fri, 05 Nov 2004 07:59:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ3dz-0001Ik-Tr
	for megaco@megatron.ietf.org; Fri, 05 Nov 2004 07:56:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08602
	for <megaco@ietf.org>; Fri, 5 Nov 2004 07:56:42 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ3tZ-0002CX-4f
	for megaco@ietf.org; Fri, 05 Nov 2004 08:12:59 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id 349333468E8
	for <megaco@ietf.org>; Fri,  5 Nov 2004 04:55:43 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 06884-7C0B67F1;
	Fri, 05 Nov 2004 04:55:43 -0800
Received: from Mahesh (unknown [172.25.0.61])
	by smtp.ccpu.com (Postfix) with ESMTP id 71E7D3468E8
	for <megaco@ietf.org>; Fri,  5 Nov 2004 04:55:41 -0800 (PST)
From: "Mahesh" <mahesh@ccpu.com>
To: <megaco@ietf.org>
Date: Fri, 5 Nov 2004 18:25:45 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcTDNsO1K67N2RsKQtGQ2BlUf8h8sA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-Id: <20041105125541.71E7D3468E8@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.57; host: smtp)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f8ee348dcc4be4a59bc395f7cd6343ad
Subject: [Megaco] Question related to Txn pending and Pending limit 
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0572680043=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0572680043==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0019_01C4C364.DE935540"

This is a multi-part message in MIME format.

------=_NextPart_000_0019_01C4C364.DE935540
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

HI  All,

 

I would like to clarify the sending of the error response 506 , when the
pending limit gets crossed .

 

Consider a situation like this

MGOriginated pending limit is 1 .

This is set at MG side by MGC using appropriate message.

MGC send a command to MG .

MG is waiting for the response from user .With in this time the provisional
response timer times out .

MG sends the txn pending to MGC .

Now MGC gets the txn pending message .It finds that the pending limit has
crossed and  do some actions , and abort the

Txn.

 

 

The questions is what time  MG have to send the 506 .whether it has to send
the error message along with the txnpending message.Whether this makes any
sense 

OR 

Whether the MG have to wait for some time to send the final 506.

 

Since MGC is tracking the number of txn pending messages send by MG, When
MGC  finds that the number of

Pending limit have crossed the limit , will it leads to some inconsistency
.The actual error response may come only after

Some time.

 

 

Could you please clarify this.

 

With regards

Mahesh

 

 

 

 


------=_NextPart_000_0019_01C4C364.DE935540
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>HI &nbsp;All,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I would like to clarify the sending of the error =
response
506 , when the pending limit gets crossed .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Consider a situation like =
this<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MGOriginated pending limit is 1 =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This is set at MG side by MGC using appropriate =
message.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MGC send a command to MG =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MG is waiting for the response from user .With in =
this time
the provisional response timer times out .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MG sends the txn pending to MGC =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Now MGC gets the txn pending message .It finds that =
the
pending limit has crossed and&nbsp; do some actions , and abort =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Txn.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The questions is what time&nbsp; MG have to send the =
506
.whether it has to send the error message along with the txnpending =
message.Whether
this makes any sense <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>OR <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Whether the MG have to wait for some time to send the =
final 506.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Since MGC is tracking the number of txn pending =
messages
send by MG, When MGC&nbsp; finds that the number =
of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Pending limit have crossed the limit , will it leads =
to some
inconsistency .The actual error response may come only =
after<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Some time.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Could you please clarify =
this.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>With regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Mahesh<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0019_01C4C364.DE935540--




--===============0572680043==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0572680043==--





From megaco-bounces@ietf.org  Fri Nov  5 10:00:44 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18322
	for <megaco-archive@lists.ietf.org>; Fri, 5 Nov 2004 10:00:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CQ5TD-0004LY-8r; Fri, 05 Nov 2004 09:53:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ5NX-0003E1-DH
	for megaco@megatron.ietf.org; Fri, 05 Nov 2004 09:47:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17390
	for <megaco@ietf.org>; Fri, 5 Nov 2004 09:47:49 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ5dH-0004k0-UA
	for megaco@ietf.org; Fri, 05 Nov 2004 10:04:08 -0500
Received: from zcard303.ca.nortel.com (zcard303.ca.nortel.com [47.129.242.59])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iA5ElFx14705; Fri, 5 Nov 2004 09:47:15 -0500 (EST)
Received: from [47.102.178.119] (archt12f.us.nortel.com [47.102.178.119]) by
	zcard303.ca.nortel.com with SMTP (Microsoft Exchange Internet
	Mail Service Version 5.5.2653.13)
	id W14F3QMJ; Fri, 5 Nov 2004 09:47:15 -0500
Message-ID: <418B9271.2080205@nortelnetworks.com>
Date: Fri, 05 Nov 2004 09:47:13 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: kkyewan@samsung.com
Subject: Re: [MEGACO] Number of Call Processing Blocks in VMG ?
References: <0I6P005ZA2EYNG@ms7.samsung.com>
In-Reply-To: <0I6P005ZA2EYNG@ms7.samsung.com>
Content-Type: text/plain; charset=EUC-KR
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

The second architecture is definitely possible.  It is also possible to h=
ave a
pool of processes.  The size of the pool is governed by engineering
considerations, but messages are queued by a central dispatch process and=
 handed
off to members of the pool as they become available.

=B1=E8=B0=E8=BF=CF wrote:
> Hello.
>=20
> =20
>=20
> I wonder about the number of call processing block (CP) in VMG.
>=20
> In VMG, I think the below 2 sw architecture can be possible. (is correc=
t=20
> my thinking?)
>=20
> If my thinking is correct, which architecture is more general ?
>=20
> =20
>=20
> 1. model 1 (CP1=3D>VMG1,CP2=3D>MG2)
>=20
> Process CP1 controls VMG1 call control, Another process CP2 controls=20
> VMG2 call control.
>=20
> if N VMGs, the number N call processing blocks is running simultaneousl=
y
>=20
> =20
>=20
> 2. model 2 (Common CP=3D>VMG1,VMG2)
>=20
> Common process CP controls VMG1, VMG2.  The CP can manage VMG1,VMG2=20
> internally.
>=20
> in N VMGs, only one call processing block is running.
>=20
> =20
>=20
>=20
> -----------------------------------------------------------------------=
-
>=20
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco

--=20
Tom Taylor
Carrier VoIP Standards Development
Nortel Networks
Phone +1 613 763 1496  (ESN 393-1496)
E-mail: taylor@nortelnetworks.com


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


From megaco-bounces@ietf.org  Mon Nov  8 07:22:25 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27296
	for <megaco-archive@lists.ietf.org>; Mon, 8 Nov 2004 07:22:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CR8Uw-00070P-6y; Mon, 08 Nov 2004 07:19:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CR8T4-0006rO-V6
	for megaco@megatron.ietf.org; Mon, 08 Nov 2004 07:17:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26853
	for <megaco@ietf.org>; Mon, 8 Nov 2004 07:17:51 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CR8TR-0006cp-6q
	for megaco@ietf.org; Mon, 08 Nov 2004 07:18:28 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id 2BA583468C3
	for <megaco@ietf.org>; Mon,  8 Nov 2004 05:16:52 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 14493-741AEA72;
	Mon, 08 Nov 2004 05:16:52 -0800
Received: from Mahesh (unknown [172.25.0.61])
	by smtp.ccpu.com (Postfix) with ESMTP id D768F3468C3
	for <megaco@ietf.org>; Mon,  8 Nov 2004 05:16:50 -0800 (PST)
From: "Mahesh" <mahesh@ccpu.com>
To: <megaco@ietf.org>
Date: Mon, 8 Nov 2004 17:46:47 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcTFjNFiDCGAtaTZTtqgYCgTj/v3vQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-Id: <20041108131650.D768F3468C3@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.60; host: smtp)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ccfb4541e989aa743998098cd315d0fd
Subject: [Megaco] Protocol Version negotiation
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2109333253=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2109333253==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0042_01C4C5BA.EEB3DB90"

This is a multi-part message in MIME format.

------=_NextPart_000_0042_01C4C5BA.EEB3DB90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

HI  All,

 

I would like to clarify one doubt regarding version negotiation.

 

Assume a scenario like this.

MG is sending MGC a service change  with version 1.

MGC sends a reply With version 2 .

What should be the expected behavior from the MG side .Assume that

Both MG and MGC supports versions 1 and 2 .

 

 

I think the section (11.3  )  doesn't explains this scenario clearly .

 

Could you please correct me if I am wrong?

 

With regards

Mahesh

 

 


------=_NextPart_000_0042_01C4C5BA.EEB3DB90
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>HI&nbsp; All,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I would like to clarify one doubt regarding version =
negotiation.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Assume a scenario like =
this.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MG is sending MGC a service change&nbsp; with version =
1.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MGC sends a reply With version 2 =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>What should be the expected behavior from the MG side =
.Assume
that<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Both MG and MGC supports versions 1 and 2 =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I think the section (11.3&nbsp; ) &nbsp;doesn&#8217;t =
explains
this scenario clearly .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Could you please correct me if I am =
wrong?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>With regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Mahesh<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0042_01C4C5BA.EEB3DB90--




--===============2109333253==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============2109333253==--





From megaco-bounces@ietf.org  Mon Nov  8 07:24:41 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27490
	for <megaco-archive@lists.ietf.org>; Mon, 8 Nov 2004 07:24:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CR8Uw-00070V-PS; Mon, 08 Nov 2004 07:19:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CR8T4-0006rP-V6
	for megaco@megatron.ietf.org; Mon, 08 Nov 2004 07:17:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26856
	for <megaco@ietf.org>; Mon, 8 Nov 2004 07:17:51 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CR8Tb-0006d6-O3
	for megaco@ietf.org; Mon, 08 Nov 2004 07:18:28 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id 7DD963468F0
	for <megaco@ietf.org>; Mon,  8 Nov 2004 05:17:08 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 14528-7DB66821;
	Mon, 08 Nov 2004 05:17:08 -0800
Received: from Mahesh (unknown [172.25.0.61])
	by smtp.ccpu.com (Postfix) with ESMTP id 45A3B3468F0
	for <megaco@ietf.org>; Mon,  8 Nov 2004 05:17:07 -0800 (PST)
From: "Mahesh" <mahesh@ccpu.com>
To: <megaco@ietf.org>
Date: Mon, 8 Nov 2004 17:47:08 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcTDNsO1K67N2RsKQtGQ2BlUf8h8sACVhGZA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-Id: <20041108131707.45A3B3468F0@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.60; host: smtp)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 3be09dac38eaa50f02d21c7fcee1128c
Subject: [Megaco] Question related to Txn pending and Pending limit 
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1760561355=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1760561355==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0046_01C4C5BA.F88D1140"

This is a multi-part message in MIME format.

------=_NextPart_000_0046_01C4C5BA.F88D1140
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

 

 

HI  All,

 

I would like to clarify the sending of the error response 506 , when the
pending limit gets crossed .

 

Consider a situation like this

MGOriginated pending limit is 1 .

This is set at MG side by MGC using appropriate message.

MGC send a command to MG .

MG is waiting for the response from user .With in this time the provisional
response timer times out .

MG sends the txn pending to MGC .

Now MGC gets the txn pending message .It finds that the pending limit has
crossed and  do some actions , and abort the

Txn.

 

 

The questions is what time  MG have to send the 506 .whether it has to send
the error message along with the txnpending message.Whether this makes any
sense 

OR 

Whether the MG have to wait for some time to send the final 506.

 

Since MGC is tracking the number of txn pending messages send by MG, When
MGC  finds that the number of

Pending limit have crossed the limit , will it leads to some inconsistency
.The actual error response may come only after

Some time.

 

 

Could you please clarify this.

 

With regards

Mahesh

 

 

 

 


------=_NextPart_000_0046_01C4C5BA.F88D1140
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>HI &nbsp;All,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I would like to clarify the sending of the error =
response
506 , when the pending limit gets crossed .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Consider a situation like =
this<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MGOriginated pending limit is 1 =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This is set at MG side by MGC using appropriate =
message.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MGC send a command to MG =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MG is waiting for the response from user .With in =
this time
the provisional response timer times out .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MG sends the txn pending to MGC =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Now MGC gets the txn pending message .It finds that =
the
pending limit has crossed and&nbsp; do some actions , and abort =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Txn.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The questions is what time&nbsp; MG have to send the =
506
.whether it has to send the error message along with the txnpending
message.Whether this makes any sense <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>OR <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Whether the MG have to wait for some time to send the =
final
506.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Since MGC is tracking the number of txn pending =
messages
send by MG, When MGC&nbsp; finds that the number =
of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Pending limit have crossed the limit , will it leads =
to some
inconsistency .The actual error response may come only =
after<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Some time.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Could you please clarify =
this.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>With regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Mahesh<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0046_01C4C5BA.F88D1140--




--===============1760561355==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1760561355==--





From megaco-bounces@ietf.org  Mon Nov  8 07:56:44 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01008
	for <megaco-archive@lists.ietf.org>; Mon, 8 Nov 2004 07:56:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CR8wT-0001m2-7B; Mon, 08 Nov 2004 07:48:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CR8o5-0000d5-3C
	for megaco@megatron.ietf.org; Mon, 08 Nov 2004 07:39:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28879
	for <megaco@ietf.org>; Mon, 8 Nov 2004 07:39:34 -0500 (EST)
Received: from sulu.siemens.com.br ([200.186.153.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CR8oP-00078G-PE
	for megaco@ietf.org; Mon, 08 Nov 2004 07:40:09 -0500
X-Envelope-Sender-Is: thiago.mello@siemens.com (at relayer sulu.siemens.com.br)
Received: from sao0021x.siemens.com.br ([200.186.153.35])
	by sulu.siemens.com.br (8.12.10/8.9.3) with ESMTP id iA8CcklZ052545
	for <megaco@ietf.org>; Mon, 8 Nov 2004 10:38:46 -0200 (BRST)
Received: from sao1022a.br002.siemens.net.br ([129.214.31.222])
	by sao0021x.siemens.com.br (8.12.10/8.9.3) with ESMTP id iA9CLqDP047274
	for <megaco@ietf.org>; Tue, 9 Nov 2004 10:21:52 -0200 (BRST)
Received: from sao1023a.br002.siemens.net.br ([129.214.31.23]) by sao1022a
	with InterScan Messaging Security Suite;
	Mon, 08 Nov 2004 10:38:14 -0200
Received: from CUR1006V.br002.siemens.net.br ([129.214.65.6]) by
	sao1023a.br002.siemens.net.br with Microsoft SMTPSVC(5.0.2195.6713); 
	Mon, 8 Nov 2004 10:38:14 -0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Megaco] Protocol Version negotiation
Date: Mon, 8 Nov 2004 10:38:13 -0200
Message-ID: <6F370EA7A7381442975C0387BF3062BD02F5D836@CUR1006V.br002.siemens.net.br>
Thread-Topic: [Megaco] Protocol Version negotiation
Thread-Index: AcTFjNFiDCGAtaTZTtqgYCgTj/v3vQAAshjQ
From: "THIAGO MELLO" <thiago.mello@siemens.com>
To: "Mahesh" <mahesh@ccpu.com>, <megaco@ietf.org>
X-OriginalArrivalTime: 08 Nov 2004 12:38:14.0136 (UTC)
	FILETIME=[D0723F80:01C4C58F]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1953463095=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1953463095==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C58F.D0224DFD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C58F.D0224DFD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As the same section, I interpreted that the MGC will send a reply with
version 1.
=20

Thiago Mello - <thiago.mello@siemens.com>
------------------------------------------
Siemens Brazil - http://www.siemens.com.br <http://www.siemens.com.br/>=20
COM RCC R&D SWC - SW Control Development
Tel.: +55 (41) 3025-9728 / 9958-0802 =20

	-----Original Message-----
	From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]
On Behalf Of Mahesh
	Sent: Monday, November 08, 2004 10:17 AM
	To: megaco@ietf.org
	Subject: [Megaco] Protocol Version negotiation
=09
=09

	HI  All,

	=20

	I would like to clarify one doubt regarding version negotiation.

	=20

	Assume a scenario like this.

	MG is sending MGC a service change  with version 1.

	MGC sends a reply With version 2 .

	What should be the expected behavior from the MG side .Assume
that

	Both MG and MGC supports versions 1 and 2 .

	=20

	=20

	I think the section (11.3  )  doesn't explains this scenario
clearly .

	=20

	Could you please correct me if I am wrong?

	=20

	With regards

	Mahesh

	=20

	=20


------_=_NextPart_001_01C4C58F.D0224DFD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D491423612-08112004><FONT face=3DArial color=3D#0000ff =
size=3D2>As the=20
same section, I interpreted that the MGC will send a reply with version=20
1.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV><!-- Converted from text/plain format -->
<P><FONT size=3D2>Thiago Mello -=20
&lt;thiago.mello@siemens.com&gt;<BR>-------------------------------------=
-----<BR>Siemens=20
Brazil - <A=20
href=3D"http://www.siemens.com.br/">http://www.siemens.com.br</A><BR>COM =
RCC=20
R&amp;D SWC - SW Control Development<BR>Tel.: +55 (41) 3025-9728 /=20
9958-0802&nbsp; </FONT></P>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; 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-bounces@ietf.org [mailto:megaco-bounces@ietf.org] <B>On Behalf =
Of=20
  </B>Mahesh<BR><B>Sent:</B> Monday, November 08, 2004 10:17 =
AM<BR><B>To:</B>=20
  megaco@ietf.org<BR><B>Subject:</B> [Megaco] Protocol Version=20
  negotiation<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">HI&nbsp;=20
  All,<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I would like to clarify =
one doubt=20
  regarding version negotiation.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Assume a scenario like=20
  this.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">MG is sending MGC a =
service=20
  change&nbsp; with version 1.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">MGC sends a reply With =
version 2=20
  .<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">What should be the =
expected=20
  behavior from the MG side .Assume that<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Both MG and MGC supports =
versions=20
  1 and 2 .<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I think the section =
(11.3&nbsp; )=20
  &nbsp;doesn&#8217;t explains this scenario clearly =
.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Could you please correct =
me if I=20
  am wrong?<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">With=20
  regards<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Mahesh<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

------_=_NextPart_001_01C4C58F.D0224DFD--


--===============1953463095==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1953463095==--



From megaco-bounces@ietf.org  Mon Nov  8 09:28:09 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12060
	for <megaco-archive@lists.ietf.org>; Mon, 8 Nov 2004 09:28:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRALA-00028c-KW; Mon, 08 Nov 2004 09:17:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRA6g-0006m6-TP
	for megaco@megatron.ietf.org; Mon, 08 Nov 2004 09:02:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09483
	for <megaco@ietf.org>; Mon, 8 Nov 2004 09:02:53 -0500 (EST)
Received: from [61.144.161.55] (helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRA6f-0001Ka-Ki
	for megaco@ietf.org; Mon, 08 Nov 2004 09:03:29 -0500
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0I6V00B764H5TT@szxga03-in.huawei.com> for
	megaco@ietf.org; Mon, 08 Nov 2004 21:36:42 +0800 (CST)
Received: from szxml01-in ([172.24.1.3])
	by szxga03-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTP id	<0I6V006DD4H508@szxga03-in.huawei.com>
	formegaco@ietf.org; Mon, 08 Nov 2004 21:36:41 +0800 (CST)
Received: from r70036l ([10.125.31.5])
	by szxml01-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTPA id	<0I6V007I74LYJR@szxml01-in.huawei.com>; Mon,
	08 Nov 2004 21:39:40 +0800 (CST)
Date: Mon, 08 Nov 2004 13:38:20 +0000
From: Rajeev K R <rajeev@huawei.com>
Subject: RE: [Megaco] Question related to Txn pending and Pending limit
In-reply-to: <20041108131707.45A3B3468F0@smtp.ccpu.com>
To: "'Mahesh'" <mahesh@ccpu.com>, megaco@ietf.org
Message-id: <004d01c4c598$38fe3060$7080a8c0@r70036l>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cbb41f2dbf0f142369614756642005e3
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0058596416=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0058596416==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_5xSOcBqCHHxGDiwrO8vqZA)"

This is a multi-part message in MIME format.

--Boundary_(ID_5xSOcBqCHHxGDiwrO8vqZA)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

>From H.248.1:

If the MGC supports a higher version than the MG but is able to support the
lower version proposed by the MG, it shall send a ServiceChangeReply with
the lower version and thereafter all the messages between MG and MGC shall
conform to the lower version of the protocol. If the MGC is unable to
comply, it shall reject the association, with Error 406 (Version Not
Supported).

In your case it looks like the MGC is violating the protocol.

If MGC intends to say that it suppors version 2 only and cannot support
version 1, it should have rejected

ServiceChange with error 406.

Since your MG cannot support version 2, it should behave as if the version
negotiation failed (and reject all commands from MGC with error 406).

Rajeev

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Mahesh
Sent: Monday, November 08, 2004 12:17 PM
To: megaco@ietf.org
Subject: [Megaco] Question related to Txn pending and Pending limit



 

 

 

HI  All,

 

I would like to clarify the sending of the error response 506 , when the
pending limit gets crossed .

 

Consider a situation like this

MGOriginated pending limit is 1 .

This is set at MG side by MGC using appropriate message.

MGC send a command to MG .

MG is waiting for the response from user .With in this time the provisional
response timer times out .

MG sends the txn pending to MGC .

Now MGC gets the txn pending message .It finds that the pending limit has
crossed and  do some actions , and abort the

Txn.

 

 

The questions is what time  MG have to send the 506 .whether it has to send
the error message along with the txnpending message.Whether this makes any
sense 

OR 

Whether the MG have to wait for some time to send the final 506.

 

Since MGC is tracking the number of txn pending messages send by MG, When
MGC  finds that the number of

Pending limit have crossed the limit , will it leads to some inconsistency
.The actual error response may come only after

Some time.

 

 

Could you please clarify this.

 

With regards

Mahesh

 

 

 

 


--Boundary_(ID_5xSOcBqCHHxGDiwrO8vqZA)
Content-type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = 
"urn:schemas-microsoft-com:office:office" xmlns:w = 
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1476" name=GENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV>
<P class=MsoNormal style="MARGIN: 6pt 0in 0pt"><SPAN lang=EN-GB 
style="LAYOUT-GRID-MODE: line"><SPAN class=084313113-08112004><FONT face=Arial 
color=#0000ff size=2>From H.248.1:</FONT></SPAN></SPAN></P>
<P class=MsoNormal style="MARGIN: 6pt 0in 0pt"><SPAN lang=EN-GB 
style="LAYOUT-GRID-MODE: line">If the MGC supports a higher version than the MG 
but is able to support the lower version proposed by the MG, it shall send a 
ServiceChangeReply with the lower version and thereafter all the messages 
between MG and MGC shall conform to the lower version of the protocol. If the 
MGC is unable to comply, it shall reject the association, with Error 406 
(Version Not Supported).</SPAN></P>
<P class=MsoNormal style="MARGIN: 6pt 0in 0pt"><SPAN lang=EN-GB 
style="LAYOUT-GRID-MODE: line"><o:p><FONT face=Arial color=#0000ff size=2><SPAN 
class=084313113-08112004>In your case it looks like the MGC is violating the 
protocol.</SPAN></FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 6pt 0in 0pt"><SPAN lang=EN-GB 
style="LAYOUT-GRID-MODE: line"><o:p><FONT face=Arial color=#0000ff size=2><SPAN 
class=084313113-08112004>If MGC intends to say that it suppors version 2 only 
and cannot support version 1, it should have 
rejected</SPAN></FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 6pt 0in 0pt"><SPAN lang=EN-GB 
style="LAYOUT-GRID-MODE: line"><o:p><FONT face=Arial color=#0000ff size=2><SPAN 
class=084313113-08112004>ServiceChange with error 
406.</SPAN></FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 6pt 0in 0pt"><SPAN lang=EN-GB 
style="LAYOUT-GRID-MODE: line"><o:p><FONT face=Arial color=#0000ff size=2><SPAN 
class=084313113-08112004>Since your MG cannot support version 2, it should 
behave as if the version negotiation failed&nbsp;(and reject all commands from 
MGC with error 406).</SPAN></FONT></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN: 6pt 0in 0pt"><SPAN lang=EN-GB 
style="LAYOUT-GRID-MODE: line"><o:p><FONT face=Arial color=#0000ff size=2><SPAN 
class=084313113-08112004>Rajeev</SPAN></FONT></o:p></SPAN></P></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
  megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] <B>On Behalf Of 
  </B>Mahesh<BR><B>Sent:</B> Monday, November 08, 2004 12:17 PM<BR><B>To:</B> 
  megaco@ietf.org<BR><B>Subject:</B> [Megaco] Question related to Txn pending 
  and Pending limit<BR><BR></FONT></DIV>
  <DIV class=Section1>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
  style="FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">HI 
  &nbsp;All,<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I would like to clarify the 
  sending of the error response 506 , when the pending limit gets crossed 
  .<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Consider a situation like 
  this<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">MGOriginated pending limit is 1 
  .<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">This is set at MG side by MGC 
  using appropriate message.<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">MGC send a command to MG 
  .<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">MG is waiting for the response 
  from user .With in this time the provisional response timer times out 
  .<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">MG sends the txn pending to MGC 
  .<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Now MGC gets the txn pending 
  message .It finds that the pending limit has crossed and&nbsp; do some actions 
  , and abort the<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Txn.<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The questions is what time&nbsp; 
  MG have to send the 506 .whether it has to send the error message along with 
  the txnpending message.Whether this makes any sense 
  <o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">OR <o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Whether the MG have to wait for 
  some time to send the final 506.<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Since MGC is tracking the number 
  of txn pending messages send by MG, When MGC&nbsp; finds that the number 
  of<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Pending limit have crossed the 
  limit , will it leads to some inconsistency .The actual error response may 
  come only after<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Some 
  time.<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Could you please clarify 
  this.<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">With 
  regards<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Mahesh<o:p></o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_5xSOcBqCHHxGDiwrO8vqZA)--


--===============0058596416==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0058596416==--



From megaco-bounces@ietf.org  Mon Nov  8 09:32:25 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12612
	for <megaco-archive@lists.ietf.org>; Mon, 8 Nov 2004 09:32:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRAM5-0002ZU-NQ; Mon, 08 Nov 2004 09:18:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRA9q-0007pM-8g
	for megaco@megatron.ietf.org; Mon, 08 Nov 2004 09:06:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09913
	for <megaco@ietf.org>; Mon, 8 Nov 2004 09:06:08 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRAAL-0001f2-FS
	for megaco@ietf.org; Mon, 08 Nov 2004 09:06:44 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iA8E5Uo20385
	for <megaco@ietf.org>; Mon, 8 Nov 2004 09:05:30 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WP4QKB4B>; Mon, 8 Nov 2004 09:05:30 -0500
Message-ID: <B258A372CEA20246A363BB86753DB53684CC59@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Mahesh <mahesh@ccpu.com>, megaco@ietf.org
Subject: RE: [Megaco] Protocol Version negotiation
Date: Mon, 8 Nov 2004 09:05:20 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is not permitted.  The procedures clearly state that the MGC can only
offer a lower version.  If the MG offers v1, and the MGC supports it, it
should start communicating using V1.
 
To quote: 

Upon receiving such a message, if the MGC supports only a lower version,
then the MGC shall send a ServiceChangeReply with the lower version and,
thereafter, all the messages between MG and MGC shall conform to the lower
version of the protocol. 

[clip]

If the MGC supports a higher version than the MG but is able to support the
lower version proposed by the MG, it shall send a ServiceChangeReply with
the lower version and thereafter all the messages between MG and MGC shall
conform to the lower version of the protocol.

 
This means that even if the MGC supports v2, if v1 is what the MG offers,
the MGC either has to use v1 or NACK.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Mahesh
Sent: Monday, November 08, 2004 7:17 AM
To: megaco@ietf.org
Subject: [Megaco] Protocol Version negotiation



HI  All,

 

I would like to clarify one doubt regarding version negotiation.

 

Assume a scenario like this.

MG is sending MGC a service change  with version 1.

MGC sends a reply With version 2 .

What should be the expected behavior from the MG side .Assume that

Both MG and MGC supports versions 1 and 2 .

 

 

I think the section (11.3  )  doesn't explains this scenario clearly .

 

Could you please correct me if I am wrong?

 

With regards

Mahesh

 

 


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


From megaco-bounces@ietf.org  Mon Nov  8 09:42:38 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13787
	for <megaco-archive@lists.ietf.org>; Mon, 8 Nov 2004 09:42:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRAPB-0003P5-NA; Mon, 08 Nov 2004 09:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRAG1-00017I-2v
	for megaco@megatron.ietf.org; Mon, 08 Nov 2004 09:12:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10395
	for <megaco@ietf.org>; Mon, 8 Nov 2004 09:12:31 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRAGZ-0001mj-G7
	for megaco@ietf.org; Mon, 08 Nov 2004 09:13:07 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iA8EC0o21574
	for <megaco@ietf.org>; Mon, 8 Nov 2004 09:12:01 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WP4QKCPR>; Mon, 8 Nov 2004 09:12:01 -0500
Message-ID: <B258A372CEA20246A363BB86753DB53684CC8E@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Mahesh <mahesh@ccpu.com>, megaco@ietf.org
Subject: RE: [Megaco] Question related to Txn pending and Pending limit 
Date: Mon, 8 Nov 2004 09:11:40 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

If the pending limit is 1, then the MGC wouldn't take any action until it
receives the SECOND pending or a transaction reply.
 
The MG should send the error descriptor in a transaction reply.  Another
pending is not needed.  If the MG knows that it cannot complete the command
before issuing the second pending, it should go ahead and send the NACK
reply, to allow quicker cleanup and recovery.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Mahesh
Sent: Monday, November 08, 2004 7:17 AM
To: megaco@ietf.org
Subject: [Megaco] Question related to Txn pending and Pending limit 



 

 

 

HI  All,

 

I would like to clarify the sending of the error response 506 , when the
pending limit gets crossed .

 

Consider a situation like this

MGOriginated pending limit is 1 .

This is set at MG side by MGC using appropriate message.

MGC send a command to MG .

MG is waiting for the response from user .With in this time the provisional
response timer times out .

MG sends the txn pending to MGC .

Now MGC gets the txn pending message .It finds that the pending limit has
crossed and  do some actions , and abort the

Txn.

 

 

The questions is what time  MG have to send the 506 .whether it has to send
the error message along with the txnpending message.Whether this makes any
sense 

OR 

Whether the MG have to wait for some time to send the final 506.

 

Since MGC is tracking the number of txn pending messages send by MG, When
MGC  finds that the number of

Pending limit have crossed the limit , will it leads to some inconsistency
.The actual error response may come only after

Some time.

 

 

Could you please clarify this.

 

With regards

Mahesh

 

 

 

 


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


From megaco-bounces@ietf.org  Mon Nov  8 09:43:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13917
	for <megaco-archive@lists.ietf.org>; Mon, 8 Nov 2004 09:43:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRAPC-0003PY-UF; Mon, 08 Nov 2004 09:22:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRAGG-0001Ic-9g
	for megaco@megatron.ietf.org; Mon, 08 Nov 2004 09:12:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10412
	for <megaco@ietf.org>; Mon, 8 Nov 2004 09:12:45 -0500 (EST)
Received: from [61.144.161.55] (helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRAGg-0001mg-Fm
	for megaco@ietf.org; Mon, 08 Nov 2004 09:13:22 -0500
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0I6V00BCO5MRTT@szxga03-in.huawei.com> for
	megaco@ietf.org; Mon, 08 Nov 2004 22:01:40 +0800 (CST)
Received: from szxml01-in ([172.24.1.3])
	by szxga03-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTP id	<0I6V006G85MR08@szxga03-in.huawei.com>
	formegaco@ietf.org; Mon, 08 Nov 2004 22:01:39 +0800 (CST)
Received: from r70036l ([10.125.31.5])
	by szxml01-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTPA id	<0I6V007HQ5RKJR@szxml01-in.huawei.com>; Mon,
	08 Nov 2004 22:04:38 +0800 (CST)
Date: Mon, 08 Nov 2004 14:03:18 +0000
From: Rajeev K R <rajeev@huawei.com>
Subject: RE: [Megaco] SS7 point code of MGC for Handoff
In-reply-to: <6BB2DEB822D3D111817B00805FBE5F021518276C@mstelefonica6.telefon
	ica.com.ar>
To: "'Pellegrino Jose Luis'" <pellegrj@TELEFONICA.COM.AR>, megaco@ietf.org
Message-id: <005201c4c59b$b5dae1c0$7080a8c0@r70036l>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sensitivity: Company-Confidential
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0403923940=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0403923940==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_pLRCg5Kj0uxuOzseRs2hqg)"

This is a multi-part message in MIME format.

--Boundary_(ID_pLRCg5Kj0uxuOzseRs2hqg)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

This depends on your SS7/Sigtran architecture.
The SG can route messages to softswitches based on DPC and also other
parameters like CIC, NI etc.
So it is not mandatory that two MGC's in load sharing mode should have
different DPCs.
The MGCs may share the same point code but handle different range of =
CICs or
different NIs.
=20
After switch over, the active MGC should be able to handle the SS7 =
traffic
of the failed MGC also.
This means it should handle the DPC+NI+CIC combination the other one was
supposed to handle.
And if you were having different point codes for two MGCs, the active =
one
should now handle both
the point codes after switchover.=20
=20
The same happns at the H.248 also.
The active MGC should now control the MGs(physical or virtual) which =
were
earlier controlled by the failed MGC.
Rajeev=20
=20
=20

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf =
Of
Pellegrino Jose Luis
Sent: Wednesday, November 03, 2004 4:12 PM
To: 'megaco@ietf.org'
Subject: [Megaco] (no subject)
Sensitivity: Confidential




Hi, I have some questions about NGN (trunking) architecture using H.248 =
and
the interworking with ISUP.=20

Suppose two MGCs which controlate N MGs in a trunking network. Each MG =
is
conected to a tradicional TDM switch and the ISUP messages sent by the
switches are received by the signalling gateway via STP. There's no =
class
five services.


RFC 3525, point 11.5 "failure of an MGC" describe the procedures for the =
MG
in order to switch to another MGC in case of failure of the primary MGC.
This is in  my opinion one of the facilities that make MEGACO better =
than
MGCP.

-In my understanding, the mechanism described above is possible only if =
the
MGC's are working in the "Hot/Stand by" modality. =BFAm I right?

-The Signalling Gateways have an unique DPC (destination point code).
Having different DPC is not possible =BFIs this correct?.

Now, Suppose that you have the same  two MGCs, but  working in the =
"Sharing
load" modality, each of them controlling a group of MG's.

-In this architecture each MGC have a DPC different from the other.=BFIs =
this
correct?=20
-In this case, switching to another MGC is not possible because the =
vocals
trunks (wich are asociated with the fisical terminations), are related =
to
ONE DPC. =BFIs this correct?

However, in a sharing load scenario, it's possible to use Virtual MGs in
order give redundance to NGN - TDM conection (point 11.1 "Multiple =
Virtual
MGs").

So, making a summary, if I'm not wrong, depending on the Architecture,
"Hot/Stand by" or in the other hand "Sharing load", you can take =
advantage
of using switching mechanism or virtual MGs.

I will appreciate all the comments,=20

Thanks in advance,=20

Jos=E9 Luis=20




--Boundary_(ID_pLRCg5Kj0uxuOzseRs2hqg)
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>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1476" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D386354013-08112004>This=20
depends on your SS7/Sigtran architecture.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D386354013-08112004>The SG=20
can route messages to softswitches based on DPC and also other =
parameters like=20
CIC, NI etc.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D386354013-08112004>So it=20
is not mandatory that two MGC's in load sharing mode should have =
different=20
DPCs.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D386354013-08112004>The=20
MGCs may&nbsp;share the same point code but handle different range of =
CICs or=20
different NIs.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D386354013-08112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D386354013-08112004>After=20
switch over, the active MGC should be able to handle the SS7 traffic of =
the=20
failed&nbsp;MGC also.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D386354013-08112004>This=20
means it should handle the DPC+NI+CIC combination the other one was =
supposed to=20
handle.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D386354013-08112004>And if=20
you were having different point codes for two MGCs, the active one =
should now=20
handle both</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D386354013-08112004>the=20
point codes after switchover. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D386354013-08112004></SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2><SPAN class=3D386354013-08112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D386354013-08112004>The=20
same happns at the H.248 also.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D386354013-08112004>The=20
active MGC should now control the MGs(physical or virtual) which were =
earlier=20
controlled by the failed MGC.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D386354013-08112004>Rajeev&nbsp;</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D386354013-08112004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D386354013-08112004></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE 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-bounces@ietf.org [mailto:megaco-bounces@ietf.org] <B>On Behalf =
Of=20
  </B>Pellegrino Jose Luis<BR><B>Sent:</B> Wednesday, November 03, 2004 =
4:12=20
  PM<BR><B>To:</B> 'megaco@ietf.org'<BR><B>Subject:</B> [Megaco] (no=20
  subject)<BR><B>Sensitivity:</B> Confidential<BR><BR></FONT></DIV><BR>
  <P><FONT face=3DArial size=3D2>Hi, I have some questions about NGN =
(trunking)=20
  architecture using H.248 and the interworking with ISUP.</FONT> </P>
  <P><FONT face=3DArial size=3D2>Suppose two MGCs which controlate N MGs =
in a=20
  trunking network. Each MG is conected to a tradicional TDM switch and =
the ISUP=20
  messages sent by the switches are received by the signalling gateway =
via STP.=20
  There's no class five services.</FONT></P><BR>
  <P><FONT face=3DArial size=3D2>RFC 3525, point 11.5 "failure of an =
MGC" describe=20
  the procedures for the MG in order to switch to another MGC in case of =
failure=20
  of the primary MGC. This is in&nbsp; my opinion one of the facilities =
that=20
  make MEGACO better than MGCP.</FONT></P>
  <P><FONT face=3DArial size=3D2>-In my understanding, the mechanism =
described above=20
  is possible only if the MGC's are working in the "Hot/Stand by" =
modality. =BFAm=20
  I right?</FONT></P>
  <P><FONT face=3DArial size=3D2>-The Signalling Gateways have an unique =
DPC=20
  (destination point code).&nbsp; Having different DPC is not possible =
=BFIs this=20
  correct?.</FONT></P>
  <P><FONT face=3DArial size=3D2>Now, Suppose that you have the =
same&nbsp; two MGCs,=20
  but&nbsp; working in the "Sharing load" modality, each of them =
controlling a=20
  group of MG's.</FONT></P>
  <P><FONT face=3DArial size=3D2>-In this architecture each MGC have a =
DPC different=20
  from the other.=BFIs this correct?</FONT> <BR><FONT face=3DArial =
size=3D2>-In this=20
  case, switching to another MGC is not possible because the vocals =
trunks (wich=20
  are asociated with the fisical terminations), are related to ONE DPC. =
=BFIs this=20
  correct?</FONT></P>
  <P><FONT face=3DArial size=3D2>However, in a sharing load scenario, =
it's possible=20
  to use Virtual MGs in order give redundance to NGN - TDM conection =
(point 11.1=20
  "Multiple Virtual MGs").</FONT></P>
  <P><FONT face=3DArial size=3D2>So, making a summary, if I'm not wrong, =
depending=20
  on the Architecture, "Hot/Stand by" or in the other hand "Sharing =
load", you=20
  can take advantage of using switching mechanism or virtual =
MGs.</FONT></P>
  <P><FONT face=3DArial size=3D2>I will appreciate all the comments, =
</FONT></P>
  <P><FONT face=3DArial size=3D2>Thanks in advance,</FONT> </P>
  <P><FONT face=3DArial size=3D2>Jos=E9 Luis</FONT>=20
</P><BR><BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_pLRCg5Kj0uxuOzseRs2hqg)--


--===============0403923940==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0403923940==--



From megaco-bounces@ietf.org  Mon Nov  8 18:13:46 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16221
	for <megaco-archive@lists.ietf.org>; Mon, 8 Nov 2004 18:13:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRIWk-0004DF-AF; Mon, 08 Nov 2004 18:02:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRIMk-00087n-GJ
	for megaco@megatron.ietf.org; Mon, 08 Nov 2004 17:52:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12637
	for <megaco@ietf.org>; Mon, 8 Nov 2004 17:51:59 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRINN-0000K2-CY
	for megaco@ietf.org; Mon, 08 Nov 2004 17:52:41 -0500
Received: from wink.ho.lucent.com (h135-112-126-3.lucent.com [135.112.126.3])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iA8MpTYo007642
	for <megaco@ietf.org>; Mon, 8 Nov 2004 16:51:29 -0600 (CST)
Received: by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id RAA25361; Mon, 8 Nov 2004 17:51:26 -0500 (EST)
Received: from [135.112.108.30] by wink.ho.lucent.com (8.9.3+Sun/EMS-1.5 sol2)
	id RAA25349; Mon, 8 Nov 2004 17:51:24 -0500 (EST)
Message-ID: <418FFA9B.7070105@lucent.com>
Date: Mon, 08 Nov 2004 18:00:43 -0500
From: Richard Sun <xsun@lucent.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kevin Boyle <kboyle@nortelnetworks.com>
Original-CC: megaco@ietf.org
References: <B258A372CEA20246A363BB86753DB5366BA7E4@zrtphxm2>
In-Reply-To: <B258A372CEA20246A363BB86753DB5366BA7E4@zrtphxm2>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org
Subject: [Megaco] what package supports "held tone" now?
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Kevin,
or any expert there who can help please:

I am trying to implement "held tone" feature.
Searching the web, found draft-boyle-megaco-tonepkgs-05.txt:

       Held Tone
           SignalID: ht (0x0051)

           Generate held tone, indicating that the remote end has the
           call in a held state.

           Tone Direction
                 ParameterID: btd (0x01)
                 Type: Enumeration
                 Possible Values: External   ext  (0x01),
                                  Internal   int  (0x02),
                                  Both       both (0x03)

Yes, this is exactly what I need. But this was removed since
draft-boyle-megaco-tonepkgs-06.txt (=H248.27).
I can not find any discussion on why "ht" was removed.
Could you please let me know what is the standard package
to suppor "ht" equivalent now?

Thanks,
-Richard


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


From megaco-bounces@ietf.org  Tue Nov  9 08:33:25 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24946
	for <megaco-archive@lists.ietf.org>; Tue, 9 Nov 2004 08:33:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRVxo-0002y9-EM; Tue, 09 Nov 2004 08:23:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRVwF-0002Ii-AO
	for megaco@megatron.ietf.org; Tue, 09 Nov 2004 08:21:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23757
	for <megaco@ietf.org>; Tue, 9 Nov 2004 08:21:33 -0500 (EST)
Received: from filter3.kt.co.kr ([147.6.45.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRVww-00038c-Dp
	for megaco@ietf.org; Tue, 09 Nov 2004 08:22:22 -0500
Received: from external ([147.6.74.219]) by Filter3 (1.0) id iA9DKxm00F91;
	Tue, 09 Nov 2004 22:20:59 +0900
X-SMF-UNIQ33B8657C0E4123ECDBACEB8E52847943: iA9DKxm00F91
From: =?ks_c_5601-1987?B?vsjFwsH4?= <ahntj@kt.co.kr>
To: <megaco@ietf.org>
Date: Tue, 9 Nov 2004 22:20:49 +0900
Message-ID: <003b01c4c65e$edd7b9e0$db4a0693@tjahn>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 83867a50fd8f547996ccdaf89af24437
Subject: [Megaco] Management of MG's state
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1612724275=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1612724275==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_003C_01C4C6AA.5DBF61E0"

This is a multi-part message in MIME format.

------=_NextPart_000_003C_01C4C6AA.5DBF61E0
Content-Type: text/plain;
 charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

Dear all Megaco members.
=20
I have a question about the management of MG=A1=AFs state from the =
MGC=A1=AFs
point of view.
Is there any Megaco message or recommended way to check the state of MG
at the=20
protocol(Megaco) level like heartbeat mechanism?
=20
With regards
Ahn.
=20
=20
=20

------=_NextPart_000_003C_01C4C6AA.5DBF61E0
Content-Type: text/html;
 charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-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=3Dks_c_5601-1987">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C4C6AA.5D4CF100">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  =
<w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEve=
ry>
  =
<w:DisplayVerticalDrawingGridEvery>2</w:DisplayVerticalDrawingGridEvery>
  <w:Compatibility>
   <w:SpaceForUL/>
   <w:BalanceSingleByteDoubleByteWidth/>
   <w:DoNotLeaveBackslashAlone/>
   <w:ULTrailSpace/>
   <w:DoNotExpandShiftReturn/>
   <w:AdjustLineHeightInTable/>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:UseFELayout/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
 {font-family:=B9=D9=C5=C1;
 panose-1:2 3 6 0 0 1 1 1 1 1;
 mso-font-alt:Batang;
 mso-font-charset:129;
 mso-generic-font-family:roman;
 mso-font-pitch:variable;
 mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
@font-face
 {font-family:=B1=BC=B8=B2;
 panose-1:2 11 6 0 0 1 1 1 1 1;
 mso-font-alt:Gulim;
 mso-font-charset:129;
 mso-generic-font-family:modern;
 mso-font-pitch:variable;
 mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
@font-face
 {font-family:"\@=B1=BC=B8=B2";
 panose-1:2 11 6 0 0 1 1 1 1 1;
 mso-font-charset:129;
 mso-generic-font-family:modern;
 mso-font-pitch:variable;
 mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
@font-face
 {font-family:"\@=B9=D9=C5=C1";
 panose-1:2 3 6 0 0 1 1 1 1 1;
 mso-font-charset:129;
 mso-generic-font-family:roman;
 mso-font-pitch:variable;
 mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
 {mso-style-parent:"";
 margin:0mm;
 margin-bottom:.0001pt;
 text-align:justify;
 text-justify:inter-ideograph;
 mso-pagination:none;
 text-autospace:none;
 word-break:break-hangul;
 font-size:10.0pt;
 mso-bidi-font-size:12.0pt;
 font-family:=B9=D9=C5=C1;
 mso-hansi-font-family:"Times New Roman";
 mso-bidi-font-family:"Times New Roman";
 mso-font-kerning:1.0pt;}
a:link, span.MsoHyperlink
 {color:blue;
 text-decoration:underline;
 text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
 {color:purple;
 text-decoration:underline;
 text-underline:single;}
span.EmailStyle17
 {mso-style-type:personal-compose;
 mso-style-noshow:yes;
 mso-ansi-font-size:10.0pt;
 mso-bidi-font-size:10.0pt;
 font-family:=B1=BC=B8=B2;
 mso-ascii-font-family:=B1=BC=B8=B2;
 mso-fareast-font-family:=B1=BC=B8=B2;
 mso-hansi-font-family:Arial;
 mso-bidi-font-family:Arial;
 color:windowtext;}
span.SpellE
 {mso-style-name:"";
 mso-spl-e:yes;}
span.GramE
 {mso-style-name:"";
 mso-gram-e:yes;}
 /* Page Definitions */
 @page
 {mso-page-border-surround-header:no;
 mso-page-border-surround-footer:no;}
@page Section1
 {size:595.3pt 841.9pt;
 margin:99.25pt 30.0mm 30.0mm 30.0mm;
 mso-header-margin:42.55pt;
 mso-footer-margin:49.6pt;
 mso-paper-source:0;
 layout-grid:18.0pt;}
div.Section1
 {page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
 {mso-style-name:"=C7=A5=C1=D8 =C7=A5";
 mso-tstyle-rowband-size:0;
 mso-tstyle-colband-size:0;
 mso-style-noshow:yes;
 mso-style-parent:"";
 mso-padding-alt:0mm 5.4pt 0mm 5.4pt;
 mso-para-margin:0mm;
 mso-para-margin-bottom:.0001pt;
 mso-pagination:widow-orphan;
 font-size:10.0pt;
 font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DKO link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:40.0pt'>

<div class=3DSection1 style=3D'layout-grid:18.0pt'>

<p class=3DMsoNormal><font size=3D2 face=3D=B1=BC=B8=B2><span =
lang=3DEN-US style=3D'font-size:10.0pt;
mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=B2;mso-hansi-font-family:=
Arial;
mso-bidi-font-family:Arial'>Dear all <span class=3DSpellE>Megaco</span> =
members.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D=B1=BC=B8=B2><span =
lang=3DEN-US style=3D'font-size:10.0pt;
mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=B2;mso-hansi-font-family:=
Arial;
mso-bidi-font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D=B1=BC=B8=B2><span =
lang=3DEN-US style=3D'font-size:10.0pt;
mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=B2;mso-hansi-font-family:=
Arial;
mso-bidi-font-family:Arial'>I have a question about the management of =
<span
class=3DSpellE>MG<font face=3DArial><span =
style=3D'font-family:Arial;mso-ascii-font-family:
=B1=BC=B8=B2'>=A1=AF</span></font>s</span> state from the <span =
class=3DSpellE>MGC<font
face=3DArial><span =
style=3D'font-family:Arial;mso-ascii-font-family:=B1=BC=B8=B2'>=A1=AF</sp=
an></font>s</span>
point of view.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D=B1=BC=B8=B2><span =
lang=3DEN-US style=3D'font-size:10.0pt;
mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=B2;mso-hansi-font-family:=
Arial;
mso-bidi-font-family:Arial'>Is there any <span =
class=3DSpellE>Megaco</span> message
or recommended way to check the state of MG at the =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><span class=3DGramE><font size=3D2 =
face=3D=B1=BC=B8=B2><span lang=3DEN-US
style=3D'font-size:10.0pt;mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=
=B2;mso-hansi-font-family:
Arial;mso-bidi-font-family:Arial'>protocol(</span></font></span><span
class=3DSpellE><font face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'mso-bidi-font-size:10.0pt;
font-family:=B1=BC=B8=B2;mso-hansi-font-family:Arial;mso-bidi-font-family=
:Arial'>Megaco</span></font></span><font
face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=B2;
mso-hansi-font-family:Arial;mso-bidi-font-family:Arial'>) level like =
heartbeat
mechanism?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D=B1=BC=B8=B2><span =
lang=3DEN-US style=3D'font-size:10.0pt;
mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=B2;mso-hansi-font-family:=
Arial;
mso-bidi-font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D=B1=BC=B8=B2><span =
lang=3DEN-US style=3D'font-size:10.0pt;
mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=B2;mso-hansi-font-family:=
Arial;
mso-bidi-font-family:Arial'>With regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><span class=3DSpellE><span class=3DGramE><font =
size=3D2 face=3D=B1=BC=B8=B2><span
lang=3DEN-US =
style=3D'font-size:10.0pt;mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=
=B2;
mso-hansi-font-family:Arial;mso-bidi-font-family:Arial'>Ahn</span></font>=
</span></span><span
class=3DGramE><font face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'mso-bidi-font-size:10.0pt;
font-family:=B1=BC=B8=B2;mso-hansi-font-family:Arial;mso-bidi-font-family=
:Arial'>.</span></font></span><font
face=3D=B1=BC=B8=B2><span lang=3DEN-US =
style=3D'mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=B2;
mso-hansi-font-family:Arial;mso-bidi-font-family:Arial'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D=B1=BC=B8=B2><span =
lang=3DEN-US style=3D'font-size:10.0pt;
mso-bidi-font-size:10.0pt;font-family:=B1=BC=B8=B2;mso-hansi-font-family:=
Arial;
mso-bidi-font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3D2 color=3Dnavy face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:"Times New Roman";color:navy;mso-no-proof:yes'><span
style=3D'mso-bidi-font-size:12.0pt'>&nbsp;<o:p></o:p></span></span></font=
></p>

<p class=3DMsoNormal><font size=3D2 face=3D=B9=D9=C5=C1><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_003C_01C4C6AA.5DBF61E0--



--===============1612724275==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1612724275==--




From megaco-bounces@ietf.org  Tue Nov  9 09:02:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28516
	for <megaco-archive@lists.ietf.org>; Tue, 9 Nov 2004 09:02:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRWP0-0007bz-7Q; Tue, 09 Nov 2004 08:51:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRWKb-0006cL-Hm
	for megaco@megatron.ietf.org; Tue, 09 Nov 2004 08:46:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26251
	for <megaco@ietf.org>; Tue, 9 Nov 2004 08:46:43 -0500 (EST)
From: Albrecht.Schwarz@alcatel.de
Received: from mailrelay1.alcatel.de ([194.113.59.55]
	helo=mailrelay2.alcatel.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRWLM-0003nw-3p
	for megaco@ietf.org; Tue, 09 Nov 2004 08:47:32 -0500
Received: from demail05.netfr.alcatel.fr (demail05.netfr.alcatel.fr
	[155.132.182.205])
	by mailrelay2.alcatel.de (8.12.11/8.12.10) with ESMTP id iA9Dk96t025972;
	Tue, 9 Nov 2004 14:46:09 +0100 (MET)
In-Reply-To: <003b01c4c65e$edd7b9e0$db4a0693@tjahn>
Subject: Re: [Megaco] Management of MG's state
To: =?euc-kr?B?vsjFwsH4?= <ahntj@kt.co.kr>
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF37CAE605.DD62710C-ONC1256F47.004AFE75-C1256F47.004BA237@netfr.alcatel.fr>
Date: Tue, 9 Nov 2004 14:46:07 +0100
X-MIMETrack: Serialize by Router on DEMAIL05/DE/ALCATEL(Release 5.0.11 |July
	24, 2002) at 11/09/2004 14:46:09
MIME-Version: 1.0
Content-type: text/plain; charset=iso-2022-kr
X-AES-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

$)C
Hi Ahn,

we've proposed sth for next SG16 meeting, see ITU-T server:
T05-SG16-041116-D-0054!!MSW-E.doc

A pre-version is accessible on avc-site:
http://ftp3.itu.int/av-arch/avc-site/2001-2004/0411_Gen/Alcatel09_H.248.1_V3_OperationStateMonitoring.zip

A more in depth background provides:
http://ftp3.itu.int/av-arch/avc-site/2001-2004/0408_San/AVD-2543.zip

The contributions are not yet discussed.
Pls follow H.248.1 Version 3 progress.

Regards
Albrecht

PS
it's "state monitoring", "state management" is not in scope




                                                                                                                                
                      >HEBAx                                                                                                    
                      <ahntj@kt.co.kr>         To:      <megaco@ietf.org>                                                       
                      Sent by:                 cc:                                                                              
                      megaco-bounces@i         Subject: [Megaco] Management of MG's state                                       
                      etf.org                                                                                                   
                                                                                                                                
                                                                                                                                
                      09.11.2004 14:20                                                                                          
                                                                                                                                




Dear all Megaco members.





I have a question about the management of MG!/s state from the MGC!/s point
of view.


Is there any Megaco message or recommended way to check the state of MG at
the


protocol(Megaco) level like heartbeat mechanism?





With regards


Ahn.








 _______________________________________________
Megaco mailing list
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-bounces@ietf.org  Tue Nov  9 11:09:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13825
	for <megaco-archive@lists.ietf.org>; Tue, 9 Nov 2004 11:09:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRYSu-00014n-9E; Tue, 09 Nov 2004 11:03:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRYGG-0006k6-SX
	for megaco@megatron.ietf.org; Tue, 09 Nov 2004 10:50:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12146
	for <megaco@ietf.org>; Tue, 9 Nov 2004 10:50:22 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRYH2-00073h-UN
	for megaco@ietf.org; Tue, 09 Nov 2004 10:51:13 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iA9Fnpp07629
	for <megaco@ietf.org>; Tue, 9 Nov 2004 10:49:52 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WP4QQNK9>; Tue, 9 Nov 2004 10:49:42 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5368BA9B2@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: ??? <ahntj@kt.co.kr>, megaco@ietf.org
Subject: RE: [Megaco] Management of MG's state
Date: Tue, 9 Nov 2004 10:49:26 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

There are many ways to do this, including having the MGC send an empty audit
from time to time.  How this would be accomplished is up to the discretion
of the implementations.
 
Kevin

  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
ahntj@kt.co.kr
Sent: Tuesday, November 09, 2004 8:21 AM
To: megaco@ietf.org
Subject: [Megaco] Management of MG's state


Dear all Megaco members.
 
I have a question about the management of MG's state from the MGC's point of
view.
Is there any Megaco message or recommended way to check the state of MG at
the 
protocol(Megaco) level like heartbeat mechanism?
 
With regards
Ahn.
 
 
 

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


From megaco-bounces@ietf.org  Tue Nov  9 18:51:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29880
	for <megaco-archive@lists.ietf.org>; Tue, 9 Nov 2004 18:51:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRfjz-0005FV-5Z; Tue, 09 Nov 2004 18:49:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRfij-000502-AN
	for megaco@megatron.ietf.org; Tue, 09 Nov 2004 18:48:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29669
	for <megaco@ietf.org>; Tue, 9 Nov 2004 18:48:14 -0500 (EST)
Received: from alageremail1.agere.com ([192.19.193.106])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRfjZ-00026a-Mi
	for megaco@ietf.org; Tue, 09 Nov 2004 18:49:10 -0500
Received: from alerelay.agere.com (alerelay.agere.com [135.14.190.33])
	by alageremail1.agere.com (8.11.7+Sun/8.10.2) with ESMTP id
	iA9NlkL07107
	for <megaco@ietf.org>; Tue, 9 Nov 2004 18:47:46 -0500 (EST)
Received: from pauex2kf02.ags.agere.com (pauex2kf02.agere.com [135.14.186.97])
	by alerelay.agere.com (8.11.6+Sun/8.11.6) with ESMTP id iA9Nlju17425
	for <megaco@ietf.org>; Tue, 9 Nov 2004 18:47:45 -0500 (EST)
Received: from pauex2ku06.ags.agere.com ([135.14.188.42]) by
	pauex2kf02.ags.agere.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Tue, 9 Nov 2004 18:47:45 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Tue, 9 Nov 2004 18:47:45 -0500
Message-ID: <717DBF3DD8906D4D86EB77637C40E5430A3802@pauex2ku06.agere.com>
Thread-Topic: MGC/MG Failure
Thread-Index: AcTGtoLDjtigcLldRw2Yedngt6hWlA==
From: "Jones, Nevin R \(Nevin\)" <nrjones@agere.com>
To: <megaco@ietf.org>
X-OriginalArrivalTime: 09 Nov 2004 23:47:45.0610 (UTC)
	FILETIME=[82EC7AA0:01C4C6B6]
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: "Jones, Nevin R \(Nevin\)" <nrjones@agere.com>
Subject: [Megaco] MGC/MG Failure
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1088506357=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1088506357==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C6B6.82EA7D35"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C6B6.82EA7D35
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All:

I am a newbie to the megao list so please forgive me if this question
was asked and answered previously. Is there a stipulation (and better
yet, mechanism) somewhere in the Megaco/H.248 standard for the maximum
switching time from one MGC to another in the case of a handover? I ask
this question with the concern that if real time IP based services are
to operate at 5 nines availability, then it would seem that the MGC
switchover would have to be in the 10s of milliseconds.

Thanks!

Regards

Nevin Jones


------_=_NextPart_001_01C4C6B6.82EA7D35
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6617.6">
<TITLE>MGC/MG Failure</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Comic Sans MS">All:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Comic Sans MS">I am a newbie to the megao list =
so please forgive me if this question was asked and answered previously. =
Is there a stipulation (and better yet, mechanism) somewhere in the =
Megaco/H.248 standard for the maximum switching time from one MGC to =
another in the case of a handover? I ask this question with the concern =
that if real time IP based services are to operate at 5 nines =
availability, then it would seem that the MGC switchover would have to =
be in the 10s of milliseconds.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Comic Sans MS">Thanks!</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Comic Sans MS">Regards</FONT>
</P>

<P><FONT FACE=3D"Comic Sans MS">Nevin Jones<B></B></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4C6B6.82EA7D35--


--===============1088506357==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1088506357==--



From megaco-bounces@ietf.org  Wed Nov 10 03:08:05 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05321
	for <megaco-archive@lists.ietf.org>; Wed, 10 Nov 2004 03:08:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRnTO-0001hB-3k; Wed, 10 Nov 2004 03:04:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRnSs-0001bc-4T
	for megaco@megatron.ietf.org; Wed, 10 Nov 2004 03:04:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05049
	for <megaco@ietf.org>; Wed, 10 Nov 2004 03:04:23 -0500 (EST)
From: ksaurabh@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRnTZ-00038I-3W
	for megaco@ietf.org; Wed, 10 Nov 2004 03:05:22 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAA7xN2j027358
	for <megaco@ietf.org>; Wed, 10 Nov 2004 13:30:40 +0530 (IST)
Received: from sandesh.hss.hns.com (sandesh [172.16.32.19])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAA6trJl007548;
	Wed, 10 Nov 2004 12:25:59 +0530 (IST)
In-Reply-To: <717DBF3DD8906D4D86EB77637C40E5430A3802@pauex2ku06.agere.com>
MIME-Version: 1.0
To: "Jones, Nevin R \(Nevin\)" <nrjones@agere.com>
Subject: Re: [Megaco] MGC/MG Failure
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF56875B8F.84CFA7FC-ON65256F48.0023C5B7-65256F48.0024E474@hssworld.com>
Date: Wed, 10 Nov 2004 12:09:17 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26,
	2002) at 10/11/2004 12:42:44 PM,
	Serialize complete at 10/11/2004 12:42:44 PM
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc: megaco@ietf.org, "Jones, Nevin R \(Nevin\)" <nrjones@agere.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1388737385=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multipart message in MIME format.
--===============1388737385==
Content-Type: multipart/alternative;
	boundary="=_alternative 0024E47365256F48_="

This is a multipart message in MIME format.
--=_alternative 0024E47365256F48_=
Content-Type: text/plain; charset="US-ASCII"


Hello ,

The Megaco base protocol does not talk about any upper limit for the time 
taken for handoff from one MGC to the other.

However, the MGC side application could define an upper limit for the 
entire operation based on a number of factors such as MG execution time, 
Network delay, maximum allowed downtime etc. But for the success of this 
kind of an arrangement, Active MGC is required to trigger the handedoff 
MGC about the initiation of the handoff procedure.

Also based on the requirement, the MGC can have more stringent parameters 
for service change timeout as compared to non service change transaction 
timeout.

Regards, 
Saurabh 
Hughes Software Systems
www.hssworld.com






Sent by:        megaco-bounces@ietf.org
To:     <megaco@ietf.org>
cc:     "Jones, Nevin R \(Nevin\)" <nrjones@agere.com> 

Subject:        [Megaco] MGC/MG Failure





All:

I am a newbie to the megao list so please forgive me if this question was 
asked and answered previously. Is there a stipulation (and better yet, 
mechanism) somewhere in the Megaco/H.248 standard for the maximum 
switching time from one MGC to another in the case of a handover? I ask 
this question with the concern that if real time IP based services are to 
operate at 5 nines availability, then it would seem that the MGC 
switchover would have to be in the 10s of milliseconds.

Thanks! 

Regards 

Nevin Jones 

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



*****************    HSS-Restricted    *************

"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
--=_alternative 0024E47365256F48_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2>Hello ,</font>
<br>
<br><font size=2>The Megaco base protocol does not talk about any upper
limit for the time taken for handoff from one MGC to the other.</font>
<br>
<br><font size=2>However, the MGC side application could define an upper
limit for the entire operation based on a number of factors such as MG
execution time, Network delay, maximum allowed downtime etc. But for the
success of this kind of an arrangement, Active MGC is required to trigger
the handedoff MGC about the initiation of the handoff procedure.</font>
<br>
<br><font size=2>Also based on the requirement, the MGC can have more stringent
parameters for service change timeout as compared to non service change
transaction timeout.</font>
<br>
<br><font size=2>Regards,</font><font size=3> </font>
<br><font size=2>Saurabh</font><font size=3> </font>
<br><font size=2>Hughes Software Systems</font>
<br><font size=2>www.hssworld.com</font>
<br>
<br>
<br>
<br>
<div>
<br>
<div>
<br>
<p><font size=1 color=#800080 face="sans-serif">Sent by: &nbsp; &nbsp;
&nbsp; &nbsp;megaco-bounces@ietf.org</font>
<p><font size=1 color=#800080 face="sans-serif">To: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">&lt;megaco@ietf.org&gt;</font>
<br><font size=1 color=#800080 face="sans-serif">cc: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">&quot;Jones, Nevin
R \(Nevin\)&quot; &lt;nrjones@agere.com&gt;</font><font size=1 color=#800080 face="sans-serif">
</font>
<br>
<br><font size=1 color=#800080 face="sans-serif">Subject: &nbsp; &nbsp;
&nbsp; &nbsp;</font><font size=1 face="sans-serif">[Megaco] MGC/MG
Failure</font>
<br>
<br>
<br>
<br>
<br>
<br><font size=2>All:</font>
<br>
<br><font size=2>I am a newbie to the megao list so please forgive me if
this question was asked and answered previously. Is there a stipulation
(and better yet, mechanism) somewhere in the Megaco/H.248 standard for
the maximum switching time from one MGC to another in the case of a handover?
I ask this question with the concern that if real time IP based services
are to operate at 5 nines availability, then it would seem that the MGC
switchover would have to be in the 10s of milliseconds.</font>
<br>
<br><font size=2>Thanks!</font><font size=3> </font>
<br>
<br><font size=2>Regards</font><font size=3> </font>
<br>
<br><font size=3>Nevin Jones </font>
<br>
<br><font size=2><tt>_______________________________________________<br>
Megaco mailing list<br>
Megaco@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/megaco</tt></font>
<br>
<br>
<br><font size=1 face="sans-serif"><br>
***************** &nbsp; &nbsp;HSS-Restricted &nbsp; &nbsp;*************</font></div></div>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
</pre></font></td></tr></table>
--=_alternative 0024E47365256F48_=--


--===============1388737385==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1388737385==--



From megaco-bounces@ietf.org  Wed Nov 10 07:02:44 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26693
	for <megaco-archive@lists.ietf.org>; Wed, 10 Nov 2004 07:02:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRr9l-0005Ps-Ft; Wed, 10 Nov 2004 07:00:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRr92-0005KO-QH; Wed, 10 Nov 2004 07:00:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26515;
	Wed, 10 Nov 2004 07:00:07 -0500 (EST)
From: bvswamy@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CRr9k-00089F-Dh; Wed, 10 Nov 2004 07:01:10 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAABuYxL020438;
	Wed, 10 Nov 2004 17:26:34 +0530 (IST)
Received: from webmail.hss.hns.com (webmail.hss.hns.com [192.168.100.50])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAABuW2P020415;
	Wed, 10 Nov 2004 17:26:32 +0530 (IST)
In-Reply-To: <418FFA9B.7070105@lucent.com>
To: Richard Sun <xsun@lucent.com>
Subject: Re: [Megaco] what package supports "held tone" now?
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF5C91C4EA.04009FCB-ON65256F48.00411EDA-65256F48.0041D45F@hssworld.com>
Date: Wed, 10 Nov 2004 17:24:23 +0530
X-MIMETrack: S/MIME Sign by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/10/2004 05:29:02 PM,
	Serialize by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/10/2004 05:29:02 PM,
	Serialize complete at 11/10/2004 05:29:02 PM,
	S/MIME Sign failed at 11/10/2004 05:29:02 PM: The cryptographic key was
	not found,
	Serialize by Router on WebMail/HSS(Release 6.5.1|January 21,
	2004) at 11/10/2004 05:24:35 PM,
	Serialize complete at 11/10/2004 05:24:35 PM
X-Spam-Score: 3.9 (+++)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
Cc: megaco-bounces@ietf.org, megaco@ietf.org,
        Kevin Boyle <kboyle@nortelnetworks.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1968211042=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multipart message in MIME format.
--===============1968211042==
Content-Type: multipart/alternative;
	boundary="=_alternative 0041D45665256F48_="

This is a multipart message in MIME format.
--=_alternative 0041D45665256F48_=
Content-Type: text/plain; charset="US-ASCII"


Hi Richard

All the packages defined in the draft below are now part of the Q.1950 
document.
Refer the Q.1950(Bearer independent call bearer control protocol, 
12/2002), subsection number A.10.3.3 under Basic services tones generation 
package section.


regards
B. Venkat S.R Swamy
Hughes Software systems
www.hssworld.com





Richard Sun <xsun@lucent.com> 
Sent by: megaco-bounces@ietf.org
11/09/2004 04:30 AM


To
Kevin Boyle <kboyle@nortelnetworks.com>
cc
megaco@ietf.org
Subject
[Megaco] what package supports "held tone" now?






Kevin,
or any expert there who can help please:

I am trying to implement "held tone" feature.
Searching the web, found draft-boyle-megaco-tonepkgs-05.txt:

Held Tone
SignalID: ht (0x0051)

Generate held tone, indicating that the remote end has the
call in a held state.

Tone Direction
ParameterID: btd (0x01)
Type: Enumeration
Possible Values: External   ext  (0x01),
Internal   int  (0x02),
Both       both (0x03)

Yes, this is exactly what I need. But this was removed since
draft-boyle-megaco-tonepkgs-06.txt (=H248.27).
I can not find any discussion on why "ht" was removed.
Could you please let me know what is the standard package
to suppor "ht" equivalent now?

Thanks,
-Richard


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


***********************  HSS-Private   ***********************

"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
--=_alternative 0041D45665256F48_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Richard</font>
<br>
<br><font size=2 face="sans-serif">All the packages defined in the draft
below are now part of the Q.1950 document.</font>
<br><font size=2 face="sans-serif">Refer the Q.1950(</font><font size=2 face="Arial"><b>Bearer
independent call bearer control protocol</b></font><font size=2 face="sans-serif">,
12/2002), subsection number A.10.3.3 under </font><font size=3 face="Times New Roman">Basic
services tones generation package</font><font size=2 face="sans-serif">
section.</font>
<br>
<br>
<br><font size=2 face="sans-serif">regards</font>
<br><font size=2 face="sans-serif">B. Venkat S.R Swamy</font>
<br><font size=2 face="sans-serif">Hughes Software systems</font>
<br><font size=2 face="sans-serif">www.hssworld.com</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Richard Sun &lt;xsun@lucent.com&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: megaco-bounces@ietf.org</font>
<p><font size=1 face="sans-serif">11/09/2004 04:30 AM</font>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">Kevin Boyle &lt;kboyle@nortelnetworks.com&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">megaco@ietf.org</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">[Megaco] what package supports
&quot;held tone&quot; now?</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Kevin,<br>
or any expert there who can help please:<br>
</tt></font>
<br><font size=2><tt>I am trying to implement &quot;held tone&quot; feature.<br>
Searching the web, found draft-boyle-megaco-tonepkgs-05.txt:<br>
</tt></font>
<br><font size=2><tt>Held Tone<br>
SignalID: ht (0x0051)</tt></font>
<br>
<br><font size=2><tt>Generate held tone, indicating that the remote end
has the<br>
call in a held state.</tt></font>
<br>
<br><font size=2><tt>Tone Direction<br>
ParameterID: btd (0x01)<br>
Type: Enumeration<br>
Possible Values: External &nbsp; ext &nbsp;(0x01),</tt></font>
<br><font size=2><tt>Internal &nbsp; int &nbsp;(0x02),<br>
Both &nbsp; &nbsp; &nbsp; both (0x03)</tt></font>
<br>
<br><font size=2><tt>Yes, this is exactly what I need. But this was removed
since<br>
draft-boyle-megaco-tonepkgs-06.txt (=H248.27).<br>
I can not find any discussion on why &quot;ht&quot; was removed.<br>
Could you please let me know what is the standard package<br>
to suppor &quot;ht&quot; equivalent now?<br>
</tt></font>
<br><font size=2><tt>Thanks,<br>
-Richard<br>
</tt></font>
<br>
<br><font size=2><tt>_______________________________________________<br>
Megaco mailing list<br>
Megaco@ietf.org</tt></font>
<br><font size=2><tt>https://www1.ietf.org/mailman/listinfo/megaco</tt></font>
<br><font size=2 face="sans-serif"><br>
<br>
*********************** &nbsp;HSS-Private &nbsp; ***********************</font>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
</pre></font></td></tr></table>
--=_alternative 0041D45665256F48_=--


--===============1968211042==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1968211042==--



From megaco-bounces@ietf.org  Wed Nov 10 07:10:29 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27405
	for <megaco-archive@lists.ietf.org>; Wed, 10 Nov 2004 07:10:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRrHi-0006SD-6Z; Wed, 10 Nov 2004 07:09:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRrHG-0006Lc-FN
	for megaco@megatron.ietf.org; Wed, 10 Nov 2004 07:08:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27193
	for <megaco@ietf.org>; Wed, 10 Nov 2004 07:08:39 -0500 (EST)
From: bvswamy@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRrIB-0008LQ-R8
	for megaco@ietf.org; Wed, 10 Nov 2004 07:09:41 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAAC4xxL024153
	for <megaco@ietf.org>; Wed, 10 Nov 2004 17:34:59 +0530 (IST)
Received: from webmail.hss.hns.com (webmail.hss.hns.com [192.168.100.50])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAAC4s2P024102;
	Wed, 10 Nov 2004 17:34:57 +0530 (IST)
In-Reply-To: <B258A372CEA20246A363BB86753DB5368BA9B2@zrtphxm2>
To: ??? <ahntj@kt.co.kr>
Subject: RE: [Megaco] Management of MG's state
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFB8684E40.B9C7D58D-ON65256F48.0041ED8D-65256F48.00429C28@hssworld.com>
Date: Wed, 10 Nov 2004 17:32:54 +0530
X-MIMETrack: S/MIME Sign by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/10/2004 05:37:33 PM,
	Serialize by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/10/2004 05:37:33 PM,
	Serialize complete at 11/10/2004 05:37:33 PM,
	S/MIME Sign failed at 11/10/2004 05:37:33 PM: The cryptographic key was
	not found,
	Serialize by Router on WebMail/HSS(Release 6.5.1|January 21,
	2004) at 11/10/2004 05:33:00 PM,
	Serialize complete at 11/10/2004 05:33:00 PM
X-Spam-Score: 3.9 (+++)
X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1021411661=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multipart message in MIME format.
--===============1021411661==
Content-Type: multipart/alternative;
	boundary="=_alternative 00429C2465256F48_="

This is a multipart message in MIME format.
--=_alternative 00429C2465256F48_=
Content-Type: text/plain; charset="US-ASCII"


Hi

Also Inactivity Timer package(H248.14) can serve the purpose of HeartBeat. 
Although its purpose is to let MG know the failure of its Active MGC.

Regards
B. Venkat S.R Swamy
Hughes Software Systems
www.hssworld.com





"Kevin Boyle" <kboyle@nortelnetworks.com> 
Sent by: megaco-bounces@ietf.org
11/09/2004 09:19 PM


To
??? <ahntj@kt.co.kr>, megaco@ietf.org
cc

Subject
RE: [Megaco] Management of MG's state






There are many ways to do this, including having the MGC send an empty 
audit
from time to time.  How this would be accomplished is up to the discretion
of the implementations.

Kevin

_____

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf 
Of
ahntj@kt.co.kr
Sent: Tuesday, November 09, 2004 8:21 AM
To: megaco@ietf.org
Subject: [Megaco] Management of MG's state


Dear all Megaco members.

I have a question about the management of MG's state from the MGC's point 
of
view.
Is there any Megaco message or recommended way to check the state of MG at
the
protocol(Megaco) level like heartbeat mechanism?

With regards
Ahn.




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


***********************  HSS-Private   ***********************

"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
--=_alternative 00429C2465256F48_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi</font>
<br>
<br><font size=2 face="sans-serif">Also Inactivity Timer package(H248.14)
can serve the purpose of HeartBeat. Although its purpose is to let MG know
the failure of its Active MGC.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">B. Venkat S.R Swamy</font>
<br><font size=2 face="sans-serif">Hughes Software Systems</font>
<br><font size=2 face="sans-serif">www.hssworld.com</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Kevin Boyle&quot;
&lt;kboyle@nortelnetworks.com&gt;</b> </font>
<br><font size=1 face="sans-serif">Sent by: megaco-bounces@ietf.org</font>
<p><font size=1 face="sans-serif">11/09/2004 09:19 PM</font>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">??? &lt;ahntj@kt.co.kr&gt;,
megaco@ietf.org</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">RE: [Megaco] Management of
MG's state</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>There are many ways to do this, including having the
MGC send an empty audit<br>
from time to time. &nbsp;How this would be accomplished is up to the discretion<br>
of the implementations.<br>
</tt></font>
<br><font size=2><tt>Kevin<br>
</tt></font>
<br><font size=2><tt>_____<br>
</tt></font>
<br><font size=2><tt>From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]
On Behalf Of<br>
ahntj@kt.co.kr<br>
Sent: Tuesday, November 09, 2004 8:21 AM<br>
To: megaco@ietf.org<br>
Subject: [Megaco] Management of MG's state<br>
</tt></font>
<br>
<br><font size=2><tt>Dear all Megaco members.<br>
</tt></font>
<br><font size=2><tt>I have a question about the management of MG's state
from the MGC's point of<br>
view.<br>
Is there any Megaco message or recommended way to check the state of MG
at<br>
the<br>
protocol(Megaco) level like heartbeat mechanism?<br>
</tt></font>
<br><font size=2><tt>With regards<br>
Ahn.<br>
</tt></font>
<br>
<br>
<br>
<br><font size=2><tt>_______________________________________________<br>
Megaco mailing list<br>
Megaco@ietf.org</tt></font>
<br><font size=2><tt>https://www1.ietf.org/mailman/listinfo/megaco</tt></font>
<br><font size=2 face="sans-serif"><br>
<br>
*********************** &nbsp;HSS-Private &nbsp; ***********************</font>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
</pre></font></td></tr></table>
--=_alternative 00429C2465256F48_=--


--===============1021411661==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1021411661==--



From megaco-bounces@ietf.org  Wed Nov 10 10:03:53 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15538
	for <megaco-archive@lists.ietf.org>; Wed, 10 Nov 2004 10:03:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRttW-0006Xe-TT; Wed, 10 Nov 2004 09:56:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRthV-00046d-KJ
	for megaco@megatron.ietf.org; Wed, 10 Nov 2004 09:43:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13312
	for <megaco@ietf.org>; Wed, 10 Nov 2004 09:43:54 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRtiS-0003dr-9H
	for megaco@ietf.org; Wed, 10 Nov 2004 09:44:56 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAAEhMk24567
	for <megaco@ietf.org>; Wed, 10 Nov 2004 09:43:23 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WP4QWCWK>; Wed, 10 Nov 2004 09:43:19 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536932045@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "Jones, Nevin R (Nevin)" <nrjones@agere.com>, megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure
Date: Wed, 10 Nov 2004 09:43:04 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is an implementation detail that would depend upon your needs.  Note
that Megaco does not have sole use in the real-time services arena,
therefore it is inappropriate for any timing requirements to be specified as
part of the protocol.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Jones, Nevin R (Nevin)
Sent: Tuesday, November 09, 2004 6:48 PM
To: megaco@ietf.org
Cc: Jones, Nevin R (Nevin)
Subject: [Megaco] MGC/MG Failure



All: 

I am a newbie to the megao list so please forgive me if this question was
asked and answered previously. Is there a stipulation (and better yet,
mechanism) somewhere in the Megaco/H.248 standard for the maximum switching
time from one MGC to another in the case of a handover? I ask this question
with the concern that if real time IP based services are to operate at 5
nines availability, then it would seem that the MGC switchover would have to
be in the 10s of milliseconds.

Thanks! 

Regards 

Nevin Jones 


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


From megaco-bounces@ietf.org  Wed Nov 10 10:07:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16074
	for <megaco-archive@lists.ietf.org>; Wed, 10 Nov 2004 10:07:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRttX-0006Xk-KQ; Wed, 10 Nov 2004 09:56:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRtiN-0004CN-50
	for megaco@megatron.ietf.org; Wed, 10 Nov 2004 09:44:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13400
	for <megaco@ietf.org>; Wed, 10 Nov 2004 09:44:49 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRtjK-0003fF-DU
	for megaco@ietf.org; Wed, 10 Nov 2004 09:45:51 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAAEiHQ25652
	for <megaco@ietf.org>; Wed, 10 Nov 2004 09:44:17 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WP4QWC7Y>; Wed, 10 Nov 2004 09:44:17 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536932049@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: bvswamy@hssworld.com, Richard Sun <xsun@lucent.com>
Subject: RE: [Megaco] what package supports "held tone" now?
Date: Wed, 10 Nov 2004 09:44:05 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is not true.  Some of the packages are in Q.1950 Annex A, and the rest
are in H.248.27.
 
Kevin


  _____  

From: bvswamy@hssworld.com [mailto:bvswamy@hssworld.com] 
Sent: Wednesday, November 10, 2004 6:54 AM
To: Richard Sun
Cc: Boyle, Kevin [NCRTP:3Z40:EXCH]; megaco@ietf.org; megaco-bounces@ietf.org
Subject: Re: [Megaco] what package supports "held tone" now?



Hi Richard 

All the packages defined in the draft below are now part of the Q.1950
document. 
Refer the Q.1950(Bearer independent call bearer control protocol, 12/2002),
subsection number A.10.3.3 under Basic services tones generation package
section. 


regards 
B. Venkat S.R Swamy 
Hughes Software systems 
www.hssworld.com 





Richard Sun <xsun@lucent.com> 
Sent by: megaco-bounces@ietf.org 


11/09/2004 04:30 AM 



To
Kevin Boyle <kboyle@nortelnetworks.com> 

cc
megaco@ietf.org 

Subject
[Megaco] what package supports "held tone" now?

	




Kevin,
or any expert there who can help please:

I am trying to implement "held tone" feature.
Searching the web, found draft-boyle-megaco-tonepkgs-05.txt:

Held Tone
SignalID: ht (0x0051) 

Generate held tone, indicating that the remote end has the
call in a held state. 

Tone Direction
ParameterID: btd (0x01)
Type: Enumeration
Possible Values: External   ext  (0x01), 
Internal   int  (0x02),
Both       both (0x03) 

Yes, this is exactly what I need. But this was removed since
draft-boyle-megaco-tonepkgs-06.txt (=H248.27).
I can not find any discussion on why "ht" was removed.
Could you please let me know what is the standard package
to suppor "ht" equivalent now?

Thanks,
-Richard


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


***********************  HSS-Private   *********************** 

"Please note:The email domain of Hughes Software Systems Ltd. has been
changed to "hssworld.com" from hss.hns.com"



"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended 

solely for the use of the individual to whom it is addressed. It may contain
privileged or 

confidential information and should not be circulated or used for any
purpose other than for 

what it is intended. If you have received this message in error, please
notify the originator 

immediately. If you are not the intended recipient, you are notified that
you are strictly 

prohibited from using, copying, altering, or disclosing the contents of this
message. HSS 

accepts no responsibility for loss or damage arising from the use of the
information transmitted 

by this email including damage from virus."


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


From megaco-bounces@ietf.org  Wed Nov 10 10:15:10 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17523
	for <megaco-archive@lists.ietf.org>; Wed, 10 Nov 2004 10:15:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRtvw-0007Eq-6A; Wed, 10 Nov 2004 09:58:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRtlV-0004uQ-6u
	for megaco@megatron.ietf.org; Wed, 10 Nov 2004 09:48:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13723
	for <megaco@ietf.org>; Wed, 10 Nov 2004 09:48:03 -0500 (EST)
Received: from alageremail2.agere.com ([192.19.192.110])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRtmT-0003ir-KY
	for megaco@ietf.org; Wed, 10 Nov 2004 09:49:06 -0500
Received: from alerelay.agere.com (alerelay.agere.com [135.14.190.33])
	by alageremail2.agere.com (8.11.7+Sun/8.10.2) with ESMTP id
	iAAElTf04634; Wed, 10 Nov 2004 09:47:29 -0500 (EST)
Received: from pauex2kf02.ags.agere.com (pauex2kf02.agere.com [135.14.186.97])
	by alerelay.agere.com (8.11.6+Sun/8.11.6) with ESMTP id iAAElSi16448;
	Wed, 10 Nov 2004 09:47:28 -0500 (EST)
Received: from pauex2ku06.ags.agere.com ([135.14.188.42]) by
	pauex2kf02.ags.agere.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Wed, 10 Nov 2004 09:47:28 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Subject: RE: [Megaco] MGC/MG Failure
Date: Wed, 10 Nov 2004 09:47:28 -0500
Message-ID: <717DBF3DD8906D4D86EB77637C40E54363B3C3@pauex2ku06.agere.com>
Thread-Topic: [Megaco] MGC/MG Failure
Thread-Index: AcTHM6hJ1gLk1dpVSt+4pd0k0tLkWAAACVyg
From: "Jones, Nevin R \(Nevin\)" <nrjones@agere.com>
To: "Kevin Boyle" <kboyle@nortelnetworks.com>, <megaco@ietf.org>
X-OriginalArrivalTime: 10 Nov 2004 14:47:28.0857 (UTC)
	FILETIME=[33724490:01C4C734]
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1167427132=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1167427132==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4C734.334D5D75"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4C734.334D5D75
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Kevin:
=20
I agree that Megaco is not particularly specific to rt- services but it
does purport to support VoIP services. If such services are to be
"carrier grade" i.e. 5 nines then this would therefore suggest some need
to address the matter of rapid failover times for MGCs.
=20
Regards,

	-----Original Message-----
	From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]=20
	Sent: Wednesday, November 10, 2004 9:43 AM
	To: Jones, Nevin R (Nevin); megaco@ietf.org
	Subject: RE: [Megaco] MGC/MG Failure
=09
=09
	This is an implementation detail that would depend upon your
needs.  Note that Megaco does not have sole use in the real-time
services arena, therefore it is inappropriate for any timing
requirements to be specified as part of the protocol.
	=20
	Kevin


  _____ =20

		From: megaco-bounces@ietf.org
[mailto:megaco-bounces@ietf.org] On Behalf Of Jones, Nevin R (Nevin)
		Sent: Tuesday, November 09, 2004 6:48 PM
		To: megaco@ietf.org
		Cc: Jones, Nevin R (Nevin)
		Subject: [Megaco] MGC/MG Failure
	=09
	=09

		All:=20

		I am a newbie to the megao list so please forgive me if
this question was asked and answered previously. Is there a stipulation
(and better yet, mechanism) somewhere in the Megaco/H.248 standard for
the maximum switching time from one MGC to another in the case of a
handover? I ask this question with the concern that if real time IP
based services are to operate at 5 nines availability, then it would
seem that the MGC switchover would have to be in the 10s of
milliseconds.

		Thanks!=20

		Regards=20

		Nevin Jones=20


------_=_NextPart_001_01C4C734.334D5D75
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1458" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D244384414-10112004><FONT face=3D"Comic Sans MS" =
color=3D#0000ff=20
size=3D2>Kevin:</FONT></SPAN></DIV>
<DIV><SPAN class=3D244384414-10112004><FONT face=3D"Comic Sans MS" =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D244384414-10112004><FONT face=3D"Comic Sans MS" =
color=3D#0000ff=20
size=3D2>I agree that Megaco is not particularly specific to rt- =
services but it=20
does purport to support VoIP services. If such services are to be =
"carrier=20
grade" i.e. 5 nines then this&nbsp;would therefore suggest some need to =
address=20
the matter of rapid failover times for MGCs.</FONT></SPAN></DIV>
<DIV><SPAN class=3D244384414-10112004><FONT face=3D"Comic Sans MS" =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D244384414-10112004><FONT face=3D"Comic Sans MS" =
color=3D#0000ff=20
size=3D2>Regards,</FONT></SPAN></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> =
Kevin Boyle=20
  [mailto:kboyle@nortelnetworks.com] <BR><B>Sent:</B> Wednesday, =
November 10,=20
  2004 9:43 AM<BR><B>To:</B> Jones, Nevin R (Nevin);=20
  megaco@ietf.org<BR><B>Subject:</B> RE: [Megaco] MGC/MG=20
  Failure<BR><BR></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D784274114-10112004>This is an implementation detail that would =
depend=20
  upon your needs.&nbsp; Note that Megaco does not have sole use in the=20
  real-time services arena, therefore it is inappropriate for any timing =

  requirements to be specified as part of the =
protocol.</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D784274114-10112004></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D784274114-10112004>Kevin</SPAN></FONT></DIV><BR>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> megaco-bounces@ietf.org=20
    [mailto:megaco-bounces@ietf.org] <B>On Behalf Of </B>Jones, Nevin R=20
    (Nevin)<BR><B>Sent:</B> Tuesday, November 09, 2004 6:48 =
PM<BR><B>To:</B>=20
    megaco@ietf.org<BR><B>Cc:</B> Jones, Nevin R =
(Nevin)<BR><B>Subject:</B>=20
    [Megaco] MGC/MG Failure<BR></FONT><BR></DIV>
    <DIV></DIV><!-- Converted from text/rtf format -->
    <P><FONT face=3D"Comic Sans MS" size=3D2>All:</FONT> </P>
    <P><FONT face=3D"Comic Sans MS" size=3D2>I am a newbie to the megao =
list so=20
    please forgive me if this question was asked and answered =
previously. Is=20
    there a stipulation (and better yet, mechanism) somewhere in the=20
    Megaco/H.248 standard for the maximum switching time from one MGC to =
another=20
    in the case of a handover? I ask this question with the concern that =
if real=20
    time IP based services are to operate at 5 nines availability, then =
it would=20
    seem that the MGC switchover would have to be in the 10s of=20
    milliseconds.</FONT></P>
    <P><FONT face=3D"Comic Sans MS" size=3D2>Thanks!</FONT> </P>
    <P><FONT face=3D"Comic Sans MS" size=3D2>Regards</FONT> </P>
    <P><FONT face=3D"Comic Sans MS">Nevin Jones<B></B></FONT>=20
</P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
=00
------_=_NextPart_001_01C4C734.334D5D75--


--===============1167427132==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1167427132==--



From megaco-bounces@ietf.org  Wed Nov 10 10:17:54 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17923
	for <megaco-archive@lists.ietf.org>; Wed, 10 Nov 2004 10:17:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CRu71-00040A-Px; Wed, 10 Nov 2004 10:10:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CRtuQ-0006np-O0
	for megaco@megatron.ietf.org; Wed, 10 Nov 2004 09:57:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14660
	for <megaco@ietf.org>; Wed, 10 Nov 2004 09:57:16 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRtvO-00040d-BV
	for megaco@ietf.org; Wed, 10 Nov 2004 09:58:18 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAAEui429525
	for <megaco@ietf.org>; Wed, 10 Nov 2004 09:56:45 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WP4QW1T3>; Wed, 10 Nov 2004 09:56:41 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5369320BC@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "Jones, Nevin R (Nevin)" <nrjones@agere.com>, megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure
Date: Wed, 10 Nov 2004 09:56:31 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Then you will need to determine the permissible timings for your
implementation and its intended application.  This is not a spec issue.
 
Note that there are several H.248 implementations in live deployment in
real-time scenarios today.  Those implementations must surely have addressed
this already for their own purposes.
 
Kevin


  _____  

From: Jones, Nevin R (Nevin) [mailto:nrjones@agere.com] 
Sent: Wednesday, November 10, 2004 9:47 AM
To: Boyle, Kevin [NCRTP:3Z40:EXCH]; megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


Kevin:
 
I agree that Megaco is not particularly specific to rt- services but it does
purport to support VoIP services. If such services are to be "carrier grade"
i.e. 5 nines then this would therefore suggest some need to address the
matter of rapid failover times for MGCs.
 
Regards,

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] 
Sent: Wednesday, November 10, 2004 9:43 AM
To: Jones, Nevin R (Nevin); megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


This is an implementation detail that would depend upon your needs.  Note
that Megaco does not have sole use in the real-time services arena,
therefore it is inappropriate for any timing requirements to be specified as
part of the protocol.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Jones, Nevin R (Nevin)
Sent: Tuesday, November 09, 2004 6:48 PM
To: megaco@ietf.org
Cc: Jones, Nevin R (Nevin)
Subject: [Megaco] MGC/MG Failure



All: 

I am a newbie to the megao list so please forgive me if this question was
asked and answered previously. Is there a stipulation (and better yet,
mechanism) somewhere in the Megaco/H.248 standard for the maximum switching
time from one MGC to another in the case of a handover? I ask this question
with the concern that if real time IP based services are to operate at 5
nines availability, then it would seem that the MGC switchover would have to
be in the 10s of milliseconds.

Thanks! 

Regards 

Nevin Jones 


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


From megaco-bounces@ietf.org  Wed Nov 10 21:52:50 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04614
	for <megaco-archive@lists.ietf.org>; Wed, 10 Nov 2004 21:52:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CS52V-0007mm-07; Wed, 10 Nov 2004 21:50:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CS4rK-00060I-HI
	for megaco@megatron.ietf.org; Wed, 10 Nov 2004 21:38:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03647
	for <megaco@ietf.org>; Wed, 10 Nov 2004 21:38:48 -0500 (EST)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS4sI-00062K-3I
	for megaco@ietf.org; Wed, 10 Nov 2004 21:39:57 -0500
Received: from [61.144.161.53] (helo=huawei.com)
	by mx2.foretec.com with esmtp (Exim 4.24) id 1CS4r6-0003x2-5d
	for megaco@ietf.org; Wed, 10 Nov 2004 21:38:37 -0500
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0I6Z0053ZTD5ZM@szxga01-in.huawei.com> for
	megaco@ietf.org; Thu, 11 Nov 2004 10:24:41 +0800 (CST)
Received: from szxml02-in ([172.24.1.6])
	by szxga01-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTP id	<0I6Z002KHTD5EE@szxga01-in.huawei.com>
	formegaco@ietf.org; Thu, 11 Nov 2004 10:24:41 +0800 (CST)
Received: from r70036a ([10.78.228.199])
	by szxml02-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTPA id	<0I6Z00AZ7TDJ7X@szxml02-in.huawei.com>; Thu,
	11 Nov 2004 10:24:55 +0800 (CST)
Date: Thu, 11 Nov 2004 10:28:45 +0800
From: Rajeev K R <rajeev@huawei.com>
Subject: RE: [Megaco] MGC/MG Failure
In-reply-to: <717DBF3DD8906D4D86EB77637C40E54363B3C3@pauex2ku06.agere.com>
To: "'Jones, Nevin R (Nevin)'" <nrjones@agere.com>,
        "'Kevin Boyle'" <kboyle@nortelnetworks.com>, megaco@ietf.org
Message-id: <004601c4c796$2add8940$c7e44e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 72dbfff5c6b8ad2b1b727c13be042129
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1713025322=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1713025322==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_k4QlTskXOxU2oHkdI+e6Sg)"

This is a multi-part message in MIME format.

--Boundary_(ID_k4QlTskXOxU2oHkdI+e6Sg)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

Hi,
 
There are some other factors to be considerd here.
 
In a 5 nine reliable network, you simply cannot afford to have an MGC
switchover in normal situations.
Since there are network delays involved, it is almost impossible to switch
over and restore service within 1 minute.
Major factors being failure detection time and MG re-registration time
(including avalanche protection timer).
(You can switch over faster, but that would result in  stray switch overs.)
 
So MGC switch over can be considered only as a disaster recovery method when
you lose the service
of one MGC completely due to physical destruction of the equipment or
network.
In such cases up to 5 minutes is acceptable to restore service. 
(5 nines translate to 5 minutes downtime per year)
 
But in normal running, the MGC should not fail to that extent.
Internal failures of an MGC should be taken care by other mechanisms and
should not result in MGC switchover.
The MGC should have 6 nines availability (or close) by itself, for the total
service availability to be 5 nines.
 
Anyway, wrt H.248, I agree with Kevin that this timing need not be enforced
by protocol.
 
Rajeev
 
 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Jones, Nevin R (Nevin)
Sent: Wednesday, November 10, 2004 10:47 PM
To: Kevin Boyle; megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


Kevin:
 
I agree that Megaco is not particularly specific to rt- services but it does
purport to support VoIP services. If such services are to be "carrier grade"
i.e. 5 nines then this would therefore suggest some need to address the
matter of rapid failover times for MGCs.
 
Regards,

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] 
Sent: Wednesday, November 10, 2004 9:43 AM
To: Jones, Nevin R (Nevin); megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


This is an implementation detail that would depend upon your needs.  Note
that Megaco does not have sole use in the real-time services arena,
therefore it is inappropriate for any timing requirements to be specified as
part of the protocol.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Jones, Nevin R (Nevin)
Sent: Tuesday, November 09, 2004 6:48 PM
To: megaco@ietf.org
Cc: Jones, Nevin R (Nevin)
Subject: [Megaco] MGC/MG Failure



All: 

I am a newbie to the megao list so please forgive me if this question was
asked and answered previously. Is there a stipulation (and better yet,
mechanism) somewhere in the Megaco/H.248 standard for the maximum switching
time from one MGC to another in the case of a handover? I ask this question
with the concern that if real time IP based services are to operate at 5
nines availability, then it would seem that the MGC switchover would have to
be in the 10s of milliseconds.

Thanks! 

Regards 

Nevin Jones 


--Boundary_(ID_k4QlTskXOxU2oHkdI+e6Sg)
Content-type: text/html; charset=us-ascii
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=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1458" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>There 
are some other factors to be considerd here.</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>In 
a&nbsp;5 nine&nbsp;reliable network, you simply cannot afford to have an MGC 
switchover in normal situations.</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>Since 
there are network delays involved, it is almost impossible to switch over and 
restore service within 1 minute.</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>Major 
factors being failure detection time and&nbsp;MG re-registration time (including 
avalanche&nbsp;protection timer).</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=140000502-11112004><FONT face=Arial color=#0000ff size=2>(<SPAN 
class=140000502-11112004><FONT face=Arial color=#0000ff size=2>You can switch 
over faster, but that would result in &nbsp;stray switch 
overs.)</FONT></SPAN></FONT></SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=140000502-11112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=140000502-11112004></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=140000502-11112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=140000502-11112004></SPAN></FONT></SPAN>So MGC switch over&nbsp;can be 
considered only as a disaster recovery method when you lose the 
service</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>of one 
MGC</FONT></SPAN><SPAN class=140000502-11112004>&nbsp;<FONT face=Arial><FONT 
color=#0000ff size=2>completely due to physical destruction of the equipment or 
network.</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial><FONT color=#0000ff 
size=2>In such cases up to 5 minutes is acceptable </FONT></FONT></SPAN><SPAN 
class=140000502-11112004><FONT face=Arial color=#0000ff size=2>to restore 
service. </FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>(5 
nines&nbsp;translate to 5 minutes downtime per year)</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>But in 
normal running, the MGC should&nbsp;not fail to that extent.</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2>Internal failures of an MGC should be taken care by other mechanisms and 
should not result in MGC switchover.</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>The 
MGC&nbsp;should have&nbsp;6 nines availability (or close)&nbsp;by 
itself,&nbsp;for the total service availability&nbsp;to be&nbsp;5 
nines.</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2>Anyway, wrt H.248, I agree with Kevin that this timing need not be 
enforced by protocol.</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2>Rajeev</FONT></SPAN></DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
size=2>&nbsp;</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
  megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] <B>On Behalf Of 
  </B>Jones, Nevin R (Nevin)<BR><B>Sent:</B> Wednesday, November 10, 2004 10:47 
  PM<BR><B>To:</B> Kevin Boyle; megaco@ietf.org<BR><B>Subject:</B> RE: [Megaco] 
  MGC/MG Failure<BR><BR></FONT></DIV>
  <DIV><SPAN class=244384414-10112004><FONT face="Comic Sans MS" color=#0000ff 
  size=2>Kevin:</FONT></SPAN></DIV>
  <DIV><SPAN class=244384414-10112004><FONT face="Comic Sans MS" color=#0000ff 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=244384414-10112004><FONT face="Comic Sans MS" color=#0000ff 
  size=2>I agree that Megaco is not particularly specific to rt- services but it 
  does purport to support VoIP services. If such services are to be "carrier 
  grade" i.e. 5 nines then this&nbsp;would therefore suggest some need to 
  address the matter of rapid failover times for MGCs.</FONT></SPAN></DIV>
  <DIV><SPAN class=244384414-10112004><FONT face="Comic Sans MS" color=#0000ff 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=244384414-10112004><FONT face="Comic Sans MS" color=#0000ff 
  size=2>Regards,</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
    <DIV></DIV>
    <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
    face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Kevin Boyle 
    [mailto:kboyle@nortelnetworks.com] <BR><B>Sent:</B> Wednesday, November 10, 
    2004 9:43 AM<BR><B>To:</B> Jones, Nevin R (Nevin); 
    megaco@ietf.org<BR><B>Subject:</B> RE: [Megaco] MGC/MG 
    Failure<BR><BR></FONT></DIV>
    <DIV dir=ltr align=left><FONT face=Arial size=2><SPAN 
    class=784274114-10112004>This is an implementation detail that would depend 
    upon your needs.&nbsp; Note that Megaco does not have sole use in the 
    real-time services arena, therefore it is inappropriate for any timing 
    requirements to be specified as part of the protocol.</SPAN></FONT></DIV>
    <DIV dir=ltr align=left><FONT face=Arial size=2><SPAN 
    class=784274114-10112004></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=ltr align=left><FONT face=Arial size=2><SPAN 
    class=784274114-10112004>Kevin</SPAN></FONT></DIV><BR>
    <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
      <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
      <HR tabIndex=-1>
      <FONT face=Tahoma size=2><B>From:</B> megaco-bounces@ietf.org 
      [mailto:megaco-bounces@ietf.org] <B>On Behalf Of </B>Jones, Nevin R 
      (Nevin)<BR><B>Sent:</B> Tuesday, November 09, 2004 6:48 PM<BR><B>To:</B> 
      megaco@ietf.org<BR><B>Cc:</B> Jones, Nevin R (Nevin)<BR><B>Subject:</B> 
      [Megaco] MGC/MG Failure<BR></FONT><BR></DIV>
      <DIV></DIV><!-- Converted from text/rtf format -->
      <P><FONT face="Comic Sans MS" size=2>All:</FONT> </P>
      <P><FONT face="Comic Sans MS" size=2>I am a newbie to the megao list so 
      please forgive me if this question was asked and answered previously. Is 
      there a stipulation (and better yet, mechanism) somewhere in the 
      Megaco/H.248 standard for the maximum switching time from one MGC to 
      another in the case of a handover? I ask this question with the concern 
      that if real time IP based services are to operate at 5 nines 
      availability, then it would seem that the MGC switchover would have to be 
      in the 10s of milliseconds.</FONT></P>
      <P><FONT face="Comic Sans MS" size=2>Thanks!</FONT> </P>
      <P><FONT face="Comic Sans MS" size=2>Regards</FONT> </P>
      <P><FONT face="Comic Sans MS">Nevin Jones<B></B></FONT> 
  </P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_k4QlTskXOxU2oHkdI+e6Sg)--


--===============1713025322==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1713025322==--



From megaco-bounces@ietf.org  Thu Nov 11 04:57:05 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19684
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 04:57:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSBbs-0002yi-6g; Thu, 11 Nov 2004 04:51:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSBZn-0002le-K4
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 04:49:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19006
	for <megaco@ietf.org>; Thu, 11 Nov 2004 04:49:09 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSBal-0005Q3-Ru
	for megaco@ietf.org; Thu, 11 Nov 2004 04:50:22 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id 77F543467EF
	for <megaco@ietf.org>; Thu, 11 Nov 2004 01:48:12 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 24206-7126751C;
	Thu, 11 Nov 2004 01:48:12 -0800
Received: from Mahesh (unknown [172.25.0.61])
	by smtp.ccpu.com (Postfix) with ESMTP id 20A383468EC
	for <megaco@ietf.org>; Thu, 11 Nov 2004 01:48:11 -0800 (PST)
From: "Mahesh" <mahesh@ccpu.com>
To: <megaco@ietf.org>
Date: Thu, 11 Nov 2004 15:18:12 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcTH046hcbiivfgAQxSxeL2bU4cIWQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-Id: <20041111094811.20A383468EC@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.66; host: smtp)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Subject: [Megaco] Version negotiation in Handoff case
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1026287118=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1026287118==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0032_01C4C801.A9602730"

This is a multi-part message in MIME format.

------=_NextPart_000_0032_01C4C801.A9602730
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

HI All,

 

I will be thankful to you if you can clarify the following scenario  of
handoff .

 

 

MG can support v1 and V2 .

MG is currently in a session with Primary MGC and the negotiated version  is
V1.

Primary MGC sends a handoff to MG.

 

Then for contacting the secondary MGC which version shall the MG use in the
Service change .

 

With regards

Mahesh

 


------=_NextPart_000_0032_01C4C801.A9602730
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>HI All,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I will be thankful to you if you can clarify the =
following scenario
&nbsp;of handoff .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MG can support v1 and V2 =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MG is currently in a session with Primary MGC and the
negotiated version&nbsp; is V1.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Primary MGC sends a handoff to =
MG.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Then for contacting the secondary MGC which version =
shall
the MG use in the Service change .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>With regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Mahesh<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0032_01C4C801.A9602730--




--===============1026287118==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1026287118==--





From megaco-bounces@ietf.org  Thu Nov 11 05:21:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21755
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 05:21:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSC15-0007JY-5s; Thu, 11 Nov 2004 05:17:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSBwo-0006Lt-Rc
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 05:12:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20944
	for <megaco@ietf.org>; Thu, 11 Nov 2004 05:12:56 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSBxn-0005wy-HE
	for megaco@ietf.org; Thu, 11 Nov 2004 05:14:09 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id 6DE413468A0
	for <megaco@ietf.org>; Thu, 11 Nov 2004 02:12:17 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 28871-1B3E43CD;
	Thu, 11 Nov 2004 02:12:17 -0800
Received: from Mahesh (unknown [172.25.0.61])
	by smtp.ccpu.com (Postfix) with ESMTP id 243F23468EF
	for <megaco@ietf.org>; Thu, 11 Nov 2004 02:12:16 -0800 (PST)
From: "Mahesh" <mahesh@ccpu.com>
To: <megaco@ietf.org>
Date: Thu, 11 Nov 2004 15:42:17 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcTH1uuldhSBCoZFTEyxR1p/s+h3XA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-Id: <20041111101216.243F23468EF@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.66; host: smtp)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Subject: [Megaco] encoding scheme during hand off
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0219519416=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0219519416==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_003F_01C4C805.06A33F10"

This is a multi-part message in MIME format.

------=_NextPart_000_003F_01C4C805.06A33F10
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

HI All,

 

How can an MG know the  encoding scheme of the secondary MGC in the case of
hand off .

This is because in the case of hand off , the  address of new  MGC is given
by

Primary MGC. This new MGC may not be pre provisioned  at the MG side .

If the handoff MGC is using the default port , MG can find the encoding
scheme .But if 

Handoff  MGC is not using the default port, HOW can MG know the encoding
scheme of 

new MGC .

 

With regards

Mahesh

 


------=_NextPart_000_003F_01C4C805.06A33F10
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>HI All,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>How can an MG know the&nbsp; encoding scheme of the
secondary MGC in the case of hand off .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>This is because in the case of hand off , the =
&nbsp;address
of new &nbsp;MGC is given by<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Primary MGC. This new MGC may not be pre provisioned =
&nbsp;at
the MG side .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>If the handoff MGC is using the default port , MG can =
find
the encoding scheme .But if <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Handoff &nbsp;MGC is not using the default port, HOW =
can MG
know the encoding scheme of <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>new MGC .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>With regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Mahesh<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_003F_01C4C805.06A33F10--




--===============0219519416==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0219519416==--





From megaco-bounces@ietf.org  Thu Nov 11 06:47:30 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29268
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 06:47:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSDOi-0003sd-7E; Thu, 11 Nov 2004 06:45:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSDNs-0003e7-AU
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 06:45:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29111
	for <megaco@ietf.org>; Thu, 11 Nov 2004 06:44:57 -0500 (EST)
From: bvswamy@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSDOv-0007tC-Ag
	for megaco@ietf.org; Thu, 11 Nov 2004 06:46:12 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iABBfV6p020639
	for <megaco@ietf.org>; Thu, 11 Nov 2004 17:11:32 +0530 (IST)
Received: from webmail.hss.hns.com (webmail.hss.hns.com [192.168.100.50])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iABBfUxX020626;
	Thu, 11 Nov 2004 17:11:30 +0530 (IST)
In-Reply-To: <20041111094811.20A383468EC@smtp.ccpu.com>
To: "Mahesh" <mahesh@ccpu.com>
Subject: Re: [Megaco] Version negotiation in Handoff case
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF527B369C.5ADCAB00-ON65256F49.003F94A6-65256F49.00407850@hssworld.com>
Date: Thu, 11 Nov 2004 17:09:23 +0530
X-MIMETrack: S/MIME Sign by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/11/2004 05:14:11 PM,
	Serialize by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/11/2004 05:14:11 PM,
	Serialize complete at 11/11/2004 05:14:11 PM,
	S/MIME Sign failed at 11/11/2004 05:14:11 PM: The cryptographic key was
	not found,
	Serialize by Router on WebMail/HSS(Release 6.5.1|January 21,
	2004) at 11/11/2004 05:09:26 PM,
	Serialize complete at 11/11/2004 05:09:26 PM
X-Spam-Score: 3.9 (+++)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1570129891=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multipart message in MIME format.
--===============1570129891==
Content-Type: multipart/alternative;
	boundary="=_alternative 0040784665256F49_="

This is a multipart message in MIME format.
--=_alternative 0040784665256F49_=
Content-Type: text/plain; charset="US-ASCII"


Hi

As per the protocol specs, Version Negotiation also takes place during 
Handoff and Failover procedures.(Section 11.3)


Regards
B. Venkat S.R Swamy
Hughes Software Systems
www.hssworld.com






"Mahesh" <mahesh@ccpu.com> 
Sent by: megaco-bounces@ietf.org
11/11/2004 03:18 PM


To
<megaco@ietf.org>
cc

Subject
[Megaco] Version negotiation in Handoff case








HI All,

 

I will be thankful to you if you can clarify the following scenario  of 
handoff .

 

 

MG can support v1 and V2 .

MG is currently in a session with Primary MGC and the negotiated version  
is V1.

Primary MGC sends a handoff to MG.

 

Then for contacting the secondary MGC which version shall the MG use in 
the Service change .

 

With regards

Mahesh

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



***********************  HSS-Private   ***********************

"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
--=_alternative 0040784665256F49_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi</font>
<br>
<br><font size=2 face="sans-serif">As per the protocol specs, Version Negotiation
also takes place during Handoff and Failover procedures.(Section 11.3)</font>
<br>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">B. Venkat S.R Swamy</font>
<br><font size=2 face="sans-serif">Hughes Software Systems</font>
<br><font size=2 face="sans-serif">www.hssworld.com</font>
<br>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Mahesh&quot; &lt;mahesh@ccpu.com&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: megaco-bounces@ietf.org</font>
<p><font size=1 face="sans-serif">11/11/2004 03:18 PM</font>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">&lt;megaco@ietf.org&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">[Megaco] Version negotiation
in Handoff case</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br>
<br>
<br><font size=2>HI All,</font>
<br>
<br><font size=2>&nbsp;</font>
<br>
<br><font size=2>I will be thankful to you if you can clarify the following
scenario &nbsp;of handoff .</font>
<br>
<br><font size=2>&nbsp;</font>
<br>
<br><font size=2>&nbsp;</font>
<br>
<br><font size=2>MG can support v1 and V2 .</font>
<br>
<br><font size=2>MG is currently in a session with Primary MGC and the
negotiated version&nbsp; is V1.</font>
<br>
<br><font size=2>Primary MGC sends a handoff to MG.</font>
<br>
<br><font size=2>&nbsp;</font>
<br>
<br><font size=2>Then for contacting the secondary MGC which version shall
the MG use in the Service change .</font>
<br>
<br><font size=2>&nbsp;</font>
<br>
<br><font size=2>With regards</font>
<br>
<br><font size=2>Mahesh</font>
<br>
<br><font size=2>&nbsp;</font>
<br><font size=2><tt>_______________________________________________<br>
Megaco mailing list<br>
Megaco@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/megaco</tt></font>
<br>
<br><font size=2 face="sans-serif"><br>
<br>
*********************** &nbsp;HSS-Private &nbsp; ***********************</font>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
</pre></font></td></tr></table>
--=_alternative 0040784665256F49_=--


--===============1570129891==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1570129891==--



From megaco-bounces@ietf.org  Thu Nov 11 07:22:43 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02289
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 07:22:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSDws-0000pA-9A; Thu, 11 Nov 2004 07:21:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSDv8-0000ZZ-Eu
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 07:19:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02035
	for <megaco@ietf.org>; Thu, 11 Nov 2004 07:19:21 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSDw7-000096-VF
	for megaco@ietf.org; Thu, 11 Nov 2004 07:20:34 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP
	id 4347F34684E; Thu, 11 Nov 2004 04:18:25 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 07527-1BEB3627;
	Thu, 11 Nov 2004 04:18:25 -0800
Received: from CCPU00311 (unknown [172.25.0.119])
	by smtp.ccpu.com (Postfix) with ESMTP
	id 79C4E34684E; Thu, 11 Nov 2004 04:18:22 -0800 (PST)
From: "Rashim Anand" <ranand@ccpu.com>
To: <bvswamy@hssworld.com>, "'Mahesh'" <mahesh@ccpu.com>
Subject: RE: [Megaco] Version negotiation in Handoff case
Date: Thu, 11 Nov 2004 04:18:29 -0800
Message-ID: <002801c4c7e8$8f2a7140$770019ac@CCPU00311>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
In-Reply-To: <OF527B369C.5ADCAB00-ON65256F49.003F94A6-65256F49.00407850@hssworld.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.66; host: smtp)
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 913ee11e7c554f7d4da75d500826397e
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1830879059=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1830879059==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0029_01C4C7A5.81073140"

This is a multi-part message in MIME format.

------=_NextPart_000_0029_01C4C7A5.81073140
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Ventak,
=20
I believe that the question was which version should the MG use to =
contact
the new MGC. Should it use the version with which it was communicating =
with
the old MGC or should it use the maximum version supported at MG? =
Ofcourse,
either way there will be version negotiation with the new MGC. The final
version negotiated with the new MGC might be V1 or V2 but the doubt is =
which
version should be used in sending the srvcChng to the new MGC =
(irrespective
of the new MGC's subsequent reply).
=20
Regards,
-Rashim Anand
=20
=20
=20

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf =
Of
bvswamy@hssworld.com
Sent: Thursday, November 11, 2004 3:39 AM
To: Mahesh
Cc: megaco@ietf.org
Subject: Re: [Megaco] Version negotiation in Handoff case



Hi=20

As per the protocol specs, Version Negotiation also takes place during
Handoff and Failover procedures.(Section 11.3)=20


Regards=20
B. Venkat S.R Swamy=20
Hughes Software Systems=20
www.hssworld.com=20






"Mahesh" <mahesh@ccpu.com>=20
Sent by: megaco-bounces@ietf.org=20


11/11/2004 03:18 PM=20



To
<megaco@ietf.org>=20

cc

Subject
[Megaco] Version negotiation in Handoff case

=09






HI All,=20

 =20

I will be thankful to you if you can clarify the following scenario  of
handoff .=20

 =20

 =20

MG can support v1 and V2 .=20

MG is currently in a session with Primary MGC and the negotiated version =
 is
V1.=20

Primary MGC sends a handoff to MG.=20

 =20

Then for contacting the secondary MGC which version shall the MG use in =
the
Service change .=20

 =20

With regards=20

Mahesh=20

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



***********************  HSS-Private   ***********************=20

"Please note:The email domain of Hughes Software Systems Ltd. has been
changed to "hssworld.com" from hss.hns.com"



"DISCLAIMER: This message is proprietary to Hughes Software Systems =
Limited
(HSS) and is intended=20

solely for the use of the individual to whom it is addressed. It may =
contain
privileged or=20

confidential information and should not be circulated or used for any
purpose other than for=20

what it is intended. If you have received this message in error, please
notify the originator=20

immediately. If you are not the intended recipient, you are notified =
that
you are strictly=20

prohibited from using, copying, altering, or disclosing the contents of =
this
message. HSS=20

accepts no responsibility for loss or damage arising from the use of the
information transmitted=20

by this email including damage from virus."




------=_NextPart_000_0029_01C4C7A5.81073140
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.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D628310712-11112004><FONT face=3DArial color=3D#0000ff =
size=3D2>Hi=20
Ventak,</FONT></SPAN></DIV>
<DIV><SPAN class=3D628310712-11112004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D628310712-11112004><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
believe that the question was which version should the MG use to contact =
the new=20
MGC. Should it use the version with which it was communicating with the =
old MGC=20
or should it use the maximum version supported at MG? Ofcourse, either =
way there=20
will be version negotiation with the new MGC. The final version =
negotiated with=20
the new MGC might be V1 or V2 but the doubt is which version should be =
used in=20
sending the srvcChng to the new MGC (irrespective of the new MGC's =
subsequent=20
reply).</FONT></SPAN></DIV>
<DIV><SPAN class=3D628310712-11112004><FONT face=3DArial color=3D#0000ff =

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

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

size=3D2>-Rashim Anand</FONT></SPAN></DIV>
<DIV><SPAN class=3D628310712-11112004><FONT face=3DArial color=3D#0000ff =

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

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

size=3D2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE 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-bounces@ietf.org [mailto:megaco-bounces@ietf.org] <B>On Behalf =
Of=20
  </B>bvswamy@hssworld.com<BR><B>Sent:</B> Thursday, November 11, 2004 =
3:39=20
  AM<BR><B>To:</B> Mahesh<BR><B>Cc:</B> =
megaco@ietf.org<BR><B>Subject:</B> Re:=20
  [Megaco] Version negotiation in Handoff =
case<BR><BR></FONT></DIV><BR><FONT=20
  face=3Dsans-serif size=3D2>Hi</FONT> <BR><BR><FONT face=3Dsans-serif =
size=3D2>As per=20
  the protocol specs, Version Negotiation also takes place during =
Handoff and=20
  Failover procedures.(Section 11.3)</FONT> <BR><BR><BR><FONT =
face=3Dsans-serif=20
  size=3D2>Regards</FONT> <BR><FONT face=3Dsans-serif size=3D2>B. Venkat =
S.R=20
  Swamy</FONT> <BR><FONT face=3Dsans-serif size=3D2>Hughes Software =
Systems</FONT>=20
  <BR><FONT face=3Dsans-serif size=3D2>www.hssworld.com</FONT>=20
  <BR><BR><BR><BR><BR><BR>
  <TABLE width=3D"100%">
    <TBODY>
    <TR vAlign=3Dtop>
      <TD width=3D"40%"><FONT face=3Dsans-serif size=3D1><B>"Mahesh"=20
        &lt;mahesh@ccpu.com&gt;</B> </FONT><BR><FONT face=3Dsans-serif =
size=3D1>Sent=20
        by: megaco-bounces@ietf.org</FONT>=20
        <P><FONT face=3Dsans-serif size=3D1>11/11/2004 03:18 PM</FONT> =
<BR></P>
      <TD width=3D"59%">
        <TABLE width=3D"100%">
          <TBODY>
          <TR>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>To</FONT></DIV>
            <TD vAlign=3Dtop><FONT face=3Dsans-serif=20
              size=3D1>&lt;megaco@ietf.org&gt;</FONT>=20
          <TR>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>cc</FONT></DIV>
            <TD vAlign=3Dtop>
          <TR>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>Subject</FONT></DIV>
            <TD vAlign=3Dtop><FONT face=3Dsans-serif size=3D1>[Megaco] =
Version=20
              negotiation in Handoff =
case</FONT></TR></TBODY></TABLE><BR>
        <TABLE>
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
            =
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><BR><BR><FO=
NT=20
  size=3D2>HI All,</FONT> <BR><BR><FONT size=3D2>&nbsp;</FONT> =
<BR><BR><FONT=20
  size=3D2>I will be thankful to you if you can clarify the following =
scenario=20
  &nbsp;of handoff .</FONT> <BR><BR><FONT size=3D2>&nbsp;</FONT> =
<BR><BR><FONT=20
  size=3D2>&nbsp;</FONT> <BR><BR><FONT size=3D2>MG can support v1 and V2 =
.</FONT>=20
  <BR><BR><FONT size=3D2>MG is currently in a session with Primary MGC =
and the=20
  negotiated version&nbsp; is V1.</FONT> <BR><BR><FONT size=3D2>Primary =
MGC sends=20
  a handoff to MG.</FONT> <BR><BR><FONT size=3D2>&nbsp;</FONT> =
<BR><BR><FONT=20
  size=3D2>Then for contacting the secondary MGC which version shall the =
MG use in=20
  the Service change .</FONT> <BR><BR><FONT size=3D2>&nbsp;</FONT> =
<BR><BR><FONT=20
  size=3D2>With regards</FONT> <BR><BR><FONT size=3D2>Mahesh</FONT> =
<BR><BR><FONT=20
  size=3D2>&nbsp;</FONT> <BR><FONT=20
  size=3D2><TT>_______________________________________________<BR>Megaco =
mailing=20
  =
list<BR>Megaco@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/megaco<=
/TT></FONT>=20
  <BR><BR><FONT face=3Dsans-serif =
size=3D2><BR><BR>***********************=20
  &nbsp;HSS-Private &nbsp; ***********************</FONT>=20
  <TABLE>
    <TBODY>
    <TR>
      <TD bgColor=3D#ffffff><FONT color=3D#000000><PRE>"Please note:The =
email domain of Hughes Software Systems Ltd. has been changed to =
"hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems =
Limited (HSS) and is intended=20
solely for the use of the individual to whom it is addressed. It may =
contain  privileged or=20
confidential information and should not be circulated or used for any =
purpose other than for=20
what it is intended. If you have received this message in error, please =
notify the originator=20
immediately. If you are not the intended recipient, you are notified =
that you are strictly=20
prohibited from using, copying, altering, or disclosing the contents of =
this message. HSS=20
accepts no responsibility for loss or damage arising from the use of the =
information transmitted=20
by this email including damage from virus."
</PRE></FONT></TD></TR></TBODY></TABLE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0029_01C4C7A5.81073140--



--===============1830879059==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1830879059==--




From megaco-bounces@ietf.org  Thu Nov 11 07:25:58 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02659
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 07:25:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSDwt-0000pt-RW; Thu, 11 Nov 2004 07:21:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSDw2-0000gx-7p
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 07:20:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02134
	for <megaco@ietf.org>; Thu, 11 Nov 2004 07:20:17 -0500 (EST)
From: bvswamy@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSDx2-0000Ah-IV
	for megaco@ietf.org; Thu, 11 Nov 2004 07:21:30 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iABCGc6p003081
	for <megaco@ietf.org>; Thu, 11 Nov 2004 17:46:44 +0530 (IST)
Received: from webmail.hss.hns.com (webmail.hss.hns.com [192.168.100.50])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iABCGbxX003076;
	Thu, 11 Nov 2004 17:46:37 +0530 (IST)
In-Reply-To: <OF527B369C.5ADCAB00-ON65256F49.003F94A6-65256F49.00407850@hssworld.com>
To: "Mahesh" <mahesh@ccpu.com>
Subject: Re: [Megaco] Version negotiation in Handoff case
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFF4D741E7.0895955E-ON65256F49.0042F28B-65256F49.0043AF9D@hssworld.com>
Date: Thu, 11 Nov 2004 17:44:30 +0530
X-MIMETrack: S/MIME Sign by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/11/2004 05:49:19 PM,
	Serialize by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/11/2004 05:49:19 PM,
	Serialize complete at 11/11/2004 05:49:19 PM,
	S/MIME Sign failed at 11/11/2004 05:49:19 PM: The cryptographic key was
	not found,
	Serialize by Router on WebMail/HSS(Release 6.5.1|January 21,
	2004) at 11/11/2004 05:44:33 PM,
	Serialize complete at 11/11/2004 05:44:33 PM
X-Spam-Score: 4.2 (++++)
X-Scan-Signature: a1dc446dc7ac353b90b60743d0e479e3
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0995754336=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multipart message in MIME format.
--===============0995754336==
Content-Type: multipart/alternative;
	boundary="=_alternative 0043AF9965256F49_="

This is a multipart message in MIME format.
--=_alternative 0043AF9965256F49_=
Content-Type: text/plain; charset="US-ASCII"


small correction,
Version Negotiation "may" also take place ........
hence not mandatory.






B Venkat S.R Swamy/HSS@HSS 
Sent by: megaco-bounces@ietf.org
11/11/2004 05:09 PM


To
"Mahesh" <mahesh@ccpu.com>
cc
megaco@ietf.org
Subject
Re: [Megaco] Version negotiation in Handoff case







Hi 

As per the protocol specs, Version Negotiation also takes place during 
Handoff and Failover procedures.(Section 11.3) 


Regards 
B. Venkat S.R Swamy 
Hughes Software Systems 
www.hssworld.com 






"Mahesh" <mahesh@ccpu.com>  
Sent by: megaco-bounces@ietf.org 

11/11/2004 03:18 PM 


To
<megaco@ietf.org> 
cc

Subject
[Megaco] Version negotiation in Handoff case









HI All,

  

I will be thankful to you if you can clarify the following scenario  of 
handoff . 

  

  

MG can support v1 and V2 . 

MG is currently in a session with Primary MGC and the negotiated version  
is V1. 

Primary MGC sends a handoff to MG. 

 

Then for contacting the secondary MGC which version shall the MG use in 
the Service change . 

  

With regards 

Mahesh 

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



***********************  HSS-Private   *********************** 


"Please note:The email domain of Hughes Software Systems Ltd. has been 
changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems 
Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may 
contain  privileged or 
confidential information and should not be circulated or used for any 
purpose other than for 
what it is intended. If you have received this message in error, please 
notify the originator 
immediately. If you are not the intended recipient, you are notified that 
you are strictly 
prohibited from using, copying, altering, or disclosing the contents of 
this message. HSS 
accepts no responsibility for loss or damage arising from the use of the 
information transmitted 
by this email including damage from virus."



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



***********************  HSS-Private   ***********************

"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
--=_alternative 0043AF9965256F49_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">small correction,</font>
<br><font size=2 face="sans-serif">Version Negotiation &quot;may&quot;
also take place ........</font>
<br><font size=2 face="sans-serif">hence not mandatory.</font>
<br>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>B Venkat S.R Swamy/HSS@HSS</b>
</font>
<br><font size=1 face="sans-serif">Sent by: megaco-bounces@ietf.org</font>
<p><font size=1 face="sans-serif">11/11/2004 05:09 PM</font>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">&quot;Mahesh&quot; &lt;mahesh@ccpu.com&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">megaco@ietf.org</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: [Megaco] Version negotiation
in Handoff case</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br>
<br><font size=2>Hi</font><font size=3> </font>
<br>
<br><font size=2>As per the protocol specs, Version Negotiation also takes
place during Handoff and Failover procedures.(Section 11.3)</font><font size=3>
</font>
<br>
<br>
<br><font size=2>Regards</font><font size=3> </font>
<br><font size=2>B. Venkat S.R Swamy</font><font size=3> </font>
<br><font size=2>Hughes Software Systems</font><font size=3> </font>
<br><font size=2>www.hssworld.com</font><font size=3> </font>
<br>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1><b>&quot;Mahesh&quot; &lt;mahesh@ccpu.com&gt;</b>
</font><font size=3>&nbsp;</font>
<br><font size=1>Sent by: megaco-bounces@ietf.org</font><font size=3> </font>
<br>
<br><font size=1>11/11/2004 03:18 PM</font><font size=3> </font>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td width=19%>
<div align=right><font size=1>To</font></div>
<td width=80%><font size=1>&lt;megaco@ietf.org&gt;</font><font size=3>
</font>
<tr valign=top>
<td>
<div align=right><font size=1>cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1>Subject</font></div>
<td><font size=1>[Megaco] Version negotiation in Handoff case</font></table>
<br>
<table width=100%>
<tr valign=top>
<td width=50%>
<td width=50%></table>
<br>
<br></table>
<br>
<br>
<br>
<br>
<br><font size=2>HI All,</font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>I will be thankful to you if you can clarify the following
scenario &nbsp;of handoff .</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>MG can support v1 and V2 .</font><font size=3> </font>
<br>
<br><font size=2>MG is currently in a session with Primary MGC and the
negotiated version&nbsp; is V1.</font><font size=3> </font>
<br>
<br><font size=2>Primary MGC sends a handoff to MG.</font><font size=3>
</font>
<br>
<br><font size=2>&nbsp;</font>
<br>
<br><font size=2>Then for contacting the secondary MGC which version shall
the MG use in the Service change .</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>With regards</font><font size=3> </font>
<br>
<br><font size=2>Mahesh</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br><font size=2><tt>_______________________________________________</tt></font>
<br><font size=2><tt>Megaco mailing list</tt></font>
<br><font size=2><tt>Megaco@ietf.org</tt></font>
<br><font size=2><tt>https://www1.ietf.org/mailman/listinfo/megaco</tt></font><font size=3>
</font>
<br>
<br>
<br>
<br><font size=2>*********************** &nbsp;HSS-Private &nbsp; ***********************</font><font size=3>
</font>
<table width=100%>
<tr valign=top>
<td width=100%>
<br>
<br><font size=3><tt>&quot;Please note:The email domain of Hughes Software
Systems Ltd. has been changed to &quot;hssworld.com&quot; from hss.hns.com&quot;</tt></font>
<br>
<br><font size=3><tt>&quot;DISCLAIMER: This message is proprietary to Hughes
Software Systems Limited (HSS) and is intended </tt></font>
<br><font size=3><tt>solely for the use of the individual to whom it is
addressed. It may contain &nbsp;privileged or </tt></font>
<br><font size=3><tt>confidential information and should not be circulated
or used for any purpose other than for </tt></font>
<br><font size=3><tt>what it is intended. If you have received this message
in error, please notify the originator </tt></font>
<br><font size=3><tt>immediately. If you are not the intended recipient,
you are notified that you are strictly </tt></font>
<br><font size=3><tt>prohibited from using, copying, altering, or disclosing
the contents of this message. HSS </tt></font>
<br><font size=3><tt>accepts no responsibility for loss or damage arising
from the use of the information transmitted </tt></font>
<br><font size=3><tt>by this email including damage from virus.&quot;</tt></font>
<br>
<br></table>
<br>
<br><font size=2><tt>_______________________________________________<br>
Megaco mailing list<br>
Megaco@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/megaco</tt></font>
<br>
<br><font size=2 face="sans-serif"><br>
<br>
*********************** &nbsp;HSS-Private &nbsp; ***********************</font>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
</pre></font></td></tr></table>
--=_alternative 0043AF9965256F49_=--


--===============0995754336==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0995754336==--



From megaco-bounces@ietf.org  Thu Nov 11 07:32:18 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03248
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 07:32:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSE52-0002Gh-FL; Thu, 11 Nov 2004 07:29:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSE3b-00025y-2h
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 07:28:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02901
	for <megaco@ietf.org>; Thu, 11 Nov 2004 07:28:06 -0500 (EST)
From: bvswamy@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSE1x-0000GG-Di
	for megaco@ietf.org; Thu, 11 Nov 2004 07:29:19 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iABCLk6p004770
	for <megaco@ietf.org>; Thu, 11 Nov 2004 17:51:47 +0530 (IST)
Received: from webmail.hss.hns.com (webmail.hss.hns.com [192.168.100.50])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iABCLjxX004763;
	Thu, 11 Nov 2004 17:51:45 +0530 (IST)
In-Reply-To: <002801c4c7e8$8f2a7140$770019ac@CCPU00311>
To: "Rashim Anand" <ranand@ccpu.com>
Subject: RE: [Megaco] Version negotiation in Handoff case
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF25B47513.B59F5AA0-ON65256F49.004363B7-65256F49.0044283A@hssworld.com>
Date: Thu, 11 Nov 2004 17:49:39 +0530
X-MIMETrack: S/MIME Sign by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/11/2004 05:54:27 PM,
	Serialize by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/11/2004 05:54:27 PM,
	Serialize complete at 11/11/2004 05:54:27 PM,
	S/MIME Sign failed at 11/11/2004 05:54:27 PM: The cryptographic key was
	not found,
	Serialize by Router on WebMail/HSS(Release 6.5.1|January 21,
	2004) at 11/11/2004 05:49:41 PM,
	Serialize complete at 11/11/2004 05:49:41 PM
X-Spam-Score: 4.2 (++++)
X-Scan-Signature: 89ebdf268eceaeaf784b3acb625dc20e
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0960150707=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multipart message in MIME format.
--===============0960150707==
Content-Type: multipart/alternative;
	boundary="=_alternative 0044283665256F49_="

This is a multipart message in MIME format.
--=_alternative 0044283665256F49_=
Content-Type: text/plain; charset="US-ASCII"


Hi Rashim

If MG is doing version negotiation then I suppose MG should send Service 
Change with its highest version support.(in your case V2)


regards
B. Venkat S.R Swamy
Hughes Software Systems
www.hssworld.com




"Rashim Anand" <ranand@ccpu.com> 
11/11/2004 05:48 PM


To
B Venkat S.R Swamy/HSS@HSS, "'Mahesh'" <mahesh@ccpu.com>
cc
<megaco@ietf.org>
Subject
RE: [Megaco] Version negotiation in Handoff case







Hi  Ventak,
 
I  believe that the question was which version should the MG use to 
contact the new  MGC. Should it use the version with which it was 
communicating with the old MGC  or should it use the maximum version 
supported at MG? Ofcourse, either way there  will be version negotiation 
with the new MGC. The final version negotiated with  the new MGC might be 
V1 or V2 but the doubt is which version should be used in  sending the 
srvcChng to the new MGC (irrespective of the new MGC's subsequent  reply).
 
Regards,
-Rashim Anand
 
 
 
-----Original Message-----
From:  megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf 
Of  bvswamy@hssworld.com
Sent: Thursday, November 11, 2004 3:39  AM
To: Mahesh
Cc: megaco@ietf.org
Subject: Re:  [Megaco] Version negotiation in Handoff case



Hi 

As per  the protocol specs, Version Negotiation also takes place during 
Handoff and  Failover procedures.(Section 11.3) 


Regards 
B. Venkat S.R  Swamy 
Hughes Software Systems 
www.hssworld.com 






"Mahesh"  <mahesh@ccpu.com> 
Sent  by: megaco-bounces@ietf.org 

11/11/2004 03:18 PM 


To
<megaco@ietf.org> 
cc

Subject
[Megaco] Version  negotiation in Handoff case









HI All, 

  

I will be thankful to you if you can clarify the following scenario   of 
handoff . 

  

  

MG can support v1 and V2 . 

MG is currently in a session with Primary MGC and the  negotiated version  
is V1. 

Primary MGC sends  a handoff to MG. 

  

Then for contacting the secondary MGC which version shall the MG use in 
the Service change . 

  

With regards 

Mahesh 

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



***********************   HSS-Private   *********************** 


"Please note:The email domain of Hughes Software Systems Ltd. has been 
changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems 
Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may 
contain  privileged or 
confidential information and should not be circulated or used for any 
purpose other than for 
what it is intended. If you have received this message in error, please 
notify the originator 
immediately. If you are not the intended recipient, you are notified that 
you are strictly 
prohibited from using, copying, altering, or disclosing the contents of 
this message. HSS 
accepts no responsibility for loss or damage arising from the use of the 
information transmitted 
by this email including damage from virus."





***********************  HSS-Private   ***********************

"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
--=_alternative 0044283665256F49_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Rashim</font>
<br>
<br><font size=2 face="sans-serif">If MG is doing version negotiation then
I suppose MG should send Service Change with its highest version support.(in
your case V2)</font>
<br>
<br>
<br><font size=2 face="sans-serif">regards</font>
<br><font size=2 face="sans-serif">B. Venkat S.R Swamy</font>
<br><font size=2 face="sans-serif">Hughes Software Systems</font>
<br><font size=2 face="sans-serif">www.hssworld.com</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Rashim Anand&quot;
&lt;ranand@ccpu.com&gt;</b> </font>
<p><font size=1 face="sans-serif">11/11/2004 05:48 PM</font>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">B Venkat S.R Swamy/HSS@HSS,
&quot;'Mahesh'&quot; &lt;mahesh@ccpu.com&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">&lt;megaco@ietf.org&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">RE: [Megaco] Version negotiation
in Handoff case</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br>
<br><font size=2>Hi &nbsp;Ventak,</font>
<br><font size=3>&nbsp;</font>
<br><font size=2>I &nbsp;believe that the question was which version should
the MG use to contact the new &nbsp;MGC. Should it use the version with
which it was communicating with the old MGC &nbsp;or should it use the
maximum version supported at MG? Ofcourse, either way there &nbsp;will
be version negotiation with the new MGC. The final version negotiated with
&nbsp;the new MGC might be V1 or V2 but the doubt is which version should
be used in &nbsp;sending the srvcChng to the new MGC (irrespective of the
new MGC's subsequent &nbsp;reply).</font>
<br><font size=3>&nbsp;</font>
<br><font size=2>Regards,</font>
<br><font size=2>-Rashim Anand</font>
<br><font size=3>&nbsp;</font>
<br><font size=3>&nbsp;</font>
<br><font size=3>&nbsp;</font>
<br><font size=2>-----Original Message-----</font>
<br><font size=2><b>From:</b> &nbsp;megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]
<b>On Behalf Of &nbsp;</b>bvswamy@hssworld.com</font>
<br><font size=2><b>Sent:</b> Thursday, November 11, 2004 3:39 &nbsp;AM</font>
<br><font size=2><b>To:</b> Mahesh</font>
<br><font size=2><b>Cc:</b> megaco@ietf.org</font>
<br><font size=2><b>Subject:</b> Re: &nbsp;[Megaco] Version negotiation
in Handoff case</font>
<br>
<br>
<br>
<br><font size=2>Hi</font><font size=3> </font>
<br>
<br><font size=2>As per &nbsp;the protocol specs, Version Negotiation also
takes place during Handoff and &nbsp;Failover procedures.(Section 11.3)</font><font size=3>
</font>
<br>
<br>
<br><font size=2>Regards</font><font size=3> </font>
<br><font size=2>B. Venkat S.R &nbsp;Swamy</font><font size=3> </font>
<br><font size=2>Hughes Software Systems</font><font size=3> &nbsp;</font>
<br><font size=2>www.hssworld.com</font><font size=3> &nbsp;</font>
<br>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1><b>&quot;Mahesh&quot; &nbsp;&lt;mahesh@ccpu.com&gt;</b>
</font>
<br><font size=1>Sent &nbsp;by: megaco-bounces@ietf.org</font><font size=3>
&nbsp;</font>
<br>
<br><font size=1>11/11/2004 03:18 PM</font><font size=3> </font>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td width=13%>
<div align=right><font size=1>To</font></div>
<td width=86%><font size=1>&lt;megaco@ietf.org&gt;</font><font size=3>
&nbsp;</font>
<tr valign=top>
<td>
<div align=right><font size=1>cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1>Subject</font></div>
<td><font size=1>[Megaco] Version &nbsp;negotiation in Handoff case</font></table>
<br>
<table width=100%>
<tr valign=top>
<td width=50%>
<td width=50%></table>
<br>
<br></table>
<br>
<br>
<br>
<br>
<br><font size=2>HI All,</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>I will be thankful to you if you can clarify the following
scenario &nbsp;&nbsp;of handoff .</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>MG can support v1 and V2 .</font><font size=3> &nbsp;</font>
<br>
<br><font size=2>MG is currently in a session with Primary MGC and the
&nbsp;negotiated version&nbsp; is V1.</font><font size=3> </font>
<br>
<br><font size=2>Primary MGC sends &nbsp;a handoff to MG.</font><font size=3>
</font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>Then for contacting the secondary MGC which version shall
the MG use in &nbsp;the Service change .</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>With regards</font><font size=3> </font>
<br>
<br><font size=2>Mahesh</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br><font size=2><tt>_______________________________________________</tt></font>
<br><font size=2><tt>Megaco mailing &nbsp;list</tt></font>
<br><font size=2><tt>Megaco@ietf.org</tt></font>
<br><font size=2><tt>https://www1.ietf.org/mailman/listinfo/megaco</tt></font><font size=3>
&nbsp;</font>
<br>
<br>
<br>
<br><font size=2>*********************** &nbsp;&nbsp;HSS-Private &nbsp;
***********************</font><font size=3> &nbsp;</font>
<table width=100%>
<tr valign=top>
<td width=100%>
<br>
<br><font size=3><tt>&quot;Please note:The email domain of Hughes Software
Systems Ltd. has been changed to &quot;hssworld.com&quot; from hss.hns.com&quot;</tt></font>
<br>
<br><font size=3><tt>&quot;DISCLAIMER: This message is proprietary to Hughes
Software Systems Limited (HSS) and is intended </tt></font>
<br><font size=3><tt>solely for the use of the individual to whom it is
addressed. It may contain &nbsp;privileged or </tt></font>
<br><font size=3><tt>confidential information and should not be circulated
or used for any purpose other than for </tt></font>
<br><font size=3><tt>what it is intended. If you have received this message
in error, please notify the originator </tt></font>
<br><font size=3><tt>immediately. If you are not the intended recipient,
you are notified that you are strictly </tt></font>
<br><font size=3><tt>prohibited from using, copying, altering, or disclosing
the contents of this message. HSS </tt></font>
<br><font size=3><tt>accepts no responsibility for loss or damage arising
from the use of the information transmitted </tt></font>
<br><font size=3><tt>by this email including damage from virus.&quot;</tt></font>
<br>
<br></table>
<br>
<br><font size=2 face="sans-serif"><br>
<br>
*********************** &nbsp;HSS-Private &nbsp; ***********************</font>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
</pre></font></td></tr></table>
--=_alternative 0044283665256F49_=--


--===============0960150707==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0960150707==--



From megaco-bounces@ietf.org  Thu Nov 11 08:25:33 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08542
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 08:25:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSEs3-0001KQ-6o; Thu, 11 Nov 2004 08:20:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSEqX-000178-QM
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 08:18:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07703
	for <megaco@ietf.org>; Thu, 11 Nov 2004 08:18:40 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSEri-0001fn-6d
	for megaco@ietf.org; Thu, 11 Nov 2004 08:19:54 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iABDI8805406
	for <megaco@ietf.org>; Thu, 11 Nov 2004 08:18:08 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVCTAL1G>; Thu, 11 Nov 2004 08:18:08 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5369A94FA@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: bvswamy@hssworld.com, Rashim Anand <ranand@ccpu.com>
Subject: RE: [Megaco] Version negotiation in Handoff case
Date: Thu, 11 Nov 2004 08:17:58 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d9238570526f12788af3d33c67f37625
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

ServiceChange messages to any MGC that serve as registration or
re-registration messages MUST be encoded using version 1.  See section 11.3.
Protocol version negotiation then occurs as it would at any other time.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
bvswamy@hssworld.com
Sent: Thursday, November 11, 2004 7:20 AM
To: Rashim Anand
Cc: megaco@ietf.org
Subject: RE: [Megaco] Version negotiation in Handoff case



Hi Rashim 

If MG is doing version negotiation then I suppose MG should send Service
Change with its highest version support.(in your case V2) 


regards 
B. Venkat S.R Swamy 
Hughes Software Systems 
www.hssworld.com 




"Rashim Anand" <ranand@ccpu.com> 


11/11/2004 05:48 PM 



To
B Venkat S.R Swamy/HSS@HSS, "'Mahesh'" <mahesh@ccpu.com> 

cc
<megaco@ietf.org> 

Subject
RE: [Megaco] Version negotiation in Handoff case

	





Hi  Ventak, 
  
I  believe that the question was which version should the MG use to contact
the new  MGC. Should it use the version with which it was communicating with
the old MGC  or should it use the maximum version supported at MG? Ofcourse,
either way there  will be version negotiation with the new MGC. The final
version negotiated with  the new MGC might be V1 or V2 but the doubt is
which version should be used in  sending the srvcChng to the new MGC
(irrespective of the new MGC's subsequent  reply). 
  
Regards, 
-Rashim Anand 
  
  
  
-----Original Message----- 
From:  megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
bvswamy@hssworld.com 
Sent: Thursday, November 11, 2004 3:39  AM 
To: Mahesh 
Cc: megaco@ietf.org 
Subject: Re:  [Megaco] Version negotiation in Handoff case 



Hi 

As per  the protocol specs, Version Negotiation also takes place during
Handoff and  Failover procedures.(Section 11.3) 


Regards 
B. Venkat S.R  Swamy 
Hughes Software Systems   
www.hssworld.com   






"Mahesh"  <mahesh@ccpu.com> 
Sent  by: megaco-bounces@ietf.org   

11/11/2004 03:18 PM 
	


To
<megaco@ietf.org>   

cc

Subject
[Megaco] Version  negotiation in Handoff case

	







HI All, 

  

I will be thankful to you if you can clarify the following scenario   of
handoff . 

  

  

MG can support v1 and V2 .   

MG is currently in a session with Primary MGC and the  negotiated version
is V1. 

Primary MGC sends  a handoff to MG. 

  

Then for contacting the secondary MGC which version shall the MG use in  the
Service change . 

  

With regards 

Mahesh 

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



***********************   HSS-Private   ***********************   


"Please note:The email domain of Hughes Software Systems Ltd. has been
changed to "hssworld.com" from hss.hns.com" 

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain
privileged or 
confidential information and should not be circulated or used for any
purpose other than for 
what it is intended. If you have received this message in error, please
notify the originator 
immediately. If you are not the intended recipient, you are notified that
you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this
message. HSS 
accepts no responsibility for loss or damage arising from the use of the
information transmitted 
by this email including damage from virus." 






***********************  HSS-Private   *********************** 

"Please note:The email domain of Hughes Software Systems Ltd. has been
changed to "hssworld.com" from hss.hns.com"



"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended 

solely for the use of the individual to whom it is addressed. It may contain
privileged or 

confidential information and should not be circulated or used for any
purpose other than for 

what it is intended. If you have received this message in error, please
notify the originator 

immediately. If you are not the intended recipient, you are notified that
you are strictly 

prohibited from using, copying, altering, or disclosing the contents of this
message. HSS 

accepts no responsibility for loss or damage arising from the use of the
information transmitted 

by this email including damage from virus."


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


From megaco-bounces@ietf.org  Thu Nov 11 08:29:36 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08838
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 08:29:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSExf-0002Uf-C7; Thu, 11 Nov 2004 08:26:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSEvC-0001yX-V6
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 08:23:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08400
	for <megaco@ietf.org>; Thu, 11 Nov 2004 08:23:30 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSEwM-0001nE-K4
	for megaco@ietf.org; Thu, 11 Nov 2004 08:24:43 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iABDMvv13147
	for <megaco@ietf.org>; Thu, 11 Nov 2004 08:22:57 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVCTALWH>; Thu, 11 Nov 2004 08:22:57 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5369A950E@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Mahesh <mahesh@ccpu.com>, megaco@ietf.org
Subject: RE: [Megaco] encoding scheme during hand off
Date: Thu, 11 Nov 2004 08:22:54 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

According to spec, MGCs must support both text and binary.  So I don't see
the issue here...
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Mahesh
Sent: Thursday, November 11, 2004 5:12 AM
To: megaco@ietf.org
Subject: [Megaco] encoding scheme during hand off



HI All,

 

How can an MG know the  encoding scheme of the secondary MGC in the case of
hand off .

This is because in the case of hand off , the  address of new  MGC is given
by

Primary MGC. This new MGC may not be pre provisioned  at the MG side .

If the handoff MGC is using the default port , MG can find the encoding
scheme .But if 

Handoff  MGC is not using the default port, HOW can MG know the encoding
scheme of 

new MGC .

 

With regards

Mahesh

 


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


From megaco-bounces@ietf.org  Thu Nov 11 08:42:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10075
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 08:42:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSF5D-0003W1-2z; Thu, 11 Nov 2004 08:33:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSF4C-0003HF-OZ
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 08:32:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09055
	for <megaco@ietf.org>; Thu, 11 Nov 2004 08:32:47 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSF5N-0001yw-CL
	for megaco@ietf.org; Thu, 11 Nov 2004 08:34:01 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iABDWG807407
	for <megaco@ietf.org>; Thu, 11 Nov 2004 08:32:16 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVCTAMZ8>; Thu, 11 Nov 2004 08:32:16 -0500
Message-ID: <B258A372CEA20246A363BB86753DB5369A952E@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Rajeev K R <rajeev@huawei.com>,
        "'Jones, Nevin R (Nevin)'"
	<nrjones@agere.com>, megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure
Date: Thu, 11 Nov 2004 08:32:06 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

I disagree.  I have seen MGC switchovers with zero outage in the field under
6 9's operation from more than one implementation.  It depends upon how
redundancy is accomplished for the implementation.
 
The definition of acceptable downtime is a regulatory matter for the
locality -- generic statements of what is acceptable is misleading and
non-constructive.  Be very careful about making statements like this in an
international forum.  Just because the statement is true for your market,
does not mean it is true worldwide.
 
The statements here pertaining to MGC internal failure seem to be made with
a particular implementation in mind.  I do not believe that it would
necessarily hold true across all implementations.
 
Kevin


  _____  

From: Rajeev K R [mailto:rajeev@huawei.com] 
Sent: Wednesday, November 10, 2004 9:29 PM
To: 'Jones, Nevin R (Nevin)'; Boyle, Kevin [NCRTP:3Z40:EXCH];
megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


Hi,
 
There are some other factors to be considerd here.
 
In a 5 nine reliable network, you simply cannot afford to have an MGC
switchover in normal situations.
Since there are network delays involved, it is almost impossible to switch
over and restore service within 1 minute.
Major factors being failure detection time and MG re-registration time
(including avalanche protection timer).
(You can switch over faster, but that would result in  stray switch overs.)
 
So MGC switch over can be considered only as a disaster recovery method when
you lose the service
of one MGC completely due to physical destruction of the equipment or
network.
In such cases up to 5 minutes is acceptable to restore service. 
(5 nines translate to 5 minutes downtime per year)
 
But in normal running, the MGC should not fail to that extent.
Internal failures of an MGC should be taken care by other mechanisms and
should not result in MGC switchover.
The MGC should have 6 nines availability (or close) by itself, for the total
service availability to be 5 nines.
 
Anyway, wrt H.248, I agree with Kevin that this timing need not be enforced
by protocol.
 
Rajeev
 
 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Jones, Nevin R (Nevin)
Sent: Wednesday, November 10, 2004 10:47 PM
To: Kevin Boyle; megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


Kevin:
 
I agree that Megaco is not particularly specific to rt- services but it does
purport to support VoIP services. If such services are to be "carrier grade"
i.e. 5 nines then this would therefore suggest some need to address the
matter of rapid failover times for MGCs.
 
Regards,

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] 
Sent: Wednesday, November 10, 2004 9:43 AM
To: Jones, Nevin R (Nevin); megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


This is an implementation detail that would depend upon your needs.  Note
that Megaco does not have sole use in the real-time services arena,
therefore it is inappropriate for any timing requirements to be specified as
part of the protocol.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Jones, Nevin R (Nevin)
Sent: Tuesday, November 09, 2004 6:48 PM
To: megaco@ietf.org
Cc: Jones, Nevin R (Nevin)
Subject: [Megaco] MGC/MG Failure



All: 

I am a newbie to the megao list so please forgive me if this question was
asked and answered previously. Is there a stipulation (and better yet,
mechanism) somewhere in the Megaco/H.248 standard for the maximum switching
time from one MGC to another in the case of a handover? I ask this question
with the concern that if real time IP based services are to operate at 5
nines availability, then it would seem that the MGC switchover would have to
be in the 10s of milliseconds.

Thanks! 

Regards 

Nevin Jones 


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


From megaco-bounces@ietf.org  Thu Nov 11 08:51:43 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10901
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 08:51:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSFKx-0006O8-T0; Thu, 11 Nov 2004 08:50:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSFG5-0005To-HN
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 08:45:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10259
	for <megaco@ietf.org>; Thu, 11 Nov 2004 08:45:04 -0500 (EST)
From: bvswamy@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSFH0-0002FS-Hy
	for megaco@ietf.org; Thu, 11 Nov 2004 08:46:18 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iABDfR6p028741
	for <megaco@ietf.org>; Thu, 11 Nov 2004 19:11:28 +0530 (IST)
Received: from webmail.hss.hns.com (webmail.hss.hns.com [192.168.100.50])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iABDfQxX028730;
	Thu, 11 Nov 2004 19:11:26 +0530 (IST)
In-Reply-To: <B258A372CEA20246A363BB86753DB5369A94FA@zrtphxm2>
To: "Kevin Boyle" <kboyle@nortelnetworks.com>
Subject: RE: [Megaco] Version negotiation in Handoff case
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF96E8479C.83E57B25-ON65256F49.0048F63C-65256F49.004B7313@hssworld.com>
Date: Thu, 11 Nov 2004 19:09:18 +0530
X-MIMETrack: S/MIME Sign by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/11/2004 07:14:06 PM,
	Serialize by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/11/2004 07:14:06 PM,
	Serialize complete at 11/11/2004 07:14:06 PM,
	S/MIME Sign failed at 11/11/2004 07:14:06 PM: The cryptographic key was
	not found,
	Serialize by Router on WebMail/HSS(Release 6.5.1|January 21,
	2004) at 11/11/2004 07:09:21 PM,
	Serialize complete at 11/11/2004 07:09:21 PM
X-Spam-Score: 4.2 (++++)
X-Scan-Signature: 559439f19b20fd64c5cd872aef84c6f3
Cc: megaco@ietf.org, Rashim Anand <ranand@ccpu.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1593860225=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multipart message in MIME format.
--===============1593860225==
Content-Type: multipart/alternative;
	boundary="=_alternative 004B71CC65256F49_="

This is a multipart message in MIME format.
--=_alternative 004B71CC65256F49_=
Content-Type: text/plain; charset="US-ASCII"


Hi Kevin

I have been referring to the ServiceChangeVersion field in the Service 
Change message since IMO version negotiation is triggered only if
MG adds ServicechangeVersion field. Yes you are right that in this case 
registration or re-registration will be done by encoding using Version 1.

However if V2 based MG does not want to do version negotiation, then in 
that case MG can send Service Change message for 
registration/re-registration  encoded using Version 2.  Correct me if I am 
wrong..

regards
Venkat





"Kevin Boyle" <kboyle@nortelnetworks.com> 
11/11/2004 06:47 PM


To
B Venkat S.R Swamy/HSS@HSS, Rashim Anand <ranand@ccpu.com>
cc
megaco@ietf.org
Subject
RE: [Megaco] Version negotiation in Handoff case







ServiceChange messages to any MGC that serve as registration or 
re-registration messages MUST be encoded using version 1.  See section 
11.3.  Protocol version negotiation then occurs as it would at any other 
time.
 
Kevin


From: megaco-bounces@ietf.org  [mailto:megaco-bounces@ietf.org] On Behalf 
Of  bvswamy@hssworld.com
Sent: Thursday, November 11, 2004 7:20  AM
To: Rashim Anand
Cc: megaco@ietf.org
Subject:  RE: [Megaco] Version negotiation in Handoff case


Hi Rashim 

If MG is doing version negotiation then I suppose MG  should send Service 
Change with its highest version support.(in your case  V2) 


regards 
B. Venkat S.R Swamy 
Hughes Software Systems 
www.hssworld.com 




"Rashim Anand"  <ranand@ccpu.com>  

11/11/2004 05:48 PM 


To
B Venkat S.R  Swamy/HSS@HSS, "'Mahesh'" <mahesh@ccpu.com> 
cc
<megaco@ietf.org> 
Subject
RE: [Megaco] Version  negotiation in Handoff case








Hi  Ventak, 
  
I  believe that the question was which version should the MG use  to 
contact the new  MGC. Should it use the version with which it was 
communicating with the old MGC  or should it use the maximum version 
supported at MG? Ofcourse, either way there  will be version negotiation 
with the new MGC. The final version negotiated with  the new MGC might be 
V1 or V2 but the doubt is which version should be used in  sending the 
srvcChng to the new MGC (irrespective of the new MGC's subsequent  reply). 

  
Regards, 
-Rashim Anand 
  
  
  
-----Original Message----- 
From:  megaco-bounces@ietf.org  [mailto:megaco-bounces@ietf.org] On Behalf 
Of   bvswamy@hssworld.com 
Sent: Thursday,  November 11, 2004 3:39  AM 
To:  Mahesh 
Cc: megaco@ietf.org 
Subject: Re:  [Megaco] Version negotiation in Handoff  case 



Hi 

As per  the protocol specs, Version  Negotiation also takes place during 
Handoff and  Failover  procedures.(Section 11.3) 


Regards 
B. Venkat S.R   Swamy 
Hughes Software  Systems   
www.hssworld.com   






"Mahesh"   <mahesh@ccpu.com> 
Sent  by:  megaco-bounces@ietf.org   

11/11/2004 03:18 PM 


To
<megaco@ietf.org>   
cc

Subject
[Megaco] Version  negotiation in Handoff  case










HI All, 

  

I will be  thankful to you if you can clarify the following scenario   of 
handoff . 

  

  

MG can support v1 and V2 .    

MG is currently in a session with Primary  MGC and the  negotiated 
version  is V1. 

Primary MGC sends  a handoff to  MG. 

  

Then for contacting the secondary MGC which  version shall the MG use in 
 the Service change . 

  

With regards 

Mahesh 

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



***********************    HSS-Private   ***********************    

"Please note:The email domain  of Hughes Software Systems Ltd. has been 
changed to "hssworld.com" from  hss.hns.com" 

"DISCLAIMER: This  message is proprietary to Hughes Software Systems 
Limited (HSS) and is  intended 
solely for the use of the  individual to whom it is addressed. It may 
contain  privileged or 
confidential information and should not  be circulated or used for any 
purpose other than for 
what it is intended. If you have  received this message in error, please 
notify the originator 
immediately. If you are not the  intended recipient, you are notified that 
you are strictly 
prohibited from using, copying,  altering, or disclosing the contents of 
this message. HSS 
accepts no responsibility for loss or  damage arising from the use of the 
information transmitted 
by this email including damage from  virus." 





***********************  HSS-Private    *********************** 

"Please note:The email domain of Hughes Software Systems Ltd. has been 
changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems 
Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may 
contain  privileged or 
confidential information and should not be circulated or used for any 
purpose other than for 
what it is intended. If you have received this message in error, please 
notify the originator 
immediately. If you are not the intended recipient, you are notified that 
you are strictly 
prohibited from using, copying, altering, or disclosing the contents of 
this message. HSS 
accepts no responsibility for loss or damage arising from the use of the 
information transmitted 
by this email including damage from virus."





***********************  HSS-Restricted   ***********************

"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
--=_alternative 004B71CC65256F49_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Kevin</font>
<br>
<br><font size=2 face="sans-serif">I have been referring to the ServiceChangeVersion
field in the Service Change message since IMO version negotiation is triggered
only if</font>
<br><font size=2 face="sans-serif">MG adds ServicechangeVersion field.
Yes you are right that in this case registration or re-registration will
be done by encoding using Version 1.</font>
<br>
<br><font size=2 face="sans-serif">However if V2 based MG does not want
to do version negotiation, then in that case MG can send Service Change
message for registration/re-registration &nbsp;encoded using Version 2.
&nbsp;Correct me if I am wrong..</font>
<br>
<br><font size=2 face="sans-serif">regards</font>
<br><font size=2 face="sans-serif">Venkat</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Kevin Boyle&quot;
&lt;kboyle@nortelnetworks.com&gt;</b> </font>
<p><font size=1 face="sans-serif">11/11/2004 06:47 PM</font>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">B Venkat S.R Swamy/HSS@HSS,
Rashim Anand &lt;ranand@ccpu.com&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">megaco@ietf.org</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">RE: [Megaco] Version negotiation
in Handoff case</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br>
<br><font size=2>ServiceChange messages&nbsp;to any MGC that serve as registration
or &nbsp;re-registration messages MUST be encoded using version 1.&nbsp;
See section &nbsp;11.3.&nbsp; Protocol version negotiation then occurs
as it would at any other &nbsp;time.</font>
<br><font size=3>&nbsp;</font>
<br><font size=2>Kevin</font>
<br>
<hr>
<br>
<br><font size=2><b>From:</b> megaco-bounces@ietf.org &nbsp;[mailto:megaco-bounces@ietf.org]
<b>On Behalf Of &nbsp;</b>bvswamy@hssworld.com</font>
<br><font size=2><b>Sent:</b> Thursday, November 11, 2004 7:20 &nbsp;AM</font>
<br><font size=2><b>To:</b> Rashim Anand</font>
<br><font size=2><b>Cc:</b> megaco@ietf.org</font>
<br><font size=2><b>Subject:</b> &nbsp;RE: [Megaco] Version negotiation
in Handoff case</font>
<br>
<br>
<br><font size=2>Hi Rashim</font><font size=3> </font>
<br>
<br><font size=2>If MG is doing version negotiation then I suppose MG &nbsp;should
send Service Change with its highest version support.(in your case &nbsp;V2)</font><font size=3>
</font>
<br>
<br>
<br><font size=2>regards</font><font size=3> </font>
<br><font size=2>B. Venkat S.R Swamy</font><font size=3> </font>
<br><font size=2>Hughes Software Systems</font><font size=3> </font>
<br><font size=2>www.hssworld.com</font><font size=3> </font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1><b>&quot;Rashim Anand&quot; &nbsp;&lt;ranand@ccpu.com&gt;</b>
</font><font size=3>&nbsp;</font>
<br>
<br><font size=1>11/11/2004 05:48 PM</font><font size=3> </font>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td width=19%>
<div align=right><font size=1>To</font></div>
<td width=80%><font size=1>B Venkat S.R &nbsp;Swamy/HSS@HSS, &quot;'Mahesh'&quot;
&lt;mahesh@ccpu.com&gt;</font><font size=3> &nbsp;</font>
<tr valign=top>
<td>
<div align=right><font size=1>cc</font></div>
<td><font size=1>&lt;megaco@ietf.org&gt;</font><font size=3> &nbsp;</font>
<tr valign=top>
<td>
<div align=right><font size=1>Subject</font></div>
<td><font size=1>RE: [Megaco] Version &nbsp;negotiation in Handoff case</font></table>
<br>
<table width=100%>
<tr valign=top>
<td width=50%>
<td width=50%></table>
<br>
<br></table>
<br>
<br>
<br>
<br><font size=2>Hi &nbsp;Ventak,</font><font size=3> </font>
<br><font size=3>&nbsp; </font>
<br><font size=2>I &nbsp;believe that the question was which version should
the MG use &nbsp;to contact the new &nbsp;MGC. Should it use the version
with which it was &nbsp;communicating with the old MGC &nbsp;or should
it use the maximum version &nbsp;supported at MG? Ofcourse, either way
there &nbsp;will be version negotiation &nbsp;with the new MGC. The final
version negotiated with &nbsp;the new MGC might be &nbsp;V1 or V2 but the
doubt is which version should be used in &nbsp;sending the &nbsp;srvcChng
to the new MGC (irrespective of the new MGC's subsequent &nbsp;&nbsp;reply).</font><font size=3>
</font>
<br><font size=3>&nbsp; </font>
<br><font size=2>Regards,</font><font size=3> </font>
<br><font size=2>-Rashim Anand</font><font size=3> </font>
<br><font size=3>&nbsp; </font>
<br><font size=3>&nbsp; </font>
<br><font size=3>&nbsp; </font>
<br><font size=2>-----Original Message-----</font><font size=3> &nbsp;</font>
<br><font size=2><b>From:</b> &nbsp;megaco-bounces@ietf.org &nbsp;[mailto:megaco-bounces@ietf.org]
<b>On Behalf Of &nbsp;&nbsp;</b>bvswamy@hssworld.com</font><font size=3>
</font>
<br><font size=2><b>Sent:</b> Thursday, &nbsp;November 11, 2004 3:39 &nbsp;AM</font><font size=3>
</font>
<br><font size=2><b>To:</b> &nbsp;Mahesh</font><font size=3> </font>
<br><font size=2><b>Cc:</b> megaco@ietf.org</font><font size=3> </font>
<br><font size=2><b>Subject:</b> Re: &nbsp;[Megaco] Version negotiation
in Handoff &nbsp;case</font><font size=3> </font>
<br>
<br>
<br>
<br><font size=2>Hi</font><font size=3> &nbsp;</font>
<br>
<br><font size=2>As per &nbsp;the protocol specs, Version &nbsp;Negotiation
also takes place during Handoff and &nbsp;Failover &nbsp;procedures.(Section
11.3)</font><font size=3> </font>
<br>
<br>
<br><font size=2>Regards</font><font size=3> </font>
<br><font size=2>B. Venkat S.R &nbsp;&nbsp;Swamy</font><font size=3> </font>
<br><font size=2>Hughes Software &nbsp;Systems</font><font size=3> &nbsp;
</font>
<br><font size=2>www.hssworld.com</font><font size=3> &nbsp; &nbsp;</font>
<br>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1><b>&quot;Mahesh&quot; &nbsp;&nbsp;&lt;mahesh@ccpu.com&gt;</b>
</font>
<br><font size=1>Sent &nbsp;by: &nbsp;megaco-bounces@ietf.org</font><font size=3>
&nbsp; </font>
<br>
<br><font size=1>11/11/2004 03:18 PM</font><font size=3> </font>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td width=13%>
<div align=right><font size=1>To</font></div>
<td width=86%><font size=1>&lt;megaco@ietf.org&gt;</font><font size=3>
&nbsp; &nbsp;</font>
<tr valign=top>
<td>
<div align=right><font size=1>cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1>Subject</font></div>
<td><font size=1>[Megaco] Version &nbsp;negotiation in Handoff &nbsp;case</font></table>
<br>
<table width=100%>
<tr valign=top>
<td width=50%>
<td width=50%></table>
<br>
<br>
<br></table>
<br>
<br>
<br>
<br>
<br><font size=2>HI All,</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>I will be &nbsp;thankful to you if you can clarify the
following scenario &nbsp;&nbsp;of &nbsp;handoff .</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> &nbsp;</font>
<br>
<br><font size=2>MG can support v1 and V2 .</font><font size=3> &nbsp;&nbsp;
</font>
<br>
<br><font size=2>MG is currently in a session with Primary &nbsp;MGC and
the &nbsp;negotiated version&nbsp; is V1.</font><font size=3> &nbsp;</font>
<br>
<br><font size=2>Primary MGC sends &nbsp;a handoff to &nbsp;MG.</font><font size=3>
</font>
<br>
<br><font size=2>&nbsp;</font><font size=3> &nbsp;</font>
<br>
<br><font size=2>Then for contacting the secondary MGC which &nbsp;version
shall the MG use in &nbsp;the Service change .</font><font size=3> &nbsp;</font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br>
<br><font size=2>With regards</font><font size=3> </font>
<br>
<br><font size=2>Mahesh</font><font size=3> </font>
<br>
<br><font size=2>&nbsp;</font><font size=3> </font>
<br><font size=2><tt>_______________________________________________</tt></font><font size=3>
&nbsp;</font>
<br><font size=2><tt>Megaco mailing &nbsp;list</tt></font><font size=3>
</font>
<br><font size=2><tt>Megaco@ietf.org</tt></font><font size=3> </font>
<br><font size=2><tt>https://www1.ietf.org/mailman/listinfo/megaco</tt></font><font size=3>
&nbsp; </font>
<br>
<br>
<br>
<br><font size=2>*********************** &nbsp;&nbsp;&nbsp;HSS-Private
&nbsp; ***********************</font><font size=3> &nbsp;&nbsp; &nbsp;</font>
<table width=100%>
<tr valign=top>
<td width=100%>
<br><font size=3><tt>&quot;Please note:The email domain &nbsp;of Hughes
Software Systems Ltd. has been changed to &quot;hssworld.com&quot; from
&nbsp;hss.hns.com&quot;</tt></font><font size=3> </font>
<br>
<br><font size=3><tt>&quot;DISCLAIMER: This &nbsp;message is proprietary
to Hughes Software Systems Limited (HSS) and is &nbsp;intended </tt></font>
<br><font size=3><tt>solely for the use of the &nbsp;individual to whom
it is addressed. It may contain &nbsp;privileged or &nbsp;</tt></font>
<br><font size=3><tt>confidential information and should not &nbsp;be circulated
or used for any purpose other than for &nbsp;</tt></font>
<br><font size=3><tt>what it is intended. If you have &nbsp;received this
message in error, please notify the originator &nbsp;</tt></font>
<br><font size=3><tt>immediately. If you are not the &nbsp;intended recipient,
you are notified that you are strictly &nbsp;</tt></font>
<br><font size=3><tt>prohibited from using, copying, &nbsp;altering, or
disclosing the contents of this message. HSS &nbsp;</tt></font>
<br><font size=3><tt>accepts no responsibility for loss or &nbsp;damage
arising from the use of the information transmitted &nbsp;</tt></font>
<br><font size=3><tt>by this email including damage from &nbsp;virus.&quot;</tt></font><font size=3>
</font>
<br>
<br></table>
<br>
<br>
<br>
<br><font size=2>*********************** &nbsp;HSS-Private &nbsp; &nbsp;***********************</font><font size=3>
&nbsp;</font>
<table width=100%>
<tr valign=top>
<td width=100%>
<br><font size=3><tt>&quot;Please note:The email domain of Hughes Software
Systems Ltd. has been changed to &quot;hssworld.com&quot; from hss.hns.com&quot;</tt></font>
<br>
<br><font size=3><tt>&quot;DISCLAIMER: This message is proprietary to Hughes
Software Systems Limited (HSS) and is intended </tt></font>
<br><font size=3><tt>solely for the use of the individual to whom it is
addressed. It may contain &nbsp;privileged or </tt></font>
<br><font size=3><tt>confidential information and should not be circulated
or used for any purpose other than for </tt></font>
<br><font size=3><tt>what it is intended. If you have received this message
in error, please notify the originator </tt></font>
<br><font size=3><tt>immediately. If you are not the intended recipient,
you are notified that you are strictly </tt></font>
<br><font size=3><tt>prohibited from using, copying, altering, or disclosing
the contents of this message. HSS </tt></font>
<br><font size=3><tt>accepts no responsibility for loss or damage arising
from the use of the information transmitted </tt></font>
<br><font size=3><tt>by this email including damage from virus.&quot;</tt></font>
<br>
<br></table>
<br>
<br><font size=2 face="sans-serif"><br>
<br>
*********************** &nbsp;HSS-Restricted &nbsp; ***********************</font>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
</pre></font></td></tr></table>
--=_alternative 004B71CC65256F49_=--


--===============1593860225==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1593860225==--



From megaco-bounces@ietf.org  Thu Nov 11 18:02:30 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09849
	for <megaco-archive@lists.ietf.org>; Thu, 11 Nov 2004 18:02:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSNk6-0001yJ-Gw; Thu, 11 Nov 2004 17:48:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSNhQ-0000kI-CS
	for megaco@megatron.ietf.org; Thu, 11 Nov 2004 17:45:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08281
	for <megaco@ietf.org>; Thu, 11 Nov 2004 17:45:50 -0500 (EST)
Received: from penguin.ericsson.se ([193.180.251.47])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSNiP-0007sj-AL
	for megaco@ietf.org; Thu, 11 Nov 2004 17:47:10 -0500
Received: from esealmw141.al.sw.ericsson.se ([153.88.254.120])
	by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iABMjTh5013588
	for <megaco@ietf.org>; Thu, 11 Nov 2004 23:45:30 +0100 (MET)
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by
	esealmw141.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 11 Nov 2004 23:45:29 +0100
Received: from eaubrnt019.epa.ericsson.se ([146.11.9.165]) by
	esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WFZ27K7N; Thu, 11 Nov 2004 23:45:29 +0100
Received: from ericsson.com (EG2E500202DSEGL [146.11.22.27]) by
	eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WTM8RF72; Fri, 12 Nov 2004 09:45:25 +1100
Message-ID: <4193EC64.2040307@ericsson.com>
Date: Fri, 12 Nov 2004 09:49:08 +1100
X-Sybari-Trust: 73bc6633 ad48f3dd a486cbd5 00000179
From: Christian Groves <christian.groves@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: bvswamy@hssworld.com
Subject: Re: [Megaco] Version negotiation in Handoff case
References: <OF96E8479C.83E57B25-ON65256F49.0048F63C-65256F49.004B7313@hssworld.com>
In-Reply-To: <OF96E8479C.83E57B25-ON65256F49.0048F63C-65256F49.004B7313@hssworld.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Nov 2004 22:45:29.0904 (UTC)
	FILETIME=[25187B00:01C4C840]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 83e9494d829b08cc3f644ef6ac1b9bd4
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org, Rashim Anand <ranand@ccpu.com>,
        Kevin Boyle <kboyle@nortelnetworks.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hello Venkat,

The MG can always send "v2" but it runs the risk of being rejected. The MGC may 
have restarted and is expecting v1 messages. Safer to send a v1 message and 
ServiceChangeVersion with 2.

bvswamy@hssworld.com wrote:
> 
> Hi Kevin
> 
> I have been referring to the ServiceChangeVersion field in the Service 
> Change message since IMO version negotiation is triggered only if
> MG adds ServicechangeVersion field. Yes you are right that in this case 
> registration or re-registration will be done by encoding using Version 1.
> 
> However if V2 based MG does not want to do version negotiation, then in 
> that case MG can send Service Change message for 
> registration/re-registration  encoded using Version 2.  Correct me if I 
> am wrong..
> 
> regards
> Venkat
> 
> 
> 
> 
> "Kevin Boyle" <kboyle@nortelnetworks.com>
> 
> 11/11/2004 06:47 PM
> 
> 	
> To
> 	B Venkat S.R Swamy/HSS@HSS, Rashim Anand <ranand@ccpu.com>
> cc
> 	megaco@ietf.org
> Subject
> 	RE: [Megaco] Version negotiation in Handoff case
> 
> 
> 	
> 
> 
> 
> 
> 
> 
> ServiceChange messages to any MGC that serve as registration or 
>  re-registration messages MUST be encoded using version 1.  See section 
>  11.3.  Protocol version negotiation then occurs as it would at any 
> other  time.
>  
> Kevin
> ------------------------------------------------------------------------
> 
> 
> From: megaco-bounces@ietf.org  [mailto:megaco-bounces@ietf.org] On 
> Behalf Of  bvswamy@hssworld.com
> Sent: Thursday, November 11, 2004 7:20  AM
> To: Rashim Anand
> Cc: megaco@ietf.org
> Subject:  RE: [Megaco] Version negotiation in Handoff case
> 
> 
> Hi Rashim
> 
> If MG is doing version negotiation then I suppose MG  should send 
> Service Change with its highest version support.(in your case  V2)
> 
> 
> regards
> B. Venkat S.R Swamy
> Hughes Software Systems
> www.hssworld.com
> 
> 
> 
> "Rashim Anand"  <ranand@ccpu.com>  
> 
> 11/11/2004 05:48 PM
> 	
> To
> 	B Venkat S.R  Swamy/HSS@HSS, "'Mahesh'" <mahesh@ccpu.com>  
> cc
> 	<megaco@ietf.org>  
> Subject
> 	RE: [Megaco] Version  negotiation in Handoff case
> 
> 
> 	
> 
> 
> 
> 
> 
> 
> 
> Hi  Ventak,
>  
> I  believe that the question was which version should the MG use  to 
> contact the new  MGC. Should it use the version with which it was 
>  communicating with the old MGC  or should it use the maximum version 
>  supported at MG? Ofcourse, either way there  will be version 
> negotiation  with the new MGC. The final version negotiated with  the 
> new MGC might be  V1 or V2 but the doubt is which version should be used 
> in  sending the  srvcChng to the new MGC (irrespective of the new MGC's 
> subsequent   reply).
>  
> Regards,
> -Rashim Anand
>  
>  
>  
> -----Original Message-----  
> From:  megaco-bounces@ietf.org  [mailto:megaco-bounces@ietf.org] On 
> Behalf Of   bvswamy@hssworld.com
> Sent: Thursday,  November 11, 2004 3:39  AM
> To:  Mahesh
> Cc: megaco@ietf.org
> Subject: Re:  [Megaco] Version negotiation in Handoff  case
> 
> 
> 
> Hi  
> 
> As per  the protocol specs, Version  Negotiation also takes place during 
> Handoff and  Failover  procedures.(Section 11.3)
> 
> 
> Regards
> B. Venkat S.R   Swamy
> Hughes Software  Systems  
> www.hssworld.com    
> 
> 
> 
> 
> 
> "Mahesh"   <mahesh@ccpu.com>
> Sent  by:  megaco-bounces@ietf.org  
> 
> 11/11/2004 03:18 PM
> 	
> To
> 	<megaco@ietf.org>    
> cc
> 	
> Subject
> 	[Megaco] Version  negotiation in Handoff  case
> 
> 
> 	
> 
> 
> 
> 
> 
> 
> 
> 
> 
> HI All,
> 
>  
> 
> I will be  thankful to you if you can clarify the following scenario 
>   of  handoff .
> 
>  
> 
>    
> 
> MG can support v1 and V2 .   
> 
> MG is currently in a session with Primary  MGC and the  negotiated 
> version  is V1.  
> 
> Primary MGC sends  a handoff to  MG.
> 
>    
> 
> Then for contacting the secondary MGC which  version shall the MG use in 
>  the Service change .  
> 
>  
> 
> With regards
> 
> Mahesh
> 
>  
> _______________________________________________  
> Megaco mailing  list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco  
> 
> 
> 
> ***********************    HSS-Private   ***********************     
> 
> "Please note:The email domain  of Hughes Software Systems Ltd. has been 
> changed to "hssworld.com" from  hss.hns.com"
> 
> "DISCLAIMER: This  message is proprietary to Hughes Software Systems 
> Limited (HSS) and is  intended
> solely for the use of the  individual to whom it is addressed. It may 
> contain  privileged or  
> confidential information and should not  be circulated or used for any 
> purpose other than for  
> what it is intended. If you have  received this message in error, please 
> notify the originator  
> immediately. If you are not the  intended recipient, you are notified 
> that you are strictly  
> prohibited from using, copying,  altering, or disclosing the contents of 
> this message. HSS  
> accepts no responsibility for loss or  damage arising from the use of 
> the information transmitted  
> by this email including damage from  virus."
> 
> 
> 
> 
> 
> ***********************  HSS-Private    ***********************  
> 
> "Please note:The email domain of Hughes Software Systems Ltd. has been 
> changed to "hssworld.com" from hss.hns.com"
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systems 
> Limited (HSS) and is intended
> solely for the use of the individual to whom it is addressed. It may 
> contain  privileged or
> confidential information and should not be circulated or used for any 
> purpose other than for
> what it is intended. If you have received this message in error, please 
> notify the originator
> immediately. If you are not the intended recipient, you are notified 
> that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of 
> this message. HSS
> accepts no responsibility for loss or damage arising from the use of the 
> information transmitted
> by this email including damage from virus."
> 
> 
> 
> 
> 
> ***********************  HSS-Restricted   ***********************
> 
> "Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
> solely for the use of the individual to whom it is addressed. It may contain  privileged or 
> confidential information and should not be circulated or used for any purpose other than for 
> what it is intended. If you have received this message in error, please notify the originator 
> immediately. If you are not the intended recipient, you are notified that you are strictly 
> prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
> accepts no responsibility for loss or damage arising from the use of the information transmitted 
> by this email including damage from virus."
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco


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


From megaco-bounces@ietf.org  Fri Nov 12 02:48:45 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07771
	for <megaco-archive@lists.ietf.org>; Fri, 12 Nov 2004 02:48:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSW7G-0002KE-7W; Fri, 12 Nov 2004 02:45:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSW28-0001WQ-81
	for megaco@megatron.ietf.org; Fri, 12 Nov 2004 02:39:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07185
	for <megaco@ietf.org>; Fri, 12 Nov 2004 02:39:46 -0500 (EST)
Received: from [61.144.161.55] (helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSVz0-0001MM-T9
	for megaco@ietf.org; Fri, 12 Nov 2004 02:41:10 -0500
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0I7200I1O1PB13@szxga03-in.huawei.com> for
	megaco@ietf.org; Fri, 12 Nov 2004 15:19:59 +0800 (CST)
Received: from szxml02-in ([172.24.1.6])
	by szxga03-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTP id	<0I7200FVB1PBQX@szxga03-in.huawei.com>
	formegaco@ietf.org; Fri, 12 Nov 2004 15:19:59 +0800 (CST)
Received: from r70036a ([10.78.228.159])
	by szxml02-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTPA id	<0I7200LO31Q9YP@szxml02-in.huawei.com>; Fri,
	12 Nov 2004 15:20:34 +0800 (CST)
Date: Fri, 12 Nov 2004 15:24:20 +0800
From: Rajeev K R <rajeev@huawei.com>
Subject: RE: [Megaco] MGC/MG Failure
In-reply-to: <B258A372CEA20246A363BB86753DB5369A952E@zrtphxm2>
To: "'Kevin Boyle'" <kboyle@nortelnetworks.com>,
        "'Jones, Nevin R (Nevin)'" <nrjones@agere.com>, megaco@ietf.org
Message-id: <005b01c4c888$a094cbb0$9fe44e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 21f6736b171db90b7af90d77f0c0e285
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2109046957=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2109046957==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_VamrElqH4AOj9hWMQmLpfg)"

This is a multi-part message in MIME format.

--Boundary_(ID_VamrElqH4AOj9hWMQmLpfg)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

Hi Kevin,
I agree. The service levels are different between markets and cannot be
generalised.
So I would refrain from making statements pertaining to this.
 
But I have some questions about MGC switchover with zero outage.
Wouldn't this require switchover within milliseconds as mentioned in the
original question ?
Or is it within seconds ?(because  6 nines translate approx to down time <
30 sec/year)
 
What methods can be adopted to remove MG re-registration delay ?
Inactivity timer package delay, normalMGCexecution time, retransmission
time, no. of retries etc all gets added up here.
Because of the network delay, there is a risk in keeping these timers to the
possible minimum value.
 
Is it possible for the secondary(newly active) MGC to force the MG to
re-register to it ? 
(instead of waiting for the MG to find out by itself and initiate
re-registration)
This would be something like handoff request from secondary MGC. Does the
protocol permit this?
Assuming that MGCs have sufficient mechanism to detect failure and initiate
switchover very fast, 
this would be desirable to minimise the service outage time.
 
Rajeev
 
 

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] 
Sent: Thursday, November 11, 2004 9:32 PM
To: Rajeev K R; 'Jones, Nevin R (Nevin)'; megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


I disagree.  I have seen MGC switchovers with zero outage in the field under
6 9's operation from more than one implementation.  It depends upon how
redundancy is accomplished for the implementation.
 
The definition of acceptable downtime is a regulatory matter for the
locality -- generic statements of what is acceptable is misleading and
non-constructive.  Be very careful about making statements like this in an
international forum.  Just because the statement is true for your market,
does not mean it is true worldwide.
 
The statements here pertaining to MGC internal failure seem to be made with
a particular implementation in mind.  I do not believe that it would
necessarily hold true across all implementations.
 
Kevin


  _____  

From: Rajeev K R [mailto:rajeev@huawei.com] 
Sent: Wednesday, November 10, 2004 9:29 PM
To: 'Jones, Nevin R (Nevin)'; Boyle, Kevin [NCRTP:3Z40:EXCH];
megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


Hi,
 
There are some other factors to be considerd here.
 
In a 5 nine reliable network, you simply cannot afford to have an MGC
switchover in normal situations.
Since there are network delays involved, it is almost impossible to switch
over and restore service within 1 minute.
Major factors being failure detection time and MG re-registration time
(including avalanche protection timer).
(You can switch over faster, but that would result in  stray switch overs.)
 
So MGC switch over can be considered only as a disaster recovery method when
you lose the service
of one MGC completely due to physical destruction of the equipment or
network.
In such cases up to 5 minutes is acceptable to restore service. 
(5 nines translate to 5 minutes downtime per year)
 
But in normal running, the MGC should not fail to that extent.
Internal failures of an MGC should be taken care by other mechanisms and
should not result in MGC switchover.
The MGC should have 6 nines availability (or close) by itself, for the total
service availability to be 5 nines.
 
Anyway, wrt H.248, I agree with Kevin that this timing need not be enforced
by protocol.
 
Rajeev
 
 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Jones, Nevin R (Nevin)
Sent: Wednesday, November 10, 2004 10:47 PM
To: Kevin Boyle; megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


Kevin:
 
I agree that Megaco is not particularly specific to rt- services but it does
purport to support VoIP services. If such services are to be "carrier grade"
i.e. 5 nines then this would therefore suggest some need to address the
matter of rapid failover times for MGCs.
 
Regards,

-----Original Message-----
From: Kevin Boyle [mailto:kboyle@nortelnetworks.com] 
Sent: Wednesday, November 10, 2004 9:43 AM
To: Jones, Nevin R (Nevin); megaco@ietf.org
Subject: RE: [Megaco] MGC/MG Failure


This is an implementation detail that would depend upon your needs.  Note
that Megaco does not have sole use in the real-time services arena,
therefore it is inappropriate for any timing requirements to be specified as
part of the protocol.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Jones, Nevin R (Nevin)
Sent: Tuesday, November 09, 2004 6:48 PM
To: megaco@ietf.org
Cc: Jones, Nevin R (Nevin)
Subject: [Megaco] MGC/MG Failure



All: 

I am a newbie to the megao list so please forgive me if this question was
asked and answered previously. Is there a stipulation (and better yet,
mechanism) somewhere in the Megaco/H.248 standard for the maximum switching
time from one MGC to another in the case of a handover? I ask this question
with the concern that if real time IP based services are to operate at 5
nines availability, then it would seem that the MGC switchover would have to
be in the 10s of milliseconds.

Thanks! 

Regards 

Nevin Jones 


--Boundary_(ID_VamrElqH4AOj9hWMQmLpfg)
Content-type: text/html; charset=us-ascii
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=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2>Hi 
Kevin,</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2>I 
agree. The service levels&nbsp;are different&nbsp;between markets and cannot be 
generalised.</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2>So I 
would refrain from making statements&nbsp;pertaining to 
this.</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004></SPAN><SPAN class=734362403-12112004><FONT 
face=Arial color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff 
size=2>But&nbsp;I have some questions about MGC switchover with zero 
outage.</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff 
size=2>Wouldn't&nbsp;this require switchover within milliseconds as mentioned in 
the original question ?</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2>Or is 
it within seconds ?(because &nbsp;6 nines translate approx to&nbsp;down time 
&lt; 30 sec/year)</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2>What 
methods can be adopted to remove MG re-registration delay ?</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=734362403-12112004><FONT face=Arial color=#0000ff size=2>Inactivity timer 
package delay, normalMGCexecution time, retransmission time, no. of 
retries&nbsp;etc all gets added up here.</FONT></SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=734362403-12112004>Because of the network delay, there is a risk in 
keeping these timers to the possible minimum value.</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=734362403-12112004></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2>Is it 
possible for the secondary(newly active)&nbsp;MGC to force the MG to re-register 
to it ? </FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff 
size=2>(instead of waiting for the MG to find out by itself and initiate 
re-registration)</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2>This 
would be something like handoff request from secondary MGC. </FONT></SPAN><SPAN 
class=734362403-12112004><FONT face=Arial color=#0000ff size=2>Does the protocol 
permit this?</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff 
size=2>Assuming that MGCs have sufficient mechanism to detect failure and 
initiate switchover very fast, </FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff size=2>this 
would be desirable to minimise </FONT></SPAN><SPAN 
class=734362403-12112004><FONT face=Arial color=#0000ff size=2>the 
service&nbsp;outage time.</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff 
size=2>Rajeev</FONT></SPAN></DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=734362403-12112004><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Kevin Boyle 
  [mailto:kboyle@nortelnetworks.com] <BR><B>Sent:</B> Thursday, November 11, 
  2004 9:32 PM<BR><B>To:</B> Rajeev K R; 'Jones, Nevin R (Nevin)'; 
  megaco@ietf.org<BR><B>Subject:</B> RE: [Megaco] MGC/MG 
  Failure<BR><BR></FONT></DIV>
  <DIV dir=ltr align=left><SPAN class=032202313-11112004><FONT face=Arial 
  size=2>I disagree.&nbsp; I have seen MGC switchovers with zero outage in the 
  field under 6 9's operation from more than one implementation.&nbsp; It 
  depends upon how redundancy is accomplished for the 
  implementation.</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=032202313-11112004><FONT face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=032202313-11112004><FONT face=Arial 
  size=2>The definition of acceptable downtime is a regulatory matter for the 
  locality -- generic statements of what is acceptable is misleading and 
  non-constructive.&nbsp; Be very careful about making statements like this in 
  an international forum.&nbsp; Just because the statement is true for your 
  market, does not mean it is true worldwide.</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=032202313-11112004><FONT face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=032202313-11112004><FONT face=Arial 
  size=2>The statements here pertaining to MGC internal failure seem to be made 
  with a particular implementation in mind.&nbsp; I do not believe that it would 
  necessarily hold true across all implementations.</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=032202313-11112004><FONT face=Arial 
  size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=032202313-11112004><FONT face=Arial 
  size=2>Kevin</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
    <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
    <HR tabIndex=-1>
    <FONT face=Tahoma size=2><B>From:</B> Rajeev K R [mailto:rajeev@huawei.com] 
    <BR><B>Sent:</B> Wednesday, November 10, 2004 9:29 PM<BR><B>To:</B> 'Jones, 
    Nevin R (Nevin)'; Boyle, Kevin [NCRTP:3Z40:EXCH]; 
    megaco@ietf.org<BR><B>Subject:</B> RE: [Megaco] MGC/MG 
    Failure<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>Hi,</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>There are some other factors to be considerd 
here.</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>In 
    a&nbsp;5 nine&nbsp;reliable network, you simply cannot afford to have an MGC 
    switchover in normal situations.</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>Since there are network delays involved, it is almost impossible to 
    switch over and restore service within 1 minute.</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>Major factors being failure detection time and&nbsp;MG 
    re-registration time (including avalanche&nbsp;protection 
    timer).</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>(<SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>You can switch over faster, but that would result in &nbsp;stray 
    switch overs.)</FONT></SPAN></FONT></SPAN></FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2><SPAN 
    class=140000502-11112004></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2><SPAN class=140000502-11112004></SPAN></FONT></SPAN>So MGC switch 
    over&nbsp;can be considered only as a disaster recovery method when you lose 
    the service</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>of 
    one MGC</FONT></SPAN><SPAN class=140000502-11112004>&nbsp;<FONT 
    face=Arial><FONT color=#0000ff size=2>completely due to physical destruction 
    of the equipment or network.</FONT></FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial><FONT color=#0000ff 
    size=2>In such cases up to 5 minutes is acceptable 
    </FONT></FONT></SPAN><SPAN class=140000502-11112004><FONT face=Arial 
    color=#0000ff size=2>to restore service. </FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff size=2>(5 
    nines&nbsp;translate to 5 minutes downtime per year)</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>But in normal running, the MGC should&nbsp;not fail to that 
    extent.</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>Internal failures of an MGC should be taken care by other mechanisms 
    and should not result in MGC switchover.</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>The MGC&nbsp;should have&nbsp;6 nines availability (or close)&nbsp;by 
    itself,&nbsp;for the total service availability&nbsp;to be&nbsp;5 
    nines.</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>Anyway, wrt H.248, I agree with Kevin that this timing need not be 
    enforced by protocol.</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2>Rajeev</FONT></SPAN></DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=140000502-11112004><FONT face=Arial color=#0000ff 
    size=2></FONT></SPAN>&nbsp;</DIV>
    <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
      <DIV></DIV>
      <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
      face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
      megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] <B>On Behalf Of 
      </B>Jones, Nevin R (Nevin)<BR><B>Sent:</B> Wednesday, November 10, 2004 
      10:47 PM<BR><B>To:</B> Kevin Boyle; megaco@ietf.org<BR><B>Subject:</B> RE: 
      [Megaco] MGC/MG Failure<BR><BR></FONT></DIV>
      <DIV><SPAN class=244384414-10112004><FONT face="Comic Sans MS" 
      color=#0000ff size=2>Kevin:</FONT></SPAN></DIV>
      <DIV><SPAN class=244384414-10112004><FONT face="Comic Sans MS" 
      color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
      <DIV><SPAN class=244384414-10112004><FONT face="Comic Sans MS" 
      color=#0000ff size=2>I agree that Megaco is not particularly specific to 
      rt- services but it does purport to support VoIP services. If such 
      services are to be "carrier grade" i.e. 5 nines then this&nbsp;would 
      therefore suggest some need to address the matter of rapid failover times 
      for MGCs.</FONT></SPAN></DIV>
      <DIV><SPAN class=244384414-10112004><FONT face="Comic Sans MS" 
      color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
      <DIV><SPAN class=244384414-10112004><FONT face="Comic Sans MS" 
      color=#0000ff size=2>Regards,</FONT></SPAN></DIV>
      <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
        <DIV></DIV>
        <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
        face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Kevin 
        Boyle [mailto:kboyle@nortelnetworks.com] <BR><B>Sent:</B> Wednesday, 
        November 10, 2004 9:43 AM<BR><B>To:</B> Jones, Nevin R (Nevin); 
        megaco@ietf.org<BR><B>Subject:</B> RE: [Megaco] MGC/MG 
        Failure<BR><BR></FONT></DIV>
        <DIV dir=ltr align=left><FONT face=Arial size=2><SPAN 
        class=784274114-10112004>This is an implementation detail that would 
        depend upon your needs.&nbsp; Note that Megaco does not have sole use in 
        the real-time services arena, therefore it is inappropriate for any 
        timing requirements to be specified as part of the 
        protocol.</SPAN></FONT></DIV>
        <DIV dir=ltr align=left><FONT face=Arial size=2><SPAN 
        class=784274114-10112004></SPAN></FONT>&nbsp;</DIV>
        <DIV dir=ltr align=left><FONT face=Arial size=2><SPAN 
        class=784274114-10112004>Kevin</SPAN></FONT></DIV><BR>
        <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
          <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
          <HR tabIndex=-1>
          <FONT face=Tahoma size=2><B>From:</B> megaco-bounces@ietf.org 
          [mailto:megaco-bounces@ietf.org] <B>On Behalf Of </B>Jones, Nevin R 
          (Nevin)<BR><B>Sent:</B> Tuesday, November 09, 2004 6:48 
          PM<BR><B>To:</B> megaco@ietf.org<BR><B>Cc:</B> Jones, Nevin R 
          (Nevin)<BR><B>Subject:</B> [Megaco] MGC/MG 
Failure<BR></FONT><BR></DIV>
          <DIV></DIV><!-- Converted from text/rtf format -->
          <P><FONT face="Comic Sans MS" size=2>All:</FONT> </P>
          <P><FONT face="Comic Sans MS" size=2>I am a newbie to the megao list 
          so please forgive me if this question was asked and answered 
          previously. Is there a stipulation (and better yet, mechanism) 
          somewhere in the Megaco/H.248 standard for the maximum switching time 
          from one MGC to another in the case of a handover? I ask this question 
          with the concern that if real time IP based services are to operate at 
          5 nines availability, then it would seem that the MGC switchover would 
          have to be in the 10s of milliseconds.</FONT></P>
          <P><FONT face="Comic Sans MS" size=2>Thanks!</FONT> </P>
          <P><FONT face="Comic Sans MS" size=2>Regards</FONT> </P>
          <P><FONT face="Comic Sans MS">Nevin Jones<B></B></FONT> 
      </P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_VamrElqH4AOj9hWMQmLpfg)--


--===============2109046957==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============2109046957==--



From megaco-bounces@ietf.org  Fri Nov 12 03:42:46 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10477
	for <megaco-archive@lists.ietf.org>; Fri, 12 Nov 2004 03:42:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSWyh-0001dI-I5; Fri, 12 Nov 2004 03:40:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSWvX-00019L-0L
	for megaco@megatron.ietf.org; Fri, 12 Nov 2004 03:37:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10063
	for <megaco@ietf.org>; Fri, 12 Nov 2004 03:36:57 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSWwc-0002LF-WD
	for megaco@ietf.org; Fri, 12 Nov 2004 03:38:23 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id BCC493468F8
	for <megaco@ietf.org>; Fri, 12 Nov 2004 00:35:54 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 28532-00BA0087;
	Fri, 12 Nov 2004 00:35:02 -0800
Received: from ccpu00179 (unknown [172.25.0.135])
	by smtp.ccpu.com (Postfix) with SMTP id 705663468F7
	for <megaco@ietf.org>; Fri, 12 Nov 2004 00:34:15 -0800 (PST)
Message-ID: <00a101c4c903$f6793540$870019ac@ccpu00179>
From: "Geetha" <geetha@ccpu.com>
To: <megaco@ietf.org>
Subject: r: [Megaco] ToneID conflicts
Date: Fri, 12 Nov 2004 14:07:00 -0800
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4942.400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4942.400
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.68; host: smtp)
X-Spam-Score: 2.8 (++)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1584419724=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1584419724==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_009C_01C4C8C0.E10DCAB0"

This is a multi-part message in MIME format.

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

Hi,

1. The Value of Tone Id defined in Multi Frequency Tone generator "mfh" =
- mf signal code ST''' is given as 0x61 in the spec H.248.24(07/2003). =
This is conflicting with the value of Tone Id  "enter" - Conference =
entrance tone in the spec in H.2489.27(07/2003).
What should be the value of the Tone Id "mfh"?

Also I have one more query which I have already posted in the mailing =
list.=20

2.In RTCP XR Base Package defined in H.248.30(03/2004) the statisticsID =
are from 1 to 12. The IDs 4 to 8 of that coincides with the statisticsID =
of the base pkg, rtp version1.
Also R Factor and External R Factor have ths same strings 'ns'

Any help in this regard will be much appreciated.

Anticipating reply,
Geetha

------=_NextPart_000_009C_01C4C8C0.E10DCAB0
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.3819.300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>1. </FONT><FONT face=3DArial =
size=3D2>The Value of Tone=20
Id defined in Multi Frequency Tone generator "mfh" - mf signal code =
ST''' is=20
given as 0x61 in the spec H.248.24(07/2003). This is conflicting with =
the value=20
of Tone Id&nbsp; "enter" - Conference entrance tone in the spec in=20
H.2489.27(07/2003).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>What should be the value of the Tone Id =

"mfh"?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Also I have&nbsp;one more query which I =
have=20
already posted in the mailing list. </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>2.<FONT face=3DArial size=3D2>In RTCP =
XR Base Package=20
defined in H.248.30(03/2004) the statisticsID are from 1 to 12.&nbsp;The =
IDs 4=20
to 8 of that coincides with the statisticsID of the base pkg, rtp=20
version1.</FONT>
<DIV><FONT face=3DArial size=3D2>Also R Factor and External R Factor =
have ths same=20
strings 'ns'</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>Any help in this regard will be much appreciated.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Anticipating reply,</DIV>
<DIV>Geetha</FONT><FONT face=3DArial size=3D2><FONT face=3DTimesNewRoman =

size=3D3></DIV></DIV></FONT></FONT></BODY></HTML>

------=_NextPart_000_009C_01C4C8C0.E10DCAB0--



--===============1584419724==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1584419724==--




From megaco-bounces@ietf.org  Fri Nov 12 12:38:51 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23758
	for <megaco-archive@lists.ietf.org>; Fri, 12 Nov 2004 12:38:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CSfBz-0004kj-SD; Fri, 12 Nov 2004 12:26:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CSf4A-00033d-6N
	for megaco@megatron.ietf.org; Fri, 12 Nov 2004 12:18:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21369
	for <megaco@ietf.org>; Fri, 12 Nov 2004 12:18:27 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSf5Z-00059s-Ky
	for megaco@ietf.org; Fri, 12 Nov 2004 12:19:58 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iACHHrI21350
	for <megaco@ietf.org>; Fri, 12 Nov 2004 12:17:53 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVCTHSJ7>; Fri, 12 Nov 2004 12:17:48 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536A22DE3@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Geetha <geetha@ccpu.com>, megaco@ietf.org
Subject: RE: [Megaco] ToneID conflicts
Date: Fri, 12 Nov 2004 12:17:28 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Comments inline. [KJBII]
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Geetha
Sent: Friday, November 12, 2004 5:07 PM
To: megaco@ietf.org
Subject: r: [Megaco] ToneID conflicts


Hi,
 
1. The Value of Tone Id defined in Multi Frequency Tone generator "mfh" - mf
signal code ST''' is given as 0x61 in the spec H.248.24(07/2003). This is
conflicting with the value of Tone Id  "enter" - Conference entrance tone in
the spec in H.2489.27(07/2003).
What should be the value of the Tone Id "mfh"?

[KJBII] We are working to make playtone obsolete, because it causes many
problems (such as this).  Note that it is NOT possible to use playtone to
play "enter" and "mfh" in the same signal invocation because they are in
different packages.  This means that even though there is an apparent
conflict, in practice it is not a problem. 
 
Also I have one more query which I have already posted in the mailing list. 
 
2.In RTCP XR Base Package defined in H.248.30(03/2004) the statisticsID are
from 1 to 12. The IDs 4 to 8 of that coincides with the statisticsID of the
base pkg, rtp version1. 
Also R Factor and External R Factor have ths same strings 'ns'

[KJBII] I will see that this is added to the IG. 
 
Any help in this regard will be much appreciated.
 
Anticipating reply,
Geetha


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


From megaco-bounces@ietf.org  Mon Nov 15 16:22:43 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10662
	for <megaco-archive@lists.ietf.org>; Mon, 15 Nov 2004 16:22:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTnit-0001XS-8n; Mon, 15 Nov 2004 15:45:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTnbe-00080d-Ra; Mon, 15 Nov 2004 15:37:46 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00305;
	Mon, 15 Nov 2004 15:37:44 -0500 (EST)
Message-Id: <200411152037.PAA00305@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 15 Nov 2004 15:37:44 -0500
Cc: megaco@ietf.org
Subject: [Megaco] I-D ACTION:draft-ietf-megaco-callflows-04.txt
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@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 Call flow examples
	Author(s)	: M. Brahmanapally, P. Viswanadham, K. Gundamaraju
	Filename	: draft-ietf-megaco-callflows-04.txt
	Pages		: 295
	Date		: 2004-11-15
	
The Megaco/H.248 call flow examples draft illustrates the usage 
of Megaco - Version 1 protocol [Ref:3] defined between the Media Gateway 
Controller and Media Gateway. In light of the vast features presently 
incorporated and continuously evolving features of the protocol, it 
serves the purpose of representing typical use case scenarios. There 
are a lot of possible scenarios for usage of MEGACO protocol. It is not 
the intent of the draft to represent the inter-working functionality 
among various protocols, however, an attempt is made to depict 
its usage in such a case for the purpose of completeness in the 
larger perspective. An attempt has been made to illustrate the 
supplementary call  services using MEGACO. The call flows can 
be categorized in to two sub sections,

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-megaco-callflows-04.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-callflows-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-callflows-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: <2004-11-15155947.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-megaco-callflows-04.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-megaco-callflows-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-11-15155947.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From megaco-bounces@ietf.org  Tue Nov 16 01:40:46 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08819
	for <megaco-archive@lists.ietf.org>; Tue, 16 Nov 2004 01:40:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CTwzS-0006IY-0h; Tue, 16 Nov 2004 01:38:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CTwwX-00062U-VN
	for megaco@megatron.ietf.org; Tue, 16 Nov 2004 01:35:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08670
	for <megaco@ietf.org>; Tue, 16 Nov 2004 01:35:57 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTwyg-0004vs-6E
	for megaco@ietf.org; Tue, 16 Nov 2004 01:38:11 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAG6ZOQ18742
	for <megaco@ietf.org>; Tue, 16 Nov 2004 01:35:24 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVCT9T5Q>; Tue, 16 Nov 2004 01:35:24 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536B4ADE4@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Rashim Anand <ranand@ccpu.com>,
        "'Christian Groves'"
	<christian.groves@ericsson.com>,
        bvswamy@hssworld.com
Subject: RE: [Megaco] Version negotiation in Handoff case
Date: Tue, 16 Nov 2004 01:35:12 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 6b519fb0ef66258f34533f52ff46aedf
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Why wouldn't you want to negotiate the highest possible version?  What if
the handoff was due to an MGC upgrade?
 
Kevin


  _____  

From: Rashim Anand [mailto:ranand@ccpu.com] 
Sent: Monday, November 15, 2004 11:58 PM
To: 'Christian Groves'; bvswamy@hssworld.com
Cc: megaco@ietf.org; Boyle, Kevin [NCRTP:3Z40:EXCH]
Subject: RE: [Megaco] Version negotiation in Handoff case



Hello Christian, Kevin, 

Agreed that the MG should encode the message using V1 and have the required
version in the serviceChangeVersion field. 

But the query was what should be the value in the serviceChangeVersion field
in the service change handoff sent from the MG to the Handoff MGC. Should MG
use the maximum version the MG supports in the serviceChangeVersion field OR
should it use the value negotiated with the old MGC?

Regards, 
-Rashim Anand 





-----Original Message----- 
From: megaco-bounces@ietf.org [ <mailto:megaco-bounces@ietf.org>
mailto:megaco-bounces@ietf.org] On Behalf Of Christian Groves 
Sent: Thursday, November 11, 2004 2:49 PM 
To: bvswamy@hssworld.com 
Cc: megaco@ietf.org; Rashim Anand; Kevin Boyle 
Subject: Re: [Megaco] Version negotiation in Handoff case 


Hello Venkat, 

The MG can always send "v2" but it runs the risk of being rejected. The MGC
may 
have restarted and is expecting v1 messages. Safer to send a v1 message and 
ServiceChangeVersion with 2. 

bvswamy@hssworld.com wrote: 
> 
> Hi Kevin 
> 
> I have been referring to the ServiceChangeVersion field in the Service 
> Change message since IMO version negotiation is triggered only if 
> MG adds ServicechangeVersion field. Yes you are right that in this case 
> registration or re-registration will be done by encoding using Version 1. 
> 
> However if V2 based MG does not want to do version negotiation, then 
> in 
> that case MG can send Service Change message for 
> registration/re-registration  encoded using Version 2.  Correct me if I 
> am wrong.. 
> 
> regards 
> Venkat 
> 
> 
> 
> 
> "Kevin Boyle" <kboyle@nortelnetworks.com> 
> 
> 11/11/2004 06:47 PM 
> 
>       
> To 
>       B Venkat S.R Swamy/HSS@HSS, Rashim Anand <ranand@ccpu.com> cc 
>       megaco@ietf.org 
> Subject 
>       RE: [Megaco] Version negotiation in Handoff case 
> 
> 
>       
> 
> 
> 
> 
> 
> 
> ServiceChange messages to any MGC that serve as registration or 
>  re-registration messages MUST be encoded using version 1.  See section 
>  11.3.  Protocol version negotiation then occurs as it would at any 
> other  time. 
>  
> Kevin 
> ---------------------------------------------------------------------- 
> -- 
> 
> 
> From: megaco-bounces@ietf.org  [ <mailto:megaco-bounces@ietf.org>
mailto:megaco-bounces@ietf.org] On 
> Behalf Of  bvswamy@hssworld.com 
> Sent: Thursday, November 11, 2004 7:20  AM 
> To: Rashim Anand 
> Cc: megaco@ietf.org 
> Subject:  RE: [Megaco] Version negotiation in Handoff case 
> 
> 
> Hi Rashim 
> 
> If MG is doing version negotiation then I suppose MG  should send 
> Service Change with its highest version support.(in your case  V2) 
> 
> 
> regards 
> B. Venkat S.R Swamy 
> Hughes Software Systems 
>  <file://www.hssworld.com> www.hssworld.com 
> 
> 
> 
> "Rashim Anand"  <ranand@ccpu.com> 
> 
> 11/11/2004 05:48 PM 
>       
> To 
>       B Venkat S.R  Swamy/HSS@HSS, "'Mahesh'" <mahesh@ccpu.com> 
> cc 
>       <megaco@ietf.org>  
> Subject 
>       RE: [Megaco] Version  negotiation in Handoff case 
> 
> 
>       
> 
> 
> 
> 
> 
> 
> 
> Hi  Ventak, 
>  
> I  believe that the question was which version should the MG use  to 
> contact the new  MGC. Should it use the version with which it was 
>  communicating with the old MGC  or should it use the maximum version 
>  supported at MG? Ofcourse, either way there  will be version 
> negotiation  with the new MGC. The final version negotiated with  the 
> new MGC might be  V1 or V2 but the doubt is which version should be used 
> in  sending the  srvcChng to the new MGC (irrespective of the new MGC's 
> subsequent   reply). 
>  
> Regards, 
> -Rashim Anand 
>  
>  
>  
> -----Original Message----- 
> From:  megaco-bounces@ietf.org  [ <mailto:megaco-bounces@ietf.org>
mailto:megaco-bounces@ietf.org] On 
> Behalf Of   bvswamy@hssworld.com 
> Sent: Thursday,  November 11, 2004 3:39  AM 
> To:  Mahesh 
> Cc: megaco@ietf.org 
> Subject: Re:  [Megaco] Version negotiation in Handoff  case 
> 
> 
> 
> Hi 
> 
> As per  the protocol specs, Version  Negotiation also takes place 
> during 
> Handoff and  Failover  procedures.(Section 11.3) 
> 
> 
> Regards 
> B. Venkat S.R   Swamy 
> Hughes Software  Systems  
>  <file://www.hssworld.com> www.hssworld.com    
> 
> 
> 
> 
> 
> "Mahesh"   <mahesh@ccpu.com> 
> Sent  by:  megaco-bounces@ietf.org 
> 
> 11/11/2004 03:18 PM 
>       
> To 
>       <megaco@ietf.org>    
> cc 
>       
> Subject 
>       [Megaco] Version  negotiation in Handoff  case 
> 
> 
>       
> 
> 
> 
> 
> 
> 
> 
> 
> 
> HI All, 
> 
>  
> 
> I will be  thankful to you if you can clarify the following scenario 
>   of  handoff . 
> 
>  
> 
>    
> 
> MG can support v1 and V2 .   
> 
> MG is currently in a session with Primary  MGC and the  negotiated 
> version  is V1.  
> 
> Primary MGC sends  a handoff to  MG. 
> 
>    
> 
> Then for contacting the secondary MGC which  version shall the MG use 
> in 
>  the Service change .  
> 
>  
> 
> With regards 
> 
> Mahesh 
> 
>  
> _______________________________________________ 
> Megaco mailing  list 
> Megaco@ietf.org 
>  <https://www1.ietf.org/mailman/listinfo/megaco>
https://www1.ietf.org/mailman/listinfo/megaco  
> 
> 
> 
> ***********************    HSS-Private   ***********************     
> 
> "Please note:The email domain  of Hughes Software Systems Ltd. has 
> been 
> changed to "hssworld.com" from  hss.hns.com" 
> 
> "DISCLAIMER: This  message is proprietary to Hughes Software Systems 
> Limited (HSS) and is  intended 
> solely for the use of the  individual to whom it is addressed. It may 
> contain  privileged or  
> confidential information and should not  be circulated or used for any 
> purpose other than for  
> what it is intended. If you have  received this message in error, please 
> notify the originator  
> immediately. If you are not the  intended recipient, you are notified 
> that you are strictly  
> prohibited from using, copying,  altering, or disclosing the contents of 
> this message. HSS  
> accepts no responsibility for loss or  damage arising from the use of 
> the information transmitted  
> by this email including damage from  virus." 
> 
> 
> 
> 
> 
> ***********************  HSS-Private    ***********************  
> 
> "Please note:The email domain of Hughes Software Systems Ltd. has been 
> changed to "hssworld.com" from hss.hns.com" 
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systems 
> Limited (HSS) and is intended 
> solely for the use of the individual to whom it is addressed. It may 
> contain  privileged or 
> confidential information and should not be circulated or used for any 
> purpose other than for 
> what it is intended. If you have received this message in error, please 
> notify the originator 
> immediately. If you are not the intended recipient, you are notified 
> that you are strictly 
> prohibited from using, copying, altering, or disclosing the contents of 
> this message. HSS 
> accepts no responsibility for loss or damage arising from the use of the 
> information transmitted 
> by this email including damage from virus." 
> 
> 
> 
> 
> 
> ***********************  HSS-Restricted   *********************** 
> 
> "Please note:The email domain of Hughes Software Systems Ltd. has been 
> changed to "hssworld.com" from hss.hns.com" 
> 
> "DISCLAIMER: This message is proprietary to Hughes Software Systems 
> Limited (HSS) and is intended 
> solely for the use of the individual to whom it is addressed. It may
contain  privileged or 
> confidential information and should not be circulated or used for any
purpose other than for 
> what it is intended. If you have received this message in error, please
notify the originator 
> immediately. If you are not the intended recipient, you are notified that
you are strictly 
> prohibited from using, copying, altering, or disclosing the contents of
this message. HSS 
> accepts no responsibility for loss or damage arising from the use of the
information transmitted 
> by this email including damage from virus." 
> 
> 
> ---------------------------------------------------------------------- 
> -- 
> 
> _______________________________________________ 
> Megaco mailing list 
> Megaco@ietf.org 
>  <https://www1.ietf.org/mailman/listinfo/megaco>
https://www1.ietf.org/mailman/listinfo/megaco 


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


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


From megaco-bounces@ietf.org  Tue Nov 16 07:35:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23352
	for <megaco-archive@lists.ietf.org>; Tue, 16 Nov 2004 07:35:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CU2WX-0004hK-Gl; Tue, 16 Nov 2004 07:33:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CU2T8-000427-4e
	for megaco@megatron.ietf.org; Tue, 16 Nov 2004 07:29:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22880
	for <megaco@ietf.org>; Tue, 16 Nov 2004 07:29:57 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU2VA-00044I-EI
	for megaco@ietf.org; Tue, 16 Nov 2004 07:32:14 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id A21D43468A5
	for <megaco@ietf.org>; Tue, 16 Nov 2004 04:29:16 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 29156-4ACDEAC2;
	Tue, 16 Nov 2004 04:29:16 -0800
Received: from IBM1D647E1D46E (unknown [172.25.0.63])
	by smtp.ccpu.com (Postfix) with ESMTP id C43653468D6
	for <megaco@ietf.org>; Tue, 16 Nov 2004 04:29:14 -0800 (PST)
From: "Milton" <milton@ccpu.com>
To: <megaco@ietf.org>
Date: Tue, 16 Nov 2004 17:59:13 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTL1+EtlCsI3I/fSqyQ7HJB2bwN5g==
Message-Id: <20041116122914.C43653468D6@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.75; host: smtp)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186
Subject: [Megaco] request-id in individual audit
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1397124717=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1397124717==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0045_01C4CC05.FCAFD0E0"

This is a multi-part message in MIME format.

------=_NextPart_000_0045_01C4CC05.FCAFD0E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

In The Megaco/H.248 Gateway Control Protocol, version 2,  in section  7.2.5
describing AuditValue command, protocol text says:

 

     " -  To audit an event, the relevant stream id (optional), eventID, 

         requestID (optional) are provided. The values of all the event 

         parameters are returned including: event actions and packaged 

         defined parameters."

 

Request Id has also been made optional in the asn encoding.

 

But in Annex B text encoding of the protocol the following rule is given to
audit individual events: 

indAudeventsDescriptor     = EventsToken EQUAL RequestID  

                        LBRKT indAudrequestedEvent RBRKT ; request id is not
optional

 

Is that a bug?

 

Regards,

Milton


------=_NextPart_000_0045_01C4CC05.FCAFD0E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In The Megaco/H.248 Gateway Control Protocol, version =
2, &nbsp;in
section &nbsp;7.2.5 &nbsp;describing AuditValue command, protocol text =
says:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp; &#8220; -&nbsp; To audit an =
event,
the relevant stream id (optional), eventID, =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
requestID
(optional) are provided. The values of all the event =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
parameters
are returned including: event actions and packaged =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
defined
parameters.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Request Id has also been made optional in the asn =
encoding.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>But in Annex B text encoding of the protocol the =
following
rule is given to audit individual events: <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>indAudeventsDescriptor&nbsp;&nbsp;&nbsp;&nbsp; =3D =
EventsToken
EQUAL RequestID&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
LBRKT indAudrequestedEvent RBRKT ; request id is not =
optional<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Is that a bug?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:City w:st=3D"on"><st1:place w:st=3D"on"><font =
size=3D2
  face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Milton</span></font></st1:pl=
ace></st1:City><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

</div>

</body>

</html>

------=_NextPart_000_0045_01C4CC05.FCAFD0E0--



--===============1397124717==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1397124717==--




From megaco-bounces@ietf.org  Wed Nov 17 00:54:41 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13730
	for <megaco-archive@lists.ietf.org>; Wed, 17 Nov 2004 00:54:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUIib-0006Hc-8e; Wed, 17 Nov 2004 00:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUIeO-0005iD-5Y
	for megaco@megatron.ietf.org; Wed, 17 Nov 2004 00:46:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13159
	for <megaco@ietf.org>; Wed, 17 Nov 2004 00:46:37 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUIgZ-0007KE-Ic
	for megaco@ietf.org; Wed, 17 Nov 2004 00:49:06 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id B3BF13467EF
	for <megaco@ietf.org>; Tue, 16 Nov 2004 21:45:56 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 21511-2CFFF2AB;
	Tue, 16 Nov 2004 21:45:56 -0800
Received: from IBM1D647E1D46E (unknown [172.25.0.63])
	by smtp.ccpu.com (Postfix) with ESMTP id 8DC503467EF
	for <megaco@ietf.org>; Tue, 16 Nov 2004 21:45:54 -0800 (PST)
From: "Milton" <milton@ccpu.com>
To: <megaco@ietf.org>
Date: Wed, 17 Nov 2004 11:15:53 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTMaLMwwUAFIX+KRMazJoP0sFtkRg==
Message-Id: <20041117054554.8DC503467EF@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.76; host: smtp)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Subject: [Megaco] use of request id in individual audit request for events
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0803440635=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0803440635==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0012_01C4CC96.CEF4FFE0"

This is a multi-part message in MIME format.

------=_NextPart_000_0012_01C4CC96.CEF4FFE0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

I have already posted a query about request Id not being shown as optional
in The Megaco/H.248 Gateway Control Protocol, version 2 for individual
audits. But I have a more generic query regarding the use of request id in
individual audit of events. I understand that a new event descriptor always
replaces the current event descriptor and in that case we may not have
multiple events with same event id but multiple request ids - now since it
is mandatory to specify the eventide in the individual audit request for
events - specifying request id may not serve any purpose. Am I missing
something?

 

Regards,

Milton


------=_NextPart_000_0012_01C4CC96.CEF4FFE0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I have already posted a query about request Id not =
being
shown as optional in The Megaco/H.248 Gateway Control Protocol, version =
2 for
individual audits. But I have a more generic query regarding the use of =
request
id in individual audit of events. I understand that a new event =
descriptor
always replaces the current event descriptor and in that case we may not =
have
multiple events with same event id but multiple request ids &#8211; now =
since it
is mandatory to specify the eventide in the individual audit request for =
events
&#8211; specifying request id may not serve any purpose. Am I missing
something?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:City w:st=3D"on"><st1:place w:st=3D"on"><font =
size=3D2
  face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Milton</span></font></st1:pl=
ace></st1:City><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

</div>

</body>

</html>

------=_NextPart_000_0012_01C4CC96.CEF4FFE0--



--===============0803440635==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0803440635==--




From megaco-bounces@ietf.org  Wed Nov 17 05:37:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10559
	for <megaco-archive@lists.ietf.org>; Wed, 17 Nov 2004 05:37:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUN7U-0008Ue-Fw; Wed, 17 Nov 2004 05:33:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUN3E-0007RJ-JQ
	for megaco@megatron.ietf.org; Wed, 17 Nov 2004 05:28:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09817
	for <megaco@ietf.org>; Wed, 17 Nov 2004 05:28:34 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUN5S-000596-C9
	for megaco@ietf.org; Wed, 17 Nov 2004 05:31:05 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id 798763468ED
	for <megaco@ietf.org>; Wed, 17 Nov 2004 02:27:50 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 04061-70500497;
	Wed, 17 Nov 2004 02:27:50 -0800
Received: from IBM1D647E1D46E (unknown [172.25.0.63])
	by smtp.ccpu.com (Postfix) with ESMTP id EAFEB3468B1
	for <megaco@ietf.org>; Wed, 17 Nov 2004 02:27:47 -0800 (PST)
From: "Milton" <milton@ccpu.com>
To: <megaco@ietf.org>
Date: Wed, 17 Nov 2004 15:57:47 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTMkBTYn2EAPy+TTAqwj+C9eUULjA==
Message-Id: <20041117102747.EAFEB3468B1@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.76; host: smtp)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 94ddbad0060c343c23e74ba9bbebbccf
Subject: [Megaco] lookahead overhead for indAudauditReturnParameter
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1190580318=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1190580318==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0025_01C4CCBE.30103E80"

This is a multi-part message in MIME format.

------=_NextPart_000_0025_01C4CCBE.30103E80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

In The Megaco/H.248 Gateway Control Protocol, version 2, in annexure B,
rules for auditItem are as following: 

auditItem   = ( MuxToken / ModemToken / MediaToken /  

                      SignalsToken / EventBufferToken / 

                      DigitMapToken / StatsToken / EventsToken / 

                      ObservedEventsToken / PackagesToken ) / 

                      indAudterminationAudit)

 

indAudterminationAudit   = indAudauditReturnParameter  

                              *(COMMA indAudauditReturnParameter)  

 

  

      indAudauditReturnParameter = (indAudmediaDescriptor / /   

                     indAudeventsDescriptor /  

                     indAudsignalsDescriptor /  

                     indAuddigitMapDescriptor /  

                     indAudeventBufferDescriptor / 

                     indAudstatisticsDescriptor /  

                     indAudpackagesDescriptor)

 

indAudmediaDescriptor   = MediaToken LBRKT indAudmediaParm RBRKT

.

indAudeventBufferDescriptor= EventBufferToken  

                        LBRKT indAudeventSpec RBRKT

 

indAudeventsDescriptor     = EventsToken EQUAL RequestID  

                        LBRKT indAudrequestedEvent RBRKT

 

indAudsignalsDescriptor    = SignalsToken  

                        LBRKT [ indAudsignalParm ] RBRKT  .. Etc.

 

As we can see indAudterminationAudit ends up with a rule that would start
with one of the tokens - and hence there is a minor ambiguity decoding
auditItem, to illustrate it, both of the following strings would conform to
the rule of auditItem:

 

.Audit {

                        Events

            }

 

 And 

  .Audit{

                        Events = 111{al/on}

            }

 

As we can see we cannot distinguish between the above two texts on the basis
of the 'token' alone. To solve this problem we have to look ahead to check
the character after the tokens - Now ..

1. Looking ahead would reduce the efficiency of the parser somehow and 

2. This would be a slight deviation from normal abnf rules in megaco.

 

So wouldn't it be better to introduce new tokens for
indAudit<xxx>Descriptors? For example if we rewrite the rule for
inAudeventsDescriptor as:

indAudeventsDescriptor     = AudEventsToken EQUAL RequestID  

                        LBRKT indAudrequestedEvent RBRKT

 

Where 

AudEventsToken                = ("AuditEvents"                / "AE")

 

 

The crux of my argument is : Is not it better to add a set of tokens than to
add to parser's overhead ?

 

 

Regards,

Milton

 

 

 

 

 

 

 

 


------=_NextPart_000_0025_01C4CCBE.30103E80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In The Megaco/H.248 Gateway Control Protocol, version =
2, in
annexure B, rules for auditItem are as following: =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>auditItem&nbsp;&nbsp; =3D ( MuxToken / ModemToken / =
MediaToken
/&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
SignalsToken / EventBufferToken / <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DigitMapToken / =
StatsToken /
EventsToken / <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
ObservedEventsToken / PackagesToken ) / <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
indAudterminationAudit)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>indAudterminationAudit&nbsp;&nbsp; =3D
indAudauditReturnParameter&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
*(COMMA indAudauditReturnParameter)&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
indAudauditReturnParameter =3D
(indAudmediaDescriptor / /&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
indAudeventsDescriptor /&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
indAudsignalsDescriptor /&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
indAuddigitMapDescriptor /&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;indAude=
ventBufferDescriptor
/ <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
indAudstatisticsDescriptor /&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
indAudpackagesDescriptor)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>indAudmediaDescriptor&nbsp;&nbsp; =3D MediaToken =
LBRKT
indAudmediaParm RBRKT<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&#8230;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>indAudeventBufferDescriptor=3D EventBufferToken&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
LBRKT indAudeventSpec RBRKT<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>indAudeventsDescriptor&nbsp;&nbsp;&nbsp;&nbsp; =3D =
EventsToken
EQUAL RequestID&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
LBRKT indAudrequestedEvent RBRKT<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>indAudsignalsDescriptor&nbsp;&nbsp;&nbsp; =3D
SignalsToken&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
LBRKT [ indAudsignalParm ] RBRKT&nbsp; &#8230;. =
Etc.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>As we can see indAudterminationAudit ends up with a =
rule
that would start with one of the tokens &#8211; and hence there is a =
minor
ambiguity decoding auditItem, to illustrate it, both of the following =
strings
would conform to the rule of auditItem:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&#8230;Audit {<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; Events<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;And <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp; &#8230;Audit{<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Events
=3D 111{al/on}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; }<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>As we can see we cannot distinguish between the above =
two
texts on the basis of the &#8216;token&#8217; alone. To solve this =
problem we have
to look ahead to check the character after the tokens &#8211; Now =
..<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>1. Looking ahead would reduce the efficiency of the =
parser
somehow and <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>2. This would be a slight deviation from normal abnf =
rules
in megaco.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>So wouldn&#8217;t it be better to introduce new =
tokens for
indAudit&lt;xxx&gt;Descriptors? For example if we rewrite the rule for
inAudeventsDescriptor as:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>indAudeventsDescriptor&nbsp;&nbsp;&nbsp;&nbsp; =3D =
AudEventsToken
EQUAL RequestID&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
LBRKT indAudrequestedEvent RBRKT<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Where <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>AudEventsToken&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
=3D =
(&quot;AuditEvents&quot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
/ &quot;AE&quot;)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The crux of my argument is : Is not it better to add =
a set
of tokens than to add to parser&#8217;s overhead =
?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:City w:st=3D"on"><st1:place w:st=3D"on"><font =
size=3D2
  face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Milton</span></font></st1:pl=
ace></st1:City><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0025_01C4CCBE.30103E80--



--===============1190580318==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1190580318==--




From megaco-bounces@ietf.org  Wed Nov 17 05:49:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11358
	for <megaco-archive@lists.ietf.org>; Wed, 17 Nov 2004 05:49:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUNM6-0003Pa-9c; Wed, 17 Nov 2004 05:48:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUNLQ-0003IG-Ny
	for megaco@megatron.ietf.org; Wed, 17 Nov 2004 05:47:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11284
	for <megaco@ietf.org>; Wed, 17 Nov 2004 05:47:21 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUNNo-0005Wq-Sw
	for megaco@ietf.org; Wed, 17 Nov 2004 05:49:53 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAHAkpa26913
	for <megaco@ietf.org>; Wed, 17 Nov 2004 05:46:51 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVC4F8ZP>; Wed, 17 Nov 2004 05:46:52 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536BD0541@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Milton <milton@ccpu.com>, megaco@ietf.org
Subject: RE: [Megaco] lookahead overhead for indAudauditReturnParameter
Date: Wed, 17 Nov 2004 05:46:42 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Megaco is a context-dependent grammar.  The fact that the parser detects the
Events token does not mean that it has fulfilled some portion of the grammar
-- only that it has matched the Events token.  It seems to me that it is
very easy for a parser to tell the difference between the two actually, by
the presence or absence of a '=' following the Events token.
 
Given that there are many places in the ABNF grammar where the parser
actually has to know what the immediately following character is in order to
determine what construct it is in.  This would seem to be just one more
place.
 
Note that syntax changes, such as alteration of tokens is NOT backwards
compatible, and will break many deployed implementations.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Milton
Sent: Wednesday, November 17, 2004 5:28 AM
To: megaco@ietf.org
Subject: [Megaco] lookahead overhead for indAudauditReturnParameter



Hi,

In The Megaco/H.248 Gateway Control Protocol, version 2, in annexure B,
rules for auditItem are as following: 

auditItem   = ( MuxToken / ModemToken / MediaToken /  

                      SignalsToken / EventBufferToken / 

                      DigitMapToken / StatsToken / EventsToken / 

                      ObservedEventsToken / PackagesToken ) / 

                      indAudterminationAudit)

 

indAudterminationAudit   = indAudauditReturnParameter  

                              *(COMMA indAudauditReturnParameter)  

 

  

      indAudauditReturnParameter = (indAudmediaDescriptor / /   

                     indAudeventsDescriptor /  

                     indAudsignalsDescriptor /  

                     indAuddigitMapDescriptor /  

                     indAudeventBufferDescriptor / 

                     indAudstatisticsDescriptor /  

                     indAudpackagesDescriptor)

 

indAudmediaDescriptor   = MediaToken LBRKT indAudmediaParm RBRKT

...

indAudeventBufferDescriptor= EventBufferToken  

                        LBRKT indAudeventSpec RBRKT

 

indAudeventsDescriptor     = EventsToken EQUAL RequestID  

                        LBRKT indAudrequestedEvent RBRKT

 

indAudsignalsDescriptor    = SignalsToken  

                        LBRKT [ indAudsignalParm ] RBRKT  .... Etc.

 

As we can see indAudterminationAudit ends up with a rule that would start
with one of the tokens - and hence there is a minor ambiguity decoding
auditItem, to illustrate it, both of the following strings would conform to
the rule of auditItem:

 

...Audit {

                        Events

            }

 

 And 

  ...Audit{

                        Events = 111{al/on}

            }

 

As we can see we cannot distinguish between the above two texts on the basis
of the 'token' alone. To solve this problem we have to look ahead to check
the character after the tokens - Now ..

1. Looking ahead would reduce the efficiency of the parser somehow and 

2. This would be a slight deviation from normal abnf rules in megaco.

 

So wouldn't it be better to introduce new tokens for
indAudit<xxx>Descriptors? For example if we rewrite the rule for
inAudeventsDescriptor as:

indAudeventsDescriptor     = AudEventsToken EQUAL RequestID  

                        LBRKT indAudrequestedEvent RBRKT

 

Where 

AudEventsToken                = ("AuditEvents"                / "AE")

 

 

The crux of my argument is : Is not it better to add a set of tokens than to
add to parser's overhead ?

 

 

Regards,

Milton

 

 

 

 

 

 

 

 


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


From megaco-bounces@ietf.org  Wed Nov 17 05:57:15 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11947
	for <megaco-archive@lists.ietf.org>; Wed, 17 Nov 2004 05:57:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUNTd-0004E5-As; Wed, 17 Nov 2004 05:55:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUNO1-0003f2-6g
	for megaco@megatron.ietf.org; Wed, 17 Nov 2004 05:50:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11379
	for <megaco@ietf.org>; Wed, 17 Nov 2004 05:50:02 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUNQO-0005Z8-S5
	for megaco@ietf.org; Wed, 17 Nov 2004 05:52:34 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAHAnVg07926
	for <megaco@ietf.org>; Wed, 17 Nov 2004 05:49:32 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVC4F896>; Wed, 17 Nov 2004 05:49:32 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536BD0543@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Milton <milton@ccpu.com>, megaco@ietf.org
Subject: RE: [Megaco] request-id in individual audit
Date: Wed, 17 Nov 2004 05:49:23 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

The RequestID is only optional in the sense that it is not required for
specification of the Events token for auditing the entire descriptor.
 
This is intentional grammar.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Milton
Sent: Tuesday, November 16, 2004 7:29 AM
To: megaco@ietf.org
Subject: [Megaco] request-id in individual audit



In The Megaco/H.248 Gateway Control Protocol, version 2,  in section  7.2.5
describing AuditValue command, protocol text says:

 

     " -  To audit an event, the relevant stream id (optional), eventID, 

         requestID (optional) are provided. The values of all the event 

         parameters are returned including: event actions and packaged 

         defined parameters."

 

Request Id has also been made optional in the asn encoding.

 

But in Annex B text encoding of the protocol the following rule is given to
audit individual events: 

indAudeventsDescriptor     = EventsToken EQUAL RequestID  

                        LBRKT indAudrequestedEvent RBRKT ; request id is not
optional

 

Is that a bug?

 

Regards,

Milton


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


From megaco-bounces@ietf.org  Wed Nov 17 06:12:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13330
	for <megaco-archive@lists.ietf.org>; Wed, 17 Nov 2004 06:12:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUNgP-0006pD-5a; Wed, 17 Nov 2004 06:09:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUNgB-0006iD-I9
	for megaco@megatron.ietf.org; Wed, 17 Nov 2004 06:08:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13032
	for <megaco@ietf.org>; Wed, 17 Nov 2004 06:08:48 -0500 (EST)
Received: from albatross.ericsson.se ([193.180.251.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUNiW-0005y8-Lb
	for megaco@ietf.org; Wed, 17 Nov 2004 06:11:20 -0500
Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118])
	by albatross.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id
	iAHB8kvD006333
	for <megaco@ietf.org>; Wed, 17 Nov 2004 12:08:46 +0100 (MET)
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by
	esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 17 Nov 2004 12:08:44 +0100
Received: from eaubrnt019.epa.ericsson.se ([146.11.9.165]) by
	esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WB18T25H; Wed, 17 Nov 2004 12:08:44 +0100
Received: from ericsson.com (EG2E500202DSEGL [146.11.22.70]) by
	eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange
	Internet Mail Service Version 5.5.2657.72)
	id WTM84SAY; Wed, 17 Nov 2004 22:08:41 +1100
Message-ID: <419B2DAA.10503@ericsson.com>
Date: Wed, 17 Nov 2004 21:53:30 +1100
X-Sybari-Trust: 5a26a35a 8cefd49f cdaa5011 00000138
From: Christian Groves <christian.groves@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Milton <milton@ccpu.com>
Subject: Re: [Megaco] use of request id in individual audit request for events
References: <20041117054554.8DC503467EF@smtp.ccpu.com>
In-Reply-To: <20041117054554.8DC503467EF@smtp.ccpu.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
X-OriginalArrivalTime: 17 Nov 2004 11:08:44.0556 (UTC)
	FILETIME=[CDA51CC0:01C4CC95]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by albatross.ericsson.se
	id iAHB8kvD006333
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hello Milton,

You can have multiple eventids in the one requestID. You can also have se=
veral=20
events with the same eventID set. In this can you must use the request ID=
 to=20
distinguish between them.

With respect to the requestId being optional in an individualaudit. The A=
SN.1=20
has the requestID optional in line with the procedures. So we should prob=
ably=20
update the ABNF.

Regards, Christian

Milton wrote:

> Hi,
>=20
> I have already posted a query about request Id not being shown as=20
> optional in The Megaco/H.248 Gateway Control Protocol, version 2 for=20
> individual audits. But I have a more generic query regarding the use of=
=20
> request id in individual audit of events. I understand that a new event=
=20
> descriptor always replaces the current event descriptor and in that cas=
e=20
> we may not have multiple events with same event id but multiple request=
=20
> ids =96 now since it is mandatory to specify the eventide in the=20
> individual audit request for events =96 specifying request id may not=20
> serve any purpose. Am I missing something?
>=20
> =20
>=20
> Regards,
>=20
> Milton
>=20
>=20
> -----------------------------------------------------------------------=
-
>=20
> _______________________________________________
> Megaco mailing list
> 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-bounces@ietf.org  Thu Nov 18 01:30:32 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04625
	for <megaco-archive@lists.ietf.org>; Thu, 18 Nov 2004 01:30:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUfiB-0006bs-QT; Thu, 18 Nov 2004 01:24:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUfhR-0006RI-UO
	for megaco@megatron.ietf.org; Thu, 18 Nov 2004 01:23:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04140
	for <megaco@ietf.org>; Thu, 18 Nov 2004 01:23:20 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUfjq-0000pD-Bp
	for megaco@ietf.org; Thu, 18 Nov 2004 01:26:01 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id 904FE3468DF
	for <megaco@ietf.org>; Wed, 17 Nov 2004 22:22:31 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 31447-75A187F5;
	Wed, 17 Nov 2004 22:22:31 -0800
Received: from Mahesh (unknown [172.25.0.61])
	by smtp.ccpu.com (Postfix) with ESMTP id B35843468DD
	for <megaco@ietf.org>; Wed, 17 Nov 2004 22:22:20 -0800 (PST)
From: "Mahesh" <mahesh@ccpu.com>
To: <megaco@ietf.org>
Date: Thu, 18 Nov 2004 11:52:10 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTNNu/F3N+Te6CbSECsByMreAlvDQ==
Message-Id: <20041118062225.B35843468DD@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.78; host: smtp)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d8921dd2ebcb07edebf7bfaf4808c2ad
Subject: [Megaco] Megaco "Version" value in a service change reply
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0990173948=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0990173948==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0190_01C4CD65.10562AD0"

This is a multi-part message in MIME format.

------=_NextPart_000_0190_01C4CD65.10562AD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

HI All,

 

Could you please clarify the following .

 

MG is sending MGC the initial  service change .This service change is
encoded as V1  and  

servicechange version parameter is 2 .

 

MG to MGC

========== 

MEGACO/1 [124.124.124.222] 

      Transaction = 9998 { 

          Context = - { ServiceChange = ROOT {Services { 

                  Method=Restart,  

                  ServiceChangeVersion=2, Profile=ResGW/1} 

              } 

          } 

      }

    

 

MGC supports Version 2 and sends back  the service change reply  with
servicechange version parameter as 2 .

Now what will be the value of  the "Megacop Token SLASH Version" .

Will it be one or two 

 

MGC to MG

=========

MEGACO/2 [124.124.124.222]    OR      

 

MEGACO/1 [124.124.124.222]    

      Reply = 9998{ 

          Context = - { ServiceChange = ROOT {Services { 

                                ServiceChangeVersion=2, Profile=ResGW/1} 

              } 

          } 

      }

 

 

 

With thanks and regards

Mahesh

 

 


------=_NextPart_000_0190_01C4CD65.10562AD0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>HI All,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Could you please clarify the following =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MG is sending MGC the initial&nbsp; service change =
.This service
change is encoded as V1&nbsp; and&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>servicechange version parameter is 2 =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MG to MGC<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MEGACO/1 [124.124.124.222] =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transaction =3D 9998 { =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=

Context =3D - { ServiceChange =3D ROOT {Services { =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Method=3DRestart,&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
ServiceChangeVersion=3D2, Profile=3DResGW/1} =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;
} <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 } <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MGC supports Version 2 and sends back&nbsp; the =
service
change reply&nbsp; with servicechange version parameter as 2 =
.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Now what will be the value of&nbsp; the =
&#8220;Megacop Token
SLASH Version&#8221; .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Will it be one or two <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MGC to MG<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MEGACO/2 [124.124.124.222]&nbsp;&nbsp;&nbsp;
OR&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MEGACO/1 [124.124.124.222]&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Reply =3D 9998{ =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=

Context =3D - { ServiceChange =3D ROOT {Services { =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;ServiceChangeVersion=3D2,
Profile=3DResGW/1} <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;
} <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 } <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
}<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>With thanks and regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Mahesh<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0190_01C4CD65.10562AD0--




--===============0990173948==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0990173948==--





From megaco-bounces@ietf.org  Thu Nov 18 02:20:24 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23354
	for <megaco-archive@lists.ietf.org>; Thu, 18 Nov 2004 02:20:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUgYf-0005vY-H5; Thu, 18 Nov 2004 02:18:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUgX2-0005JD-Rt
	for megaco@megatron.ietf.org; Thu, 18 Nov 2004 02:16:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21013
	for <megaco@ietf.org>; Thu, 18 Nov 2004 02:16:39 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUgZc-0001s7-7U
	for megaco@ietf.org; Thu, 18 Nov 2004 02:19:20 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id D311C3468EE
	for <megaco@ietf.org>; Wed, 17 Nov 2004 23:16:01 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 01854-6AEA0114;
	Wed, 17 Nov 2004 23:16:01 -0800
Received: from ccpu00179 (unknown [172.25.0.135])
	by smtp.ccpu.com (Postfix) with SMTP id 3EE0E3468F7
	for <megaco@ietf.org>; Wed, 17 Nov 2004 23:16:00 -0800 (PST)
Message-ID: <006a01c4cdb0$09b324d0$870019ac@ccpu00179>
From: "Geetha" <geetha@ccpu.com>
To: <megaco@ietf.org>
Date: Thu, 18 Nov 2004 12:49:01 -0800
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4942.400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4942.400
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.12;
	VDF: 6.28.0.78; host: smtp)
X-Spam-Score: 2.8 (++)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Subject: [Megaco] Re: Analog Line Supervision Package
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0731602484=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0731602484==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0067_01C4CD6C.FA28DAC0"

This is a multi-part message in MIME format.

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

Hi All,

In Analog Line Supervision package, for the observedEvents descriptor =
parameter init of event ID on ,=20

In draft-ietf-megaco-h248v2-04,
the type is given as boolean and the possible values are given as "True" =
and "False".(Both in quotes).=20
In RFC 3015 the possible values are given as True and False(Without =
quotes)

In section B.2 ABNF specification in draft is given as=20
Boolean values are encoded as "on" and "off" and are case insensitive. =
The safechar form of value MUST be used.
 and in RFC it is said as=20
Boolean values, indicated in the text as True and False, encoded as "On" =
and "Off", respectively, in the ABNF

This is slightly confusing..What values are to be used? Either on/off or =
"True"/"False"

Thanks and Rgds,
Geetha

------=_NextPart_000_0067_01C4CD6C.FA28DAC0
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.3819.300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>Hi =
All,</FONT></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial =
size=3D2>In&nbsp;Analog Line=20
Supervision&nbsp;package, for the observedEvents descriptor parameter=20
<STRONG>init </STRONG>of event ID <STRONG>on</STRONG> , =
</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>In =
draft-ietf-megaco-h248v2-04,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the type is&nbsp;given as boolean and =
the possible=20
values are given as "True" and "False".(Both in quotes). </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>In RFC 3015 the possible values are =
given as True=20
and False(Without quotes)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>In section B.2 ABNF specification in =
draft is given=20
as </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Boolean values are encoded as "on" and =
"off" and=20
are case insensitive. The safechar form of value MUST be =
used.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;and in RFC it is said as =
<BR>Boolean values,=20
indicated in the text as True and False, encoded as "On" and "Off",=20
respectively, in the ABNF</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>This is slightly confusing..What values =
are to be=20
used? Either on/off or "True"/"False"</FONT></DIV>
<DIV>&nbsp;</DIV></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks and Rgds,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Geetha</FONT></DIV></BODY></HTML>

------=_NextPart_000_0067_01C4CD6C.FA28DAC0--



--===============0731602484==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0731602484==--




From megaco-bounces@ietf.org  Thu Nov 18 03:21:28 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29574
	for <megaco-archive@lists.ietf.org>; Thu, 18 Nov 2004 03:21:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUhVo-0008OL-UO; Thu, 18 Nov 2004 03:19:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUhSr-0007WF-Ri
	for megaco@megatron.ietf.org; Thu, 18 Nov 2004 03:16:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29279
	for <megaco@ietf.org>; Thu, 18 Nov 2004 03:16:23 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUhVR-000393-Uz
	for megaco@ietf.org; Thu, 18 Nov 2004 03:19:06 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAI8Fqo18011
	for <megaco@ietf.org>; Thu, 18 Nov 2004 03:15:53 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVC4L439>; Thu, 18 Nov 2004 03:15:53 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536C624D3@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Mahesh <mahesh@ccpu.com>, megaco@ietf.org
Subject: RE: [Megaco] Megaco "Version" value in a service change reply
Date: Thu, 18 Nov 2004 03:15:47 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

The reply will be V1.
 
All subsequent messaging will be V2.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Mahesh
Sent: Thursday, November 18, 2004 1:22 AM
To: megaco@ietf.org
Subject: [Megaco] Megaco "Version" value in a service change reply



HI All,

 

Could you please clarify the following .

 

MG is sending MGC the initial  service change .This service change is
encoded as V1  and  

servicechange version parameter is 2 .

 

MG to MGC

========== 

MEGACO/1 [124.124.124.222] 

      Transaction = 9998 { 

          Context = - { ServiceChange = ROOT {Services { 

                  Method=Restart,  

                  ServiceChangeVersion=2, Profile=ResGW/1} 

              } 

          } 

      }

    

 

MGC supports Version 2 and sends back  the service change reply  with
servicechange version parameter as 2 .

Now what will be the value of  the "Megacop Token SLASH Version" .

Will it be one or two 

 

MGC to MG

=========

MEGACO/2 [124.124.124.222]    OR      

 

MEGACO/1 [124.124.124.222]    

      Reply = 9998{ 

          Context = - { ServiceChange = ROOT {Services { 

                                ServiceChangeVersion=2, Profile=ResGW/1} 

              } 

          } 

      }

 

 

 

With thanks and regards

Mahesh

 

 


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


From megaco-bounces@ietf.org  Thu Nov 18 03:23:43 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29719
	for <megaco-archive@lists.ietf.org>; Thu, 18 Nov 2004 03:23:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUhX6-0000Wv-SP; Thu, 18 Nov 2004 03:20:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUhVi-0008KH-I2
	for megaco@megatron.ietf.org; Thu, 18 Nov 2004 03:19:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29421
	for <megaco@ietf.org>; Thu, 18 Nov 2004 03:19:20 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUhYI-0003CK-HU
	for megaco@ietf.org; Thu, 18 Nov 2004 03:22:02 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAI8Ioo18054
	for <megaco@ietf.org>; Thu, 18 Nov 2004 03:18:50 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVC4L46F>; Thu, 18 Nov 2004 03:18:50 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536C624D4@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Geetha <geetha@ccpu.com>, megaco@ietf.org
Subject: RE: [Megaco] Re: Analog Line Supervision Package
Date: Thu, 18 Nov 2004 03:18:34 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

True/False is the generic reference that is encoded in the ABNF as on/off.
Note that Annex A has defined values for true/false.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Geetha
Sent: Thursday, November 18, 2004 3:49 PM
To: megaco@ietf.org
Subject: [Megaco] Re: Analog Line Supervision Package


Hi All,
 
In Analog Line Supervision package, for the observedEvents descriptor
parameter init of event ID on , 
 
In draft-ietf-megaco-h248v2-04,
the type is given as boolean and the possible values are given as "True" and
"False".(Both in quotes). 
In RFC 3015 the possible values are given as True and False(Without quotes)
 
In section B.2 ABNF specification in draft is given as 
Boolean values are encoded as "on" and "off" and are case insensitive. The
safechar form of value MUST be used.
 and in RFC it is said as 
Boolean values, indicated in the text as True and False, encoded as "On" and
"Off", respectively, in the ABNF
 

This is slightly confusing..What values are to be used? Either on/off or
"True"/"False"
 
Thanks and Rgds,
Geetha


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


From megaco-bounces@ietf.org  Thu Nov 18 08:44:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24794
	for <megaco-archive@lists.ietf.org>; Thu, 18 Nov 2004 08:44:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUmY2-00031R-5l; Thu, 18 Nov 2004 08:42:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmF3-0006Zr-I5
	for megaco@megatron.ietf.org; Thu, 18 Nov 2004 08:22:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23135
	for <megaco@ietf.org>; Thu, 18 Nov 2004 08:22:27 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUmHW-000147-6o
	for megaco@ietf.org; Thu, 18 Nov 2004 08:25:12 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id 0D94E3468D2
	for <megaco@ietf.org>; Thu, 18 Nov 2004 05:21:47 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 20049-1AD739A7;
	Thu, 18 Nov 2004 05:21:47 -0800
Received: from IBME7B5757F240 (unknown [172.25.0.134])
	by smtp.ccpu.com (Postfix) with ESMTP id 8CA6C3468E6
	for <megaco@ietf.org>; Thu, 18 Nov 2004 05:21:45 -0800 (PST)
From: "Deepak " <deepakp@ccpu.com>
To: <megaco@ietf.org>
Date: Thu, 18 Nov 2004 18:49:43 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTNcUPS7tKwB05xS6yKNg1AAJrD5A==
Message-Id: <20041118132145.8CA6C3468E6@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.18;
	VDF: 6.28.0.79; host: smtp)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Subject: [Megaco] help
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1565048413=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1565048413==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_013B_01C4CD9F.5F047BC0"

This is a multi-part message in MIME format.

------=_NextPart_000_013B_01C4CD9F.5F047BC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi

     Can moderator of list subscribe me to this list

Regards

Deepak


------=_NextPart_000_013B_01C4CD9F.5F047BC0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-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=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp; Can moderator of list =
subscribe me to this list<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Deepak<o:p></o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_013B_01C4CD9F.5F047BC0--



--===============1565048413==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1565048413==--




From megaco-bounces@ietf.org  Thu Nov 18 08:51:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25337
	for <megaco-archive@lists.ietf.org>; Thu, 18 Nov 2004 08:51:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUmYJ-00036z-Ka; Thu, 18 Nov 2004 08:42:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmNh-0008VL-MK
	for megaco@megatron.ietf.org; Thu, 18 Nov 2004 08:31:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23735
	for <megaco@ietf.org>; Thu, 18 Nov 2004 08:31:23 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUmQK-0001Du-Dl
	for megaco@ietf.org; Thu, 18 Nov 2004 08:34:08 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id EEFB13468ED
	for <megaco@ietf.org>; Thu, 18 Nov 2004 05:30:46 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 20417-2FAD5B83;
	Thu, 18 Nov 2004 05:30:33 -0800
Received: from IBME7B5757F240 (unknown [172.25.0.134])
	by smtp.ccpu.com (Postfix) with ESMTP id 1789F3468BB
	for <megaco@ietf.org>; Thu, 18 Nov 2004 05:30:26 -0800 (PST)
From: "Deepak " <deepakp@ccpu.com>
To: <megaco@ietf.org>
Date: Thu, 18 Nov 2004 18:58:22 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTNcnmTMyA2tgEPSEKD5HrajcjOMQ==
Message-Id: <20041118133027.1789F3468BB@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.18;
	VDF: 6.28.0.79; host: smtp)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Subject: [Megaco] query on MTP3B as Transport option
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1737303269=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1737303269==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_013F_01C4CDA0.96244F80"

This is a multi-part message in MIME format.

------=_NextPart_000_013F_01C4CDA0.96244F80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi

    I have a very small query when Megaco uses MTP3B as transport .Like in
case of TCP and UDP we are having different  port for ASN and TEXT encoding.
So when we receive any message from lower layer Megaco is able to
distinguish which type of decoding to apply as it know from which port it is
receiving the message .But how can we distinguish the same case when MTP3B
is transport .Can someone help me on this query ??

 

 

Regards

Deepak


------=_NextPart_000_013F_01C4CDA0.96244F80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp; I have a very small query when =
Megaco
uses MTP3B as transport .Like in case of TCP and UDP we are having
different&nbsp; port for ASN and TEXT encoding. So when we receive any =
message
from lower layer Megaco is able to distinguish which type of decoding to =
apply
as it know from which port it is receiving the message .But how can we =
distinguish
the same case when MTP3B is transport .Can someone help me on this query =
??<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Deepak<o:p></o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_013F_01C4CDA0.96244F80--



--===============1737303269==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1737303269==--




From megaco-bounces@ietf.org  Thu Nov 18 09:28:58 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28152
	for <megaco-archive@lists.ietf.org>; Thu, 18 Nov 2004 09:28:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CUn7x-00051F-Od; Thu, 18 Nov 2004 09:19:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmyH-0001Cl-9t
	for megaco@megatron.ietf.org; Thu, 18 Nov 2004 09:09:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26617
	for <megaco@ietf.org>; Thu, 18 Nov 2004 09:09:11 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUn0u-000233-Ca
	for megaco@ietf.org; Thu, 18 Nov 2004 09:11:56 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAIE8eC26993
	for <megaco@ietf.org>; Thu, 18 Nov 2004 09:08:40 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <WVC4M9QD>; Thu, 18 Nov 2004 09:08:40 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536C626BD@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Deepak  <deepakp@ccpu.com>, megaco@ietf.org
Subject: RE: [Megaco] query on MTP3B as Transport option
Date: Thu, 18 Nov 2004 09:08:22 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

MTP3B transport is described in H.248.5.  Differentiation of encoding can be
based upon the registration message from the MG.  Try decoding it as one,
and then the other.  Which ever it is will be the encoding used throughout
the control association.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Deepak 
Sent: Thursday, November 18, 2004 8:28 AM
To: megaco@ietf.org
Subject: [Megaco] query on MTP3B as Transport option



Hi

    I have a very small query when Megaco uses MTP3B as transport .Like in
case of TCP and UDP we are having different  port for ASN and TEXT encoding.
So when we receive any message from lower layer Megaco is able to
distinguish which type of decoding to apply as it know from which port it is
receiving the message .But how can we distinguish the same case when MTP3B
is transport .Can someone help me on this query ??

 

 

Regards

Deepak


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


From megaco-bounces@ietf.org  Mon Nov 22 00:54:02 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05138
	for <megaco-archive@lists.ietf.org>; Mon, 22 Nov 2004 00:54:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CW77V-0003tB-Ow; Mon, 22 Nov 2004 00:52:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CW74h-00030N-8d
	for megaco@megatron.ietf.org; Mon, 22 Nov 2004 00:49:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04928
	for <megaco@ietf.org>; Mon, 22 Nov 2004 00:49:16 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW77u-0004qZ-Oy
	for megaco@ietf.org; Mon, 22 Nov 2004 00:52:49 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id 4B17B3468A5
	for <megaco@ietf.org>; Sun, 21 Nov 2004 21:48:36 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 24724-08435A6A;
	Sun, 21 Nov 2004 21:48:36 -0800
Received: from Mahesh (unknown [172.25.0.61])
	by smtp.ccpu.com (Postfix) with ESMTP id E2FA23468E6
	for <megaco@ietf.org>; Sun, 21 Nov 2004 21:48:34 -0800 (PST)
From: "Mahesh" <mahesh@ccpu.com>
To: <megaco@ietf.org>
Date: Mon, 22 Nov 2004 11:18:32 +0530
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcTQVuYQgcE0UrYKQyWp30lQ3f1mMQ==
Message-Id: <20041122054834.E2FA23468E6@smtp.ccpu.com>
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.18;
	VDF: 6.28.0.83; host: smtp)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Subject: [Megaco] Generic announcement package Id
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0895849377=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0895849377==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_023C_01C4D085.010D1980"

This is a multi-part message in MIME format.

------=_NextPart_000_023C_01C4D085.010D1980
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

HI,

 

Could you please let me know , whether any changes are there in the 

Package ID of  Generic announcement package (an).

Whether it is having an id of  "1d"   or whether this got changed .

 

 

With thanks and regards

Mahesh

 


------=_NextPart_000_023C_01C4D085.010D1980
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-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=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>HI,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Could you please let me know , whether any changes =
are there
in the <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Package ID of &nbsp;Generic announcement package =
(an).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Whether it is having an id of&nbsp; =
&#8220;1d&#8221;&nbsp;&nbsp; or whether
this got changed .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>With thanks and regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Mahesh<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_023C_01C4D085.010D1980--




--===============0895849377==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0895849377==--





From megaco-bounces@ietf.org  Mon Nov 22 04:27:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04977
	for <megaco-archive@lists.ietf.org>; Mon, 22 Nov 2004 04:27:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWANI-0006V6-2r; Mon, 22 Nov 2004 04:20:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWAJY-0005tU-8t
	for megaco@megatron.ietf.org; Mon, 22 Nov 2004 04:16:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04425
	for <megaco@ietf.org>; Mon, 22 Nov 2004 04:16:50 -0500 (EST)
From: ajohri@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWAMs-0000U6-F0
	for megaco@ietf.org; Mon, 22 Nov 2004 04:20:24 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAM9Ce6p023776
	for <megaco@ietf.org>; Mon, 22 Nov 2004 14:42:41 +0530 (IST)
Received: from dlfmail1.hss.hns.com (dlfmail1 [172.16.32.24])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAM9CcxX023752;
	Mon, 22 Nov 2004 14:42:39 +0530 (IST)
Subject: Re: [Megaco] Generic announcement package Id
To: "Mahesh" <mahesh@ccpu.com>
Date: Mon, 22 Nov 2004 14:33:10 +0530
Message-ID: <OFF6D1D6CA.6DD98D6C-ON65256F54.003199C2@hssworld.com>
X-MIMETrack: Serialize by Router on Dlfmail1/HSS(Release 6.0|September 26,
	2002) at 11/22/2004 02:33:26 PM
MIME-Version: 1.0
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0136815320=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

--===============0136815320==
Content-type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

DQoNCg0KDQoNCg0KSGksDQoNClRoZSBHZW5lcmljIGFubm91bmNlbWVudCBwYWNrYWdlIChhcyBk
ZWZpbmVkIGluIEgyNDguNykgaGFzIFBhY2thZ2VJRA0KMHgwMDFkLg0KVGhlIHVwZGF0ZWQgbGlz
dCBvZiBJQU5BIHJlZ2lzdGVyZWQgcGFja2FnZXMgKHdpdGggcGFja2FnZSBJRCkgY2FuIGJlIGZv
dW5kDQphdDoNCmh0dHA6Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVudHMvbWVnYWNvLWgyNDgNCg0K
UmVnYXJkcywNCkFiaGlzaGVrDQpIdWdoZXMgU29mdHdhcmUgU3lzdGVtcw0Kd3d3Lmhzc3dvcmxk
LmNvbQ0KDQoNCg0KDQoNCg0KIk1haGVzaCIgPG1haGVzaEBjY3B1LmNvbT5AaWV0Zi5vcmcgb24g
MTEvMjIvMjAwNCAxMToxODozMiBBTQ0KDQoNClNlbnQgYnk6ICAgIG1lZ2Fjby1ib3VuY2VzQGll
dGYub3JnDQoNCg0KVG86ICAgIDxtZWdhY29AaWV0Zi5vcmc+DQpjYzoNCg0KU3ViamVjdDogICAg
W01lZ2Fjb10gR2VuZXJpYyBhbm5vdW5jZW1lbnQgcGFja2FnZSBJZA0KDQoNCg0KDQoNCkhJLA0K
DQoNCg0KQ291bGQgeW91IHBsZWFzZSBsZXQgbWUga25vdyAsIHdoZXRoZXIgYW55IGNoYW5nZXMg
YXJlIHRoZXJlIGluIHRoZQ0KDQpQYWNrYWdlIElEIG9mIMKgR2VuZXJpYyBhbm5vdW5jZW1lbnQg
cGFja2FnZSAoYW4pLg0KDQpXaGV0aGVyIGl0IGlzIGhhdmluZyBhbiBpZCBvZsKgIOKAnDFk4oCd
wqDCoCBvciB3aGV0aGVyIHRoaXMgZ290IGNoYW5nZWQgLg0KDQoNCg0KDQoNCldpdGggdGhhbmtz
IGFuZCByZWdhcmRzDQoNCk1haGVzaA0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQpNZWdhY28gbWFpbGluZyBsaXN0DQpNZWdhY29AaWV0Zi5vcmcN
Cmh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21lZ2Fjbw0KDQoNCg0KKioq
KioqKioqKioqKioqKiogICAgSFNTLVVuY2xhc3NpZmllZCAgICAqKioqKioqKioqKioqDQoiUGxl
YXNlIG5vdGU6VGhlIGVtYWlsIGRvbWFpbiBvZiBIdWdoZXMgU29mdHdhcmUgU3lzdGVtcyBMdGQu
IGhhcyBiZWVuIGNoYW5nZWQgdG8gImhzc3dvcmxkLmNvbSIgZnJvbSBoc3MuaG5zLmNvbSINCg0K
IkRJU0NMQUlNRVI6IFRoaXMgbWVzc2FnZSBpcyBwcm9wcmlldGFyeSB0byBIdWdoZXMgU29mdHdh
cmUgU3lzdGVtcyBMaW1pdGVkIChIU1MpIGFuZCBpcyBpbnRlbmRlZCANCnNvbGVseSBmb3IgdGhl
IHVzZSBvZiB0aGUgaW5kaXZpZHVhbCB0byB3aG9tIGl0IGlzIGFkZHJlc3NlZC4gSXQgbWF5IGNv
bnRhaW4gIHByaXZpbGVnZWQgb3IgDQpjb25maWRlbnRpYWwgaW5mb3JtYXRpb24gYW5kIHNob3Vs
ZCBub3QgYmUgY2lyY3VsYXRlZCBvciB1c2VkIGZvciBhbnkgcHVycG9zZSBvdGhlciB0aGFuIGZv
ciANCndoYXQgaXQgaXMgaW50ZW5kZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgbWVzc2Fn
ZSBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgb3JpZ2luYXRvciANCmltbWVkaWF0ZWx5LiBJ
ZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCB5b3UgYXJlIG5vdGlmaWVkIHRo
YXQgeW91IGFyZSBzdHJpY3RseSANCnByb2hpYml0ZWQgZnJvbSB1c2luZywgY29weWluZywgYWx0
ZXJpbmcsIG9yIGRpc2Nsb3NpbmcgdGhlIGNvbnRlbnRzIG9mIHRoaXMgbWVzc2FnZS4gSFNTIA0K
YWNjZXB0cyBubyByZXNwb25zaWJpbGl0eSBmb3IgbG9zcyBvciBkYW1hZ2UgYXJpc2luZyBmcm9t
IHRoZSB1c2Ugb2YgdGhlIGluZm9ybWF0aW9uIHRyYW5zbWl0dGVkIA0KYnkgdGhpcyBlbWFpbCBp
bmNsdWRpbmcgZGFtYWdlIGZyb20gdmlydXMuIg0K


--===============0136815320==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0136815320==--


From megaco-bounces@ietf.org  Wed Nov 24 04:22:12 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02296
	for <megaco-archive@lists.ietf.org>; Wed, 24 Nov 2004 04:22:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWtJB-0002Ok-MU; Wed, 24 Nov 2004 04:19:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWt9w-00088i-Rz
	for megaco@megatron.ietf.org; Wed, 24 Nov 2004 04:09:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01618
	for <megaco@ietf.org>; Wed, 24 Nov 2004 04:09:54 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWtDa-0008PI-BR
	for megaco@ietf.org; Wed, 24 Nov 2004 04:13:54 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP id AE36634696A
	for <megaco@ietf.org>; Wed, 24 Nov 2004 01:09:06 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 08509-2785F74E;
	Wed, 24 Nov 2004 01:09:06 -0800
Received: from ccpu00179 (unknown [172.25.0.135])
	by smtp.ccpu.com (Postfix) with SMTP id 7236F34696A
	for <megaco@ietf.org>; Wed, 24 Nov 2004 01:09:05 -0800 (PST)
Message-ID: <003501c4d276$db87cae0$870019ac@ccpu00179>
From: "Geetha" <geetha@ccpu.com>
To: <megaco@ietf.org>
Date: Wed, 24 Nov 2004 14:42:18 -0800
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4942.400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4942.400
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.18;
	VDF: 6.28.0.89; host: smtp)
X-Spam-Score: 2.1 (++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [Megaco] Re: Extended DTMF packages
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1166847041=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1166847041==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0032_01C4D233.CC346F50"

This is a multi-part message in MIME format.

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

Hi,

The extended DTMF package(H.248.16 (11/2002)) adds the Extended DigitMap =
Completion Event. Is this event also a tone-id for playtone?

Pls clarify/confirm this.

Thanks & Rgds,
Geetha


------=_NextPart_000_0032_01C4D233.CC346F50
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.3819.300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The&nbsp;extended DTMF package(H.248.16 =
(11/2002))=20
adds the Extended DigitMap Completion Event. Is this event also a =
tone-id for=20
playtone?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Pls clarify/confirm this.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks &amp; Rgds,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Geetha</FONT></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0032_01C4D233.CC346F50--



--===============1166847041==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1166847041==--




From megaco-bounces@ietf.org  Wed Nov 24 04:34:15 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03096
	for <megaco-archive@lists.ietf.org>; Wed, 24 Nov 2004 04:34:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWtVq-0005ox-3c; Wed, 24 Nov 2004 04:32:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWtUq-0005Uc-Oi
	for megaco@megatron.ietf.org; Wed, 24 Nov 2004 04:31:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02987
	for <megaco@ietf.org>; Wed, 24 Nov 2004 04:31:30 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWtYf-0002O7-Kq
	for megaco@ietf.org; Wed, 24 Nov 2004 04:35:31 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAO9UwN06709
	for <megaco@ietf.org>; Wed, 24 Nov 2004 04:30:58 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XQMHLKMZ>; Wed, 24 Nov 2004 04:30:59 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536E2C165@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Geetha <geetha@ccpu.com>, megaco@ietf.org
Subject: RE: [Megaco] Re: Extended DTMF packages
Date: Wed, 24 Nov 2004 04:30:56 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

How, exactly, does one play an event as a signal?
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Geetha
Sent: Wednesday, November 24, 2004 5:42 PM
To: megaco@ietf.org
Subject: [Megaco] Re: Extended DTMF packages


Hi,
 
The extended DTMF package(H.248.16 (11/2002)) adds the Extended DigitMap
Completion Event. Is this event also a tone-id for playtone?
 
Pls clarify/confirm this.
 
Thanks & Rgds,
Geetha
 


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


From megaco-bounces@ietf.org  Wed Nov 24 06:37:31 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11677
	for <megaco-archive@lists.ietf.org>; Wed, 24 Nov 2004 06:37:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CWvQu-0007p8-7d; Wed, 24 Nov 2004 06:35:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWvPM-00077Y-3t
	for megaco@megatron.ietf.org; Wed, 24 Nov 2004 06:34:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11279
	for <megaco@ietf.org>; Wed, 24 Nov 2004 06:33:57 -0500 (EST)
From: bvswamy@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWvSx-0007Me-OX
	for megaco@ietf.org; Wed, 24 Nov 2004 06:37:59 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAOBU56p007119
	for <megaco@ietf.org>; Wed, 24 Nov 2004 17:00:05 +0530 (IST)
Received: from webmail.hss.hns.com (webmail.hss.hns.com [192.168.100.50])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iAOBU3xX007105;
	Wed, 24 Nov 2004 17:00:04 +0530 (IST)
In-Reply-To: <003501c4d276$db87cae0$870019ac@ccpu00179>
To: "Geetha" <geetha@ccpu.com>
Subject: Re: [Megaco] Re: Extended DTMF packages
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF9539B2D3.20916513-ON65256F56.003E587A-65256F56.0005B37E@hssworld.com>
Date: Wed, 24 Nov 2004 16:58:21 +0530
X-MIMETrack: S/MIME Sign by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/24/2004 06:32:16 AM,
	Serialize by Notes Client on B Venkat S.R Swamy/HSS(Release
	6.5|September 26, 2003) at 11/24/2004 06:32:16 AM,
	Serialize complete at 11/24/2004 06:32:16 AM,
	S/MIME Sign failed at 11/24/2004 06:32:16 AM: The cryptographic key was
	not found,
	Serialize by Router on WebMail/HSS(Release 6.5.1|January 21,
	2004) at 11/24/2004 04:58:25 PM,
	Serialize complete at 11/24/2004 04:58:25 PM
X-Spam-Score: 3.9 (+++)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0493531087=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multipart message in MIME format.
--===============0493531087==
Content-Type: multipart/alternative;
	boundary="=_alternative 0005B37765256F56_="

This is a multipart message in MIME format.
--=_alternative 0005B37765256F56_=
Content-Type: text/plain; charset="US-ASCII"


I think you are confused with other DTMF items(D0-DD) which are basically 
tones which can be both generated as well as detected on a endpoint,
whereas Digitmap completion event occurs whenever the digit dialling is 
over and MG has to report collected digits to MGC as per the digitmap, and 
hence this can never be a tone to be played on endpoint.


regards
B. Venkat S.R Swamy
Hughes Software Systems
www.hssworld.com






"Geetha" <geetha@ccpu.com> 
Sent by: megaco-bounces@ietf.org
11/25/2004 04:12 AM


To
<megaco@ietf.org>
cc

Subject
[Megaco] Re: Extended DTMF packages







Hi,
 
The extended DTMF package(H.248.16 (11/2002))  adds the Extended DigitMap 
Completion Event. Is this event also a tone-id for  playtone?
 
Pls clarify/confirm this.
 
Thanks & Rgds,
Geetha
 
_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco



***********************  HSS-Private   ***********************

"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
--=_alternative 0005B37765256F56_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">I think you are confused with other
DTMF items(D0-DD) which are basically tones which can be both generated
as well as detected on a endpoint,</font>
<br><font size=2 face="sans-serif">whereas Digitmap completion event occurs
whenever the digit dialling is over and MG has to report collected digits
to MGC as per the digitmap, and hence this can never be a tone to be played
on endpoint.</font>
<br>
<br>
<br><font size=2 face="sans-serif">regards</font>
<br><font size=2 face="sans-serif">B. Venkat S.R Swamy</font>
<br><font size=2 face="sans-serif">Hughes Software Systems</font>
<br><font size=2 face="sans-serif">www.hssworld.com</font>
<br>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Geetha&quot; &lt;geetha@ccpu.com&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: megaco-bounces@ietf.org</font>
<p><font size=1 face="sans-serif">11/25/2004 04:12 AM</font>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">&lt;megaco@ietf.org&gt;</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">[Megaco] Re: Extended DTMF
packages</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br>
<br><font size=2>Hi,</font>
<br><font size=3>&nbsp;</font>
<br><font size=2>The&nbsp;extended DTMF package(H.248.16 (11/2002)) &nbsp;adds
the Extended DigitMap Completion Event. Is this event also a tone-id for
&nbsp;playtone?</font>
<br><font size=3>&nbsp;</font>
<br><font size=2>Pls clarify/confirm this.</font>
<br><font size=3>&nbsp;</font>
<br><font size=2>Thanks &amp; Rgds,</font>
<br><font size=2>Geetha</font>
<br><font size=3>&nbsp;</font>
<br><font size=2><tt>_______________________________________________<br>
Megaco mailing list<br>
Megaco@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/megaco</tt></font>
<br>
<br><font size=2 face="sans-serif"><br>
<br>
*********************** &nbsp;HSS-Private &nbsp; ***********************</font>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre>"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
</pre></font></td></tr></table>
--=_alternative 0005B37765256F56_=--


--===============0493531087==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0493531087==--



From megaco-bounces@ietf.org  Wed Nov 24 22:17:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02467
	for <megaco-archive@lists.ietf.org>; Wed, 24 Nov 2004 22:17:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXA5Y-0005dR-96; Wed, 24 Nov 2004 22:14:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CX9xM-0004ZM-Ky
	for megaco@megatron.ietf.org; Wed, 24 Nov 2004 22:06:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01854
	for <megaco@ietf.org>; Wed, 24 Nov 2004 22:06:01 -0500 (EST)
Received: from ns2.nec.com.au ([147.76.180.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXA1L-0005h8-CF
	for megaco@ietf.org; Wed, 24 Nov 2004 22:10:12 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by ns2.nec.com.au (Postfix) with ESMTP id 735EB377EC
	for <megaco@ietf.org>; Thu, 25 Nov 2004 14:05:29 +1100 (EST)
Received: from ns2.nec.com.au ([127.0.0.1])
	by localhost (ns2.nec.com.au [127.0.0.1]) (amavisd-new,
	port 10024) with LMTP id 03937-01-87 for <megaco@ietf.org>;
	Thu, 25 Nov 2004 14:05:29 +1100 (EST)
Received: from smtp2.nec.com.au (smtp2.internal.nec.com.au [172.31.8.19])
	by ns2.nec.com.au (Postfix) with ESMTP id 62468377DF
	for <megaco@ietf.org>; Thu, 25 Nov 2004 14:05:29 +1100 (EST)
Received: from tns.neca.nec.com.au (localhost.localdomain [127.0.0.1])
	by smtp2.nec.com.au (8.12.8/8.12.8) with ESMTP id iAP35TAc006535
	for <megaco@ietf.org>; Thu, 25 Nov 2004 14:05:29 +1100
Received: from GWANGXP ([147.76.211.178])
	by tns.neca.nec.com.au (8.12.8/8.12.8) with SMTP id iAP35SvN000835
	for <megaco@ietf.org>; Thu, 25 Nov 2004 14:05:29 +1100
From: "Gillian Wang" <Gillian.Wang@nec.com.au>
To: <megaco@ietf.org>
Date: Thu, 25 Nov 2004 14:02:39 +1100
Message-ID: <MIELIEBFGIJGADHPKDMLOEHFCBAA.Gillian.Wang@nec.com.au>
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.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
In-Reply-To: <MIELIEBFGIJGADHPKDMLKECBCBAA.Gillian.Wang@nec.com.au>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Tone directions
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Dear Megaco members,

There are many tones specified under package/signals descriptions. Some of
them don't have directions (call progress tones), and others have
directions. My questions are below:

1/ Are all tones specified in call progress tones generator (H.248.1)
"external"?

2/ Are the directional signals/tones designed to be applied in the
post-answer stage?

3/ Can you please describe me the scenario on how the carrier dial tone
(H.248.27, carr/cdt) being used? If an MG receives a message to play
carr/cdt signal, does it mean that its direction has to be internal? Does it
also mean this MG has to apply it to the RTP steam? What message is the
other end MG supposed to receive from the MGC?

Thanks for your clarifications.

Regards
Gillian


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


From megaco-bounces@ietf.org  Thu Nov 25 00:11:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12339
	for <megaco-archive@lists.ietf.org>; Thu, 25 Nov 2004 00:11:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXBrp-0007Al-Tx; Thu, 25 Nov 2004 00:08:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXBqd-0006x1-CN
	for megaco@megatron.ietf.org; Thu, 25 Nov 2004 00:07:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11996
	for <megaco@ietf.org>; Thu, 25 Nov 2004 00:07:11 -0500 (EST)
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXBuS-00005Q-Ss
	for megaco@ietf.org; Thu, 25 Nov 2004 00:11:23 -0500
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by smtp.ccpu.com (Postfix) with ESMTP
	id 751713468C9; Wed, 24 Nov 2004 21:06:32 -0800 (PST)
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (VaMailArmor-2.0.1.16) id 30966-37A04122;
	Wed, 24 Nov 2004 21:06:32 -0800
Received: from ccpu00179 (unknown [172.25.0.135])
	by smtp.ccpu.com (Postfix) with SMTP
	id 521203468C9; Wed, 24 Nov 2004 21:06:30 -0800 (PST)
Message-ID: <004d01c4d31e$23afa610$870019ac@ccpu00179>
From: "Geetha" <geetha@ccpu.com>
To: <bvswamy@hssworld.com>
References: <OF9539B2D3.20916513-ON65256F56.003E587A-65256F56.0005B37E@hssworld.com>
Subject: Re: [Megaco] Re: Extended DTMF packages
Date: Thu, 25 Nov 2004 10:39:45 -0800
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4942.400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4942.400
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.18;
	VDF: 6.28.0.90; host: smtp)
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 578c2c9d0cb01ffe6e1ca36540edd070
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1574537933=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1574537933==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_004A_01C4D2DB.145F57C0"

This is a multi-part message in MIME format.

------=_NextPart_000_004A_01C4D2DB.145F57C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Sorry for the confusion.=20

Actually the doubt was this..
Whether the Extended DigitMap Completion Even defined in Extended DTMF =
package is also a tone-id for  the events Std, Ltd and Etd defined in =
Tone detection package?
The Enhanced DTMF package also adds an event Matched DigitMap Completion =
Event. Will this also be a tone-id for  the events Std, Ltd and Etd =
defined in Tone detection package?

Also note that the DTMF detection package which extends from the tonedet =
package adds the DTMF digits D0-DD to the toneid for the events Std, Ltd =
and Etd.

Thanks & Regards,
Geetha

  ----- Original Message -----=20
  From: bvswamy@hssworld.com=20
  To: Geetha=20
  Cc: megaco@ietf.org=20
  Sent: Wednesday, November 24, 2004 3:28 AM
  Subject: Re: [Megaco] Re: Extended DTMF packages



  I think you are confused with other DTMF items(D0-DD) which are =
basically tones which can be both generated as well as detected on a =
endpoint,=20
  whereas Digitmap completion event occurs whenever the digit dialling =
is over and MG has to report collected digits to MGC as per the =
digitmap, and hence this can never be a tone to be played on endpoint.=20


  regards=20
  B. Venkat S.R Swamy=20
  Hughes Software Systems=20
  www.hssworld.com=20





        "Geetha" <geetha@ccpu.com>=20
        Sent by: megaco-bounces@ietf.org=20
        11/25/2004 04:12 AM=20

       To <megaco@ietf.org> =20
              cc =20
              Subject [Megaco] Re: Extended DTMF packages=20

             =20

      =20




  Hi,=20
   =20
  The extended DTMF package(H.248.16 (11/2002))  adds the Extended =
DigitMap Completion Event. Is this event also a tone-id for  playtone?=20
   =20
  Pls clarify/confirm this.=20
   =20
  Thanks & Rgds,=20
  Geetha=20
   =20
  _______________________________________________
  Megaco mailing list
  Megaco@ietf.org
  https://www1.ietf.org/mailman/listinfo/megaco=20



  ***********************  HSS-Private   *********************** "Please =
note:The email domain of Hughes Software Systems Ltd. has been changed =
to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems =
Limited (HSS) and is intended=20
solely for the use of the individual to whom it is addressed. It may =
contain  privileged or=20
confidential information and should not be circulated or used for any =
purpose other than for=20
what it is intended. If you have received this message in error, please =
notify the originator=20
immediately. If you are not the intended recipient, you are notified =
that you are strictly=20
prohibited from using, copying, altering, or disclosing the contents of =
this message. HSS=20
accepts no responsibility for loss or damage arising from the use of the =
information transmitted=20
by this email including damage from virus."

      =20


------=_NextPart_000_004A_01C4D2DB.145F57C0
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.3819.300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Sorry for the confusion. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Actually the doubt was =
this..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Whether the Extended DigitMap =
Completion Even=20
defined in Extended DTMF package is also a tone-id for&nbsp;&nbsp;the =
events=20
Std, Ltd and Etd defined in Tone detection package?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The Enhanced DTMF package also adds an =
event=20
Matched DigitMap Completion Event. Will this also be a tone-id=20
for&nbsp;&nbsp;the events Std, Ltd and Etd defined in Tone detection=20
package?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Also note that the DTMF detection =
package which=20
extends&nbsp;from the tonedet&nbsp;package</FONT>&nbsp;<FONT =
face=3DArial=20
size=3D2>adds the DTMF digits D0-DD to the toneid for the events Std, =
Ltd and=20
Etd.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks &amp; Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Geetha</FONT></DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:bvswamy@hssworld.com"=20
  title=3Dbvswamy@hssworld.com>bvswamy@hssworld.com</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:geetha@ccpu.com"=20
  title=3Dgeetha@ccpu.com>Geetha</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
href=3D"mailto:megaco@ietf.org"=20
  title=3Dmegaco@ietf.org>megaco@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, November 24, =
2004 3:28=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [Megaco] Re: =
Extended DTMF=20
  packages</DIV>
  <DIV><BR></DIV><BR><FONT face=3Dsans-serif size=3D2>I think you are =
confused with=20
  other DTMF items(D0-DD) which are basically tones which can be both =
generated=20
  as well as detected on a endpoint,</FONT> <BR><FONT face=3Dsans-serif=20
  size=3D2>whereas Digitmap completion event occurs whenever the digit =
dialling is=20
  over and MG has to report collected digits to MGC as per the digitmap, =
and=20
  hence this can never be a tone to be played on endpoint.</FONT>=20
  <BR><BR><BR><FONT face=3Dsans-serif size=3D2>regards</FONT> <BR><FONT=20
  face=3Dsans-serif size=3D2>B. Venkat S.R Swamy</FONT> <BR><FONT =
face=3Dsans-serif=20
  size=3D2>Hughes Software Systems</FONT> <BR><FONT face=3Dsans-serif=20
  size=3D2>www.hssworld.com</FONT> <BR><BR><BR><BR><BR><BR>
  <TABLE width=3D"100%">
    <TBODY>
    <TR vAlign=3Dtop>
      <TD width=3D"40%"><FONT face=3Dsans-serif size=3D1><B>"Geetha"=20
        &lt;geetha@ccpu.com&gt;</B> </FONT><BR><FONT face=3Dsans-serif =
size=3D1>Sent=20
        by: megaco-bounces@ietf.org</FONT>=20
        <P><FONT face=3Dsans-serif size=3D1>11/25/2004 04:12 AM</FONT> =
<BR></P>
      <TD width=3D"59%">
        <TABLE width=3D"100%">
          <TBODY>
          <TR>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>To</FONT></DIV>
            <TD vAlign=3Dtop><FONT face=3Dsans-serif=20
              size=3D1>&lt;megaco@ietf.org&gt;</FONT>=20
          <TR>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>cc</FONT></DIV>
            <TD vAlign=3Dtop>
          <TR>
            <TD>
              <DIV align=3Dright><FONT face=3Dsans-serif =
size=3D1>Subject</FONT></DIV>
            <TD vAlign=3Dtop><FONT face=3Dsans-serif size=3D1>[Megaco] =
Re: Extended=20
              DTMF packages</FONT></TR></TBODY></TABLE><BR>
        <TABLE>
          <TBODY>
          <TR vAlign=3Dtop>
            <TD>
            =
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><BR><FONT=20
  size=3D2>Hi,</FONT> <BR><FONT size=3D3>&nbsp;</FONT> <BR><FONT=20
  size=3D2>The&nbsp;extended DTMF package(H.248.16 (11/2002)) &nbsp;adds =
the=20
  Extended DigitMap Completion Event. Is this event also a tone-id for=20
  &nbsp;playtone?</FONT> <BR><FONT size=3D3>&nbsp;</FONT> <BR><FONT =
size=3D2>Pls=20
  clarify/confirm this.</FONT> <BR><FONT size=3D3>&nbsp;</FONT> =
<BR><FONT=20
  size=3D2>Thanks &amp; Rgds,</FONT> <BR><FONT size=3D2>Geetha</FONT> =
<BR><FONT=20
  size=3D3>&nbsp;</FONT> <BR><FONT=20
  size=3D2><TT>_______________________________________________<BR>Megaco =
mailing=20
  =
list<BR>Megaco@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/megaco<=
/TT></FONT>=20
  <BR><BR><FONT face=3Dsans-serif =
size=3D2><BR><BR>***********************=20
  &nbsp;HSS-Private &nbsp; ***********************</FONT>=20
  <TABLE>
    <TBODY>
    <TR>
      <TD bgColor=3D#ffffff><FONT color=3D#000000><PRE>"Please note:The =
email domain of Hughes Software Systems Ltd. has been changed to =
"hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems =
Limited (HSS) and is intended=20
solely for the use of the individual to whom it is addressed. It may =
contain  privileged or=20
confidential information and should not be circulated or used for any =
purpose other than for=20
what it is intended. If you have received this message in error, please =
notify the originator=20
immediately. If you are not the intended recipient, you are notified =
that you are strictly=20
prohibited from using, copying, altering, or disclosing the contents of =
this message. HSS=20
accepts no responsibility for loss or damage arising from the use of the =
information transmitted=20
by this email including damage from virus."
</PRE></FONT></TD></TR></TBODY></TABLE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_004A_01C4D2DB.145F57C0--



--===============1574537933==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1574537933==--




From megaco-bounces@ietf.org  Thu Nov 25 02:23:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06955
	for <megaco-archive@lists.ietf.org>; Thu, 25 Nov 2004 02:23:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXDtY-00074s-LM; Thu, 25 Nov 2004 02:18:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXDmu-0003wx-Aa
	for megaco@megatron.ietf.org; Thu, 25 Nov 2004 02:11:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00173
	for <megaco@ietf.org>; Thu, 25 Nov 2004 02:11:31 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXDqv-0002kq-PF
	for megaco@ietf.org; Thu, 25 Nov 2004 02:15:42 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAP7AtK02912
	for <megaco@ietf.org>; Thu, 25 Nov 2004 02:10:55 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XQMHPH7G>; Thu, 25 Nov 2004 02:10:55 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536EC10E8@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Gillian Wang <Gillian.Wang@nec.com.au>, megaco@ietf.org
Subject: RE: [Megaco] Tone directions
Date: Thu, 25 Nov 2004 02:10:47 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Comments inline. [KJBII]

Kevin 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Gillian Wang
Sent: Wednesday, November 24, 2004 10:03 PM
To: megaco@ietf.org
Subject: [Megaco] Tone directions

Dear Megaco members,

There are many tones specified under package/signals descriptions. Some of
them don't have directions (call progress tones), and others have
directions. My questions are below:

1/ Are all tones specified in call progress tones generator (H.248.1)
"external"?

[KJBII] The default direction for all signals is toward the outside of the
context.  This corresponds to  "ext".

2/ Are the directional signals/tones designed to be applied in the
post-answer stage?

[KJBII] Signals are to be applied whenever the MGC requests them.

3/ Can you please describe me the scenario on how the carrier dial tone
(H.248.27, carr/cdt) being used? If an MG receives a message to play
carr/cdt signal, does it mean that its direction has to be internal? Does it
also mean this MG has to apply it to the RTP steam? What message is the
other end MG supposed to receive from the MGC?

[KJBII] As stated in the package, it is used to indicate service is being
provided by a carrier other than the default for the termination.  The MG
will apply the signal in whatever direction the MGC requests.  Signals
played in the internal direction would be played from the termination the
signal is applied to, toward all terminations in the context to which that
termination is currently connected per the Topology Descriptor.  I don't
think that any behavior for the far-end MG is implied or proscribed in this
case, as we are talking about application of a signal to a termination.

Thanks for your clarifications.

Regards
Gillian


_______________________________________________
Megaco mailing list
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-bounces@ietf.org  Thu Nov 25 02:24:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07169
	for <megaco-archive@lists.ietf.org>; Thu, 25 Nov 2004 02:24:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXDta-000768-Os; Thu, 25 Nov 2004 02:18:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXDqi-0005Yq-Iu
	for megaco@megatron.ietf.org; Thu, 25 Nov 2004 02:15:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03564
	for <megaco@ietf.org>; Thu, 25 Nov 2004 02:15:27 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXDuj-0002oZ-78
	for megaco@ietf.org; Thu, 25 Nov 2004 02:19:38 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAP7EtK02942
	for <megaco@ietf.org>; Thu, 25 Nov 2004 02:14:55 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XQMHP2GT>; Thu, 25 Nov 2004 02:14:55 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536EC10E9@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: Geetha <geetha@ccpu.com>, bvswamy@hssworld.com
Subject: RE: [Megaco] Re: Extended DTMF packages
Date: Thu, 25 Nov 2004 02:14:55 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

Completion events are not tones.  Therefore, it would not make any sense to
assign them ToneIDs.
 
Note that the completion event in E.6/H.248.1 does not have a ToneID.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Geetha
Sent: Thursday, November 25, 2004 1:40 PM
To: bvswamy@hssworld.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] Re: Extended DTMF packages


Hi,
 
Sorry for the confusion. 
 
Actually the doubt was this..
Whether the Extended DigitMap Completion Even defined in Extended DTMF
package is also a tone-id for  the events Std, Ltd and Etd defined in Tone
detection package?
The Enhanced DTMF package also adds an event Matched DigitMap Completion
Event. Will this also be a tone-id for  the events Std, Ltd and Etd defined
in Tone detection package?
 
Also note that the DTMF detection package which extends from the tonedet
package adds the DTMF digits D0-DD to the toneid for the events Std, Ltd and
Etd.
 
Thanks & Regards,
Geetha
 

----- Original Message ----- 
From: bvswamy@hssworld.com <mailto:bvswamy@hssworld.com>  
To: Geetha <mailto:geetha@ccpu.com>  
Cc: megaco@ietf.org <mailto:megaco@ietf.org>  
Sent: Wednesday, November 24, 2004 3:28 AM
Subject: Re: [Megaco] Re: Extended DTMF packages


I think you are confused with other DTMF items(D0-DD) which are basically
tones which can be both generated as well as detected on a endpoint, 
whereas Digitmap completion event occurs whenever the digit dialling is over
and MG has to report collected digits to MGC as per the digitmap, and hence
this can never be a tone to be played on endpoint. 


regards 
B. Venkat S.R Swamy 
Hughes Software Systems 
www.hssworld.com 






"Geetha" <geetha@ccpu.com> 
Sent by: megaco-bounces@ietf.org 


11/25/2004 04:12 AM 



To
<megaco@ietf.org> 

cc

Subject
[Megaco] Re: Extended DTMF packages	

		





Hi, 
  
The extended DTMF package(H.248.16 (11/2002))  adds the Extended DigitMap
Completion Event. Is this event also a tone-id for  playtone? 
  
Pls clarify/confirm this. 
  
Thanks & Rgds, 
Geetha 
  
_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco 



***********************  HSS-Private   *********************** 

"Please note:The email domain of Hughes Software Systems Ltd. has been
changed to "hssworld.com" from hss.hns.com"



"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended 

solely for the use of the individual to whom it is addressed. It may contain
privileged or 

confidential information and should not be circulated or used for any
purpose other than for 

what it is intended. If you have received this message in error, please
notify the originator 

immediately. If you are not the intended recipient, you are notified that
you are strictly 

prohibited from using, copying, altering, or disclosing the contents of this
message. HSS 

accepts no responsibility for loss or damage arising from the use of the
information transmitted 

by this email including damage from virus."




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


From megaco-bounces@ietf.org  Thu Nov 25 04:21:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19298
	for <megaco-archive@lists.ietf.org>; Thu, 25 Nov 2004 04:21:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXFji-0007Tv-H7; Thu, 25 Nov 2004 04:16:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXFam-0005GX-Ni
	for megaco@megatron.ietf.org; Thu, 25 Nov 2004 04:07:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18093
	for <megaco@ietf.org>; Thu, 25 Nov 2004 04:07:06 -0500 (EST)
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXFem-0005m0-HC
	for megaco@ietf.org; Thu, 25 Nov 2004 04:11:19 -0500
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0I7Q008RL9997C@szxga01-in.huawei.com> for
	megaco@ietf.org; Thu, 25 Nov 2004 17:05:34 +0800 (CST)
Received: from szxml02-in ([172.24.1.6])
	by szxga01-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTP id	<0I7Q0004E999BM@szxga01-in.huawei.com>
	formegaco@ietf.org; Thu, 25 Nov 2004 17:05:33 +0800 (CST)
Received: from r70036a ([10.78.228.159])
	by szxml02-in.huawei.com (iPlanet	Messaging Server 5.2 HotFix 1.25
	(built Mar3
	2004)) with ESMTPA id	<0I7Q00DZ899SF4@szxml02-in.huawei.com>; Thu,
	25 Nov 2004 17:05:52 +0800 (CST)
Date: Thu, 25 Nov 2004 17:09:21 +0800
From: Rajeev K R <rajeev@huawei.com>
Subject: RE: [Megaco] Re: Extended DTMF packages
In-reply-to: <004d01c4d31e$23afa610$870019ac@ccpu00179>
To: "'Geetha'" <geetha@ccpu.com>
Message-id: <006901c4d2ce$7352d200$9fe44e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-imss-version: 2.007
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 7118f330e2af0a096ba071c5e99ca10e
Cc: megaco@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1398226679=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1398226679==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_d2UYKKoJ+lKo+Y0vvS0AWQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_d2UYKKoJ+lKo+Y0vvS0AWQ)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

Hi,
As you have mentioned,  DTMF detection package adds the DTMF digits D0-DD to
the tone list 
for Std, Ltd and Etd events, but not the digit map completion event.
Digit map completion is an event and NOT an audio tone and hence this can
not be 
included in the tone list for the tone detection events.
Tone detection is intended to identify the tones that you "hear" on the
termination,
so it could be digits or call progress tones as defined by the extension
packages.
 
Rajeev
 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
Geetha
Sent: Friday, November 26, 2004 2:40 AM
To: bvswamy@hssworld.com
Cc: megaco@ietf.org
Subject: Re: [Megaco] Re: Extended DTMF packages


Hi,
 
Sorry for the confusion. 
 
Actually the doubt was this..
Whether the Extended DigitMap Completion Even defined in Extended DTMF
package is also a tone-id for  the events Std, Ltd and Etd defined in Tone
detection package?
The Enhanced DTMF package also adds an event Matched DigitMap Completion
Event. Will this also be a tone-id for  the events Std, Ltd and Etd defined
in Tone detection package?
 
Also note that the DTMF detection package which extends from the tonedet
package adds the DTMF digits D0-DD to the toneid for the events Std, Ltd and
Etd.
 
Thanks & Regards,
Geetha
 

----- Original Message ----- 
From: bvswamy@hssworld.com 
To: Geetha <mailto:geetha@ccpu.com>  
Cc: megaco@ietf.org 
Sent: Wednesday, November 24, 2004 3:28 AM
Subject: Re: [Megaco] Re: Extended DTMF packages



I think you are confused with other DTMF items(D0-DD) which are basically
tones which can be both generated as well as detected on a endpoint, 
whereas Digitmap completion event occurs whenever the digit dialling is over
and MG has to report collected digits to MGC as per the digitmap, and hence
this can never be a tone to be played on endpoint. 


regards 
B. Venkat S.R Swamy 
Hughes Software Systems 
www.hssworld.com 






"Geetha" <geetha@ccpu.com> 
Sent by: megaco-bounces@ietf.org 


11/25/2004 04:12 AM 



To
<megaco@ietf.org> 

cc

Subject
[Megaco] Re: Extended DTMF packages	

		





Hi, 
  
The extended DTMF package(H.248.16 (11/2002))  adds the Extended DigitMap
Completion Event. Is this event also a tone-id for  playtone? 
  
Pls clarify/confirm this. 
  
Thanks & Rgds, 
Geetha 
  
_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco 



***********************  HSS-Private   *********************** 

"Please note:The email domain of Hughes Software Systems Ltd. has been
changed to "hssworld.com" from hss.hns.com"



"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended 

solely for the use of the individual to whom it is addressed. It may contain
privileged or 

confidential information and should not be circulated or used for any
purpose other than for 

what it is intended. If you have received this message in error, please
notify the originator 

immediately. If you are not the intended recipient, you are notified that
you are strictly 

prohibited from using, copying, altering, or disclosing the contents of this
message. HSS 

accepts no responsibility for loss or damage arising from the use of the
information transmitted 

by this email including damage from virus."




--Boundary_(ID_d2UYKKoJ+lKo+Y0vvS0AWQ)
Content-type: text/html; charset=us-ascii
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=us-ascii">
<TITLE>Message</TITLE>

<META content="MSHTML 6.00.2800.1476" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=250334908-25112004><FONT face=Arial 
size=2>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=250334908-25112004><FONT face=Arial size=2>As you have 
mentioned, &nbsp;DTMF detection package <FONT face=Arial size=2>adds the DTMF 
digits D0-DD to the tone list </FONT></FONT></SPAN></DIV>
<DIV><SPAN class=250334908-25112004><FONT face=Arial size=2><FONT face=Arial 
size=2>for Std, Ltd and Etd events, </FONT></FONT></SPAN><SPAN 
class=250334908-25112004><FONT face=Arial size=2>but not the digit map 
completion event.</FONT></SPAN></DIV>
<DIV><SPAN class=250334908-25112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=250334908-25112004><FONT face=Arial color=#0000ff size=2>Digit map 
completion is an event&nbsp;and&nbsp;NOT an audio&nbsp;tone and hence 
this&nbsp;can not be </FONT></SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=250334908-25112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=250334908-25112004><FONT face=Arial color=#0000ff size=2>included in the 
tone list&nbsp;for the tone detection events.</FONT></SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=250334908-25112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=250334908-25112004>Tone detection is intended to identify the tones that 
you "hear" on the termination,</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=250334908-25112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=250334908-25112004>so it could be digits or call progress tones as defined 
by the extension packages.</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=250334908-25112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=250334908-25112004></SPAN></FONT></SPAN><SPAN 
class=250334908-25112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=250334908-25112004></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=250334908-25112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=250334908-25112004>Rajeev</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=250334908-25112004><FONT face=Arial color=#0000ff size=2><SPAN 
class=250334908-25112004></SPAN></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT 
  face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> 
  megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] <B>On Behalf Of 
  </B>Geetha<BR><B>Sent:</B> Friday, November 26, 2004 2:40 AM<BR><B>To:</B> 
  bvswamy@hssworld.com<BR><B>Cc:</B> megaco@ietf.org<BR><B>Subject:</B> Re: 
  [Megaco] Re: Extended DTMF packages<BR><BR></FONT></DIV>
  <DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Sorry for the confusion. </FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Actually the doubt was this..</FONT></DIV>
  <DIV><FONT face=Arial size=2>Whether the Extended DigitMap Completion Even 
  defined in Extended DTMF package is also a tone-id for&nbsp;&nbsp;the events 
  Std, Ltd and Etd defined in Tone detection package?</FONT></DIV>
  <DIV><FONT face=Arial size=2>The Enhanced DTMF package also adds an event 
  Matched DigitMap Completion Event. Will this also be a tone-id 
  for&nbsp;&nbsp;the events Std, Ltd and Etd defined in Tone detection 
  package?</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Also note that the DTMF detection package which 
  extends&nbsp;from the tonedet&nbsp;package</FONT>&nbsp;<FONT face=Arial 
  size=2>adds the DTMF digits D0-DD to the toneid for the events Std, Ltd and 
  Etd.</FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Thanks &amp; Regards,</FONT></DIV>
  <DIV><FONT face=Arial size=2>Geetha</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <BLOCKQUOTE 
  style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV 
    style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
    <A title=bvswamy@hssworld.com 
    href="mailto:bvswamy@hssworld.com">bvswamy@hssworld.com</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>To:</B> <A title=geetha@ccpu.com 
    href="mailto:geetha@ccpu.com">Geetha</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=megaco@ietf.org 
    href="mailto:megaco@ietf.org">megaco@ietf.org</A> </DIV>
    <DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, November 24, 2004 3:28 
    AM</DIV>
    <DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Megaco] Re: Extended DTMF 
    packages</DIV>
    <DIV><FONT face=Arial color=#0000ff size=2></FONT><BR></DIV><BR><FONT 
    face=sans-serif size=2>I think you are confused with other DTMF items(D0-DD) 
    which are basically tones which can be both generated as well as detected on 
    a endpoint,</FONT> <BR><FONT face=sans-serif size=2>whereas Digitmap 
    completion event occurs whenever the digit dialling is over and MG has to 
    report collected digits to MGC as per the digitmap, and hence this can never 
    be a tone to be played on endpoint.</FONT> <BR><BR><BR><FONT face=sans-serif 
    size=2>regards</FONT> <BR><FONT face=sans-serif size=2>B. Venkat S.R 
    Swamy</FONT> <BR><FONT face=sans-serif size=2>Hughes Software Systems</FONT> 
    <BR><FONT face=sans-serif size=2>www.hssworld.com</FONT> 
    <BR><BR><BR><BR><BR><BR>
    <TABLE width="100%">
      <TBODY>
      <TR vAlign=top>
        <TD width="40%"><FONT face=sans-serif size=1><B>"Geetha" 
          &lt;geetha@ccpu.com&gt;</B> </FONT><BR><FONT face=sans-serif 
          size=1>Sent by: megaco-bounces@ietf.org</FONT> 
          <P><FONT face=sans-serif size=1>11/25/2004 04:12 AM</FONT> <BR></P>
        <TD width="59%">
          <TABLE width="100%">
            <TBODY>
            <TR>
              <TD>
                <DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
              <TD vAlign=top><FONT face=sans-serif 
                size=1>&lt;megaco@ietf.org&gt;</FONT> 
            <TR>
              <TD>
                <DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
              <TD vAlign=top>
            <TR>
              <TD>
                <DIV align=right><FONT face=sans-serif 
                size=1>Subject</FONT></DIV>
              <TD vAlign=top><FONT face=sans-serif size=1>[Megaco] Re: 
                Extended DTMF packages</FONT></TD></TR></TBODY></TABLE><BR>
          <TABLE>
            <TBODY>
            <TR vAlign=top>
              <TD>
              <TD></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><BR><BR><BR><FONT 
    size=2>Hi,</FONT> <BR><FONT size=3>&nbsp;</FONT> <BR><FONT 
    size=2>The&nbsp;extended DTMF package(H.248.16 (11/2002)) &nbsp;adds the 
    Extended DigitMap Completion Event. Is this event also a tone-id for 
    &nbsp;playtone?</FONT> <BR><FONT size=3>&nbsp;</FONT> <BR><FONT size=2>Pls 
    clarify/confirm this.</FONT> <BR><FONT size=3>&nbsp;</FONT> <BR><FONT 
    size=2>Thanks &amp; Rgds,</FONT> <BR><FONT size=2>Geetha</FONT> <BR><FONT 
    size=3>&nbsp;</FONT> <BR><FONT 
    size=2><TT>_______________________________________________<BR>Megaco mailing 
    list<BR>Megaco@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/megaco</TT></FONT> 
    <BR><BR><FONT face=sans-serif size=2><BR><BR>*********************** 
    &nbsp;HSS-Private &nbsp; ***********************</FONT> 
    <TABLE>
      <TBODY>
      <TR>
        <TD bgColor=#ffffff><FONT color=#000000><PRE>"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."
</PRE></FONT></TD></TR></TBODY></TABLE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_d2UYKKoJ+lKo+Y0vvS0AWQ)--


--===============1398226679==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1398226679==--



From megaco-bounces@ietf.org  Thu Nov 25 05:21:35 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25065
	for <megaco-archive@lists.ietf.org>; Thu, 25 Nov 2004 05:21:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXGcD-0003Fv-87; Thu, 25 Nov 2004 05:12:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXGa1-0002Aw-Mw
	for megaco@megatron.ietf.org; Thu, 25 Nov 2004 05:10:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24340
	for <megaco@ietf.org>; Thu, 25 Nov 2004 05:10:23 -0500 (EST)
Received: from szsmtp.utstar.com.cn ([210.21.224.29])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXGe3-0007JK-O5
	for megaco@ietf.org; Thu, 25 Nov 2004 05:14:37 -0500
Received: from szmscwesley1 (sz-msc-wesley1.cn.utstarcom.com [172.19.17.155]
	(may be forged))
	by szsmtp.utstar.com.cn (8.11.6/8.11.1) with ESMTP id iAPA9qI10764;
	Thu, 25 Nov 2004 18:09:52 +0800
From: "wesley.wang" <wesley.wang@utstar.com>
To: <megaco@ietf.org>
Date: Thu, 25 Nov 2004 18:12:08 +0800
Message-ID: <JLEBLNCHJLCEGBKEMNJKOEBGCDAA.wesley.wang@utstar.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 2.5 (++)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: KellyJiang <kelly.jiang@utstar.com>
Subject: [Megaco] about servicechage with restart
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0208200660=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

--===============0208200660==
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGkgQWxsOg0KICAgIFRoZXJlIGlzIG9uZSBxdWVzdGlvbi4NCg0KICAgIFdlIGhhdmUgb25lIFRl
cm1pbmF0aW9ucyBpbiBidXN5IHN0YXR1cyh3aGljaCB3ZSBhcmUgdXNpbmcpLCBpbiBzb21lIHRp
bWUgaXQgY29tZXMgU2VydmljZUNoYW5nZSBSZXF1ZXN0IHdpdGggcmVzdGFydCBvZiB0aGlzIFRl
cm1pbmF0aW9uLiB3aGF0IHNob3VsZCB0aGUgc2VydmVyIGRvPw0KDQogICBzaG91bGQgaXQgcmVs
ZWFzZSBhbGwgdGhlIGNhbGwgcmVsYXRpdmUgd2l0aCB0aGlzIHRlcm1pbmF0aW9uPw0KDQogICBX
ZSBhcmUgdXNpbmcgb25lIE1lZGlhIGdhdGV3YXksIHdoZW4gaXQgZG9pbmcgaGFuZCBvdmVyIGlu
c2lkZSwgaXQgd2lsbCByZXBvcnQgYWxsIHRoZSBFMSByZXNvdXJjZSBTZXJ2aWNlQ2hhbmdlIHdp
dGggcmVzdGFydCBwYXJhbWV0ZXIsICBJcyB0aGlzIG5lc3Nlc2FyeT8NCg0KICAgQ2FuIFNlcnZl
ciBjb25zaWRlIHRoZSByZXNvdXJjZSBpcyBpbiBmcmVlIHN0YXRlIHdoZW4gcmVjdiBzZXJ2aWNl
Y2hhbmdlIHJlcXVlc3Qgd2l0aCByZXN0YXJ0IG1ldGhvZD8NCg0KVGhhbmtzLg0KDQpCUg==



--===============0208200660==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0208200660==--


From megaco-bounces@ietf.org  Thu Nov 25 06:05:30 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28825
	for <megaco-archive@lists.ietf.org>; Thu, 25 Nov 2004 06:05:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXHP5-0005x7-Fr; Thu, 25 Nov 2004 06:03:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXHOp-0005mb-P4
	for megaco@megatron.ietf.org; Thu, 25 Nov 2004 06:02:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28555
	for <megaco@ietf.org>; Thu, 25 Nov 2004 06:02:53 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXHSr-0008Rn-Do
	for megaco@ietf.org; Thu, 25 Nov 2004 06:07:07 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAPB2Kc15918
	for <megaco@ietf.org>; Thu, 25 Nov 2004 06:02:20 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XQMHP63K>; Thu, 25 Nov 2004 06:02:21 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536EC10ED@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "wesley.wang" <wesley.wang@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] about servicechage with restart
Date: Thu, 25 Nov 2004 06:02:20 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: KellyJiang <kelly.jiang@utstar.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

The MGC is responsible for cleaning up any terminations after it sends or
receives a ServiceChange command for those terminations.

The signalling related to a Failover of a Media Gateway to a secondary unit
is largely an implementation detail.  However, the MGC should consider the
states of the terminations unchanged unless the MG signals otherwise.

Kevin 

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
wesley.wang
Sent: Thursday, November 25, 2004 5:12 AM
To: megaco@ietf.org
Cc: KellyJiang
Subject: [Megaco] about servicechage with restart

Hi All:
    There is one question.

    We have one Terminations in busy status(which we are using), in some
time it comes ServiceChange Request with restart of this Termination. what
should the server do?

   should it release all the call relative with this termination?

   We are using one Media gateway, when it doing hand over inside, it will
report all the E1 resource ServiceChange with restart parameter,  Is this
nessesary?

   Can Server conside the resource is in free state when recv servicechange
request with restart method?

Thanks.

BR

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


From megaco-bounces@ietf.org  Thu Nov 25 20:51:54 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06362
	for <megaco-archive@lists.ietf.org>; Thu, 25 Nov 2004 20:51:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXVEo-0004kj-6N; Thu, 25 Nov 2004 20:49:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXV8O-0003Jc-JG
	for megaco@megatron.ietf.org; Thu, 25 Nov 2004 20:42:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05587
	for <megaco@ietf.org>; Thu, 25 Nov 2004 20:42:50 -0500 (EST)
Received: from szsmtp.utstar.com.cn ([210.21.224.29])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXVCY-0002b2-Hn
	for megaco@ietf.org; Thu, 25 Nov 2004 20:47:12 -0500
Received: from szmscwesley1 (sz-ssw-lemon.cn.utstarcom.com [172.19.17.155]
	(may be forged))
	by szsmtp.utstar.com.cn (8.11.6/8.11.1) with ESMTP id iAQ1gAI14870;
	Fri, 26 Nov 2004 09:42:10 +0800
From: "wesley.wang" <wesley.wang@utstar.com>
To: <megaco@ietf.org>
Subject: =?gb2312?B?tPC4tDogW01lZ2Fjb10gYWJvdXQgc2VydmljZWNoYWdlIHdpdGggcmVzdGE=?=
	=?gb2312?B?cnQ=?=
Date: Fri, 26 Nov 2004 09:44:26 +0800
Message-ID: <JLEBLNCHJLCEGBKEMNJKAEBJCDAA.wesley.wang@utstar.com>
MIME-Version: 1.0
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: <B258A372CEA20246A363BB86753DB536EC10ED@zrtphxm2>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 3.6 (+++)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
Cc: monty.wang@utstar.com, KellyJiang <kelly.jiang@utstar.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1034131358=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1034131358==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0046_01C4D39C.84C8D650"

This is a multi-part message in MIME format.

------=_NextPart_000_0046_01C4D39C.84C8D650
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

UkU6IFtNZWdhY29dIGFib3V0IHNlcnZpY2VjaGFnZSB3aXRoIHJlc3RhcnRUaGFua3MuIHN0aWxs
IEkgbSBhIGxpdHRsZSBjb25mdXNlZC4gDQpTdXBwb3NlIG9uZSBjYXNlIGJlbG93Og0KDQogICAg
V2UgaGVsZCBhbiBJU1VQIGNhbGwgd2hpY2ggbWFrZXMgVHJ1bmtUZXJtMS8xIGFuZCBJUFRlcm0x
MjM0IGluIENvbnRleHQxIE1nMS4gaW4gdGhpcyB0aW1lIHdlIHJlY2VpZXZlIGEgU2VydmljZUNo
YW5nZSBjb21tYW5kIGZyb20gTWcxIHdpdGggVGVybT1UcnVua1Rlcm0xLyogTWV0aG9yZD1SZXN0
YXJ0Lg0KDQogICAgd2hpY2ggd2F5IGlzIHRoZSBiZXN0IHRvIGhhbmRsZSB0aGlzIGJlbG93Pw0K
DQogICAgMTogV2UgbmVlZCBLZWVwICBUcnVua1Rlcm0xLzEgYW5kIElQVGVybTEyMzQgaW4gQ29u
dGV4dDEgc2luY2UgdGhlIG1ldGhvcmQgaXMgcmVzdGFydCBtZWFucyB0aGVzZSB0ZXJtcyBhcmUg
bm93IGluIEluU2VydmljZSBNb2RlLg0KDQogICAgMjogV2UgbmVlZCBSZWxlYXNlIElQVGVybTEy
MzQgYW5kIGFuZCBhbGwgdGhlIHJlbGF0aXZlIENvbnRyb2wgQmxvY2sgaW4gU2VydmVyLCANCiAg
ICAgICBubyBuZWVkIHJlbGVhc2UgVHJ1bmtUZXJtMS8xIHNpbmNlIGFmdGVyIFNlcnZpY2VDaGFu
Z2UgaXQgc2hvdWxkIGluIEZyZWUoSW5TZXJ2aWNlKSBtb2RlLg0KDQogICAgMzogV2UgbmVlZCBS
ZWxlYXNlIGJvdGggSVBUZXJtMTIzNCBhbmQgYW5kIFRydW5rVGVybTEvMSBhbmQgYWxsIHRoZSBy
ZWxhdGl2ZSBDb250cm9sIEJsb2NrIGluIFNlcnZlciBTaW5jZSB0aGUgVHJ1bmtUZXJtMS8xIHNo
b3VkbCBub3QgcmVwb3J0IFNlcnZpY2VDaGFuZ2UgV2l0aCByZXN0YXJ0IE1ldGhvcmQgaW4gSW5T
ZXJ2aWNlIFN0YXRlLiANCg0KICAgIDQ6IEFueSBPdGhlciBXYXk/DQoNCiAgICBUaGFua3MgYWxs
Lg0KICAtLS0tLdStyrzTyrz+LS0tLS0NCiAgt6K8/sjLOiBLZXZpbiBCb3lsZSBbbWFpbHRvOmti
b3lsZUBub3J0ZWxuZXR3b3Jrcy5jb21dDQogILeiy83KsbzkOiAyMDA0xOoxMdTCMjXI1SAxOTow
Mg0KICDK1bz+yMs6IHdlc2xleS53YW5nOyBtZWdhY29AaWV0Zi5vcmcNCiAgs63LzTogS2VsbHlK
aWFuZw0KICDW98ziOiBSRTogW01lZ2Fjb10gYWJvdXQgc2VydmljZWNoYWdlIHdpdGggcmVzdGFy
dA0KDQoNCiAgVGhlIE1HQyBpcyByZXNwb25zaWJsZSBmb3IgY2xlYW5pbmcgdXAgYW55IHRlcm1p
bmF0aW9ucyBhZnRlciBpdCBzZW5kcyBvciByZWNlaXZlcyBhIFNlcnZpY2VDaGFuZ2UgY29tbWFu
ZCBmb3IgdGhvc2UgdGVybWluYXRpb25zLg0KDQogIFRoZSBzaWduYWxsaW5nIHJlbGF0ZWQgdG8g
YSBGYWlsb3ZlciBvZiBhIE1lZGlhIEdhdGV3YXkgdG8gYSBzZWNvbmRhcnkgdW5pdCBpcyBsYXJn
ZWx5IGFuIGltcGxlbWVudGF0aW9uIGRldGFpbC4gIEhvd2V2ZXIsIHRoZSBNR0Mgc2hvdWxkIGNv
bnNpZGVyIHRoZSBzdGF0ZXMgb2YgdGhlIHRlcm1pbmF0aW9ucyB1bmNoYW5nZWQgdW5sZXNzIHRo
ZSBNRyBzaWduYWxzIG90aGVyd2lzZS4NCg0KICBLZXZpbiANCg0KICAtLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLSANCiAgRnJvbTogbWVnYWNvLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzptZWdh
Y28tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIHdlc2xleS53YW5nIA0KICBTZW50OiBU
aHVyc2RheSwgTm92ZW1iZXIgMjUsIDIwMDQgNToxMiBBTSANCiAgVG86IG1lZ2Fjb0BpZXRmLm9y
ZyANCiAgQ2M6IEtlbGx5SmlhbmcgDQogIFN1YmplY3Q6IFtNZWdhY29dIGFib3V0IHNlcnZpY2Vj
aGFnZSB3aXRoIHJlc3RhcnQgDQoNCiAgSGkgQWxsOiANCiAgICAgIFRoZXJlIGlzIG9uZSBxdWVz
dGlvbi4gDQoNCiAgICAgIFdlIGhhdmUgb25lIFRlcm1pbmF0aW9ucyBpbiBidXN5IHN0YXR1cyh3
aGljaCB3ZSBhcmUgdXNpbmcpLCBpbiBzb21lIHRpbWUgaXQgY29tZXMgU2VydmljZUNoYW5nZSBS
ZXF1ZXN0IHdpdGggcmVzdGFydCBvZiB0aGlzIFRlcm1pbmF0aW9uLiB3aGF0IHNob3VsZCB0aGUg
c2VydmVyIGRvPw0KDQogICAgIHNob3VsZCBpdCByZWxlYXNlIGFsbCB0aGUgY2FsbCByZWxhdGl2
ZSB3aXRoIHRoaXMgdGVybWluYXRpb24/IA0KDQogICAgIFdlIGFyZSB1c2luZyBvbmUgTWVkaWEg
Z2F0ZXdheSwgd2hlbiBpdCBkb2luZyBoYW5kIG92ZXIgaW5zaWRlLCBpdCB3aWxsIHJlcG9ydCBh
bGwgdGhlIEUxIHJlc291cmNlIFNlcnZpY2VDaGFuZ2Ugd2l0aCByZXN0YXJ0IHBhcmFtZXRlciwg
IElzIHRoaXMgbmVzc2VzYXJ5Pw0KDQogICAgIENhbiBTZXJ2ZXIgY29uc2lkZSB0aGUgcmVzb3Vy
Y2UgaXMgaW4gZnJlZSBzdGF0ZSB3aGVuIHJlY3Ygc2VydmljZWNoYW5nZSByZXF1ZXN0IHdpdGgg
cmVzdGFydCBtZXRob2Q/IA0KDQogIFRoYW5rcy4gDQoNCiAgQlIgDQo=

------=_NextPart_000_0046_01C4D39C.84C8D650
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPjxUSVRMRT5SRTogW01lZ2Fjb10gYWJvdXQgc2VydmljZWNoYWdl
IHdpdGggcmVzdGFydDwvVElUTEU+DQo8TUVUQSBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZSBjb250
ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9Z2IyMzEyIj4NCjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA2
LjAwLjI5MDAuMjUyMyIgbmFtZT1HRU5FUkFUT1I+PC9IRUFEPg0KPEJPRFk+DQo8RElWPjxGT05U
IGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjxTUEFOIGNsYXNzPTM4MDE4MjQwMS0yNjExMjAwND5UaGFu
a3MuIHN0aWxsIEkgDQptJm5ic3A7YSBsaXR0bGU8L1NQQU4+PC9GT05UPjxGT05UIGNvbG9yPSMw
MDAwZmYgc2l6ZT0yPjxTUEFOIA0KY2xhc3M9MzgwMTgyNDAxLTI2MTEyMDA0PiZuYnNwO2NvbmZ1
c2VkLiA8L1NQQU4+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBjb2xvcj0jMDAwMGZmIHNpemU9
Mj48U1BBTiBjbGFzcz0zODAxODI0MDEtMjYxMTIwMDQ+U3VwcG9zZSBvbmUgY2FzZSANCmJlbG93
OjwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjxT
UEFOIA0KY2xhc3M9MzgwMTgyNDAxLTI2MTEyMDA0PjwvU1BBTj48L0ZPTlQ+Jm5ic3A7PC9ESVY+
DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjxTUEFOIA0KY2xhc3M9MzgwMTgyNDAx
LTI2MTEyMDA0PiZuYnNwOyZuYnNwOyZuYnNwOyBXZSBoZWxkIGFuIElTVVAgY2FsbCANCndoaWNo
Jm5ic3A7bWFrZXMgVHJ1bmtUZXJtMS8xIGFuZCBJUFRlcm0xMjM0IGluIENvbnRleHQxIE1nMS4g
aW4gdGhpcyB0aW1lIHdlIA0KcmVjZWlldmUgYSBTZXJ2aWNlQ2hhbmdlIGNvbW1hbmQgZnJvbSBN
ZzEmbmJzcDt3aXRoIFRlcm09VHJ1bmtUZXJtMS8qIA0KTWV0aG9yZD1SZXN0YXJ0LjwvU1BBTj48
L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjxTUEFOIA0KY2xh
c3M9MzgwMTgyNDAxLTI2MTEyMDA0PjwvU1BBTj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxG
T05UIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjxTUEFOIA0KY2xhc3M9MzgwMTgyNDAxLTI2MTEyMDA0
PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO3doaWNoIHdheSBpcyB0aGUgYmVzdCB0byBoYW5kbGUg
DQp0aGlzIGJlbG93PzwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAw
ZmYgc2l6ZT0yPjxTUEFOIA0KY2xhc3M9MzgwMTgyNDAxLTI2MTEyMDA0PjwvU1BBTj48L0ZPTlQ+
Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjxTUEFOIA0KY2xh
c3M9MzgwMTgyNDAxLTI2MTEyMDA0PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzE6IFdlIA0KbmVl
ZCZuYnNwO0tlZXAmbmJzcDsmbmJzcDtUcnVua1Rlcm0xLzEgYW5kIElQVGVybTEyMzQgaW4gQ29u
dGV4dDEgc2luY2UgdGhlIA0KbWV0aG9yZCBpcyByZXN0YXJ0IG1lYW5zIHRoZXNlIHRlcm1zIGFy
ZSBub3cgaW4gSW5TZXJ2aWNlIA0KTW9kZS48L1NQQU4+PC9GT05UPjwvRElWPg0KPERJVj48Rk9O
VCBjb2xvcj0jMDAwMGZmIHNpemU9Mj48U1BBTiANCmNsYXNzPTM4MDE4MjQwMS0yNjExMjAwND48
L1NQQU4+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBjb2xvcj0jMDAwMGZmIHNpemU9
Mj48U1BBTiANCmNsYXNzPTM4MDE4MjQwMS0yNjExMjAwND4mbmJzcDsmbmJzcDsmbmJzcDsgMjog
V2UgbmVlZCBSZWxlYXNlIElQVGVybTEyMzQgYW5kIA0KYW5kIGFsbCB0aGUgcmVsYXRpdmUgQ29u
dHJvbCBCbG9jayBpbiBTZXJ2ZXIsIDwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNv
bG9yPSMwMDAwZmYgc2l6ZT0yPjxTUEFOIA0KY2xhc3M9MzgwMTgyNDAxLTI2MTEyMDA0PiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO25vIG5lZWQgDQpyZWxlYXNlIFRy
dW5rVGVybTEvMSBzaW5jZSBhZnRlciBTZXJ2aWNlQ2hhbmdlIGl0IHNob3VsZCBpbiBGcmVlKElu
U2VydmljZSkgDQptb2RlLjwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMw
MDAwZmYgc2l6ZT0yPjxTUEFOIGNsYXNzPTM4MDE4MjQwMS0yNjExMjAwND4NCjxESVY+PEZPTlQg
Y29sb3I9IzAwMDBmZiBzaXplPTI+PFNQQU4gDQpjbGFzcz0zODAxODI0MDEtMjYxMTIwMDQ+PC9T
UEFOPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9IzAwMDBmZiBzaXplPTI+
PFNQQU4gDQpjbGFzcz0zODAxODI0MDEtMjYxMTIwMDQ+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDM6IFdl
IG5lZWQgUmVsZWFzZSBib3RoIElQVGVybTEyMzQgDQphbmQmbmJzcDthbmQgVHJ1bmtUZXJtMS8x
IGFuZCBhbGwgdGhlIHJlbGF0aXZlIENvbnRyb2wgQmxvY2sgaW4gU2VydmVyIFNpbmNlIHRoZSAN
ClRydW5rVGVybTEvMSBzaG91ZGwgbm90IHJlcG9ydCBTZXJ2aWNlQ2hhbmdlIFdpdGggcmVzdGFy
dCZuYnNwO01ldGhvcmQgaW4gDQpJblNlcnZpY2UgU3RhdGUuJm5ic3A7PC9TUEFOPjwvRk9OVD48
L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9IzAwMDBmZiBzaXplPTI+PFNQQU4gDQpjbGFzcz0zODAx
ODI0MDEtMjYxMTIwMDQ+PC9TUEFOPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgY29s
b3I9IzAwMDBmZiBzaXplPTI+PFNQQU4gDQpjbGFzcz0zODAxODI0MDEtMjYxMTIwMDQ+Jm5ic3A7
Jm5ic3A7Jm5ic3A7IDQ6IEFueSBPdGhlciANCldheT88L1NQQU4+PC9GT05UPjwvRElWPg0KPERJ
Vj48Rk9OVCBjb2xvcj0jMDAwMGZmIHNpemU9Mj48U1BBTiANCmNsYXNzPTM4MDE4MjQwMS0yNjEx
MjAwND48L1NQQU4+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBjb2xvcj0jMDAwMGZm
IHNpemU9Mj48U1BBTiANCmNsYXNzPTM4MDE4MjQwMS0yNjExMjAwND4mbmJzcDsmbmJzcDsmbmJz
cDsgVGhhbmtzIA0KYWxsLjwvU1BBTj48L0ZPTlQ+PC9ESVY+PC9TUEFOPjwvRk9OVD48L0RJVj4N
CjxCTE9DS1FVT1RFIGRpcj1sdHIgc3R5bGU9Ik1BUkdJTi1SSUdIVDogMHB4Ij4NCiAgPERJViBj
bGFzcz1PdXRsb29rTWVzc2FnZUhlYWRlciBkaXI9bHRyIGFsaWduPWxlZnQ+PEZPTlQgDQogIHNp
emU9Mj4tLS0tLdStyrzTyrz+LS0tLS08QlI+PEI+t6K8/sjLOjwvQj4gS2V2aW4gQm95bGUgDQog
IFttYWlsdG86a2JveWxlQG5vcnRlbG5ldHdvcmtzLmNvbV08QlI+PEI+t6LLzcqxvOQ6PC9CPiAy
MDA0xOoxMdTCMjXI1SANCiAgMTk6MDI8QlI+PEI+ytW8/sjLOjwvQj4gd2VzbGV5Lndhbmc7IG1l
Z2Fjb0BpZXRmLm9yZzxCUj48Qj6zrcvNOjwvQj4gDQogIEtlbGx5Smlhbmc8QlI+PEI+1vfM4jo8
L0I+IFJFOiBbTWVnYWNvXSBhYm91dCBzZXJ2aWNlY2hhZ2Ugd2l0aCANCiAgcmVzdGFydDxCUj48
QlI+PC9GT05UPjwvRElWPg0KICA8UD48Rk9OVCBzaXplPTI+VGhlIE1HQyBpcyByZXNwb25zaWJs
ZSBmb3IgY2xlYW5pbmcgdXAgYW55IHRlcm1pbmF0aW9ucyBhZnRlciANCiAgaXQgc2VuZHMgb3Ig
cmVjZWl2ZXMgYSBTZXJ2aWNlQ2hhbmdlIGNvbW1hbmQgZm9yIHRob3NlIA0KdGVybWluYXRpb25z
LjwvRk9OVD48L1A+DQogIDxQPjxGT05UIHNpemU9Mj5UaGUgc2lnbmFsbGluZyByZWxhdGVkIHRv
IGEgRmFpbG92ZXIgb2YgYSBNZWRpYSBHYXRld2F5IHRvIGEgDQogIHNlY29uZGFyeSB1bml0IGlz
IGxhcmdlbHkgYW4gaW1wbGVtZW50YXRpb24gZGV0YWlsLiZuYnNwOyBIb3dldmVyLCB0aGUgTUdD
IA0KICBzaG91bGQgY29uc2lkZXIgdGhlIHN0YXRlcyBvZiB0aGUgdGVybWluYXRpb25zIHVuY2hh
bmdlZCB1bmxlc3MgdGhlIE1HIHNpZ25hbHMgDQogIG90aGVyd2lzZS48L0ZPTlQ+PC9QPg0KICA8
UD48Rk9OVCBzaXplPTI+S2V2aW4gPC9GT05UPjwvUD4NCiAgPFA+PEZPTlQgc2l6ZT0yPi0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tPC9GT05UPiA8QlI+PEZPTlQgc2l6ZT0yPkZyb206IA0KICBt
ZWdhY28tYm91bmNlc0BpZXRmLm9yZyBbPEEgDQogIGhyZWY9Im1haWx0bzptZWdhY28tYm91bmNl
c0BpZXRmLm9yZyI+bWFpbHRvOm1lZ2Fjby1ib3VuY2VzQGlldGYub3JnPC9BPl0gT24gDQogIEJl
aGFsZiBPZiB3ZXNsZXkud2FuZzwvRk9OVD4gPEJSPjxGT05UIHNpemU9Mj5TZW50OiBUaHVyc2Rh
eSwgTm92ZW1iZXIgMjUsIA0KICAyMDA0IDU6MTIgQU08L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+
VG86IG1lZ2Fjb0BpZXRmLm9yZzwvRk9OVD4gPEJSPjxGT05UIA0KICBzaXplPTI+Q2M6IEtlbGx5
Smlhbmc8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+U3ViamVjdDogW01lZ2Fjb10gYWJvdXQgDQog
IHNlcnZpY2VjaGFnZSB3aXRoIHJlc3RhcnQ8L0ZPTlQ+IDwvUD4NCiAgPFA+PEZPTlQgc2l6ZT0y
PkhpIEFsbDo8L0ZPTlQ+IDxCUj48Rk9OVCBzaXplPTI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IFRoZXJl
IGlzIA0KICBvbmUgcXVlc3Rpb24uPC9GT05UPiA8L1A+DQogIDxQPjxGT05UIHNpemU9Mj4mbmJz
cDsmbmJzcDsmbmJzcDsgV2UgaGF2ZSBvbmUgVGVybWluYXRpb25zIGluIGJ1c3kgDQogIHN0YXR1
cyh3aGljaCB3ZSBhcmUgdXNpbmcpLCBpbiBzb21lIHRpbWUgaXQgY29tZXMgU2VydmljZUNoYW5n
ZSBSZXF1ZXN0IHdpdGggDQogIHJlc3RhcnQgb2YgdGhpcyBUZXJtaW5hdGlvbi4gd2hhdCBzaG91
bGQgdGhlIHNlcnZlciBkbz88L0ZPTlQ+PC9QPg0KICA8UD48Rk9OVCBzaXplPTI+Jm5ic3A7Jm5i
c3A7IHNob3VsZCBpdCByZWxlYXNlIGFsbCB0aGUgY2FsbCByZWxhdGl2ZSB3aXRoIHRoaXMgDQog
IHRlcm1pbmF0aW9uPzwvRk9OVD4gPC9QPg0KICA8UD48Rk9OVCBzaXplPTI+Jm5ic3A7Jm5ic3A7
IFdlIGFyZSB1c2luZyBvbmUgTWVkaWEgZ2F0ZXdheSwgd2hlbiBpdCBkb2luZyANCiAgaGFuZCBv
dmVyIGluc2lkZSwgaXQgd2lsbCByZXBvcnQgYWxsIHRoZSBFMSByZXNvdXJjZSBTZXJ2aWNlQ2hh
bmdlIHdpdGggDQogIHJlc3RhcnQgcGFyYW1ldGVyLCZuYnNwOyBJcyB0aGlzIG5lc3Nlc2FyeT88
L0ZPTlQ+PC9QPg0KICA8UD48Rk9OVCBzaXplPTI+Jm5ic3A7Jm5ic3A7IENhbiBTZXJ2ZXIgY29u
c2lkZSB0aGUgcmVzb3VyY2UgaXMgaW4gZnJlZSBzdGF0ZSANCiAgd2hlbiByZWN2IHNlcnZpY2Vj
aGFuZ2UgcmVxdWVzdCB3aXRoIHJlc3RhcnQgbWV0aG9kPzwvRk9OVD4gPC9QPg0KICA8UD48Rk9O
VCBzaXplPTI+VGhhbmtzLjwvRk9OVD4gPC9QPg0KICA8UD48Rk9OVCBzaXplPTI+QlI8L0ZPTlQ+
IDwvUD48L0JMT0NLUVVPVEU+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_0046_01C4D39C.84C8D650--



--===============1034131358==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1034131358==--




From megaco-bounces@ietf.org  Fri Nov 26 10:48:49 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21261
	for <megaco-archive@lists.ietf.org>; Fri, 26 Nov 2004 10:48:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CXi58-0000FZ-Kg; Fri, 26 Nov 2004 10:32:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXhrH-0000JF-Ql
	for megaco@megatron.ietf.org; Fri, 26 Nov 2004 10:18:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18613
	for <megaco@ietf.org>; Fri, 26 Nov 2004 03:38:40 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXbh2-0002a0-Gv
	for megaco@ietf.org; Fri, 26 Nov 2004 03:43:04 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAQ8c6x17337
	for <megaco@ietf.org>; Fri, 26 Nov 2004 03:38:06 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XQMHT6K4>; Fri, 26 Nov 2004 03:38:06 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536EC11A7@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "wesley.wang" <wesley.wang@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] about servicechage with restart
Date: Fri, 26 Nov 2004 03:38:09 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: monty.wang@utstar.com, KellyJiang <kelly.jiang@utstar.com>
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

There is no one answer.  The actions the MGC takes depends also upon the
ServiceChangeReason.  Note that it is entirely possible that the MGC could
Subtract the physical term, then add it back to the context.  It all depends
upon the implementation.
 
Kevin


  _____  

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
wesley.wang
Sent: Thursday, November 25, 2004 8:44 PM
To: megaco@ietf.org
Cc: monty.wang@utstar.com; KellyJiang
Subject: ??: [Megaco] about servicechage with restart


Thanks. still I m a little confused. 
Suppose one case below:
 
    We held an ISUP call which makes TrunkTerm1/1 and IPTerm1234 in Context1
Mg1. in this time we receieve a ServiceChange command from Mg1 with
Term=TrunkTerm1/* Methord=Restart.
 
    which way is the best to handle this below?
 
    1: We need Keep  TrunkTerm1/1 and IPTerm1234 in Context1 since the
methord is restart means these terms are now in InService Mode.
 
    2: We need Release IPTerm1234 and and all the relative Control Block in
Server, 
       no need release TrunkTerm1/1 since after ServiceChange it should in
Free(InService) mode.

 
    3: We need Release both IPTerm1234 and and TrunkTerm1/1 and all the
relative Control Block in Server Since the TrunkTerm1/1 shoudl not report
ServiceChange With restart Methord in InService State. 
 
    4: Any Other Way?
 
    Thanks all.

-----原始邮件-----
发件人: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
发送时间: 2004年11月25日 19:02
收件人: wesley.wang; megaco@ietf.org
抄送: KellyJiang
主题: RE: [Megaco] about servicechage with restart



The MGC is responsible for cleaning up any terminations after it sends or
receives a ServiceChange command for those terminations.

The signalling related to a Failover of a Media Gateway to a secondary unit
is largely an implementation detail.  However, the MGC should consider the
states of the terminations unchanged unless the MG signals otherwise.

Kevin 

-----Original Message----- 
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org
<mailto:megaco-bounces@ietf.org> ] On Behalf Of wesley.wang 
Sent: Thursday, November 25, 2004 5:12 AM 
To: megaco@ietf.org 
Cc: KellyJiang 
Subject: [Megaco] about servicechage with restart 

Hi All: 
    There is one question. 

    We have one Terminations in busy status(which we are using), in some
time it comes ServiceChange Request with restart of this Termination. what
should the server do?

   should it release all the call relative with this termination? 

   We are using one Media gateway, when it doing hand over inside, it will
report all the E1 resource ServiceChange with restart parameter,  Is this
nessesary?

   Can Server conside the resource is in free state when recv servicechange
request with restart method? 

Thanks. 

BR 


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


From megaco-bounces@ietf.org  Sat Nov 27 20:56:13 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08999
	for <megaco-archive@lists.ietf.org>; Sat, 27 Nov 2004 20:56:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYECR-0001b2-QN; Sat, 27 Nov 2004 20:50:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXGPv-0000Mq-O2
	for megaco@megatron.ietf.org; Thu, 25 Nov 2004 04:59:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22808
	for <megaco@ietf.org>; Thu, 25 Nov 2004 04:59:57 -0500 (EST)
Received: from szsmtp.utstar.com.cn ([210.21.224.29])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXGTy-00074N-JE
	for megaco@ietf.org; Thu, 25 Nov 2004 05:04:11 -0500
Received: from szmscwesley1 (sz-08-gavinguo [172.19.17.155] (may be forged))
	by szsmtp.utstar.com.cn (8.11.6/8.11.1) with ESMTP id iAP9xMI09559
	for <megaco@ietf.org>; Thu, 25 Nov 2004 17:59:22 +0800
From: "wesley.wang" <wesley.wang@utstar.com>
To: <megaco@ietf.org>
Date: Thu, 25 Nov 2004 18:01:39 +0800
Message-ID: <JLEBLNCHJLCEGBKEMNJKEEBGCDAA.wesley.wang@utstar.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 2.5 (++)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
X-Mailman-Approved-At: Sat, 27 Nov 2004 20:50:03 -0500
Subject: [Megaco] about servicechage with restart
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1928423273=="
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

--===============1928423273==
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGkgQWxsOg0KICAgIFRoZXJlIGlzIG9uZSBxdWVzdGlvbi4NCg0KICAgIFdlIGhhdmUgb25lIFRl
cm1pbmF0aW9ucyBpbiBidXN5IHN0YXR1cyh3aGljaCB3ZSBhcmUgdXNpbmcpLCBpbiBzb21lIHRp
bWUgaXQgY29tZXMgU2VydmljZUNoYW5nZSBSZXF1ZXN0IHdpdGggcmVzdGFydCBvZiB0aGlzIFRl
cm1pbmF0aW9uLiB3aGF0IHNob3VsZCB0aGUgc2VydmVyIGRvPw0KDQogICBzaG91bGQgaXQgcmVs
ZWFzZSBhbGwgdGhlIGNhbGwgcmVsYXRpdmUgd2l0aCB0aGlzIHRlcm1pbmF0aW9uPw0KDQogICBX
ZSBhcmUgdXNpbmcgb25lIE1lZGlhIGdhdGV3YXksIHdoZW4gaXQgZG9pbmcgaGFuZCBvdmVyIGlu
c2lkZSwgaXQgd2lsbCByZXBvcnQgYWxsIHRoZSBFMSByZXNvdXJjZSBTZXJ2aWNlQ2hhbmdlIHdp
dGggcmVzdGFydCBwYXJhbWV0ZXIsICBJcyB0aGlzIG5lc3Nlc2FyeT8NCg0KICAgQ2FuIFNlcnZl
ciBjb25zaWRlIHRoZSByZXNvdXJjZSBpcyBpbiBmcmVlIHN0YXRlIHdoZW4gcmVjdiBzZXJ2aWNl
Y2hhbmdlIHJlcXVlc3Qgd2l0aCByZXN0YXJ0IG1ldGhvZD8NCg0KVGhhbmtzLg0KDQpCUg==



--===============1928423273==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1928423273==--


From megaco-bounces@ietf.org  Mon Nov 29 01:04:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02241
	for <megaco-archive@lists.ietf.org>; Mon, 29 Nov 2004 01:04:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CYed1-0001tJ-Kt; Mon, 29 Nov 2004 01:03:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CYeYo-0001Ge-CX
	for megaco@megatron.ietf.org; Mon, 29 Nov 2004 00:58:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01845
	for <megaco@ietf.org>; Mon, 29 Nov 2004 00:58:51 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYede-00006i-Qf
	for megaco@ietf.org; Mon, 29 Nov 2004 01:03:55 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id iAT5wLI27177
	for <megaco@ietf.org>; Mon, 29 Nov 2004 00:58:21 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XQM2A0R2>; Mon, 29 Nov 2004 00:58:21 -0500
Message-ID: <B258A372CEA20246A363BB86753DB536EC13FD@zrtphxm2>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "wesley.wang" <wesley.wang@utstar.com>, megaco@ietf.org
Subject: RE: [Megaco] about servicechage with restart
Date: Mon, 29 Nov 2004 00:58:18 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Sender: megaco-bounces@ietf.org
Errors-To: megaco-bounces@ietf.org

What the MGC does is completely within its domain.  If the termination
restarted, I assume the termination would need to be subtracted for any
context it is in, but that is really dependent upon your application.

Note that there is no "call" in H.248.  Terminations are grouped together in
contexts.  One or more contests might constitute the common ides of a
"call", but then again it may not.

The MG may send ServiceChanges whenever it likes.  I don't know that it is
necessary for it to do so on a Failover (Handoff is for redundant takeover
in MGCs, not MGs) -- but again, it would depend upon the application and
what the terminations require after the Failover.

The state of the terminations is dependent upon BOTH the ServiceChangeMethod
and the ServiceChangeReason.  The MGC must consider both when deciding if
the terminations have retained any state.  Note that Reason is MANDATORY in
ServiceChange commands.

Kevin

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of
wesley.wang
Sent: Thursday, November 25, 2004 5:02 AM
To: megaco@ietf.org
Subject: [Megaco] about servicechage with restart

Hi All:
    There is one question.

    We have one Terminations in busy status(which we are using), in some
time it comes ServiceChange Request with restart of this Termination. what
should the server do?

   should it release all the call relative with this termination?

   We are using one Media gateway, when it doing hand over inside, it will
report all the E1 resource ServiceChange with restart parameter,  Is this
nessesary?

   Can Server conside the resource is in free state when recv servicechange
request with restart method?

Thanks.

BR

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


