
From karavelaschris@gmail.com  Thu Jun  4 07:49:03 2009
Return-Path: <karavelaschris@gmail.com>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 394893A6D67 for <megaco@core3.amsl.com>; Thu,  4 Jun 2009 07:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dc8Z18DJDb8g for <megaco@core3.amsl.com>; Thu,  4 Jun 2009 07:49:02 -0700 (PDT)
Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by core3.amsl.com (Postfix) with ESMTP id B7CAB3A6D11 for <megaco@ietf.org>; Thu,  4 Jun 2009 07:48:43 -0700 (PDT)
Received: by bwz9 with SMTP id 9so797693bwz.37 for <megaco@ietf.org>; Thu, 04 Jun 2009 07:48:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=b58oVD944199ai9GmKlw3MBkiiyIwnSb4KvO5LgUmKk=; b=TAsQxcg5l0LrSO05apVZlLyNHJbPJHamTnpbmIDVjdkM5jgneB848hMPTJdpInm9zy 5SnVadsPS7eiswdcg6HtT+l1sR3MQI0lWPgOic9T9j3M1xa9nTN9dXzw4ioetABshi9W w2GH3fpa9NBdMOo6Q2V5PHs9U2jWtzCK8cKMI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=K8b8A24Ta739kKb4cniU+Cbx/Ln1MDBiyNApKqXtPDhOXstQtvgJggUc/kFgKMKlPR HjrU+Ifx8kOvtvWtUX6HPVwF1ejX5jQoBEKhBHK7CYkY40rxdz8FWflFicCEi7SV+H9u m/qM21nupgjP8dlcEyqm/xdvHDSyo0sNfk5WI=
MIME-Version: 1.0
Received: by 10.103.168.12 with SMTP id v12mr1437755muo.130.1244126922273;  Thu, 04 Jun 2009 07:48:42 -0700 (PDT)
Date: Thu, 4 Jun 2009 17:48:42 +0300
Message-ID: <56512cde0906040748w57103140va929bde3a2ab447b@mail.gmail.com>
From: Karavelas Christos <karavelaschris@gmail.com>
To: megaco@ietf.org
Content-Type: multipart/alternative; boundary=0016367ed50841f433046b86df1e
Subject: [Megaco] Failed Reply to a command of an H.248 Transaction Request
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 14:49:03 -0000

--0016367ed50841f433046b86df1e
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hello,

*A. According to H.248.1 V1/2/3, RFC 3525 Chapter 8 =93Transactions=94:*

=93=85.

Transactions guarantee ordered Command processing.
That is, Commands within a Transaction are executed sequentially

.=85

At the first failing Command in a Transaction,
processing of the remaining Commands in that Transaction stops.

=85

A TransactionReply includes the results for all of the Commands in
the corresponding TransactionRequest.  The TransactionReply includes

the return values for the Commands that were executed successfully,
and the Command and error descriptor for any Command that failed.=94

*

**and the Implementors Guide for H.248 V2 Chapter 6.32.1 =938 Transaction*


which is mentioning the use of a wildcarded TerminationID in a TransactionR=
eply.

*

When a problem occurs with the addition of the ephemeral termination,
the reply below is valid for the corresponding Transaction Request:

*

T=3D564{C=3D${A=3Dal/1/1/25{M{O{MO=3D
SR,RV=3DOFF,RG=3DOFF}},E=3D353{al/on{strict=3Dexact},al/of{strict=3Dexact},=
al/fl},SG{}},
                 A=3D${M{O{MO=3DIN,RV=3DOFF,RG=3DOFF},L{=85=85..}, R{=85=85=
.}}}}}

