[Megaco] Mux Related Detail Document
Atul Saini <Atul@huawei.com> Wed, 14 January 2004 01:43 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26629 for <megaco-archive@lists.ietf.org>; Tue, 13 Jan 2004 20:43:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aga3h-0007Gs-4N; Tue, 13 Jan 2004 20:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aga3E-0007Fu-3v for megaco@optimus.ietf.org; Tue, 13 Jan 2004 20:42:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26588 for <megaco@ietf.org>; Tue, 13 Jan 2004 20:42:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aga3B-0002i1-00 for megaco@ietf.org; Tue, 13 Jan 2004 20:42:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aga1J-0002eO-00 for megaco@ietf.org; Tue, 13 Jan 2004 20:40:36 -0500
Received: from mta1.huawei.com ([61.144.161.40] helo=huawei.com) by ietf-mx with esmtp (Exim 4.12) id 1AgZzj-0002c4-00 for megaco@ietf.org; Tue, 13 Jan 2004 20:38:55 -0500
Received: from a70444 (huawei.com [172.17.1.60]) by mta1.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTPA id <0HRG00LWVHIBW5@mta1.huawei.com> for megaco@ietf.org; Wed, 14 Jan 2004 09:30:13 +0800 (CST)
Date: Wed, 14 Jan 2004 09:39:18 +0800
From: Atul Saini <Atul@huawei.com>
To: megaco@ietf.org
Message-id: <002001c3da3f$3a4ceaa0$6a00460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
X-Mailer: Microsoft Outlook Express 5.50.4927.1200
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <20040113202900.3883.9447.Mailman@www1.ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40, HTML_FONTCOLOR_BLUE, HTML_MESSAGE autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Mux Related Detail Document
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Hi All ,
I am looking for some detail document regarding using for MUX termination.
for handling media coming from H324 terminal to be sent to RTP Audio and
Video Stream..
If Any one have some details .Please send it ASAP .
Thanks and Regards,
Atul Saini
"You are never given a wish without being given the power to make it true;
You may have to work for it however"
Richard Bach
----- Original Message -----
From: <megaco-request@ietf.org>
To: <megaco@ietf.org>
Sent: Wednesday, January 14, 2004 4:29 AM
Subject: Megaco digest, Vol 1 #1057 - 5 msgs
> Send Megaco mailing list submissions to
> megaco@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www1.ietf.org/mailman/listinfo/megaco
> or, via email, send a message with subject or body 'help' to
> megaco-request@ietf.org
>
> You can reach the person managing the list at
> megaco-admin@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Megaco digest..."
>
>
> Today's Topics:
>
> 1. RE: TPKT value for H.248 over TCP (Sampath Komanduri)
> 2. Termination Id = *
(=?iso-8859-1?Q?Carlos_Rodr=EDguez_Alcal=E1_Villagra?=)
> 3. RE: Termination Id = * (Sampath Komanduri)
> 4. RE: Termination Id = * (Kevin Boyle)
> 5. RE: Termination Id = * (Sampath Komanduri)
>
> --__--__--
>
> Message: 1
> Reply-To: <sampathk@cisco.com>
> From: "Sampath Komanduri" <sampathk@cisco.com>
> To: "'MEGACO list'" <megaco@ietf.org>
> Subject: RE: [Megaco] TPKT value for H.248 over TCP
> Date: Tue, 13 Jan 2004 09:24:39 -0800
> Organization: Cisco Systems
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_000C_01C3D9B7.12247E90
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> Could the author of Annex D pls. respond?
>
> Thanks,
> Sampath
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> Sampath Komanduri
> Sent: Tuesday, January 06, 2004 8:16 PM
> To: 'MEGACO list'
> Subject: [Megaco] TPKT value for H.248 over TCP
> Importance: High
>
>
> Hi List,
> I am not sure if this question was already raised in the list. If it
> was, pls. point me to the discussion and the consensus.
>
> According to ANNEX D of H.248.1 protocol, "TPKT, according to
> <http://www.faqs.org/rfcs/rfc1006.html> RFC 1006, SHALL be used to
> delineate messages within the TCP stream". RFC 1006 limits the size of
> TPDU to 65524. Replicating the relevant text here for convenience:
>
> ***************************************************
> "A TPKT consists of two parts: a packet-header and a TPDU.
> The format of the header is constant regardless of the type of
> packet.
> The format of the packet-header is as follows:
>
> 0 1 2 3
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | vrsn | reserved | packet length |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> where:
>
> vrsn 8 bits
>
> This field is always 3 for the version of the protocol described
> in this memo.
>
> packet length 16 bits (min=7, max=65535)
>
> This field contains the length of entire packet in octets,
> including packet-header.
> This permits a maximum TPDU size of 65531 octets.
> Based on the size of the data transfer (DT) TPDU, this permits a
> maximum
> TSDU size of 65524 octets."
> *********************************************************
>
> This causes an issue. Based on the wildcard level of Audit and the
> descriptors involved, this size could easily exceed 64K size (especially
> if MG and MGC are using Long text format and white spaces in the
> messages). In few cases, it is possible to return an error code (533:
> Response exceeds maximum transport PDU size).
> However, in some cases returning 533 is not an option.
> Consider for example the following scenario: After an association is
> DISCONNECTED, MGC may want to get the list of non-null contexts on the
> gateway using the following command (pls. ignore if there is any mistake
> in the message and reply construct):
>
> !/1 [10.102.2.201]:4000 T=3700003{C=*{AV=ROOT{AT{}}}}
> !/1 ABCD_MG P=3700003{C=1{AV=C{*}},C=2{AV=C{*}},C=3{AV=C{*}}, ....and so
> on}
>
> In the best case (i.e. no white-space, no audit descriptor and short
> format), this allows for an MG to have only 5000 active contexts on the
> card. Anything more (or any variation in the audit command) will reduce
> the number of active contexts that an MG can have even with TCP as the
> transport option.
> Responding with 533 is not an option here since that would leave MG-MGC
> in state from where there is no elegant way out (at least from H.248
> protocol).
>
> How do the gurus' on list suggest we solve this issue? Couple of ideas
> that come to mind are:
>
> 1. Define a Bulk-Audit Package/scheme: As was done for MGCP, define
> a Bulk-Audit package/scheme especially with support for
> RangeWildcard = "[" NumericalRange *( "," NumericalRange ) "]" and
> NumericalRange = 1*(DIGIT) [ "-" 1*(DIGIT) ].
> This will certainly reduce the cases and scenarios when MG/MGC will
> run into the issue under discussion but may not eliminate it.
>
> 2. Add more information on W- Audit support in the protocol.
>
> 3. Introduce RFC 1006 modification (with version field 4) such that
> "packet length" of packet header in TPKT is 32 bits as opposed to 16
> bits.
>
> 4. Combination of the above schemes.
>
> 5. Anything else?
>
> Pls. advice on how this problem can be solved?
>
> Thanks,
> Sampath
>
>
> ------=_NextPart_000_000C_01C3D9B7.12247E90
> Content-Type: text/html;
> charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
> charset=3Dus-ascii">
> <TITLE>Message</TITLE>
>
> <META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR></HEAD>
> <BODY>
> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
> class=3D673442317-13012004>Could=20
> the author of Annex D pls. respond?</SPAN></FONT></DIV>
> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
> class=3D673442317-13012004></SPAN></FONT> </DIV>
> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
> class=3D673442317-13012004>Thanks,</SPAN></FONT></DIV>
> <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
> class=3D673442317-13012004>Sampath</SPAN></FONT></DIV>
> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
> <DIV></DIV>
> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
> align=3Dleft><FONT=20
> face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
> megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] <B>On Behalf Of=20
> </B>Sampath Komanduri<BR><B>Sent:</B> Tuesday, January 06, 2004 8:16=20
> PM<BR><B>To:</B> 'MEGACO list'<BR><B>Subject:</B> [Megaco] TPKT value =
> for=20
> H.248 over TCP<BR><B>Importance:</B> High<BR><BR></FONT></DIV><!-- =
> Converted from text/plain format -->
> <DIV><FONT face=3DArial size=3D2>Hi List,<BR>I am not sure if this =
> question was=20
> already raised in the list. If it was, pls. point me to the discussion =
> and the=20
> consensus.<BR></FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>According to ANNEX D of H.248.1 =
> protocol, "TPKT,=20
> according to </FONT><A =
> href=3D"http://www.faqs.org/rfcs/rfc1006.html"><FONT=20
> face=3DArial size=3D2>RFC 1006</FONT></A><FONT face=3DArial size=3D2>, =
> SHALL be used=20
> to delineate messages within the TCP stream". RFC =
> 1006 limits the=20
> size of TPDU to 65524. Replicating the relevant text here for=20
> convenience:</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial=20
> =
> size=3D2>***************************************************</FONT></DIV>=
>
> <DIV><FONT face=3DArial size=3D2> "A TPKT =
> consists of two=20
> parts: a packet-header and a TPDU. </FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> The =
> format of the=20
> header is constant regardless of the type of=20
> packet.<BR> The format of the =
> packet-header is=20
> as follows:<BR><BR> =20
> =
> 0 =
> =20
> =
> 1 =
> =20
> =
> 2 =
> =20
> 3<BR> 0 1 2 3 4 5 6 7 8 9 0 =
> 1 2 3 4=20
> 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 =
> 1<BR> =20
> =
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbs=
> p; =20
> | vrsn =20
> | reserved =20
> | packet=20
> length =20
> |<BR> =20
> =
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR><BR>=
> =20
> where:<BR><BR> =20
> =
> vrsn &nb=
> sp; &nbs=
> p;=20
> 8 bits<BR><BR> This field is always 3 =
> for the=20
> version of the protocol described in this=20
> memo.<BR><BR> packet=20
> =
> length &=
> nbsp; =20
> 16 bits (min=3D7, max=3D65535)<BR><BR> =
> This field=20
> contains the length of entire packet in octets, including=20
> packet-header.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> This =
> permits a maximum=20
> TPDU size of 65531 octets.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> Based on =
> the size of=20
> the data transfer (DT) TPDU, this permits a maximum </FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> T</FONT><FONT=20
> face=3DArial size=3D2>SDU size of 65524=20
> =
> octets."<BR>*********************************************************<BR>=
> </FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>This causes an issue. Based on =
> the wildcard=20
> level of Audit and the descriptors involved, this size could =
> easily=20
> exceed 64K size (especially if MG and MGC are using Long text format =
> and white=20
> spaces in the messages). In few cases, it is possible to return=20
> an error code (533: Response exceeds maximum transport PDU=20
> size).</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>However, in some cases returning 533 =
> is not an=20
> option. </FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Consider for example the following =
> scenario:=20
> After an association is DISCONNECTED, MGC may want to get =
> the list of=20
> non-null contexts on the gateway using the following command (pls. =
> ignore if=20
> there is any mistake in the message and reply construct):</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT size=3D2><FONT face=3DArial>!/1 [10.102.2.201]:4000=20
> T=3D3700003{C=3D*{AV=3DROOT{AT{}}}}<BR></FONT><FONT face=3DArial>!/1=20
> ABCD_MG P=3D3700003{C=3D</FONT></FONT><FONT face=3DArial=20
> size=3D2>1{AV=3DC{*}},C=3D2<FONT face=3DArial>{AV=3DC{*}},C=3D3<FONT=20
> face=3DArial>{AV=3DC{*}}, ....and so =
> on}</FONT></FONT><BR></FONT><FONT=20
> face=3DArial></FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>In the best case (i.e. no =
> white-space, no audit=20
> descriptor and short format), this allows for an MG to have only =
> 5000=20
> active contexts on the card. Anything more (or any variation in the =
> audit=20
> command) will reduce the number of active contexts that an MG can have =
> even=20
> with TCP as the transport option.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Responding with 533 is not an option =
> here since=20
> that would leave MG-MGC in state from where there is no elegant way =
> out (at=20
> least from H.248 protocol).</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>How do the gurus' on list suggest we =
> solve this=20
> issue? Couple of ideas that come to mind are:</FONT></DIV>
> <OL>
> <LI><FONT face=3DArial><FONT size=3D2>Define a Bulk-Audit =
> Package/scheme: As was=20
> done for MGCP, define a Bulk-Audit package/scheme especially with =
> support=20
> for <BR> =20
> RangeWildcard =3D "[" NumericalRange *( "," NumericalRange ) "]"=20
> and<BR> NumericalRange =3D =
> 1*(DIGIT)=20
> [ "-" 1*(DIGIT) ].<BR> This will certainly reduce =
> the=20
> cases and scenarios when MG/MGC will run into the issue under =
> discussion but=20
> may not eliminate it.</FONT></FONT>=20
> <LI><FONT face=3DArial size=3D2>Add more information on W- Audit =
> support in the=20
> protocol.</FONT>=20
> <LI><FONT face=3DArial><FONT size=3D2>Introduce RFC 1006 =
> modification (with=20
> version field 4) such that "packet length" of packet header in TPKT =
> is 32=20
> bits as opposed to 16 bits.</FONT></FONT>=20
> <LI><FONT face=3DArial><FONT size=3D2>Combination of the above=20
> schemes.</FONT></FONT>=20
> <LI><FONT face=3DArial size=3D2>Anything else?</FONT></LI></OL>
> <DIV><FONT face=3DArial size=3D2>Pls. advice on how this problem can =
> be=20
> solved?</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
> size=3D2></FONT><FONT=20
> face=3DArial size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT =
> face=3DArial=20
> size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
> size=3D2></FONT><FONT face=3DArial size=3D2></FONT><BR><FONT =
> face=3DArial><FONT=20
> =
> size=3D2>Thanks,<BR>Sampath</FONT></DIV></BLOCKQUOTE></FONT></BODY></HTML=
> >
>
> ------=_NextPart_000_000C_01C3D9B7.12247E90--
>
>
>
> --__--__--
>
> Message: 2
> From: =?iso-8859-1?Q?Carlos_Rodr=EDguez_Alcal=E1_Villagra?=
<crav@conexion.com.py>
> To: <megaco@ietf.org>
> Date: Tue, 13 Jan 2004 16:51:24 +0100
> Subject: [Megaco] Termination Id = *
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0011_01C3D9F5.7AF16080
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
>
> Can I create this packet??
>
> Mgc to mg1:
> MEGACO/1 [123.123.123.4]:55555
> Transaction=3D10001{
> Context =3D - {
> Modify =3D * { ;with this parameter as * ????
> Events =3D 1111{ al /of}
> }
> }
> }
>
>
> ***************
> It's posible to put in Context * or it must be a Real Termonation Id
> Thanks
> =20
>
> ------=_NextPart_000_0011_01C3D9F5.7AF16080
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META http-equiv=3DContent-Type content=3D"text/html; =
> charset=3Diso-8859-1">
> <META content=3D"MSHTML 6.00.2734.1600" name=3DGENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=3D#ffffff>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Can I create this packet??</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Mgc to mg1:</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>MEGACO/1 =
> [123.123.123.4]:55555</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Transaction=3D10001{</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> Context =3D =
> -</FONT><FONT=20
> face=3DArial size=3D2> {</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> Modify =3D *=20
> { ;with this =
> parameter=20
> as * ????</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =20
> Events =3D 1111{ al =
> /of}</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =20
> }</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =20
> }</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>}</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>***************</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>It's posible to put in Context * or it =
> must be a=20
> Real Termonation Id</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =20
> =
> =20
> =20
> </FONT></DIV></BODY></HTML>
>
> ------=_NextPart_000_0011_01C3D9F5.7AF16080--
>
>
>
> --__--__--
>
> Message: 3
> Reply-To: <sampathk@cisco.com>
> From: "Sampath Komanduri" <sampathk@cisco.com>
> To: "=?iso-8859-1?Q?'Carlos_Rodr=EDguez_Alcal=E1_Villagra'?="
<crav@conexion.com.py>,
> <megaco@ietf.org>
> Subject: RE: [Megaco] Termination Id = *
> Date: Tue, 13 Jan 2004 12:00:09 -0800
> Organization: Cisco Systems
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0023_01C3D9CC.CB97B9E0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> No, you can't. al/of is an event for SCN termination. Based on the
> recent discussions, SCN terminations should be specific or partially
> specific (see the discussion in=20
> http://www.ietf.org/mail-archive/working-groups/megaco/current/msg04781.
> html)=20
> =20
> Thanks,
> Sampath
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> Carlos Rodr=EDguez Alcal=E1 Villagra
> Sent: Tuesday, January 13, 2004 7:51 AM
> To: megaco@ietf.org
> Subject: [Megaco] Termination Id =3D *
>
>
> =20
> Can I create this packet??
> =20
> Mgc to mg1:
> MEGACO/1 [123.123.123.4]:55555
> Transaction=3D10001{
> Context =3D - {
> Modify =3D * { ;with this parameter as * ????
> Events =3D 1111{ al /of}
> }
> }
> }
> =20
> =20
> ***************
> It's posible to put in Context * or it must be a Real Termonation Id
> Thanks
> =20
>
>
> ------=_NextPart_000_0023_01C3D9CC.CB97B9E0
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
> charset=3Diso-8859-1">
> <TITLE>Message</TITLE>
>
> <META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=3D#ffffff>
> <DIV><SPAN class=3D695305619-13012004><FONT face=3DArial color=3D#0000ff =
> size=3D2>No,=20
> you can't. al/of is an event for SCN termination. Based on the recent=20
> discussions, SCN terminations should be specific or partially =
> specific (see=20
> the discussion in </FONT></SPAN></DIV>
> <DIV><SPAN class=3D695305619-13012004><FONT face=3DArial color=3D#0000ff =
> size=3D2><A=20
> href=3D"http://www.ietf.org/mail-archive/working-groups/megaco/current/ms=
> g04781.html">http://www.ietf.org/mail-archive/working-groups/megaco/curre=
> nt/msg04781.html</A>)</FONT></SPAN><SPAN=20
> class=3D695305619-13012004> </SPAN></DIV>
> <DIV><SPAN class=3D695305619-13012004><FONT face=3DArial color=3D#0000ff =
>
> size=3D2></FONT></SPAN> </DIV>
> <DIV><SPAN class=3D695305619-13012004><FONT face=3DArial color=3D#0000ff =
>
> size=3D2>Thanks,</FONT></SPAN></DIV>
> <DIV><SPAN class=3D695305619-13012004><FONT face=3DArial color=3D#0000ff =
>
> size=3D2>Sampath</FONT></SPAN></DIV>
> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
> <DIV></DIV>
> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
> align=3Dleft><FONT=20
> face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
> megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] <B>On Behalf Of=20
> </B>Carlos Rodr=EDguez Alcal=E1 Villagra<BR><B>Sent:</B> Tuesday, =
> January 13, 2004=20
> 7:51 AM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> [Megaco] =
> Termination=20
> Id =3D *<BR><BR></FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Can I create this =
> packet??</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Mgc to mg1:</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>MEGACO/1 =
> [123.123.123.4]:55555</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Transaction=3D10001{</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> Context =3D =
> -</FONT><FONT=20
> face=3DArial size=3D2> {</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> Modify =3D *=20
> { ;with this =
> parameter=20
> as * ????</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
>
> Events =3D 1111{ al =
> /of}</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
>
> }</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
>
> }</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>}</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>***************</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>It's posible to put in Context * or =
> it must be a=20
> Real Termonation Id</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
>
> =
> =20
> =20
> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
> ------=_NextPart_000_0023_01C3D9CC.CB97B9E0--
>
>
>
> --__--__--
>
> Message: 4
> From: "Kevin Boyle" <kboyle@nortelnetworks.com>
> To: =?iso-8859-1?Q?Carlos_Rodr=EDguez_Alcal=E1_Villagra?=
> <crav@conexion.com.py>,
> megaco@ietf.org
> Subject: RE: [Megaco] Termination Id = *
> Date: Tue, 13 Jan 2004 15:04:14 -0500
>
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
>
> ------_=_NextPart_001_01C3DA10.6AB1E562
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> The message as constructed below would apply the given Events =
> descriptor to
> all terminations in the NULL context.
> =20
> Kevin
>
>
> _____ =20
>
> From: Carlos Rodr=EDguez Alcal=E1 Villagra =
> [mailto:crav@conexion.com.py]=20
> Sent: Tuesday, January 13, 2004 10:51 AM
> To: megaco@ietf.org
> Subject: [Megaco] Termination Id =3D *
>
>
> =20
> Can I create this packet??
> =20
> Mgc to mg1:
> MEGACO/1 [123.123.123.4]:55555
> Transaction=3D10001{
> Context =3D - {
> Modify =3D * { ;with this parameter as * ????
> Events =3D 1111{ al /of}
> }
> }
> }
> =20
> =20
> ***************
> It's posible to put in Context * or it must be a Real Termonation Id
> Thanks
> =20
>
>
> ------_=_NextPart_001_01C3DA10.6AB1E562
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
> charset=3Diso-8859-1">
>
>
> <META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=3D#ffffff>
> <DIV dir=3Dltr align=3Dleft><SPAN class=3D973370220-13012004><FONT =
> face=3DArial=20
> size=3D2>The message as constructed below would apply the given Events =
> descriptor=20
> to all terminations in the NULL context.</FONT></SPAN></DIV>
> <DIV dir=3Dltr align=3Dleft><SPAN class=3D973370220-13012004><FONT =
> face=3DArial=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV dir=3Dltr align=3Dleft><SPAN class=3D973370220-13012004><FONT =
> face=3DArial=20
> size=3D2>Kevin</FONT></SPAN></DIV><BR>
> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
> align=3Dleft>
> <HR tabIndex=3D-1>
> <FONT face=3DTahoma size=3D2><B>From:</B> Carlos Rodr=EDguez Alcal=E1 =
> Villagra=20
> [mailto:crav@conexion.com.py] <BR><B>Sent:</B> Tuesday, January 13, =
> 2004 10:51=20
> AM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> [Megaco] =
> Termination Id =3D=20
> *<BR></FONT><BR></DIV>
> <DIV></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Can I create this =
> packet??</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Mgc to mg1:</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>MEGACO/1 =
> [123.123.123.4]:55555</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Transaction=3D10001{</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> Context =3D =
> -</FONT><FONT=20
> face=3DArial size=3D2> {</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> Modify =3D *=20
> { ;with this =
> parameter=20
> as * ????</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> =20
> Events =3D 1111{ al =
> /of}</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> =20
> }</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> =20
> }</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>}</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>***************</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>It's posible to put in Context * or =
> it must be a=20
> Real Termonation Id</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> =20
> =
> =20
> =20
> </FONT></DIV></BLOCKQUOTE></BODY></HTML>
>
> ------_=_NextPart_001_01C3DA10.6AB1E562--
>
>
> --__--__--
>
> Message: 5
> Reply-To: <sampathk@cisco.com>
> From: "Sampath Komanduri" <sampathk@cisco.com>
> To: "'Kevin Boyle'" <kboyle@nortelnetworks.com>,
> "=?iso-8859-1?Q?'Carlos_Rodr=EDguez_Alcal=E1_Villagra'?="
<crav@conexion.com.py>,
> <megaco@ietf.org>
> Subject: RE: [Megaco] Termination Id = *
> Date: Tue, 13 Jan 2004 12:25:09 -0800
> Organization: Cisco Systems
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0033_01C3D9D0.4972EF80
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> Sorry, I didn't notice context "-"
>
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> Kevin Boyle
> Sent: Tuesday, January 13, 2004 12:04 PM
> To: Carlos Rodr=EDguez Alcal=E1 Villagra; megaco@ietf.org
> Subject: RE: [Megaco] Termination Id =3D *
>
>
> The message as constructed below would apply the given Events descriptor
> to all terminations in the NULL context.
> =20
> Kevin
>
>
> _____ =20
>
> From: Carlos Rodr=EDguez Alcal=E1 Villagra [mailto:crav@conexion.com.py] =
>
> Sent: Tuesday, January 13, 2004 10:51 AM
> To: megaco@ietf.org
> Subject: [Megaco] Termination Id =3D *
>
>
> =20
> Can I create this packet??
> =20
> Mgc to mg1:
> MEGACO/1 [123.123.123.4]:55555
> Transaction=3D10001{
> Context =3D - {
> Modify =3D * { ;with this parameter as * ????
> Events =3D 1111{ al /of}
> }
> }
> }
> =20
> =20
> ***************
> It's posible to put in Context * or it must be a Real Termonation Id
> Thanks
> =20
>
>
> ------=_NextPart_000_0033_01C3D9D0.4972EF80
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
> charset=3Diso-8859-1">
> <TITLE>Message</TITLE>
>
> <META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=3D#ffffff>
> <DIV><SPAN class=3D569492420-13012004><FONT face=3DArial color=3D#0000ff =
> size=3D2>Sorry,=20
> I didn't notice context "-"</FONT></SPAN></DIV>
> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
> <DIV></DIV>
> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
> align=3Dleft><FONT=20
> face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
> megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] <B>On Behalf Of =
> </B>Kevin=20
> Boyle<BR><B>Sent:</B> Tuesday, January 13, 2004 12:04 PM<BR><B>To:</B> =
> Carlos=20
> Rodr=EDguez Alcal=E1 Villagra; megaco@ietf.org<BR><B>Subject:</B> RE: =
> [Megaco]=20
> Termination Id =3D *<BR><BR></FONT></DIV>
> <DIV dir=3Dltr align=3Dleft><SPAN class=3D973370220-13012004><FONT =
> face=3DArial=20
> size=3D2>The message as constructed below would apply the given Events =
>
> descriptor to all terminations in the NULL =
> context.</FONT></SPAN></DIV>
> <DIV dir=3Dltr align=3Dleft><SPAN class=3D973370220-13012004><FONT =
> face=3DArial=20
> size=3D2></FONT></SPAN> </DIV>
> <DIV dir=3Dltr align=3Dleft><SPAN class=3D973370220-13012004><FONT =
> face=3DArial=20
> size=3D2>Kevin</FONT></SPAN></DIV><BR>
> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
> align=3Dleft>
> <HR tabIndex=3D-1>
> <FONT face=3DTahoma size=3D2><B>From:</B> Carlos Rodr=EDguez =
> Alcal=E1 Villagra=20
> [mailto:crav@conexion.com.py] <BR><B>Sent:</B> Tuesday, January 13, =
> 2004=20
> 10:51 AM<BR><B>To:</B> megaco@ietf.org<BR><B>Subject:</B> [Megaco]=20
> Termination Id =3D *<BR></FONT><BR></DIV>
> <DIV></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Can I create this =
> packet??</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Mgc to mg1:</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>MEGACO/1 =
> [123.123.123.4]:55555</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Transaction=3D10001{</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> Context =3D =
> -</FONT><FONT=20
> face=3DArial size=3D2> {</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> Modify =3D=20
> * { ;with =
> this=20
> parameter as * ????</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> =20
> Events =3D 1111{ al =
> /of}</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> =20
> }</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> =20
> }</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>}</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>***************</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>It's posible to put in Context * or =
> it must be=20
> a Real Termonation Id</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2> =
> =20
> =
> =20
> =20
> </FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
>
> ------=_NextPart_000_0033_01C3D9D0.4972EF80--
>
>
>
>
> --__--__--
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>
>
> End of Megaco Digest
_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
- [Megaco] Mux Related Detail Document Atul Saini