Reply=3D564{Context=3D52{Add=3Dal/1/1/25,Add=3D${Error=3D500{"Error creatin=
g
Stream"}}}}

The reply above means that the addition of the physical termination is
successful resulting that the
created context is included in the reply and the addition of the ephemeral
termination by the Access Gateway
was unsuccessful due to for example lack of resources or to Access Gateway
internal error.

 Is that reply according to the above standards?

*B. I**t is noticed that some MGCs have a different behavior in relation to
accept the above reply*

*as described below:*

*B1. MGC does not support the =93ADD=3D$=94 in the failed transaction comma=
nd
reply from AGW to the above request:*

MGC expects that the =93ADD=3D$=94 must *not* be specified in the failed
transaction command reply, instead it expects:

Reply=3D564{Context=3D52{Add=3Dal/1/1/25,*Error=3D500{"Error creating Strea=
m"}*}}

 Is the above syntax of the reply valid and therefore acceptable?

*B2. MGC expects =93Context=3D*-*=93 in the failed transaction reply from A=
GW to
the above request*
MGC expects =93Context=3D-=93 in the failed transaction reply from AGW assu=
ming
also that the physical termination
was not added to a context as a result of the ephemeral termination additio=
n
failure:

Reply=3D564{*Context=3D**-*{Add=3Dal/1/1/25,Error=3D500{"Error creating Str=
eam"}}}

Is the above assumption by MGC and the syntax of the Transaction Reply vali=
d
and therefore acceptable?

Could you please reply to the above three questions as this is important fo=
r
our design?

Regards,

Chris

--0016367ed50841f433046b86df1e
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size: 1=
0pt; font-family: Arial; color: black;" lang=3D"EN-US">Hello,</span></font>



<p><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size=
: 10pt; font-family: Arial; color: black;" lang=3D"EN-US"></span></font><b>=
<font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size: 1=
0pt; font-family: Arial; color: black; font-weight: bold;" lang=3D"EN-US">A=
. According
to H.248.1 V1/2/3, RFC 3525 Chapter 8 =93Transactions=94:</span></font></b>=
</p>

<p><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size=
: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB">=93=85.</span></f=
ont></p>

<pre><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-si=
ze: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB">Transactions gu=
arantee ordered Command processing.<br>That is, Commands within a Transacti=
on are executed sequentially<br>
<br>.</span></font><font color=3D"black" face=3D"Arial" size=3D"2"><span st=
yle=3D"font-size: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB">=
=85</span></font></pre>



<pre><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-si=
ze: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB">At the first fa=
iling Command in a Transaction,<br>processing of the remaining Commands in =
that Transaction stops.</span></font><font color=3D"black" face=3D"Arial" s=
ize=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; color: black;=
" lang=3D"EN-GB"><br>
<br>=85</span></font></pre>



<pre><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-si=
ze: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB">A TransactionRe=
ply includes the results for all of the Commands in <br>the corresponding T=
ransactionRequest.=A0 The TransactionReply includes<br>
<br>the return values for the Commands that were executed successfully,<br>=
and the Command and error descriptor for any Command that failed.=94</span>=
</font></pre><pre><font color=3D"black" face=3D"Arial" size=3D"2"><span sty=
le=3D"font-size: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB"><b=
><br>
<br></b></span></font><b><font color=3D"black" face=3D"Arial" size=3D"2"><s=
pan style=3D"font-size: 10pt; font-family: Arial; color: black; font-weight=
: bold;" lang=3D"EN-GB">and the Implementors Guide for H.248 V2 Chapter 6.3=
2.1 =938 Transaction</span></font></b><font color=3D"black" face=3D"Arial" =
size=3D"2"><span style=3D"font-family: Arial; color: black;" lang=3D"EN-GB"=
></span><span style=3D"font-size: 10pt; font-family: Arial; color: black;" =
lang=3D"EN-GB"><br>
<br><br>which is mentioning the use of a wildcarded TerminationID in a Tran=
sactionReply.<br></span></font></pre><pre><b><font color=3D"black" face=3D"=
Arial" size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; color=
: black; font-weight: bold;" lang=3D"EN-GB"><br>
<br>When a problem occurs with the addition of the ephemeral termination,<b=
r>the reply below is valid for the corresponding Transaction Request:<br><b=
r></span></font></b></pre>T=3D564{C=3D${A=3Dal/1/1/25{M{O{MO=3D<div>SR,RV=
=3DOFF,RG=3DOFF}},E=3D353{al/on{strict=3Dexact},al/of{strict=3Dexact},al/fl=
},SG{}},<br>

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 A=3D${M{O{MO=3DIN,RV=3DOFF=
,RG=3DOFF},L{=85=85..}, R{=85=85.}}}}}<br><br>Reply=3D564{Context=3D52{Add=
=3Dal/1/1/25,Add=3D${Error=3D500{&quot;Error creating Stream&quot;}}}}<br><=
br>The reply above means that the addition of the physical termination is s=
uccessful resulting that the<br>

created context is included in the reply and the addition of the ephemeral =
termination by the Access Gateway<br>was unsuccessful due to for example la=
ck of resources or to Access Gateway internal error.<br><br>=A0Is that repl=
y according to the above standards?=A0<p>

<b><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size=
: 10pt; font-family: Arial; color: black; font-weight: bold;" lang=3D"EN-GB=
">B. I</span></font></b><b><font color=3D"black" face=3D"Arial" size=3D"2">=
<span style=3D"font-size: 10pt; font-family: Arial; color: black; font-weig=
ht: bold;" lang=3D"EN-US">t is noticed that some MGCs
have a different behavior in relation to accept the above reply</span></fon=
t></b></p>

<p><b><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-s=
ize: 10pt; font-family: Arial; color: black; font-weight: bold;" lang=3D"EN=
-US">as
described below:</span></font></b></p>



<p><i><u><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"fon=
t-size: 10pt; font-family: Arial; color: black; font-style: italic;" lang=
=3D"EN-US">B1.
MGC does not support the =93ADD=3D$=94 in the failed transaction command
reply from AGW to the above request:</span></font></u></i></p>





<p><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size=
: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB">MGC expects that =
the
=93ADD=3D$=94 must <b><span style=3D"font-weight: bold;">not</span></b> be
specified in the failed transaction command reply, instead it expects:</spa=
n></font></p><p><font color=3D"black" face=3D"Arial" size=3D"2"><span style=
=3D"font-size: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB">Repl=
y=3D564{Context=3D52{Add=3Dal/1/1/25,<u>Error=3D500{&quot;Error
creating Stream&quot;}</u>}}</span></font></p>



<p><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size=
: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB">=A0Is the above s=
yntax of
the reply valid and therefore acceptable?</span></font></p>

<p><i><u><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"fon=
t-size: 10pt; font-family: Arial; color: black; font-style: italic;" lang=
=3D"EN-US">B2.
MGC expects =93Context=3D</span></font></u><font color=3D"black" face=3D"Ar=
ial" size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; color: =
black; font-style: italic;" lang=3D"EN-US"></span></font></i><font size=3D"=
4"><font color=3D"black" face=3D"Arial"><span style=3D"font-size: 20pt; fon=
t-family: Arial; color: black;" lang=3D"EN-US">-</span></font></font><i><fo=
nt color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt=
; font-family: Arial; color: black; font-style: italic;" lang=3D"EN-US"></s=
pan></font><u><font color=3D"black" face=3D"Arial" size=3D"2"><span style=
=3D"font-size: 10pt; font-family: Arial; color: black; font-style: italic;"=
 lang=3D"EN-US">=93 in the failed transaction reply
from AGW to the above request</span></font></u></i></p>MGC expects =93Conte=
xt=3D-=93 in the failed transaction reply from AGW assuming also that the p=
hysical termination<br>was not added to a context as a result of the epheme=
ral termination addition failure:<p>

Reply=3D564{<u><b>Context=3D</b></u><b><font size=3D"4">-</font></b>{Add=3D=
al/1/1/25,Error=3D500{&quot;Error creating Stream&quot;}}}<font color=3D"bl=
ack" face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; font-family:=
 Arial; color: black;" lang=3D"EN-GB"><br>

</span></font></p>

<p><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size=
: 10pt; font-family: Arial; color: black;" lang=3D"EN-US">Is the above assu=
mption
by MGC and the </span></font><font color=3D"black" face=3D"Arial" size=3D"2=
"><span style=3D"font-size: 10pt; font-family: Arial; color: black;" lang=
=3D"EN-GB">syntax of the
Transaction Reply valid and therefore acceptable?</span></font></p>





<p><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size=
: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB"></span></font></p=
><p><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-siz=
e: 10pt; font-family: Arial; color: black;" lang=3D"EN-GB">Could you please=
 reply
to the above three questions as this is important for our design?</span></f=
ont></p>



<p><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"font-size=
: 10pt; font-family: Arial; color: black;" lang=3D"EN-US">Regards,</span></=
font></p><p><font color=3D"black" face=3D"Arial" size=3D"2"><span style=3D"=
font-size: 10pt; font-family: Arial; color: black;" lang=3D"EN-US">Chris </=
span></font></p>
</div>

--0016367ed50841f433046b86df1e--

From kboyle@huawei.com  Fri Jun  5 14:56:23 2009
Return-Path: <kboyle@huawei.com>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E59BE3A69EA for <megaco@core3.amsl.com>; Fri,  5 Jun 2009 14:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U+0pummY4vXV for <megaco@core3.amsl.com>; Fri,  5 Jun 2009 14:56:22 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 7C1873A69DA for <megaco@ietf.org>; Fri,  5 Jun 2009 14:56:22 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KKS00D6NCY1LD@usaga01-in.huawei.com> for megaco@ietf.org; Fri, 05 Jun 2009 14:56:25 -0700 (PDT)
Received: from B90927 (cpe-069-134-162-056.nc.res.rr.com [69.134.162.56]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KKS00EEQCXQ82@usaga01-in.huawei.com> for megaco@ietf.org; Fri, 05 Jun 2009 14:56:25 -0700 (PDT)
Date: Fri, 05 Jun 2009 17:56:07 -0400
From: Kevin Boyle <kboyle@huawei.com>
In-reply-to: <56512cde0906040748w57103140va929bde3a2ab447b@mail.gmail.com>
To: 'Karavelas Christos' <karavelaschris@gmail.com>, megaco@ietf.org
Message-id: <2C895715CC4D47C8A4C1D7C884F0BA14@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_TKyTK8fCOnl68V+Is3X/JA)"
Thread-index: AcnlI7WX5y/s2A0pSWm0BSFOJaqVSAAIPKGw
References: <56512cde0906040748w57103140va929bde3a2ab447b@mail.gmail.com>
Subject: Re: [Megaco] Failed Reply to a command of an H.248 Transaction Request
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jun 2009 21:56:24 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_TKyTK8fCOnl68V+Is3X/JA)
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: quoted-printable

Comments inline. [KJBII]
=20
Kevin


  _____ =20

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf =
Of
Karavelas Christos
Sent: Thursday, June 04, 2009 10:49 AM
To: megaco@ietf.org
Subject: [Megaco] Failed Reply to a command of an H.248 Transaction =
Request


Hello,=20

A. According to H.248.1 V1/2/3, RFC 3525 Chapter 8 =93Transactions=94:

=93=85.

Transactions guarantee ordered Command processing.
That is, Commands within a Transaction are executed sequentially



.=85
At the first failing Command in a Transaction,
processing of the remaining Commands in that Transaction stops.



=85
A TransactionReply includes the results for all of the Commands in=20
the corresponding TransactionRequest.  The TransactionReply includes



the return values for the Commands that were executed successfully,
and the Command and error descriptor for any Command that failed.=94




and the Implementors Guide for H.248 V2 Chapter 6.32.1 =938 Transaction




which is mentioning the use of a wildcarded TerminationID in a
TransactionReply.





When a problem occurs with the addition of the ephemeral termination,
the reply below is valid for the corresponding Transaction Request:


T=3D564{C=3D${A=3Dal/1/1/25{M{O{MO=3D=20
SR,RV=3DOFF,RG=3DOFF}},E=3D353{al/on{strict=3Dexact},al/of{strict=3Dexact=
},al/fl},SG{}
},
                 A=3D${M{O{MO=3DIN,RV=3DOFF,RG=3DOFF},L{=85=85..}, =
R{=85=85.}}}}}

Reply=3D564{Context=3D52{Add=3Dal/1/1/25,Add=3D${Error=3D500{"Error =
creating
Stream"}}}}

The reply above means that the addition of the physical termination is
successful resulting that the
created context is included in the reply and the addition of the =
ephemeral
termination by the Access Gateway
was unsuccessful due to for example lack of resources or to Access =
Gateway
internal error.

 Is that reply according to the above standards?
[KJBII] This is legal.  =20

B. It is noticed that some MGCs have a different behavior in relation to
accept the above reply

as described below:

B1. MGC does not support the =93ADD=3D$=94 in the failed transaction =
command reply
from AGW to the above request:

MGC expects that the =93ADD=3D$=94 must not be specified in the failed =
transaction
command reply, instead it expects:

Reply=3D564{Context=3D52{Add=3Dal/1/1/25,Error=3D500{"Error creating =
Stream"}}}

 Is the above syntax of the reply valid and therefore acceptable?
[KJBII] This is acceptable, though MGCs ought to accept the message in A =
as
well. Some MGCs do message validation as they parse.  In this case, =
those
MGCs might mark the message in A as a failure, because MGs are not =
supposed
to send CHOOSE.  Either way, the ephemeral Add Command shows up as an =
error
in the MGC, either due to erroneous message handling or because the MGC
actually processes the message in A correctly.  I would see this as a =
minor
issue, and it certainly shouldn't affect operation of the MGC.  The =
worst
that would happen is that the MGC would incorrectly log that the MG is
sending malformed messages.  The easy fix is for the MGC not to mark the
message as malformed until it gets through the rest of the command.  If =
it
finds an Error Descriptor, then it can ignore the earlier "error" as =
being
correct.

B2. MGC expects =93Context=3D-=93 in the failed transaction reply from =
AGW to the
above request

MGC expects =93Context=3D-=93 in the failed transaction reply from AGW =
assuming
also that the physical termination
was not added to a context as a result of the ephemeral termination =
addition
failure:=20

Reply=3D564{Context=3D-{Add=3Dal/1/1/25,Error=3D500{"Error creating =
Stream"}}}


Is the above assumption by MGC and the syntax of the Transaction Reply =
valid
and therefore acceptable?
[KJBII] This is NOT acceptable.  There are many problems here: 1)
Terminations cannot be added to NULL, so returning NULL to an Add =
Command is
a violation of protocol; 2) Assuming the Add of the physical termination =
is
faulty logic and is incorrect -- all commands that receive non-error
responses prior to an error in a message are valid commands, and are
executed; 3) Because the Add Command for the physical succeeded, the MGC
needs to know what context it was placed in so that it can execute =
further
commands on it if necessary. The MG must never return the NULL Context =
in a
reply to an Add Command.



Could you please reply to the above three questions as this is important =
for
our design?

Regards,

Chris=20


--Boundary_(ID_TKyTK8fCOnl68V+Is3X/JA)
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18702"></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D828394518-04062009>Comments inline. [KJBII]</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D828394518-04062009></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D828394518-04062009>Kevin</SPAN></FONT></DIV><BR>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px" dir=3Dltr>
  <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>From:</B> megaco-bounces@ietf.org=20
  [mailto:megaco-bounces@ietf.org] <B>On Behalf Of </B>Karavelas=20
  Christos<BR><B>Sent:</B> Thursday, June 04, 2009 10:49 =
AM<BR><B>To:</B>=20
  megaco@ietf.org<BR><B>Subject:</B> [Megaco] Failed Reply to a command =
of an=20
  H.248 Transaction Request<BR></FONT><BR></DIV>
  <DIV></DIV><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt"=20
  lang=3DEN-US>Hello,</SPAN></FONT>=20
  <P><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt"=20
  lang=3DEN-US></SPAN></FONT><B><FONT color=3Dblack size=3D2 =
face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt; =
FONT-WEIGHT: bold"=20
  lang=3DEN-US>A. According to H.248.1 V1/2/3, RFC 3525 Chapter 8=20
  =93Transactions=94:</SPAN></FONT></B></P>
  <P><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt"=20
  lang=3DEN-GB>=93=85.</SPAN></FONT></P><PRE><FONT color=3Dblack =
size=3D2 face=3DArial><SPAN style=3D"FONT-FAMILY: Arial; COLOR: black; =
FONT-SIZE: 10pt" lang=3DEN-GB>Transactions guarantee ordered Command =
processing.<BR>That is, Commands within a Transaction are executed =
sequentially<BR>
<BR>.</SPAN></FONT><FONT color=3Dblack size=3D2 face=3DArial><SPAN =
style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt" =
lang=3DEN-GB>=85</SPAN></FONT></PRE><PRE><FONT color=3Dblack size=3D2 =
face=3DArial><SPAN style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: =
10pt" lang=3DEN-GB>At the first failing Command in a =
Transaction,<BR>processing of the remaining Commands in that Transaction =
stops.</SPAN></FONT><FONT color=3Dblack size=3D2 face=3DArial><SPAN =
style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt" =
lang=3DEN-GB><BR>
<BR>=85</SPAN></FONT></PRE><PRE><FONT color=3Dblack size=3D2 =
face=3DArial><SPAN style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: =
10pt" lang=3DEN-GB>A TransactionReply includes the results for all of =
the Commands in <BR>the corresponding TransactionRequest.&nbsp; The =
TransactionReply includes<BR>
<BR>the return values for the Commands that were executed =
successfully,<BR>and the Command and error descriptor for any Command =
that failed.=94</SPAN></FONT></PRE><PRE><FONT color=3Dblack size=3D2 =
face=3DArial><SPAN style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: =
10pt" lang=3DEN-GB><B><BR>
<BR></B></SPAN></FONT><B><FONT color=3Dblack size=3D2 face=3DArial><SPAN =
style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt; FONT-WEIGHT: =
bold" lang=3DEN-GB>and the Implementors Guide for H.248 V2 Chapter =
6.32.1 =938 Transaction</SPAN></FONT></B><FONT color=3Dblack size=3D2 =
face=3DArial><SPAN style=3D"FONT-FAMILY: Arial; COLOR: black" =
lang=3DEN-GB></SPAN><SPAN style=3D"FONT-FAMILY: Arial; COLOR: black; =
FONT-SIZE: 10pt" lang=3DEN-GB><BR>
<BR><BR>which is mentioning the use of a wildcarded TerminationID in a =
TransactionReply.<BR></SPAN></FONT></PRE><PRE><B><FONT color=3Dblack =
size=3D2 face=3DArial><SPAN style=3D"FONT-FAMILY: Arial; COLOR: black; =
FONT-SIZE: 10pt; FONT-WEIGHT: bold" lang=3DEN-GB><BR>
<BR>When a problem occurs with the addition of the ephemeral =
termination,<BR>the reply below is valid for the corresponding =
Transaction =
Request:<BR><BR></SPAN></FONT></B></PRE>T=3D564{C=3D${A=3Dal/1/1/25{M{O{M=
O=3D
  =
<DIV>SR,RV=3DOFF,RG=3DOFF}},E=3D353{al/on{strict=3Dexact},al/of{strict=3D=
exact},al/fl},SG{}},<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  A=3D${M{O{MO=3DIN,RV=3DOFF,RG=3DOFF},L{=85=85..},=20
  =
R{=85=85.}}}}}<BR><BR>Reply=3D564{Context=3D52{Add=3Dal/1/1/25,Add=3D${Er=
ror=3D500{"Error=20
  creating Stream"}}}}<BR><BR>The reply above means that the addition of =
the=20
  physical termination is successful resulting that the<BR>created =
context is=20
  included in the reply and the addition of the ephemeral termination by =
the=20
  Access Gateway<BR>was unsuccessful due to for example lack of =
resources or to=20
  Access Gateway internal error.<BR><BR>&nbsp;Is that reply according to =
the=20
  above standards?<BR><SPAN class=3D828394518-04062009><FONT =
color=3D#0000ff size=3D2=20
  face=3DArial>[KJBII]&nbsp;This is legal.&nbsp;</FONT></SPAN>&nbsp;
  <P><B><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt; =
FONT-WEIGHT: bold"=20
  lang=3DEN-GB>B. I</SPAN></FONT></B><B><FONT color=3Dblack size=3D2 =
face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt; =
FONT-WEIGHT: bold"=20
  lang=3DEN-US>t is noticed that some MGCs have a different behavior in =
relation=20
  to accept the above reply</SPAN></FONT></B></P>
  <P><B><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt; =
FONT-WEIGHT: bold"=20
  lang=3DEN-US>as described below:</SPAN></FONT></B></P>
  <P><I><U><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-STYLE: italic; FONT-FAMILY: Arial; COLOR: black; =
FONT-SIZE: 10pt"=20
  lang=3DEN-US>B1. MGC does not support the =93ADD=3D$=94 in the failed =
transaction=20
  command reply from AGW to the above request:</SPAN></FONT></U></I></P>
  <P><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt" =
lang=3DEN-GB>MGC=20
  expects that the =93ADD=3D$=94 must <B><SPAN=20
  style=3D"FONT-WEIGHT: bold">not</SPAN></B> be specified in the failed=20
  transaction command reply, instead it expects:</SPAN></FONT></P>
  <P><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt"=20
  =
lang=3DEN-GB>Reply=3D564{Context=3D52{Add=3Dal/1/1/25,<U>Error=3D500{"Err=
or creating=20
  Stream"}</U>}}</SPAN></FONT></P>
  <P><FONT color=3Dblack><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt" =
lang=3DEN-GB>&nbsp;Is=20
  the above syntax of the reply valid and therefore acceptable?<BR><SPAN =

  class=3D828394518-04062009><FONT color=3D#0000ff>[KJBII]&nbsp;This is =
acceptable,=20
  though MGCs ought to accept the message in A as well.&nbsp;Some MGCs =
do=20
  message validation as they parse.&nbsp; In this case, those MGCs might =
mark=20
  the message in A as a failure, because MGs are not supposed to send=20
  CHOOSE.&nbsp; Either way, the ephemeral Add Command shows up as an =
error in=20
  the MGC, either due to erroneous message handling or because the MGC =
actually=20
  processes the message in A correctly.&nbsp; I would see this as a =
minor issue,=20
  and it certainly shouldn't affect operation of the MGC.&nbsp; The =
worst that=20
  would happen is that the MGC would incorrectly log that the MG is =
sending=20
  malformed messages.&nbsp; The easy fix is for the MGC not to mark the =
message=20
  as malformed until it gets through the rest of the command.&nbsp; If =
it finds=20
  an Error Descriptor, then it can ignore the earlier "error" as being=20
  correct.</FONT></SPAN></SPAN></FONT></P>
  <P><I><U><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-STYLE: italic; FONT-FAMILY: Arial; COLOR: black; =
FONT-SIZE: 10pt"=20
  lang=3DEN-US>B2. MGC expects =93Context=3D</SPAN></FONT></U><FONT =
color=3Dblack size=3D2=20
  face=3DArial><SPAN=20
  style=3D"FONT-STYLE: italic; FONT-FAMILY: Arial; COLOR: black; =
FONT-SIZE: 10pt"=20
  lang=3DEN-US></SPAN></FONT></I><FONT size=3D4><FONT color=3Dblack =
face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 20pt"=20
  lang=3DEN-US>-</SPAN></FONT></FONT><I><FONT color=3Dblack size=3D2 =
face=3DArial><SPAN=20
  style=3D"FONT-STYLE: italic; FONT-FAMILY: Arial; COLOR: black; =
FONT-SIZE: 10pt"=20
  lang=3DEN-US></SPAN></FONT><U><FONT color=3Dblack size=3D2 =
face=3DArial><SPAN=20
  style=3D"FONT-STYLE: italic; FONT-FAMILY: Arial; COLOR: black; =
FONT-SIZE: 10pt"=20
  lang=3DEN-US>=93 in the failed transaction reply from AGW to the above =

  request</SPAN></FONT></U></I></P>MGC expects =93Context=3D-=93 in the =
failed=20
  transaction reply from AGW assuming also that the physical =
termination<BR>was=20
  not added to a context as a result of the ephemeral termination =
addition=20
  failure:
  <P>Reply=3D564{<U><B>Context=3D</B></U><B><FONT=20
  size=3D4>-</FONT></B>{Add=3Dal/1/1/25,Error=3D500{"Error creating =
Stream"}}}<FONT=20
  color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt"=20
  lang=3DEN-GB><BR></SPAN></FONT></P>
  <P><FONT color=3Dblack><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt" =
lang=3DEN-US>Is the=20
  above assumption by MGC and the </SPAN></FONT><FONT =
color=3Dblack><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt" =
lang=3DEN-GB>syntax of=20
  the Transaction Reply valid and therefore acceptable?<BR><SPAN=20
  class=3D828394518-04062009><FONT color=3D#0000ff>[KJBII]&nbsp;This is =
NOT=20
  acceptable.&nbsp;&nbsp;There are many problems here: 1) Terminations =
cannot=20
  be&nbsp;added to NULL, so returning NULL to an Add&nbsp;Command is a =
violation=20
  of protocol; 2) Assuming the&nbsp;Add of the physical termination is =
faulty=20
  logic and is incorrect -- all commands&nbsp;that receive non-error =
responses=20
  prior to an error in a message are valid commands, and are executed; =
3)=20
  Because the Add Command for the physical succeeded, the MGC needs to =
know what=20
  context it was placed in so that it can&nbsp;execute further =
commands&nbsp;on=20
  it if necessary.&nbsp;The MG must never return the NULL Context in a =
reply to=20
  an Add Command.</FONT></SPAN></SPAN></FONT></P>
  <P><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt"=20
  lang=3DEN-GB></SPAN></FONT></P>
  <P><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt" =
lang=3DEN-GB>Could you=20
  please reply to the above three questions as this is important for our =

  design?</SPAN></FONT></P>
  <P><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt"=20
  lang=3DEN-US>Regards,</SPAN></FONT></P>
  <P><FONT color=3Dblack size=3D2 face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial; COLOR: black; FONT-SIZE: 10pt" =
lang=3DEN-US>Chris=20
  </SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_TKyTK8fCOnl68V+Is3X/JA)--

From srikant86.panda@gmail.com  Tue Jun  9 09:40:22 2009
Return-Path: <srikant86.panda@gmail.com>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AAD83A6BC8 for <megaco@core3.amsl.com>; Tue,  9 Jun 2009 09:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JUcuGxZnRxM0 for <megaco@core3.amsl.com>; Tue,  9 Jun 2009 09:40:21 -0700 (PDT)
Received: from mail-qy0-f196.google.com (mail-qy0-f196.google.com [209.85.221.196]) by core3.amsl.com (Postfix) with ESMTP id 59A9C3A6AA3 for <megaco@ietf.org>; Tue,  9 Jun 2009 09:40:21 -0700 (PDT)
Received: by qyk34 with SMTP id 34so155158qyk.32 for <megaco@ietf.org>; Tue, 09 Jun 2009 09:40:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=EVwzVHm1ZoGnVVnBGbjLhkM5e4gnHPuiqMGuSSvrHu0=; b=nU63sypYVGHfeh0xLGGVSyvbC3pkV+/3GboOMou29IpnZzAsdKB3wZGOFKIT1Wjaf/ ljCZdyjWFmMwk8H59s++ZEuLjKDylOblExwsQpvS0ghLkaY5chOuf91PDXtv85scVDlO SOj3xtvhdZlRUcnPvKThhtoBn6oBrjmUwGKDE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=h+pM+WJN4HQPPyodHJBCiUcxcp7F9qGI31R+axvuaObzpVG9+l5q/XIVeU92czV+/z JbJwjlpxoNuDsipWJISrFd0FbXCHuh9Ti3cisLyixqWEwagV8SPpGQ/CuR88Iy2oREoH 1YoAqf3LQ+Juq+QPxGhLWENuExStxT7VsN4w8=
MIME-Version: 1.0
Received: by 10.220.100.16 with SMTP id w16mr388511vcn.110.1244565624118; Tue,  09 Jun 2009 09:40:24 -0700 (PDT)
Date: Tue, 9 Jun 2009 22:10:23 +0530
Message-ID: <d3e059610906090940m70a58646m3642a8f76dac9b@mail.gmail.com>
From: Sriku Panda <srikant86.panda@gmail.com>
To: megaco@ietf.org
Content-Type: multipart/alternative; boundary=0016e64715d4ece27f046bed03a8
X-Mailman-Approved-At: Wed, 10 Jun 2009 08:05:45 -0700
Subject: [Megaco] what is cold start and warm start..in Megaco
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2009 16:46:17 -0000

--0016e64715d4ece27f046bed03a8
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

what is cold start and warm start..in Megaco??

--0016e64715d4ece27f046bed03a8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

what is cold start and warm start..in Megaco??<br>

--0016e64715d4ece27f046bed03a8--

From srikant86.panda@gmail.com  Tue Jun  9 09:54:10 2009
Return-Path: <srikant86.panda@gmail.com>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E4413A67E1 for <megaco@core3.amsl.com>; Tue,  9 Jun 2009 09:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.133
X-Spam-Level: 
X-Spam-Status: No, score=-2.133 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XSKJwVZRYoHv for <megaco@core3.amsl.com>; Tue,  9 Jun 2009 09:54:10 -0700 (PDT)
Received: from mail-pz0-f181.google.com (mail-pz0-f181.google.com [209.85.222.181]) by core3.amsl.com (Postfix) with ESMTP id 09B5D3A67D7 for <megaco@ietf.org>; Tue,  9 Jun 2009 09:54:10 -0700 (PDT)
Received: by pzk11 with SMTP id 11so127078pzk.29 for <megaco@ietf.org>; Tue, 09 Jun 2009 09:54:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=7JW3EIHmxsyNk+S6HCeJTAHqIEpDo0W+ktRGxAUDu5k=; b=FyM16rUbfLSVlq3DwZ4KaR8KEBAUt8zhqUcaS9BIqC3rSo4pVvkHeuHR/nEfR3BnEb YtV6kkgotYv4Ebkt4DJtweEwtWovAEleWLsK5JPZgq2Dc0l2fVgCoqlSzn0bbWCXsbtx BGYY8+wrC4sE/fnaYikHMdCEpz70BCxiOGGIs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=u2t2Ze8n8z8qv+wB+PS9P0Ha1ol91cNHaM1R0J8xBliQavaKQymnFtCzAP8qEWsP4l u9cHnutPDUiXUaiVQ9sRln8WGQFF0Ry4D3/A3jtl/KhHrQ8fLYB7IM1fgg0MriHHLbCi G7FBClCQLC5jkMa/Q7Shs+v97bWczUGvZighk=
MIME-Version: 1.0
Received: by 10.220.98.17 with SMTP id o17mr413066vcn.86.1244566451844; Tue,  09 Jun 2009 09:54:11 -0700 (PDT)
In-Reply-To: <d3e059610906090940m70a58646m3642a8f76dac9b@mail.gmail.com>
References: <d3e059610906090940m70a58646m3642a8f76dac9b@mail.gmail.com>
Date: Tue, 9 Jun 2009 22:24:11 +0530
Message-ID: <d3e059610906090954u3f64d568qb203abe15458057d@mail.gmail.com>
From: Sriku Panda <srikant86.panda@gmail.com>
To: megaco@ietf.org
Content-Type: multipart/alternative; boundary=0016e648084242f6da046bed3507
X-Mailman-Approved-At: Wed, 10 Jun 2009 08:05:45 -0700
Subject: [Megaco] what is cold start and warm start..in Megaco
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2009 16:54:10 -0000

--0016e648084242f6da046bed3507
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

what is cold start and warm start..in Megaco??

--0016e648084242f6da046bed3507
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<br><br><div class="gmail_quote"><br><br><br>what is cold start and warm start..in Megaco??<br>
</div><br>

--0016e648084242f6da046bed3507--

From Albrecht.Schwarz@alcatel-lucent.de  Thu Jun 11 01:40:19 2009
Return-Path: <Albrecht.Schwarz@alcatel-lucent.de>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 434783A6910 for <megaco@core3.amsl.com>; Thu, 11 Jun 2009 01:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3u36XHww5roy for <megaco@core3.amsl.com>; Thu, 11 Jun 2009 01:40:14 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id BF0C43A6B34 for <megaco@ietf.org>; Thu, 11 Jun 2009 01:40:13 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.dc-m.alcatel-lucent.com [155.132.6.78]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5B8eHMV011795;  Thu, 11 Jun 2009 10:40:18 +0200
Received: from FRVELSMBS23.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS06.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Jun 2009 10:40:17 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9EA70.3F372837"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 11 Jun 2009 10:40:16 +0200
Message-ID: <F4562D4585113D42AC08DC47FDEC49B001F27ADC@FRVELSMBS23.ad2.ad.alcatel.com>
In-Reply-To: <d3e059610906090954u3f64d568qb203abe15458057d@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Megaco] what is cold start and warm start..in Megaco
thread-index: Acnp3PwFhZ/oqjPGQUmocwOGQJLSvQAks3yA
References: <d3e059610906090940m70a58646m3642a8f76dac9b@mail.gmail.com> <d3e059610906090954u3f64d568qb203abe15458057d@mail.gmail.com>
From: "Schwarz Albrecht" <Albrecht.Schwarz@alcatel-lucent.de>
To: "Sriku Panda" <srikant86.panda@gmail.com>, <megaco@ietf.org>
X-OriginalArrivalTime: 11 Jun 2009 08:40:17.0959 (UTC) FILETIME=[3F838370:01C9EA70]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: Re: [Megaco] what is cold start and warm start..in Megaco
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jun 2009 08:40:19 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9EA70.3F372837
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

just think about the "data & state synchronization" requirement for
distributed systems, when one entity makes an IS-to-OoS-to-IS
("In-Service", "Out-of-Service") transition.
After the OoS phase there are different options to re-synchronize again,
typically dependent on loss of info or ... or ...=20
=20


________________________________

	From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]
On Behalf Of Sriku Panda
	Sent: Dienstag, 9. Juni 2009 18:54
	To: megaco@ietf.org
	Subject: [Megaco] what is cold start and warm start..in Megaco
=09
=09





	what is cold start and warm start..in Megaco??
=09



------_=_NextPart_001_01C9EA70.3F372837
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.5764" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D778003708-11062009><FONT =
face=3D"Trebuchet MS"=20
color=3D#800000 size=3D2>just think about the "data &amp; state =
synchronization"=20
requirement for distributed systems, when one entity makes an =
IS-to-OoS-to-IS=20
("In-Service", "Out-of-Service") transition.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D778003708-11062009><FONT =
face=3D"Trebuchet MS"=20
color=3D#800000 size=3D2>After the OoS phase there are different options =
to=20
re-synchronize again, typically dependent on loss of info or ... or ...=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D778003708-11062009></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; 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>Sriku=20
  Panda<BR><B>Sent:</B> Dienstag, 9. Juni 2009 18:54<BR><B>To:</B>=20
  megaco@ietf.org<BR><B>Subject:</B> [Megaco] what is cold start and =
warm=20
  start..in Megaco<BR></FONT><BR></DIV>
  <DIV></DIV><BR><BR>
  <DIV class=3Dgmail_quote><BR><BR><BR>what is cold start and warm =
start..in=20
  Megaco??<BR></DIV><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C9EA70.3F372837--

From Christian.Groves@nteczone.com  Tue Jun 16 23:11:36 2009
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B93A23A6DDA for <megaco@core3.amsl.com>; Tue, 16 Jun 2009 23:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.305
X-Spam-Level: 
X-Spam-Status: No, score=-1.305 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, RCVD_IN_DNSWL_LOW=-1, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bfz8UB7SUpzU for <megaco@core3.amsl.com>; Tue, 16 Jun 2009 23:11:35 -0700 (PDT)
Received: from ipmail04.adl2.internode.on.net (ipmail04.adl2.internode.on.net [203.16.214.57]) by core3.amsl.com (Postfix) with ESMTP id EC24A3A6DCF for <megaco@ietf.org>; Tue, 16 Jun 2009 23:11:30 -0700 (PDT)
Received: from ppp118-208-226-60.lns10.mel6.internode.on.net (HELO [127.0.0.1]) ([118.208.226.60]) by ipmail04.adl2.internode.on.net with ESMTP; 17 Jun 2009 15:41:32 +0930
Message-ID: <4A38890E.5090701@nteczone.com>
Date: Wed, 17 Jun 2009 16:11:26 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: megaco ietf <megaco@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Q.3/16 Media Control Protocol Meeting
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2009 06:11:36 -0000

Hello all,

For those interested in next weeks Q.3/16 meeting, the documents are now 
available at:
http://wftp3.itu.int/av-arch/avc-site/2009-2012/0906_Gen/0906_Gen.html

The agenda will be available shortly as TD-04.

Regards, Christian

From Christian.Groves@nteczone.com  Tue Jun 16 23:22:06 2009
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4545B3A6DE2 for <megaco@core3.amsl.com>; Tue, 16 Jun 2009 23:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.28
X-Spam-Level: 
X-Spam-Status: No, score=-2.28 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A8CQOSr8TA4p for <megaco@core3.amsl.com>; Tue, 16 Jun 2009 23:22:05 -0700 (PDT)
Received: from ipmail04.adl2.internode.on.net (ipmail04.adl2.internode.on.net [203.16.214.57]) by core3.amsl.com (Postfix) with ESMTP id 029B43A6DE0 for <megaco@ietf.org>; Tue, 16 Jun 2009 23:22:04 -0700 (PDT)
Received: from ppp118-208-226-60.lns10.mel6.internode.on.net (HELO [127.0.0.1]) ([118.208.226.60]) by ipmail04.adl2.internode.on.net with ESMTP; 17 Jun 2009 15:49:20 +0930
Message-ID: <4A388AE3.7010308@nteczone.com>
Date: Wed, 17 Jun 2009 16:19:15 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: megaco ietf <megaco@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Deprecation of elements in H.248.4 "SCTP transport" and H.248.5 "ATM Transport"
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2009 06:22:06 -0000

Hello all,

Contributions:
AVD-3741 "H.248.4: Deprecate use of lower layer mechanisms to ensure 
at-most-once functionality"
http://wftp3.itu.int/av-arch/avc-site/2009-2012/0906_Gen/AVD-3741.zip

H.248.5: Deprecate use of lower layer mechanisms to ensure at-most-once 
functionality
http://wftp3.itu.int/av-arch/avc-site/2009-2012/0906_Gen/AVD-3742.zip

Propose to deprecate existing functionality associated with H.248.4 and 
H.248.5. Do people on the this list have any problems with this or any 
feedback on the contributions?

Regards, Christian

From Albrecht.Schwarz@alcatel-lucent.de  Wed Jun 17 07:45:28 2009
Return-Path: <Albrecht.Schwarz@alcatel-lucent.de>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A9133A6E2F for <megaco@core3.amsl.com>; Wed, 17 Jun 2009 07:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.248
X-Spam-Level: 
X-Spam-Status: No, score=-4.248 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fF1vO6XTBAE0 for <megaco@core3.amsl.com>; Wed, 17 Jun 2009 07:45:27 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id DFBB53A6A7A for <megaco@ietf.org>; Wed, 17 Jun 2009 07:45:26 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.dc-m.alcatel-lucent.com [155.132.6.78]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5HEhicq004130;  Wed, 17 Jun 2009 16:43:46 +0200
Received: from FRVELSMBS23.ad2.ad.alcatel.com ([155.132.6.56]) by FRVELSBHS06.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 17 Jun 2009 16:43:44 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Jun 2009 16:39:34 +0200
Message-ID: <F4562D4585113D42AC08DC47FDEC49B001F82844@FRVELSMBS23.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Late AVD-3803 on Deep Packet Inspection ("H.248.DPI"); RE: [Megaco] Q.3/16 Media Control Protocol Meeting
Thread-Index: AcnvWW5/viT3ZMcAT6Od3rpGKz6E3Q==
From: "Schwarz Albrecht" <Albrecht.Schwarz@alcatel-lucent.de>
To: "Christian Groves" <Christian.Groves@nteczone.com>, "megaco ietf" <megaco@ietf.org>
X-OriginalArrivalTime: 17 Jun 2009 14:43:44.0432 (UTC) FILETIME=[03A9BB00:01C9EF5A]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: Yoshinori Goto <goto@ansl.ntt.co.jp>
Subject: [Megaco] Late AVD-3803 on Deep Packet Inspection ("H.248.DPI"); RE:  Q.3/16 Media Control Protocol Meeting
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2009 14:45:28 -0000

... was just uploaded to the Incoming folder:
http://wftp3.itu.int/av-arch/avc-site/Incoming/

-Albrecht

PS=20
Will appear later under URL
http://wftp3.itu.int/av-arch/avc-site/2009-2012/0906_Gen/AVD-3803.zip
=20
=20
-----------
=20
Hello all,


For those interested in next weeks Q.3/16 meeting, the documents are now
available at:=20
http://wftp3.itu.int/av-arch/avc-site/2009-2012/0906_Gen/0906_Gen.html

The agenda will be available shortly as TD-04.

Regards, Christian


From goto@ansl.ntt.co.jp  Wed Jun 17 18:14:08 2009
Return-Path: <goto@ansl.ntt.co.jp>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B9553A6B18 for <megaco@core3.amsl.com>; Wed, 17 Jun 2009 18:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LgLwQVvFMtct for <megaco@core3.amsl.com>; Wed, 17 Jun 2009 18:14:07 -0700 (PDT)
Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147]) by core3.amsl.com (Postfix) with ESMTP id 86DA63A6A5A for <megaco@ietf.org>; Wed, 17 Jun 2009 18:14:07 -0700 (PDT)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149]) by tama50.ecl.ntt.co.jp (8.14.2/8.14.2) with ESMTP id n5I1EB9S024321; Thu, 18 Jun 2009 10:14:11 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 52A496ACA; Thu, 18 Jun 2009 10:14:11 +0900 (JST)
Received: from gw02.makuhari.ansl.ntt.co.jp (gw02.makuhari.ansl.ntt.co.jp [129.60.177.253]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 43888693A; Thu, 18 Jun 2009 10:14:11 +0900 (JST)
Received: from gw02.makuhari.ansl.ntt.co.jp (localhost [127.0.0.1]) by gw02.makuhari.ansl.ntt.co.jp (8.14.3/8.14.3) with ESMTP id n5I1EA3O004167; Thu, 18 Jun 2009 10:14:10 +0900 (JST)
Received: from [129.60.231.138] ([129.60.231.138]) by gw02.makuhari.ansl.ntt.co.jp (8.14.3/8.14.3) with ESMTP id n5I1E85D004152; Thu, 18 Jun 2009 10:14:09 +0900 (JST)
Message-ID: <4A399521.5040505@ansl.ntt.co.jp>
Date: Thu, 18 Jun 2009 10:15:13 +0900
From: Yoshinori Goto <goto@ansl.ntt.co.jp>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Schwarz Albrecht <Albrecht.Schwarz@alcatel-lucent.de>
References: <F4562D4585113D42AC08DC47FDEC49B001F82844@FRVELSMBS23.ad2.ad.alcatel.com>
In-Reply-To: <F4562D4585113D42AC08DC47FDEC49B001F82844@FRVELSMBS23.ad2.ad.alcatel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 18 Jun 2009 09:09:15 -0700
Cc: megaco ietf <megaco@ietf.org>
Subject: Re: [Megaco] Late AVD-3803 on Deep Packet Inspection ("H.248.DPI"); RE:  Q.3/16 Media Control Protocol Meeting
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jun 2009 01:14:08 -0000

Dear Schwarz,

I found the file and moved to the AVC-site.
FYI, this is a late arrival document.
So, we need to ask the agreement at the begining of the meeting.

Best regards,

> ... was just uploaded to the Incoming folder:
> http://wftp3.itu.int/av-arch/avc-site/Incoming/
>
> -Albrecht
>
> PS 
> Will appear later under URL
> http://wftp3.itu.int/av-arch/avc-site/2009-2012/0906_Gen/AVD-3803.zip
>  
>  
> -----------
>  
> Hello all,
>
>
> For those interested in next weeks Q.3/16 meeting, the documents are now
> available at: 
> http://wftp3.itu.int/av-arch/avc-site/2009-2012/0906_Gen/0906_Gen.html
>
> The agenda will be available shortly as TD-04.
>
> Regards, Christian
>
>
>   


-- 
<><><><><><><><><><><><><><><><><><><><><><><><>
              Yoshinori Goto
   NTT Access Network Service Systems Labs.
 TEL:+81 43 211 2109     FAX:+81 43 211 7493
        e-mail:goto@ansl.ntt.co.jp
<><><><><><><><><><><><><><><><><><><><><><><><> 


From rginotra@cisco.com  Thu Jun 25 04:16:04 2009
Return-Path: <rginotra@cisco.com>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E79AB3A6C57 for <megaco@core3.amsl.com>; Thu, 25 Jun 2009 04:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.35
X-Spam-Level: 
X-Spam-Status: No, score=-1.35 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, DATE_IN_FUTURE_12_24=2.189, HTML_MESSAGE=0.001,  J_CHICKENPOX_14=0.6, J_CHICKENPOX_29=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y4dLfUfJsmLr for <megaco@core3.amsl.com>; Thu, 25 Jun 2009 04:16:04 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id CC6C93A6D8F for <megaco@ietf.org>; Thu, 25 Jun 2009 04:16:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,290,1243814400";  d="scan'208,217";a="205481109"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-1.cisco.com with ESMTP; 25 Jun 2009 11:16:03 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5PBG3lB015054 for <megaco@ietf.org>; Thu, 25 Jun 2009 04:16:03 -0700
Received: from sj-webmail-7.cisco.com (sj-webmail-7.cisco.com [171.70.159.6]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id n5PBG3hX022632 for <megaco@ietf.org>; Thu, 25 Jun 2009 11:16:03 GMT
Received: from sj-webmail-7.cisco.com (localhost.localdomain [127.0.0.1]) by sj-webmail-7.cisco.com (8.13.1/8.13.1) with ESMTP id n5PBG2Hx005665 for <megaco@ietf.org>; Thu, 25 Jun 2009 04:16:02 -0700
Received: from sj-webmail-7 (root@localhost) by sj-webmail-7.cisco.com (8.13.1/8.13.1/Submit) with ESMTP id n5PBG201005664 for <megaco@ietf.org>; Thu, 25 Jun 2009 04:16:02 -0700
Received: from rginotrawxp03 ( [10.78.164.143]) by sj-webmail-7 (Scalix SMTP Relay 10.0.5.3) via ESMTP; Thu, 25 Jun 2009 04:16:02 -0700 (PDT)
Date: Thu, 25 Jun 2009 16:44:42 -0700
From: Rajiv Ginotra <rginotra@cisco.com>
To: <megaco@ietf.org>
Message-ID: <002c01c9f5ee$eaa82740$8fa44e0a@rginotrawxp03>
x-scalix-Hops: 1
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acn17ulmaRTywoKSQ3avd+BjlY84yA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002D_01C9F5B4.3E494F40"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9476; t=1245928563; x=1246792563; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rginotra@cisco.com; z=From:=20Rajiv=20Ginotra=20<rginotra@cisco.com> |Subject:=20MG=20Behavior=20on=20getting=20pending=20messag e=20response=20from=20MGC=20on=20ITO(Inactivity=20Timer)=20t imeout |Sender:=20; bh=Rd1CGV0MpCIsgcxhTHv0XlM1nTneFEht8Rn5zxea6oQ=; b=Zgv6gHJQz4aUFL/hrRFNrIRAfWn8guArMNL7+ZtOgkhI+scDUbFPmVdlVf 7ll6ftE9msRO9RePVpXQItqU/sQVwIAwkEyE+hWSpY4/HbGbClYFbtuln9LD 0+pQxGIwZAHLOuLDgbe7TOeRsb1NnX14E6eetPfesglLWRQPw2EpQ=;
Authentication-Results: sj-dkim-1; header.From=rginotra@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: [Megaco] MG Behavior on getting pending message response from MGC on ITO(Inactivity Timer) timeout
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jun 2009 11:16:05 -0000

------=_NextPart_000_002D_01C9F5B4.3E494F40
Content-Type: text/plain;
	charset="US-ASCII"
Content-Disposition: inline

Hello All,
 
Consider the following scenario:
When the MG is sending the ITO timeout notify and the MGC sends the pending
message along with IA(Immediate Acknowledgment) in the same  message.
 
 
Question 1: After the ITO transaction retries are  finished, should MG sends
a "909 MGC Impending Failure" service change message to other MGCs
configured in the list or the send a ITO timeout notify with a new
transaction ID.
 
Question 2: Does the IA in the above reply from MGC make the behavior
different?
 
I have enclosed the call flow for reference
 
Regards
Rajiv
 
Call flow
======
[1196396 (10 ms)] !/2 [10.78.161.24]:5099 Transaction=2 {
Context = - {
Modify = ROOT {
Events = 1111 {it/ito {mit = 1000}}
}
}}
 
[10.78.161.24]:5099 [1196396 (10 ms)] !/2 [183.1.13.2]:2965 P = 2{ C = -
{mf=ROOT }}

ITO Timeout notify starts and MGC started sending pending messages:
----------------------------------------------------------------------------
--------------------------
 
[10.78.161.24]:5099 [1197496 (10 ms)] !/2 [183.1.13.2]:2965 T = 538{ C = -
{n=ROOT  { oe = 1111 { IT/ITO }  } }}
 
[1197503 (10 ms)] !/2 [10.78.161.24]:5099 Reply=538 {IA, C  =  - { n=root {
Error = 506 {"506"} }}}
 
[10.78.161.24]:5099 [1197503 (10 ms)] !/2 [183.1.13.2]:2965 k{537,538}
 
[10.78.161.24]:5099 [1198403 (10 ms)] !/2 [183.1.13.2]:2965 T = 539{ C = -
{n=ROOT  { oe = 1111 { IT/ITO }  } }}
 
[1198408 (10 ms)] !/2 [10.78.161.24]:5099 Reply=539 {IA, C  =  - { n=root {
Error = 506 {"506"} }}}
 
[10.78.161.24]:5099 [1198408 (10 ms)] !/2 [183.1.13.2]:2965 k{539}
 
[10.78.161.24]:5099 [1199408 (10 ms)] !/2 [183.1.13.2]:2965 T = 540{ C = -
{n=ROOT  { oe = 1111 { IT/ITO }  } }}
 
[1199412 (10 ms)] !/2 [10.78.161.24]:5099 Reply=540 {IA, C  =  - { n=root {
Error = 506 {"506"} }}}
 
[10.78.161.24]:5099 [1199412 (10 ms)] !/2 [183.1.13.2]:2965 k{540}
 
[10.78.161.24]:5099 [1200412 (10 ms)] !/2 [183.1.13.2]:2965 T = 541{ C = -
{n=ROOT  { oe = 1111 { IT/ITO }  } }}
 
[1200417 (10 ms)] !/2 [10.78.161.24]:5099 Reply=541 {IA, C  =  - { n=root {
Error = 506 {"506"} }}}
 
[10.78.161.24]:5099 [1200417 (10 ms)] !/2 [183.1.13.2]:2965 k{541}
 
Now the ITO retries get finished. what would be the next transaction???
 

------=_NextPart_000_002D_01C9F5B4.3E494F40
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Hello=20
All,</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Conside=
r the=20
following scenario:</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>When th=
e MG is=20
sending the ITO timeout notify and&nbsp;the MGC sends the pending message=
 along=20
with IA(Immediate Acknowledgment)&nbsp;in the same=20
&nbsp;message.</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Questio=
n 1: After=20
the ITO transaction retries are&nbsp; finished, should MG sends a <FONT=20
size=3D2>"909 MGC Impending Failure" </FONT>service change message to oth=
er MGCs=20
configured in the list or the send a ITO timeout notify with a new transa=
ction=20
ID.</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Questio=
n 2: Does the=20
IA in the above reply from MGC make the behavior different?</FONT></SPAN>=
</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>I have e=
nclosed the=20
call flow for reference</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009></SPAN><SPAN class=3D546533522-2506=
2009><FONT=20
face=3DArial size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>Rajiv</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Call=20
flow</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>=3D=3D=3D=3D=3D=3D</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[119639=
6 (10 ms)]=20
!/2 [10.78.161.24]:5099 Transaction=3D2 {<BR>Context =3D - {<BR>Modify =3D=
 ROOT=20
{<BR>Events =3D 1111 {it/ito {mit =3D 1000}}<BR>}<BR>}}</FONT></SPAN></DI=
V>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1196396 (10 ms)] !/2 [183.1.13.2]:2965 P =3D 2{ C =3D - {mf=3DROOT=20
}}<BR></FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>ITO Tim=
eout notify=20
starts and MGC started sending pending messages:</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>----------------------------------------------------------------=
--------------------------------------</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1197496 (10 ms)] !/2 [183.1.13.2]:2965 T =3D 538{ C =3D - {n=3DROOT&nbsp=
; { oe =3D 1111=20
{ IT/ITO }&nbsp; } }}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[119750=
3 (10 ms)]=20
!/2 [10.78.161.24]:5099 Reply=3D538 {IA, C&nbsp; =3D&nbsp; - { n=3Droot {=
 Error =3D 506=20
{"506"} }}}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1197503 (10 ms)] !/2 [183.1.13.2]:2965 k{537,538}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1198403 (10 ms)] !/2 [183.1.13.2]:2965 T =3D 539{ C =3D - {n=3DROOT&nbsp=
; { oe =3D 1111=20
{ IT/ITO }&nbsp; } }}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[119840=
8 (10 ms)]=20
!/2 [10.78.161.24]:5099 Reply=3D539 {IA, C&nbsp; =3D&nbsp; - { n=3Droot {=
 Error =3D 506=20
{"506"} }}}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1198408 (10 ms)] !/2 [183.1.13.2]:2965 k{539}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1199408 (10 ms)] !/2 [183.1.13.2]:2965 T =3D 540{ C =3D - {n=3DROOT&nbsp=
; { oe =3D 1111=20
{ IT/ITO }&nbsp; } }}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[119941=
2 (10 ms)]=20
!/2 [10.78.161.24]:5099 Reply=3D540 {IA, C&nbsp; =3D&nbsp; - { n=3Droot {=
 Error =3D 506=20
{"506"} }}}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1199412 (10 ms)] !/2 [183.1.13.2]:2965 k{540}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1200412 (10 ms)] !/2 [183.1.13.2]:2965 T =3D 541{ C =3D - {n=3DROOT&nbsp=
; { oe =3D 1111=20
{ IT/ITO }&nbsp; } }}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[120041=
7 (10 ms)]=20
!/2 [10.78.161.24]:5099 Reply=3D541 {IA, C&nbsp; =3D&nbsp; - { n=3Droot {=
 Error =3D 506=20
{"506"} }}}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1200417 (10 ms)] !/2 [183.1.13.2]:2965 k{541}</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Now the=
 ITO retries=20
get finished. what would be the next transaction???</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>&nbsp;</DIV></FONT></SPAN></BODY></HTML>

------=_NextPart_000_002D_01C9F5B4.3E494F40--

From rginotra@cisco.com  Thu Jun 25 04:20:31 2009
Return-Path: <rginotra@cisco.com>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2ED7A3A6D8F; Thu, 25 Jun 2009 04:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.28
X-Spam-Level: 
X-Spam-Status: No, score=-2.28 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, DATE_IN_FUTURE_12_24=2.189, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_29=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d-HJmHj6Knd0; Thu, 25 Jun 2009 04:20:30 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 0D0FE3A6DA8; Thu, 25 Jun 2009 04:20:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,290,1243814400";  d="scan'208,217";a="180267953"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 25 Jun 2009 11:19:45 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5PBJheU019383;  Thu, 25 Jun 2009 04:19:43 -0700
Received: from sj-webmail-7.cisco.com (sj-webmail-7.cisco.com [171.70.159.6]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n5PBJgR0027430;  Thu, 25 Jun 2009 11:19:42 GMT
Received: from sj-webmail-7.cisco.com (localhost.localdomain [127.0.0.1]) by sj-webmail-7.cisco.com (8.13.1/8.13.1) with ESMTP id n5PBJgpQ006807;  Thu, 25 Jun 2009 04:19:42 -0700
Received: from sj-webmail-7 (root@localhost) by sj-webmail-7.cisco.com (8.13.1/8.13.1/Submit) with ESMTP id n5PBJgAB006806; Thu, 25 Jun 2009 04:19:42 -0700
Received: from rginotrawxp03 ( [10.78.164.143]) by sj-webmail-7 (Scalix SMTP Relay 10.0.5.3) via ESMTP; Thu, 25 Jun 2009 04:19:42 -0700 (PDT)
Date: Thu, 25 Jun 2009 16:48:22 -0700
From: Rajiv Ginotra <rginotra@cisco.com>
To: <megaco-request@ietf.org>, <megaco@ietf.org>
Message-ID: <003401c9f5ef$6d9c2bb0$8fa44e0a@rginotrawxp03>
x-scalix-Hops: 1
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acn17ulmaRTywoKSQ3avd+BjlY84yAAAHXaA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0035_01C9F5B4.C13FC4B0"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9502; t=1245928783; x=1246792783; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rginotra@cisco.com; z=From:=20Rajiv=20Ginotra=20<rginotra@cisco.com> |Subject:=20MG=20Behavior=20on=20getting=20pending=20messag e=20response=20from=20MGC=20on=20ITO(Inactivity=20Timer)=20t imeout |Sender:=20; bh=8FXUjOZSgwtWmOIz0ZxXBXiMMWQW6RB0kvNUsKWGtvA=; b=s6W1oEJy4zqTNgUW5aUsK40xtqKwKtzTbTHm1pX/9AEvPrPSabJsc8l7vw xmDK+R0uhxOniF/4IAGPdlBitucMqLmwNvMYSbKpToyifc9Oian30qphU0tx hQjcZnqd6ES8wfw0+D+tAcf+xINTEbGaM3HN3UK8W2jBmMxRCDOoU=;
Authentication-Results: sj-dkim-1; header.From=rginotra@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Subject: [Megaco] MG Behavior on getting pending message response from MGC on ITO(Inactivity Timer) timeout
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jun 2009 11:20:31 -0000

------=_NextPart_000_0035_01C9F5B4.C13FC4B0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Disposition: inline

Hello All,
 
Consider the following scenario:
When the MG is sending the ITO timeout notify and the MGC sends the pending
message along with IA(Immediate Acknowledgment) in the same  message.
 
 
Question 1: After the ITO transaction retries are  finished, should MG sends
a "909 MGC Impending Failure" service change message to other MGCs
configured in the list or the send a ITO timeout notify with a new
transaction ID.
 
Question 2: Does the IA in the above reply from MGC make the behavior
different?
 
I have enclosed the call flow for reference
 
Regards
Rajiv
 
Call flow
======
[1196396 (10 ms)] !/2 [10.78.161.24]:5099 Transaction=2 {
Context = - {
Modify = ROOT {
Events = 1111 {it/ito {mit = 1000}}
}
}}
 
[10.78.161.24]:5099 [1196396 (10 ms)] !/2 [183.1.13.2]:2965 P = 2{ C = -
{mf=ROOT }}

ITO Timeout notify starts and MGC started sending pending messages:
----------------------------------------------------------------------------
--------------------------
 
[10.78.161.24]:5099 [1197496 (10 ms)] !/2 [183.1.13.2]:2965 T = 538{ C = -
{n=ROOT  { oe = 1111 { IT/ITO }  } }}
 
[1197503 (10 ms)] !/2 [10.78.161.24]:5099 Reply=538 {IA, C  =  - { n=root {
Error = 506 {"506"} }}}
 
[10.78.161.24]:5099 [1197503 (10 ms)] !/2 [183.1.13.2]:2965 k{537,538}
 
[10.78.161.24]:5099 [1198403 (10 ms)] !/2 [183.1.13.2]:2965 T = 539{ C = -
{n=ROOT  { oe = 1111 { IT/ITO }  } }}
 
[1198408 (10 ms)] !/2 [10.78.161.24]:5099 Reply=539 {IA, C  =  - { n=root {
Error = 506 {"506"} }}}
 
[10.78.161.24]:5099 [1198408 (10 ms)] !/2 [183.1.13.2]:2965 k{539}
 
[10.78.161.24]:5099 [1199408 (10 ms)] !/2 [183.1.13.2]:2965 T = 540{ C = -
{n=ROOT  { oe = 1111 { IT/ITO }  } }}
 
[1199412 (10 ms)] !/2 [10.78.161.24]:5099 Reply=540 {IA, C  =  - { n=root {
Error = 506 {"506"} }}}
 
[10.78.161.24]:5099 [1199412 (10 ms)] !/2 [183.1.13.2]:2965 k{540}
 
[10.78.161.24]:5099 [1200412 (10 ms)] !/2 [183.1.13.2]:2965 T = 541{ C = -
{n=ROOT  { oe = 1111 { IT/ITO }  } }}
 
[1200417 (10 ms)] !/2 [10.78.161.24]:5099 Reply=541 {IA, C  =  - { n=root {
Error = 506 {"506"} }}}
 
[10.78.161.24]:5099 [1200417 (10 ms)] !/2 [183.1.13.2]:2965 k{541}
 
Now the ITO retries get finished. what would be the next transaction???
 

------=_NextPart_000_0035_01C9F5B4.C13FC4B0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D546533522-25062009><FONT face=3D=
Arial=20
size=3D2>Hello All,</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Conside=
r the=20
following scenario:</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>When th=
e MG is=20
sending the ITO timeout notify and&nbsp;the MGC sends the pending message=
 along=20
with IA(Immediate Acknowledgment)&nbsp;in the same=20
&nbsp;message.</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Questio=
n 1: After=20
the ITO transaction retries are&nbsp; finished, should MG sends a <FONT=20
size=3D2>"909 MGC Impending Failure" </FONT>service change message to oth=
er MGCs=20
configured in the list or the send a ITO timeout notify with a new transa=
ction=20
ID.</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Questio=
n 2: Does the=20
IA in the above reply from MGC make the behavior different?</FONT></SPAN>=
</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>I have e=
nclosed the=20
call flow for reference</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009></SPAN><SPAN class=3D546533522-2506=
2009><FONT=20
face=3DArial size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>Rajiv</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Call=20
flow</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>=3D=3D=3D=3D=3D=3D</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[119639=
6 (10 ms)]=20
!/2 [10.78.161.24]:5099 Transaction=3D2 {<BR>Context =3D - {<BR>Modify =3D=
 ROOT=20
{<BR>Events =3D 1111 {it/ito {mit =3D 1000}}<BR>}<BR>}}</FONT></SPAN></DI=
V>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1196396 (10 ms)] !/2 [183.1.13.2]:2965 P =3D 2{ C =3D - {mf=3DROOT=20
}}<BR></FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>ITO Tim=
eout notify=20
starts and MGC started sending pending messages:</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>----------------------------------------------------------------=
--------------------------------------</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1197496 (10 ms)] !/2 [183.1.13.2]:2965 T =3D 538{ C =3D - {n=3DROOT&nbsp=
; { oe =3D 1111=20
{ IT/ITO }&nbsp; } }}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[119750=
3 (10 ms)]=20
!/2 [10.78.161.24]:5099 Reply=3D538 {IA, C&nbsp; =3D&nbsp; - { n=3Droot {=
 Error =3D 506=20
{"506"} }}}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1197503 (10 ms)] !/2 [183.1.13.2]:2965 k{537,538}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1198403 (10 ms)] !/2 [183.1.13.2]:2965 T =3D 539{ C =3D - {n=3DROOT&nbsp=
; { oe =3D 1111=20
{ IT/ITO }&nbsp; } }}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[119840=
8 (10 ms)]=20
!/2 [10.78.161.24]:5099 Reply=3D539 {IA, C&nbsp; =3D&nbsp; - { n=3Droot {=
 Error =3D 506=20
{"506"} }}}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1198408 (10 ms)] !/2 [183.1.13.2]:2965 k{539}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1199408 (10 ms)] !/2 [183.1.13.2]:2965 T =3D 540{ C =3D - {n=3DROOT&nbsp=
; { oe =3D 1111=20
{ IT/ITO }&nbsp; } }}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[119941=
2 (10 ms)]=20
!/2 [10.78.161.24]:5099 Reply=3D540 {IA, C&nbsp; =3D&nbsp; - { n=3Droot {=
 Error =3D 506=20
{"506"} }}}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1199412 (10 ms)] !/2 [183.1.13.2]:2965 k{540}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1200412 (10 ms)] !/2 [183.1.13.2]:2965 T =3D 541{ C =3D - {n=3DROOT&nbsp=
; { oe =3D 1111=20
{ IT/ITO }&nbsp; } }}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[120041=
7 (10 ms)]=20
!/2 [10.78.161.24]:5099 Reply=3D541 {IA, C&nbsp; =3D&nbsp; - { n=3Droot {=
 Error =3D 506=20
{"506"} }}}</FONT></SPAN></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>[10.78.=
161.24]:5099=20
[1200417 (10 ms)] !/2 [183.1.13.2]:2965 k{541}</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Now the=
 ITO retries=20
get finished. what would be the next transaction???</FONT></SPAN></DIV>
<DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>&nbsp;</DIV></FONT></SPAN></BODY></HTML>

------=_NextPart_000_0035_01C9F5B4.C13FC4B0--

From Albrecht.Schwarz@alcatel-lucent.de  Thu Jun 25 11:17:09 2009
Return-Path: <Albrecht.Schwarz@alcatel-lucent.de>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 546283A6A3B for <megaco@core3.amsl.com>; Thu, 25 Jun 2009 11:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.315
X-Spam-Level: 
X-Spam-Status: No, score=-4.315 tagged_above=-999 required=5 tests=[AWL=0.733,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_29=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TMsRc-3j8vZr for <megaco@core3.amsl.com>; Thu, 25 Jun 2009 11:17:08 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id CA0833A68DC for <megaco@ietf.org>; Thu, 25 Jun 2009 11:17:07 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.dc-m.alcatel-lucent.com [155.132.6.77]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5PI4UgC010276 for <megaco@ietf.org>; Thu, 25 Jun 2009 20:04:30 +0200
Received: from FRVELSMBS23.ad2.ad.alcatel.com ([155.132.6.53]) by FRVELSBHS05.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 25 Jun 2009 20:04:30 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9F5BF.626D82F8"
Date: Thu, 25 Jun 2009 20:04:29 +0200
Message-ID: <F4562D4585113D42AC08DC47FDEC49B001FE2CB7@FRVELSMBS23.ad2.ad.alcatel.com>
In-Reply-To: <003401c9f5ef$6d9c2bb0$8fa44e0a@rginotrawxp03>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Megaco] MG Behavior on getting pending message response from MGCon ITO(Inactivity Timer) timeout
Thread-Index: Acn17ulmaRTywoKSQ3avd+BjlY84yAAAHXaAAAwREQA=
References: <003401c9f5ef$6d9c2bb0$8fa44e0a@rginotrawxp03>
From: "Schwarz Albrecht" <Albrecht.Schwarz@alcatel-lucent.de>
To: <megaco@ietf.org>
X-OriginalArrivalTime: 25 Jun 2009 18:04:30.0547 (UTC) FILETIME=[63030230:01C9F5BF]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: Re: [Megaco] MG Behavior on getting pending message response from MGCon ITO(Inactivity Timer) timeout
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jun 2009 18:17:09 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9F5BF.626D82F8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I'm not sure, but this looks like a bug in the MGC implementation. Hm?
Should be corrected first before thinking about subsequent ServiceChange
procedures.
(At least the it/ito-based "MGC-polling by MG" mechanism can't be used
correctly ...)
=20


________________________________

	From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org]
On Behalf Of Rajiv Ginotra
	Sent: Freitag, 26. Juni 2009 01:48
	To: megaco-request@ietf.org; megaco@ietf.org
	Subject: [Megaco] MG Behavior on getting pending message
response from MGCon ITO(Inactivity Timer) timeout
=09
=09
	Hello All,
	=20
	Consider the following scenario:
	When the MG is sending the ITO timeout notify and the MGC sends
the pending message along with IA(Immediate Acknowledgment) in the same
message.
	=20
	=20
	Question 1: After the ITO transaction retries are  finished,
should MG sends a "909 MGC Impending Failure" service change message to
other MGCs configured in the list or the send a ITO timeout notify with
a new transaction ID.
	=20
	Question 2: Does the IA in the above reply from MGC make the
behavior different?
	=20
	I have enclosed the call flow for reference
	=20
	Regards
	Rajiv
	=20
	Call flow
	=3D=3D=3D=3D=3D=3D
	[1196396 (10 ms)] !/2 [10.78.161.24]:5099 Transaction=3D2 {
	Context =3D - {
	Modify =3D ROOT {
	Events =3D 1111 {it/ito {mit =3D 1000}}
	}
	}}
	=20
	[10.78.161.24]:5099 [1196396 (10 ms)] !/2 [183.1.13.2]:2965 P =3D
2{ C =3D - {mf=3DROOT }}
=09
	ITO Timeout notify starts and MGC started sending pending
messages:
=09
------------------------------------------------------------------------
------------------------------
	=20
	[10.78.161.24]:5099 [1197496 (10 ms)] !/2 [183.1.13.2]:2965 T =3D
538{ C =3D - {n=3DROOT  { oe =3D 1111 { IT/ITO }  } }}
	=20
	[1197503 (10 ms)] !/2 [10.78.161.24]:5099 Reply=3D538 {IA, C  =3D  -
{ n=3Droot { Error =3D 506 {"506"} }}}
	=20
	[10.78.161.24]:5099 [1197503 (10 ms)] !/2 [183.1.13.2]:2965
k{537,538}
	=20
	[10.78.161.24]:5099 [1198403 (10 ms)] !/2 [183.1.13.2]:2965 T =3D
539{ C =3D - {n=3DROOT  { oe =3D 1111 { IT/ITO }  } }}
	=20
	[1198408 (10 ms)] !/2 [10.78.161.24]:5099 Reply=3D539 {IA, C  =3D  -
{ n=3Droot { Error =3D 506 {"506"} }}}
	=20
	[10.78.161.24]:5099 [1198408 (10 ms)] !/2 [183.1.13.2]:2965
k{539}
	=20
	[10.78.161.24]:5099 [1199408 (10 ms)] !/2 [183.1.13.2]:2965 T =3D
540{ C =3D - {n=3DROOT  { oe =3D 1111 { IT/ITO }  } }}
	=20
	[1199412 (10 ms)] !/2 [10.78.161.24]:5099 Reply=3D540 {IA, C  =3D  -
{ n=3Droot { Error =3D 506 {"506"} }}}
	=20
	[10.78.161.24]:5099 [1199412 (10 ms)] !/2 [183.1.13.2]:2965
k{540}
	=20
	[10.78.161.24]:5099 [1200412 (10 ms)] !/2 [183.1.13.2]:2965 T =3D
541{ C =3D - {n=3DROOT  { oe =3D 1111 { IT/ITO }  } }}
	=20
	[1200417 (10 ms)] !/2 [10.78.161.24]:5099 Reply=3D541 {IA, C  =3D  -
{ n=3Droot { Error =3D 506 {"506"} }}}
	=20
	[10.78.161.24]:5099 [1200417 (10 ms)] !/2 [183.1.13.2]:2965
k{541}
	=20
	Now the ITO retries get finished. what would be the next
transaction???
	=20


------_=_NextPart_001_01C9F5BF.626D82F8
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.5803" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"Trebuchet MS" color=3D#800000 =
size=3D2><SPAN=20
class=3D725290218-25062009>I'm not sure, but this looks like a bug in =
the MGC=20
implementation. Hm?</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"Trebuchet MS" color=3D#800000 =
size=3D2><SPAN=20
class=3D725290218-25062009>Should be corrected first before thinking =
about=20
subsequent ServiceChange procedures.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"Trebuchet MS" color=3D#800000 =
size=3D2><SPAN=20
class=3D725290218-25062009>(At least the&nbsp;it/ito-based "MGC-polling =
by MG"=20
mechanism can't be used correctly ...)</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D"Trebuchet MS" color=3D#800000=20
size=3D2></FONT>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; 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>Rajiv=20
  Ginotra<BR><B>Sent:</B> Freitag, 26. Juni 2009 01:48<BR><B>To:</B>=20
  megaco-request@ietf.org; megaco@ietf.org<BR><B>Subject:</B> [Megaco] =
MG=20
  Behavior on getting pending message response from MGCon ITO(Inactivity =
Timer)=20
  timeout<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D546533522-25062009><FONT =
face=3DArial=20
  size=3D2>Hello All,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial =
size=3D2>Consider the=20
  following scenario:</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>When =
the MG is=20
  sending the ITO timeout notify and&nbsp;the MGC sends the pending =
message=20
  along with IA(Immediate Acknowledgment)&nbsp;in the same=20
  &nbsp;message.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial =
size=3D2>Question 1: After=20
  the ITO transaction retries are&nbsp; finished, should MG sends a =
<FONT=20
  size=3D2>"909 MGC Impending Failure" </FONT>service change message to =
other MGCs=20
  configured in the list or the send a ITO timeout notify with a new =
transaction=20
  ID.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial =
size=3D2>Question 2: Does=20
  the IA in the above reply from MGC make the behavior=20
  different?</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>I =
have enclosed=20
  the call flow for reference</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009></SPAN><SPAN=20
  class=3D546533522-25062009><FONT face=3DArial =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>Regards</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>Rajiv</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Call =

  flow</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>=3D=3D=3D=3D=3D=3D</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial =
size=3D2>[1196396 (10 ms)]=20
  !/2 [10.78.161.24]:5099 Transaction=3D2 {<BR>Context =3D - {<BR>Modify =
=3D ROOT=20
  {<BR>Events =3D 1111 {it/ito {mit =3D =
1000}}<BR>}<BR>}}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>[10.78.161.24]:5099 [1196396 (10 ms)] !/2 [183.1.13.2]:2965 P =
=3D 2{ C =3D=20
  - {mf=3DROOT }}<BR></FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>ITO =
Timeout notify=20
  starts and MGC started sending pending messages:</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  =
size=3D2>----------------------------------------------------------------=
--------------------------------------</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>[10.78.161.24]:5099 [1197496 (10 ms)] !/2 [183.1.13.2]:2965 T =
=3D 538{ C=20
  =3D - {n=3DROOT&nbsp; { oe =3D 1111 { IT/ITO }&nbsp; } =
}}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial =
size=3D2>[1197503 (10 ms)]=20
  !/2 [10.78.161.24]:5099 Reply=3D538 {IA, C&nbsp; =3D&nbsp; - { =
n=3Droot { Error =3D=20
  506 {"506"} }}}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>[10.78.161.24]:5099 [1197503 (10 ms)] !/2 [183.1.13.2]:2965=20
  k{537,538}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>[10.78.161.24]:5099 [1198403 (10 ms)] !/2 [183.1.13.2]:2965 T =
=3D 539{ C=20
  =3D - {n=3DROOT&nbsp; { oe =3D 1111 { IT/ITO }&nbsp; } =
}}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial =
size=3D2>[1198408 (10 ms)]=20
  !/2 [10.78.161.24]:5099 Reply=3D539 {IA, C&nbsp; =3D&nbsp; - { =
n=3Droot { Error =3D=20
  506 {"506"} }}}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>[10.78.161.24]:5099 [1198408 (10 ms)] !/2 [183.1.13.2]:2965=20
  k{539}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>[10.78.161.24]:5099 [1199408 (10 ms)] !/2 [183.1.13.2]:2965 T =
=3D 540{ C=20
  =3D - {n=3DROOT&nbsp; { oe =3D 1111 { IT/ITO }&nbsp; } =
}}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial =
size=3D2>[1199412 (10 ms)]=20
  !/2 [10.78.161.24]:5099 Reply=3D540 {IA, C&nbsp; =3D&nbsp; - { =
n=3Droot { Error =3D=20
  506 {"506"} }}}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>[10.78.161.24]:5099 [1199412 (10 ms)] !/2 [183.1.13.2]:2965=20
  k{540}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>[10.78.161.24]:5099 [1200412 (10 ms)] !/2 [183.1.13.2]:2965 T =
=3D 541{ C=20
  =3D - {n=3DROOT&nbsp; { oe =3D 1111 { IT/ITO }&nbsp; } =
}}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial =
size=3D2>[1200417 (10 ms)]=20
  !/2 [10.78.161.24]:5099 Reply=3D541 {IA, C&nbsp; =3D&nbsp; - { =
n=3Droot { Error =3D=20
  506 {"506"} }}}</FONT></SPAN></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2>[10.78.161.24]:5099 [1200417 (10 ms)] !/2 [183.1.13.2]:2965=20
  k{541}</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial size=3D2>Now =
the ITO=20
  retries get finished. what would be the next=20
transaction???</FONT></SPAN></DIV>
  <DIV><SPAN class=3D546533522-25062009><FONT face=3DArial=20
size=3D2>&nbsp;</DIV></BLOCKQUOTE></FONT></SPAN></BODY></HTML>

------_=_NextPart_001_01C9F5BF.626D82F8--

From thomas.miesch@smallmgc.org  Thu Jun 25 09:15:22 2009
Return-Path: <thomas.miesch@smallmgc.org>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 812AC3A6B0E for <megaco@core3.amsl.com>; Thu, 25 Jun 2009 09:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2G2se5fh5Fc for <megaco@core3.amsl.com>; Thu, 25 Jun 2009 09:15:21 -0700 (PDT)
Received: from mail14.bluewin.ch (mail14.bluewin.ch [195.186.19.62]) by core3.amsl.com (Postfix) with ESMTP id 13D8A3A6F21 for <megaco@ietf.org>; Thu, 25 Jun 2009 09:15:15 -0700 (PDT)
X-FXIT-IP: IPv4[83.78.37.149] Epoch[1245945664]
Received: from [83.78.37.149] ([83.78.37.149:20425] helo=[192.168.1.58]) by mail14.bluewin.ch (envelope-from <thomas.miesch@smallmgc.org>) (ecelerity 2.2.2.36 r(27513/27514)) with ESMTP id 08/15-03095-E3F934A4; Thu, 25 Jun 2009 16:01:04 +0000
Message-ID: <4A439F3D.3050401@smallmgc.org>
Date: Thu, 25 Jun 2009 18:01:01 +0200
From: Thomas Miesch <thomas.miesch@smallmgc.org>
User-Agent: Thunderbird 2.0.0.21 (X11/20090409)
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 26 Jun 2009 08:04:16 -0700
Subject: [Megaco] Open Source Media Gateway Controller
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jun 2009 16:34:32 -0000

Hi All,

I would like to inform the interested people, that I have started a 
project which should conclude in a open source media gateway controller.

More information can be obtained here
www.smallmgc.org

I hope it is not considered to be inappropriate to publish this 
information in this list.
But I have read in the past questions about open source gateway 
controllers and to my knowledge there was until now only one from 
Ericcson in Erlang.
So if somebody is still interested he could have a look.

Regards
Thomas





From Albrecht.Schwarz@alcatel-lucent.de  Fri Jun 26 12:36:50 2009
Return-Path: <Albrecht.Schwarz@alcatel-lucent.de>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C46CD28C140 for <megaco@core3.amsl.com>; Fri, 26 Jun 2009 12:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.850, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1j7w3ACrOcQV for <megaco@core3.amsl.com>; Fri, 26 Jun 2009 12:36:50 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id BDB633A6BA9 for <megaco@ietf.org>; Fri, 26 Jun 2009 12:36:49 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.dc-m.alcatel-lucent.com [155.132.6.75]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5QJb6Gw025335;  Fri, 26 Jun 2009 21:37:06 +0200
Received: from FRVELSMBS23.ad2.ad.alcatel.com ([155.132.6.53]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 26 Jun 2009 21:37:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 26 Jun 2009 21:36:30 +0200
Message-ID: <F4562D4585113D42AC08DC47FDEC49B001FE3003@FRVELSMBS23.ad2.ad.alcatel.com>
In-Reply-To: <4A439F3D.3050401@smallmgc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Megaco] Open Source Media Gateway Controller
Thread-Index: Acn2b35jCFu/K/r/QmWxEEkSPtSJNQAJOA8g
References: <4A439F3D.3050401@smallmgc.org>
From: "Schwarz Albrecht" <Albrecht.Schwarz@alcatel-lucent.de>
To: "Thomas Miesch" <thomas.miesch@smallmgc.org>, <megaco@ietf.org>
X-OriginalArrivalTime: 26 Jun 2009 19:37:06.0154 (UTC) FILETIME=[7CD31CA0:01C9F695]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Subject: Re: [Megaco] Open Source Media Gateway Controller
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2009 19:36:50 -0000

Thomas,

guess that any announcements about open source projects are certainly
appreciated by the H.248 community.

Got a quick look on your side, which is mentioning first MGC
applications for RGW/AGW and TGW, i.e. PSTN emulation subsystem
solutions.

Question: is your MGC code "general purpose", or already "profiled" for
these PES applications?
If "profile", is the code compliant to=20
- ETSI TISPAN H.248 profile for RAGWs (-> ES 283 002)?
- ETSI TISPAN H.248 profile for TGWs (-> ES 283 024 / 283 049)?
- or any 3GPP profile?

Might be interesting for the community when evaluating the applicability
of open source code.

Regards,
Albrecht


> -----Original Message-----
> From: megaco-bounces@ietf.org=20
> [mailto:megaco-bounces@ietf.org] On Behalf Of Thomas Miesch
> Sent: Donnerstag, 25. Juni 2009 18:01
> To: megaco@ietf.org
> Subject: [Megaco] Open Source Media Gateway Controller
>=20
> Hi All,
>=20
> I would like to inform the interested people, that I have=20
> started a project which should conclude in a open source=20
> media gateway controller.
>=20
> More information can be obtained here
> www.smallmgc.org
>=20
> I hope it is not considered to be inappropriate to publish=20
> this information in this list.
> But I have read in the past questions about open source=20
> gateway controllers and to my knowledge there was until now=20
> only one from Ericcson in Erlang.
> So if somebody is still interested he could have a look.
>=20
> Regards
> Thomas
>=20
>=20
>=20
>=20
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>=20

From Albrecht.Schwarz@alcatel-lucent.de  Sat Jun 27 02:08:06 2009
Return-Path: <Albrecht.Schwarz@alcatel-lucent.de>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB41A3A6963 for <megaco@core3.amsl.com>; Sat, 27 Jun 2009 02:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.387
X-Spam-Level: 
X-Spam-Status: No, score=-4.387 tagged_above=-999 required=5 tests=[AWL=0.779,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vIJt-THOxKBV for <megaco@core3.amsl.com>; Sat, 27 Jun 2009 02:08:05 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [62.23.212.56]) by core3.amsl.com (Postfix) with ESMTP id 73BE63A6863 for <megaco@ietf.org>; Sat, 27 Jun 2009 02:08:04 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.dc-m.alcatel-lucent.com [155.132.6.77]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n5R98I9X010825;  Sat, 27 Jun 2009 11:08:20 +0200
Received: from FRVELSMBS23.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS05.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 27 Jun 2009 11:08:19 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 27 Jun 2009 11:07:07 +0200
Message-ID: <F4562D4585113D42AC08DC47FDEC49B001FE3005@FRVELSMBS23.ad2.ad.alcatel.com>
In-Reply-To: <4A45D76F.2070305@smallmgc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Megaco] Open Source Media Gateway Controller
Thread-Index: Acn3ANRIBgRiaY3cTcKvDuMqcfJAcgABazfA
References: <4A439F3D.3050401@smallmgc.org> <F4562D4585113D42AC08DC47FDEC49B001FE3003@FRVELSMBS23.ad2.ad.alcatel.com> <4A45D76F.2070305@smallmgc.org>
From: "Schwarz Albrecht" <Albrecht.Schwarz@alcatel-lucent.de>
To: "Thomas Miesch" <thomas.miesch@smallmgc.org>
X-OriginalArrivalTime: 27 Jun 2009 09:08:19.0631 (UTC) FILETIME=[D07A4BF0:01C9F706]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
Cc: megaco@ietf.org
Subject: Re: [Megaco] Open Source Media Gateway Controller
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jun 2009 09:08:06 -0000

Thanks!
Which H.248 message encoding mode do you support, - binary, text or
both?=20

> -----Original Message-----
> From: Thomas Miesch [mailto:thomas.miesch@smallmgc.org]=20
> Sent: Samstag, 27. Juni 2009 10:25
> To: Schwarz Albrecht
> Cc: megaco@ietf.org
> Subject: Re: [Megaco] Open Source Media Gateway Controller
>=20
> Hi Albrecht,
>=20
> At the moment I don't follow any profile. My goal is and was=20
> to be able to do calls.
> That is possible with the version I have published.
> You see I have labeled the version as 0.006 so the project is=20
> at the very beginning.
> But I think it still can be useful for some persons in a Lab.
>=20
> This as to clarify the status of the project.
>=20
> At the moment my code is general purpose. That is that I=20
> don't follow any profile for the moment!
>=20
> But as I have mentioned finally SmallMGC could take the role=20
> of an AGCF in the IMS network.
> I am not sure if for that function already a profile exists.
> But for such function the ETSI TISPAN H.248 profile for RAGWs=20
> (-> ES 283
> 002) is more applicable.
> So in the future it will be clearly necessary to implement=20
> this profile.
>=20
> On the hand hand I would also like to implement the  ETSI=20
> TISPAN H.248 profile for TGWs  (-> ES 283 024 / 283 049). But=20
> if this is going to happen I will decide in the future,=20
> depending on the responses I receive.
>=20
>=20
> Regards
> Thomas
>=20
>=20
>=20
> Schwarz Albrecht wrote:
> > Thomas,
> >
> > guess that any announcements about open source projects are=20
> certainly=20
> > appreciated by the H.248 community.
> >
> > Got a quick look on your side, which is mentioning first MGC=20
> > applications for RGW/AGW and TGW, i.e. PSTN emulation subsystem=20
> > solutions.
> >
> > Question: is your MGC code "general purpose", or already "profiled"=20
> > for these PES applications?
> > If "profile", is the code compliant to
> > - ETSI TISPAN H.248 profile for RAGWs (-> ES 283 002)?
> > - ETSI TISPAN H.248 profile for TGWs (-> ES 283 024 / 283 049)?
> > - or any 3GPP profile?
> >
> > Might be interesting for the community when evaluating the=20
> > applicability of open source code.
> >
> > Regards,
> > Albrecht
> >
> >
> >  =20
> >> -----Original Message-----
> >> From: megaco-bounces@ietf.org
> >> [mailto:megaco-bounces@ietf.org] On Behalf Of Thomas Miesch
> >> Sent: Donnerstag, 25. Juni 2009 18:01
> >> To: megaco@ietf.org
> >> Subject: [Megaco] Open Source Media Gateway Controller
> >>
> >> Hi All,
> >>
> >> I would like to inform the interested people, that I have=20
> started a=20
> >> project which should conclude in a open source media gateway=20
> >> controller.
> >>
> >> More information can be obtained here www.smallmgc.org
> >>
> >> I hope it is not considered to be inappropriate to publish this=20
> >> information in this list.
> >> But I have read in the past questions about open source gateway=20
> >> controllers and to my knowledge there was until now only one from=20
> >> Ericcson in Erlang.
> >> So if somebody is still interested he could have a look.
> >>
> >> Regards
> >> Thomas
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Megaco mailing list
> >> Megaco@ietf.org
> >> https://www.ietf.org/mailman/listinfo/megaco
> >>
> >>    =20
> >
> >
> >  =20
>=20
>=20

From Christian.Groves@nteczone.com  Sat Jun 27 08:46:24 2009
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9A4E3A6ABC for <megaco@core3.amsl.com>; Sat, 27 Jun 2009 08:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.364
X-Spam-Level: *
X-Spam-Status: No, score=1.364 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FvoMYd-RbP5b for <megaco@core3.amsl.com>; Sat, 27 Jun 2009 08:46:24 -0700 (PDT)
Received: from quasar.websiteactive.com (unknown [202.191.61.216]) by core3.amsl.com (Postfix) with ESMTP id C85B93A6919 for <megaco@ietf.org>; Sat, 27 Jun 2009 08:46:23 -0700 (PDT)
Received: from [195.15.20.10] (helo=[127.0.0.1]) by quasar.websiteactive.com with esmtpa (Exim 4.69) (envelope-from <Christian.Groves@nteczone.com>) id 1MKa6x-0005Yt-Hs for megaco@ietf.org; Sun, 28 Jun 2009 01:46:39 +1000
Message-ID: <4A463ED8.9020702@nteczone.com>
Date: Sun, 28 Jun 2009 01:46:32 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: megaco ietf <megaco@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - quasar.websiteactive.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
Subject: [Megaco] Results of ITU-T Q.3/16 Meeting
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jun 2009 15:46:24 -0000

Hello all,

The results of the ITU-T Q3/16 meeting addressing Media Gateway Control 
protocols are now available.

The meeting report can be found at:
http://wftp3.itu.int/av-arch/avc-site/2009-2012/0906_Gen/TD-15.zip

The output drafts can be found at:
http://wftp3.itu.int/av-arch/avc-site/2009-2012/0906_Gen/0906_Gen.html

Regards, Christian


From thomas.miesch@smallmgc.org  Sat Jun 27 02:21:10 2009
Return-Path: <thomas.miesch@smallmgc.org>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 391CC3A69E2 for <megaco@core3.amsl.com>; Sat, 27 Jun 2009 02:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.516
X-Spam-Level: 
X-Spam-Status: No, score=-1.516 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MEEFYREvAzY for <megaco@core3.amsl.com>; Sat, 27 Jun 2009 02:21:09 -0700 (PDT)
Received: from mail17.bluewin.ch (mail17.bluewin.ch [195.186.18.64]) by core3.amsl.com (Postfix) with ESMTP id ACBB13A6A7B for <megaco@ietf.org>; Sat, 27 Jun 2009 02:21:08 -0700 (PDT)
X-FXIT-IP: IPv4[83.77.197.179] Epoch[1246094486]
Received: from [83.77.197.179] ([83.77.197.179:4963] helo=[192.168.1.58]) by mail17.bluewin.ch (envelope-from <thomas.miesch@smallmgc.org>) (ecelerity 2.2.2.36 r(27513/27514)) with ESMTP id 20/78-02822-494E54A4; Sat, 27 Jun 2009 09:21:26 +0000
Message-ID: <4A45E493.5080704@smallmgc.org>
Date: Sat, 27 Jun 2009 11:21:23 +0200
From: Thomas Miesch <thomas.miesch@smallmgc.org>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: Schwarz Albrecht <Albrecht.Schwarz@alcatel-lucent.de>
References: <4A439F3D.3050401@smallmgc.org> <F4562D4585113D42AC08DC47FDEC49B001FE3003@FRVELSMBS23.ad2.ad.alcatel.com> <4A45D76F.2070305@smallmgc.org> <F4562D4585113D42AC08DC47FDEC49B001FE3005@FRVELSMBS23.ad2.ad.alcatel.com>
In-Reply-To: <F4562D4585113D42AC08DC47FDEC49B001FE3005@FRVELSMBS23.ad2.ad.alcatel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 27 Jun 2009 12:08:22 -0700
Cc: megaco@ietf.org
Subject: Re: [Megaco] Open Source Media Gateway Controller
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jun 2009 09:21:10 -0000

You are absolutely right. That I have never mentioned.

The Encoding is text and text only.
Binary I have never considered.
I don't know if binary encoding is really used in Networks.

Schwarz Albrecht wrote:
> Thanks!
> Which H.248 message encoding mode do you support, - binary, text or
> both? 
>
>   
>> -----Original Message-----
>> From: Thomas Miesch [mailto:thomas.miesch@smallmgc.org] 
>> Sent: Samstag, 27. Juni 2009 10:25
>> To: Schwarz Albrecht
>> Cc: megaco@ietf.org
>> Subject: Re: [Megaco] Open Source Media Gateway Controller
>>
>> Hi Albrecht,
>>
>> At the moment I don't follow any profile. My goal is and was 
>> to be able to do calls.
>> That is possible with the version I have published.
>> You see I have labeled the version as 0.006 so the project is 
>> at the very beginning.
>> But I think it still can be useful for some persons in a Lab.
>>
>> This as to clarify the status of the project.
>>
>> At the moment my code is general purpose. That is that I 
>> don't follow any profile for the moment!
>>
>> But as I have mentioned finally SmallMGC could take the role 
>> of an AGCF in the IMS network.
>> I am not sure if for that function already a profile exists.
>> But for such function the ETSI TISPAN H.248 profile for RAGWs 
>> (-> ES 283
>> 002) is more applicable.
>> So in the future it will be clearly necessary to implement 
>> this profile.
>>
>> On the hand hand I would also like to implement the  ETSI 
>> TISPAN H.248 profile for TGWs  (-> ES 283 024 / 283 049). But 
>> if this is going to happen I will decide in the future, 
>> depending on the responses I receive.
>>
>>
>> Regards
>> Thomas
>>
>>
>>
>> Schwarz Albrecht wrote:
>>     
>>> Thomas,
>>>
>>> guess that any announcements about open source projects are 
>>>       
>> certainly 
>>     
>>> appreciated by the H.248 community.
>>>
>>> Got a quick look on your side, which is mentioning first MGC 
>>> applications for RGW/AGW and TGW, i.e. PSTN emulation subsystem 
>>> solutions.
>>>
>>> Question: is your MGC code "general purpose", or already "profiled" 
>>> for these PES applications?
>>> If "profile", is the code compliant to
>>> - ETSI TISPAN H.248 profile for RAGWs (-> ES 283 002)?
>>> - ETSI TISPAN H.248 profile for TGWs (-> ES 283 024 / 283 049)?
>>> - or any 3GPP profile?
>>>
>>> Might be interesting for the community when evaluating the 
>>> applicability of open source code.
>>>
>>> Regards,
>>> Albrecht
>>>
>>>
>>>   
>>>       
>>>> -----Original Message-----
>>>> From: megaco-bounces@ietf.org
>>>> [mailto:megaco-bounces@ietf.org] On Behalf Of Thomas Miesch
>>>> Sent: Donnerstag, 25. Juni 2009 18:01
>>>> To: megaco@ietf.org
>>>> Subject: [Megaco] Open Source Media Gateway Controller
>>>>
>>>> Hi All,
>>>>
>>>> I would like to inform the interested people, that I have 
>>>>         
>> started a 
>>     
>>>> project which should conclude in a open source media gateway 
>>>> controller.
>>>>
>>>> More information can be obtained here www.smallmgc.org
>>>>
>>>> I hope it is not considered to be inappropriate to publish this 
>>>> information in this list.
>>>> But I have read in the past questions about open source gateway 
>>>> controllers and to my knowledge there was until now only one from 
>>>> Ericcson in Erlang.
>>>> So if somebody is still interested he could have a look.
>>>>
>>>> Regards
>>>> Thomas
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Megaco mailing list
>>>> Megaco@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/megaco
>>>>
>>>>     
>>>>         
>>>   
>>>       
>>     
>
>
>   


From thomas.miesch@smallmgc.org  Sat Jun 27 01:25:08 2009
Return-Path: <thomas.miesch@smallmgc.org>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A3813A6CCB for <megaco@core3.amsl.com>; Sat, 27 Jun 2009 01:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.516
X-Spam-Level: 
X-Spam-Status: No, score=-1.516 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qfc9sDtpVduo for <megaco@core3.amsl.com>; Sat, 27 Jun 2009 01:25:06 -0700 (PDT)
Received: from mail15.bluewin.ch (mail15.bluewin.ch [195.186.18.63]) by core3.amsl.com (Postfix) with ESMTP id 4E59D3A69B6 for <megaco@ietf.org>; Sat, 27 Jun 2009 01:25:05 -0700 (PDT)
X-FXIT-IP: IPv4[83.77.197.179] Epoch[1246091123]
Received: from [83.77.197.179] ([83.77.197.179:3084] helo=[192.168.1.58]) by mail15.bluewin.ch (envelope-from <thomas.miesch@smallmgc.org>) (ecelerity 2.2.2.36 r(27513/27514)) with ESMTP id DD/31-31053-177D54A4; Sat, 27 Jun 2009 08:25:23 +0000
Message-ID: <4A45D76F.2070305@smallmgc.org>
Date: Sat, 27 Jun 2009 10:25:19 +0200
From: Thomas Miesch <thomas.miesch@smallmgc.org>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: Schwarz Albrecht <Albrecht.Schwarz@alcatel-lucent.de>
References: <4A439F3D.3050401@smallmgc.org> <F4562D4585113D42AC08DC47FDEC49B001FE3003@FRVELSMBS23.ad2.ad.alcatel.com>
In-Reply-To: <F4562D4585113D42AC08DC47FDEC49B001FE3003@FRVELSMBS23.ad2.ad.alcatel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 27 Jun 2009 12:08:46 -0700
Cc: megaco@ietf.org
Subject: Re: [Megaco] Open Source Media Gateway Controller
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jun 2009 08:25:08 -0000

Hi Albrecht,

At the moment I don't follow any profile. My goal is and was to be able 
to do calls.
That is possible with the version I have published.
You see I have labeled the version as 0.006 so the project is at the 
very beginning.
But I think it still can be useful for some persons in a Lab.

This as to clarify the status of the project.

At the moment my code is general purpose. That is that I don't follow 
any profile for the moment!

But as I have mentioned finally SmallMGC could take the role of an AGCF 
in the IMS network.
I am not sure if for that function already a profile exists.
But for such function the ETSI TISPAN H.248 profile for RAGWs (-> ES 283 
002) is more applicable.
So in the future it will be clearly necessary to implement this profile.

On the hand hand I would also like to implement the  ETSI TISPAN H.248 
profile for TGWs  (-> ES 283 024 / 283 049). But if this is going to 
happen I will decide in the future, depending on the responses I receive.


Regards
Thomas



Schwarz Albrecht wrote:
> Thomas,
>
> guess that any announcements about open source projects are certainly
> appreciated by the H.248 community.
>
> Got a quick look on your side, which is mentioning first MGC
> applications for RGW/AGW and TGW, i.e. PSTN emulation subsystem
> solutions.
>
> Question: is your MGC code "general purpose", or already "profiled" for
> these PES applications?
> If "profile", is the code compliant to 
> - ETSI TISPAN H.248 profile for RAGWs (-> ES 283 002)?
> - ETSI TISPAN H.248 profile for TGWs (-> ES 283 024 / 283 049)?
> - or any 3GPP profile?
>
> Might be interesting for the community when evaluating the applicability
> of open source code.
>
> Regards,
> Albrecht
>
>
>   
>> -----Original Message-----
>> From: megaco-bounces@ietf.org 
>> [mailto:megaco-bounces@ietf.org] On Behalf Of Thomas Miesch
>> Sent: Donnerstag, 25. Juni 2009 18:01
>> To: megaco@ietf.org
>> Subject: [Megaco] Open Source Media Gateway Controller
>>
>> Hi All,
>>
>> I would like to inform the interested people, that I have 
>> started a project which should conclude in a open source 
>> media gateway controller.
>>
>> More information can be obtained here
>> www.smallmgc.org
>>
>> I hope it is not considered to be inappropriate to publish 
>> this information in this list.
>> But I have read in the past questions about open source 
>> gateway controllers and to my knowledge there was until now 
>> only one from Ericcson in Erlang.
>> So if somebody is still interested he could have a look.
>>
>> Regards
>> Thomas
>>
>>
>>
>>
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>
>>     
>
>
>   


From claudio.fontana@gmail.com  Sat Jun 27 15:14:11 2009
Return-Path: <claudio.fontana@gmail.com>
X-Original-To: megaco@core3.amsl.com
Delivered-To: megaco@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19D3E3A6947 for <megaco@core3.amsl.com>; Sat, 27 Jun 2009 15:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xogfpmBSOo-v for <megaco@core3.amsl.com>; Sat, 27 Jun 2009 15:14:10 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by core3.amsl.com (Postfix) with ESMTP id 7AF9C3A6B17 for <megaco@ietf.org>; Sat, 27 Jun 2009 15:14:04 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id e12so229435fga.18 for <megaco@ietf.org>; Sat, 27 Jun 2009 15:14:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=TG7Fz0ooQJoltiH+Dni3UvQQ5Ygpi4G84NVXwEornBY=; b=bA+4aS+NS2MoHVxsdefvxWUujlzgVzVwkURf7isMHtmtE9FYwGTAiMZdCRKJ0z8LtD ebH4vdXZFOh+GoBDrWv8MetPU8BUzDWU19OJeAeOMhhNDRHCSjvA9jUAVEGCo+bzOIl6 gB9wZ5Hcyu8p3jGKDxzTjuU87QKFh/jCWtpk8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ABOgLt9KX8+hcbFPQ3Zq5nwJH5xetcsqJfhhUxO1/xR9yIf/m+oaW3eeATPoPvnont Ux4qgYAIZRB1VioOFnY0a3gou47x0IPUzD9NA6Bs5wICa6Pp6ogijRjHNURWTe6ojqDp wNUm5kepNqQh8oULv3VFitYz/6h1loLRiHMP4=
Received: by 10.86.89.6 with SMTP id m6mr775736fgb.1.1246140862285; Sat, 27 Jun 2009 15:14:22 -0700 (PDT)
Received: from ?192.168.0.10? (77-57-218-172.dclient.hispeed.ch [77.57.218.172]) by mx.google.com with ESMTPS id d6sm11223667fga.5.2009.06.27.15.14.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 27 Jun 2009 15:14:21 -0700 (PDT)
Message-ID: <4A469A08.7000309@gmail.com>
Date: Sun, 28 Jun 2009 00:15:36 +0200
From: Claudio Fontana <claudio.fontana@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080213)
MIME-Version: 1.0
To: Thomas Miesch <thomas.miesch@smallmgc.org>
References: <4A439F3D.3050401@smallmgc.org>	<F4562D4585113D42AC08DC47FDEC49B001FE3003@FRVELSMBS23.ad2.ad.alcatel.com>	<4A45D76F.2070305@smallmgc.org>	<F4562D4585113D42AC08DC47FDEC49B001FE3005@FRVELSMBS23.ad2.ad.alcatel.com> <4A45E493.5080704@smallmgc.org>
In-Reply-To: <4A45E493.5080704@smallmgc.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org, Schwarz Albrecht <Albrecht.Schwarz@alcatel-lucent.de>
Subject: Re: [Megaco] Open Source Media Gateway Controller
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jun 2009 22:14:53 -0000

Thomas Miesch wrote:
> You are absolutely right. That I have never mentioned.
> 
> The Encoding is text and text only.
> Binary I have never considered.
> I don't know if binary encoding is really used in Networks.

Yes, it is.

