Message

From: megaco-bounces@ietf.org=20 [mailto:megaco-bounces@ietf.org] On Behalf Of Tamar Nemet
Se= nt:=20 Tuesday, September 02, 2008 10:18 AM
To: megaco@ietf.org
= Cc:=20 Anat Garber
Subject: [Megaco] Megaco message

Hi,

&n= bsp;

As much as I kno= w the=20 following Megaco command is illegal, am I correct ?

&n= bsp;

!/1=20 [10.100.4.28]:2944=20 T=3D9608{C=3D680399{MF=3Deph_2291{M{O{MO=3DSR},L{v=3D0
  &nb= sp; c=3DIN IP4=20 $
    m=3Daudio $ RTP/AVP 8
   =20 a=3Dptime:20
    },R{v=3D0
    o=3D- = 1845908136 0=20 IN IP4 10.20.21.104
    s=3D-
    c=3D= IN IP4=20 10.20.21.104
    t=3D0 0
    m=3Daudi= o 4050=20 RTP/AVP 8
    .
    200 62305=20 OK
    }}}}}

&= nbsp; It=20 looks that in the end of the remote SDP there is reply for MGCP message a= nd as=20 much as I know this is wrong message, is it true ?

&= nbsp; Thanks=20 for your help,

Tamar

=20

IMPORTANT: The contents of this email and any attachments are confidentia= l. They are intended for the=20 named recipient(s) only.
If you have received this email in error, please notify the system manage= r or the sender immediately and do=20 not disclose the contents to anyone or make copies thereof.
*** eSafe scanned this email for viruses, vandals, and malicious c= ontent. ***

------_=_NextPart_001_01C90CCD.7152DA13-- --===============0845791358== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============0845791358==-- From megaco-bounces@ietf.org Tue Sep 2 00:28:11 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 469BB28C0EC; Tue, 2 Sep 2008 00:28:11 -0700 (PDT) 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 5CF4A28C0E2 for ; Tue, 2 Sep 2008 00:28:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.506 X-Spam-Level: * X-Spam-Status: No, score=1.506 tagged_above=-999 required=5 tests=[AWL=-1.454, BAYES_20=-0.74, FRT_SOMA2=2.199, HTML_MESSAGE=0.001, MIME_ASCII0=1.5] 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 oi2F3cZACZuu for ; Tue, 2 Sep 2008 00:28:09 -0700 (PDT) Received: from tparelay1.telrad.com (tparelay1.telrad.com [62.90.58.240]) by core3.amsl.com (Postfix) with ESMTP id 8FB5828C0F2 for ; Tue, 2 Sep 2008 00:28:06 -0700 (PDT) Received: from tparelay1.telrad.com (localhost.localdomain [127.0.0.1]) by tparelay1.telrad.com (8.12.11.20060308/8.12.11) with ESMTP id m827Nf6P000661 for ; Tue, 2 Sep 2008 10:23:41 +0300 Received: from TLRD-MAIL1.Telrad.co.il ([141.226.76.177]) by tparelay1.telrad.com (8.12.11.20060308/8.12.11) with SMTP id m827NfHt000658 for ; Tue, 2 Sep 2008 10:23:41 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 2 Sep 2008 10:29:01 +0300 Message-ID: <6FC94336B3E3F6468408F294C14A9ECB02121BD5@TLRD-MAIL1.Telrad.co.il> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Observed events question Thread-Index: AckMzXWUEir47LcRS7ShVs0tfrNokw== From: "Tamar Nemet" To: Cc: Michael Putter Subject: [Megaco] Observed events question X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1569780812==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org This is a multi-part message in MIME format. --===============1569780812== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C90CCD.92073C38" This is a multi-part message in MIME format. ------_=_NextPart_001_01C90CCD.92073C38 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 Please look at the following megaco messages: =20 =20 MGC -> MG: T=3D22127{C=3D3983{S=3De1/05/5{AT{}}},C=3D-{MF=3De1/05/5{E=3D8591{bcas/sz= ,bcas/casf, icas/casf},SG{icas/rlg},M{O{MO=3DIN}}}}} =20 MG -> MGC: = T=3D22129{C=3D*{S=3De1/05/5{AT{}}},C=3D-{MF=3De1/05/5{SG,M{O{MO=3DIN}}}}}= =20 MG -> MGC: = T=3D233{C=3D-{N=3DE1/05/5{OE=3D8591{20080811T00550054:BCAS/SZ}}}} MGC reply to MG: P=3D233{C=3D-{N=3De1/05/5{ER=3D410{"Unknown Request = ID"}}}}=20 =20 In the second message there is Subtract command that delete all the signals (SG) but there is nothing regarding requested events, so the MG still wait for the requested events from the first message. =20 When the MG send Notify with the observed event (in the third message) , the MGC answer with Unknown Request ID.=20 =20 We don't understand why this is an Unknown Request ID, this is the last one that the MGC asked and nothing canceled this request ID. =20 Can you explain please ? =20 Thanks, Tamar ------_=_NextPart_001_01C90CCD.92073C38 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

Hi,

Please = look at the=20 following megaco messages:

MGC -> MG:=20 T=3D22127{C=3D3983{S=3De1/05/5{AT{}}},C=3D-{MF=3De1/05/5{E=3D8591{bcas/sz= ,bcas/casf,icas/casf},SG{icas/rlg},M{O{MO=3DIN}}}}}

MG -> MGC:=20 T=3D22129{C=3D*{S=3De1/05/5{AT{}}},C=3D-{MF=3De1/05/5{SG,M{O{MO=3DIN}}}}}=

MG -> MGC:=20 T=3D233{C=3D-{N=3DE1/05/5{OE=3D8591{20080811T00550054:BCAS/SZ}}}}
MGC = reply to MG:=20 P=3D233{C=3D-{N=3De1/05/5{ER=3D410{"Unknown Request ID"}}}} =

In the = second=20 message there is Subtract command that delete all the signals (SG) but = there is=20 nothing regarding requested events, so the MG still wait for the = requested=20 events from the first message.

When = the MG send=20 Notify with the observed event (in the third message) , the MGC answer = with=20 Unknown Request ID.

We = don't understand=20 why this is an Unknown Request ID, this is the last one that the MGC = asked and=20 nothing canceled this request ID.

Can = you explain=20 please ?

Thanks,

Tamar

=00 ------_=_NextPart_001_01C90CCD.92073C38-- --===============1569780812== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============1569780812==-- From megaco-bounces@ietf.org Tue Sep 2 17:28:45 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4ADA3A684A; Tue, 2 Sep 2008 17:28:45 -0700 (PDT) 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 E46FD3A684A for ; Tue, 2 Sep 2008 17:28:43 -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 JyAFhlBZSbTH for ; Tue, 2 Sep 2008 17:28:43 -0700 (PDT) Received: from smtp128.rog.mail.re2.yahoo.com (smtp128.rog.mail.re2.yahoo.com [206.190.53.33]) by core3.amsl.com (Postfix) with SMTP id D6DFE3A6832 for ; Tue, 2 Sep 2008 17:28:42 -0700 (PDT) Received: (qmail 98539 invoked from network); 3 Sep 2008 00:28:48 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:Content-Type; b=PjDvIRpmCTeCaASV2bo3nPAw1PimTohjsMLfxCmg8x7A1faKU3qKX96J3MJN2iyFhX5F5Yc3LDr7jF211mgrTIaOMDFmX4604qit8zHRDzcQc02hpxkr2UAQ7G7s8lFnKSwqwC0mLlfl+vEZe1AVwvqXy12VJwiAtK7z+JmPW9o= ; Received: from unknown (HELO ?192.168.1.103?) (tom.taylor@rogers.com@62.167.71.113 with plain) by smtp128.rog.mail.re2.yahoo.com with SMTP; 3 Sep 2008 00:28:48 -0000 X-YMail-OSG: 1Cr_eN8VM1kyyzfkH0pNuwd6_2_IDJfn_bfN_soRvLi_l.VcA7CH7Fkxw6klQOgTeg-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <48BDDA41.5090007@rogers.com> Date: Wed, 03 Sep 2008 02:28:49 +0200 From: Tom Taylor User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: megaco ietf Content-Type: multipart/mixed; boundary="------------000208060103070109090306" Cc: BEHAR ALDANA RONALD Subject: [Megaco] IP 0.0.0.0 In remote descriptor X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org This is a multi-part message in MIME format. --------------000208060103070109090306 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit For some reason the following message was bounced from the list. I am forwarding it on, copy the originator. Tom Taylor > ------------------------------------------------------------------------ > > Subject: > IP 0.0.0.0 In remote descriptor > From: > "BEHAR ALDANA RONALD" > Date: > Tue, 2 Sep 2008 11:56:22 +0200 > To: > > > To: > > > > Hi to all > > Is IP 0.0.0.0 valid as a connection information in a remote descriptor. > > c= IN IP4 0.0.0.0 > > regards > > CTAC Engineer > Madrid/Spain > > -------- Original Message -------- Subject: Uncaught bounce notification Date: Tue, 02 Sep 2008 02:56:24 -0700 From: mailman-bounces@ietf.org To: megaco-owner@ietf.org The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s). For more information see: https://www.ietf.org/mailman/admin/megaco/bounce --------------000208060103070109090306 Content-Type: message/rfc822; name="ForwardedMessage.eml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ForwardedMessage.eml" Return-Path: X-Original-To: megaco-bounces@core3.amsl.com Delivered-To: megaco-bounces@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E09E63A67C0 for ; Tue, 2 Sep 2008 02:56:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.352 X-Spam-Level: X-Spam-Status: No, score=0.352 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_FR=0.35, 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 TztLRfxXbceZ for ; Tue, 2 Sep 2008 02:56:20 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id F3E003A6945 for ; Tue, 2 Sep 2008 02:56:19 -0700 (PDT) Received: from FRVELSBHS07.ad2.ad.alcatel.com (frvelsbhs07.ad2.ad.alcatel.com [155.132.6.79]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m829uNQM008529 for ; Tue, 2 Sep 2008 11:56:23 +0200 Received: from FRMRSSMBS33.ad2.ad.alcatel.com ([155.132.6.16]) by FRVELSBHS07.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 2 Sep 2008 11:56:23 +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_01C90CE2.27DBC52D" Subject: IP 0.0.0.0 In remote descriptor Date: Tue, 2 Sep 2008 11:56:22 +0200 Message-ID: <87F6BC6EF55C1942BABCB8E1AA931FB501286E30@FRMRSSMBS33.ad2.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IP 0.0.0.0 In remote descriptor Thread-Index: AckM4ieZCQG434UKRemG9YJrGvB7nA== From: "BEHAR ALDANA RONALD" To: X-OriginalArrivalTime: 02 Sep 2008 09:56:23.0316 (UTC) FILETIME=[28303540:01C90CE2] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 This is a multi-part message in MIME format. ------_=_NextPart_001_01C90CE2.27DBC52D Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi to all Is IP 0.0.0.0 valid as a connection information in a remote descriptor. c=3D IN IP4 0.0.0.0 regards CTAC Engineer Madrid/Spain ------_=_NextPart_001_01C90CE2.27DBC52D Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable IP 0.0.0.0 In remote descriptor

Hi to all

Is IP 0.0.0.0 valid as a connection = information in a remote descriptor.

c=3D IN IP4 0.0.0.0

regards

CTAC Engineer
Madrid/Spain

------_=_NextPart_001_01C90CE2.27DBC52D-- --------------000208060103070109090306 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --------------000208060103070109090306-- From megaco-bounces@ietf.org Tue Sep 2 22:08:54 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6A533A6BE9; Tue, 2 Sep 2008 22:08:54 -0700 (PDT) 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 1108E3A6BE9 for ; Tue, 2 Sep 2008 22:08:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.201 X-Spam-Level: X-Spam-Status: No, score=0.201 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_SOMA2=2.199, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6] 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 Eck7P4kIlPRR for ; Tue, 2 Sep 2008 22:08:48 -0700 (PDT) Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by core3.amsl.com (Postfix) with ESMTP id 259903A6BD8 for ; Tue, 2 Sep 2008 22:08:46 -0700 (PDT) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by jaguar.aricent.com (8.13.8/8.13.8) with ESMTP id m8355sjv000504 for ; Wed, 3 Sep 2008 10:35:54 +0530 Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (8.13.8/8.13.8) with ESMTP id m8355qSC000466 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Wed, 3 Sep 2008 10:35:52 +0530 Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.130]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Wed, 3 Sep 2008 10:38:43 +0530 From: Deepak Bissa To: Tamar Nemet , "megaco@ietf.org" Date: Wed, 3 Sep 2008 10:38:42 +0530 Thread-Topic: Observed events question Thread-Index: AckMzXWUEir47LcRS7ShVs0tfrNokwAtCpuQ Message-ID: <31F873353B13F2419C80FD0833E1189513148EA218@GUREXMB01.ASIAN.AD.ARICENT.COM> References: <6FC94336B3E3F6468408F294C14A9ECB02121BD5@TLRD-MAIL1.Telrad.co.il> In-Reply-To: <6FC94336B3E3F6468408F294C14A9ECB02121BD5@TLRD-MAIL1.Telrad.co.il> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Michael Putter Subject: Re: [Megaco] Observed events question X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2007145415==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org --===============2007145415== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_31F873353B13F2419C80FD0833E1189513148EA218GUREXMB01ASIA_" --_000_31F873353B13F2419C80FD0833E1189513148EA218GUREXMB01ASIA_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, There is minor correction in messages shown in red below. I would like to know that what is MG's reply to the first two messages. Ideally, MG shall reply back successfully to first message and for the seco= nd message it should send an error reply. The reason being that termination has been already moved to NULL context by= the effect of subtract command in first message. Thus, for second message, MG will not be able to find the termination in an= y Non-Null context and should send error as 435, "Termination ID is not in = specified Context". But if MG replied successfully to subtract command in second message then M= GC shall assume that all descriptors for the termination have been reset to= default values (Refer H.248.1 (V3) section 7.2.3). MGC will not be able to match the request ID as reported by MG in such a co= ndition. With regards, Deepak Bissa ________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= Tamar Nemet Sent: Tuesday, September 02, 2008 12:59 PM To: megaco@ietf.org Cc: Michael Putter Subject: [Megaco] Observed events question Hi, Please look at the following megaco messages: MGC -> MG: T=3D22127{C=3D3983{S=3De1/05/5{AT{}}},C=3D-{MF=3De1/05/5{E=3D859= 1{bcas/sz,bcas/casf,icas/casf},SG{icas/rlg},M{O{MO=3DIN}}}}} MGC -> MG: T=3D22129{C=3D*{S=3De1/05/5{AT{}}},C=3D-{MF=3De1/05/5{SG,M{O{MO= =3DIN}}}}} MG -> MGC: T=3D233{C=3D-{N=3DE1/05/5{OE=3D8591{20080811T00550054:BCAS/SZ}}}= } MGC reply to MG: P=3D233{C=3D-{N=3De1/05/5{ER=3D410{"Unknown Request ID"}}}= } In the second message there is Subtract command that delete all the signals= (SG) but there is nothing regarding requested events, so the MG still wait= for the requested events from the first message. When the MG send Notify with the observed event (in the third message) , th= e MGC answer with Unknown Request ID. We don't understand why this is an Unknown Request ID, this is the last one= that the MGC asked and nothing canceled this request ID. Can you explain please ? Thanks, Tamar ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely = for the use of the individual to whom it is addressed. It may contain privi= leged or confidential information and should not be circulated or used for = any purpose other than for what it is intended. If you have received this m= essage in error,please notify the originator immediately. If you are not th= e intended recipient, you are notified that you are strictly prohibited fro= m using, copying, altering, or disclosing the contents of this message. Ari= cent accepts no responsibility forloss or damage arising from the use of th= e information transmitted by this email including damage from virus." --_000_31F873353B13F2419C80FD0833E1189513148EA218GUREXMB01ASIA_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

Hello,

There is minor correction in messages = shown in red below.

I would like to know that what is MG&#= 8217;s reply to the first two messages.

Ideally, MG shall reply back successfu= lly to first message and for the second message it should send an error rep= ly.

The reason being that termination has = been already moved to NULL context by the effect of subtract command in fir= st message.

Thus, for second message, MG will not = be able to find the termination in any Non-Null context and should send err= or as 435, “Termination ID is not in specified Context”.

But if MG replied successfully to subt= ract command in second message then MGC shall assume that all descriptors f= or the termination have been reset to default values (Refer H.248.1 (V3) section 7.2.3).

MGC will not be able to match the requ= est ID as reported by MG in such a condition.

With regards,

Deepak Bissa

From: mega= co-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Tamar Nemet
Sent: Tuesday, September 02,= 2008 12:59 PM
To: megaco@ietf.org
Cc: Michael Putter
Subject: [Megaco] Observed e= vents question

Hi,

Please look at the following megaco messages:

MGC -> MG: T=3D22127{C=3D3983{S=3De1/05/5{AT{}}},C=3D= -{MF=3De1/05/5{E=3D8591{bcas/sz,bcas/casf,icas/casf},SG{icas/rlg},M{O{MO=3D= IN}}}}}

MGC -> MG: T=3D22129{C=3D*{S=3De1/05/5{AT{}}},C=3D-{M= F=3De1/05/5{SG,M{O{MO=3DIN}}}}}

MG -> MGC: T=3D233{C=3D-{N=3DE1/05/5{OE=3D8591{200808= 11T00550054:BCAS/SZ}}}}
MGC reply to MG: P=3D233{C=3D-{N=3De1/05/5{ER=3D410{"Unknown Request I= D"}}}}

In the second message there is Subtract command that del= ete all the signals (SG) but there is nothing regarding requested events, s= o the MG still wait for the requested events from the first message.

When the MG send Notify with the observed event (in the = third message) , the MGC answer with Unknown Request ID.

We don't understand why this is an Unknown Request ID, t= his is the last one that the MGC asked and nothing canceled this request ID= .

Can you explain please ?

Thanks,

Tamar

"DISCLAIMER: This messa= ge is proprietary to Aricent and is intended solely for the use of the indi= vidual to whom it is addressed. It may contain privileged or confidential i= nformation and should not be circulated or used for any purpose other than for what it is intended. If you have recei= ved this message in error,please notify the originator immediately. If you = are not the intended recipient, you are notified that you are strictly proh= ibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibil= ity forloss or damage arising from the use of the information transmitted b= y this email including damage from virus."
--_000_31F873353B13F2419C80FD0833E1189513148EA218GUREXMB01ASIA_-- --===============2007145415== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============2007145415==-- From megaco-bounces@ietf.org Wed Sep 3 05:43:09 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0CC93A6A58; Wed, 3 Sep 2008 05:43:09 -0700 (PDT) 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 038AF3A6A3D for ; Wed, 3 Sep 2008 05:43:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.399 X-Spam-Level: X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_56=0.6] 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 Uz1SVcwjSqet for ; Wed, 3 Sep 2008 05:43:08 -0700 (PDT) Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by core3.amsl.com (Postfix) with ESMTP id B0EB63A67D6 for ; Wed, 3 Sep 2008 05:43:07 -0700 (PDT) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by jaguar.aricent.com (8.13.8/8.13.8) with ESMTP id m83CT2IM014621 for ; Wed, 3 Sep 2008 17:59:03 +0530 Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (8.13.8/8.13.8) with ESMTP id m83CT2pK014593 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Wed, 3 Sep 2008 17:59:02 +0530 Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.130]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Wed, 3 Sep 2008 18:01:55 +0530 From: Divij Agarwal To: Tom Taylor , megaco ietf Date: Wed, 3 Sep 2008 18:01:52 +0530 Thread-Topic: [Megaco] IP 0.0.0.0 In remote descriptor Thread-Index: AckNvAd8nFDxVwwWQ9mCM9aDsqdQmgABHL4w Message-ID: <31F873353B13F2419C80FD0833E1189513148EA880@GUREXMB01.ASIAN.AD.ARICENT.COM> References: <48BDDA41.5090007@rogers.com> In-Reply-To: <48BDDA41.5090007@rogers.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: BEHAR ALDANA RONALD Subject: Re: [Megaco] IP 0.0.0.0 In remote descriptor X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org Setting IP in c line to 0.0.0.0 is one of the ways of putting call on Hold. Receiving c=IN IP4 0.0.0.0 in remote descriptor can inform the receiving party that the call has been put on hold by the remote party. With Regards, Divij Agarwal Senior Software Engineer A R I C E N T -----Original Message----- From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Tom Taylor Sent: Wednesday, September 03, 2008 5:59 AM To: megaco ietf Cc: BEHAR ALDANA RONALD Subject: [Megaco] IP 0.0.0.0 In remote descriptor For some reason the following message was bounced from the list. I am forwarding it on, copy the originator. Tom Taylor > ------------------------------------------------------------------------ > > Subject: > IP 0.0.0.0 In remote descriptor > From: > "BEHAR ALDANA RONALD" > Date: > Tue, 2 Sep 2008 11:56:22 +0200 > To: > > > To: > > > > Hi to all > > Is IP 0.0.0.0 valid as a connection information in a remote descriptor. > > c= IN IP4 0.0.0.0 > > regards > > CTAC Engineer > Madrid/Spain > > -------- Original Message -------- Subject: Uncaught bounce notification Date: Tue, 02 Sep 2008 02:56:24 -0700 From: mailman-bounces@ietf.org To: megaco-owner@ietf.org The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s). For more information see: https://www.ietf.org/mailman/admin/megaco/bounce "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility forloss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco From megaco-bounces@ietf.org Wed Sep 3 07:07:11 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B9E53A6BD9; Wed, 3 Sep 2008 07:07:11 -0700 (PDT) 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 2BCE63A6BD9 for ; Wed, 3 Sep 2008 07:07:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.349 X-Spam-Level: X-Spam-Status: No, score=-0.349 tagged_above=-999 required=5 tests=[AWL=0.700, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_12=0.6, J_CHICKENPOX_56=0.6] 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 6ZF5CHcQVNSz for ; Wed, 3 Sep 2008 07:07:09 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id EB3123A6BB4 for ; Wed, 3 Sep 2008 07:07:08 -0700 (PDT) Received: from FRVELSBHS07.ad2.ad.alcatel.com (frvelsbhs07.ad2.ad.alcatel.com [155.132.6.79]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m83E7A2a010368; Wed, 3 Sep 2008 16:07:10 +0200 Received: from FRMRSSMBS33.ad2.ad.alcatel.com ([155.132.6.16]) by FRVELSBHS07.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Wed, 3 Sep 2008 16:07:10 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 3 Sep 2008 16:06:56 +0200 Message-ID: <87F6BC6EF55C1942BABCB8E1AA931FB50128747D@FRMRSSMBS33.ad2.ad.alcatel.com> In-Reply-To: <31F873353B13F2419C80FD0833E1189513148EA880@GUREXMB01.ASIAN.AD.ARICENT.COM> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Megaco] IP 0.0.0.0 In remote descriptor Thread-Index: AckNvAd8nFDxVwwWQ9mCM9aDsqdQmgABHL4wAANVTJA= References: <48BDDA41.5090007@rogers.com> <31F873353B13F2419C80FD0833E1189513148EA880@GUREXMB01.ASIAN.AD.ARICENT.COM> From: "BEHAR ALDANA RONALD" To: "Divij Agarwal" , "Tom Taylor" , "megaco ietf" X-OriginalArrivalTime: 03 Sep 2008 14:07:10.0391 (UTC) FILETIME=[5B5B6470:01C90DCE] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Subject: Re: [Megaco] IP 0.0.0.0 In remote descriptor X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org Thanks for the comment This type of action was established by SIP in RFC 2543 and continues to be = used to provide compatibility with this RFC, but Megaco has other descripto= rs to handle RTP flows. Is this connection information valid in Megaco, my = question is because it's not a host address. regards = -----Mensaje original----- De: Divij Agarwal [mailto:Divij.Agarwal@aricent.com] = Enviado el: mi=E9rcoles, 03 de septiembre de 2008 14:32 Para: Tom Taylor; megaco ietf CC: BEHAR ALDANA RONALD Asunto: RE: [Megaco] IP 0.0.0.0 In remote descriptor Setting IP in c line to 0.0.0.0 is one of the ways of putting call on Hold. Receiving c=3DIN IP4 0.0.0.0 in remote descriptor can inform the receiving = party that the call has been put on hold by the remote party. With Regards, Divij Agarwal Senior Software Engineer A R I C E N T -----Original Message----- From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= Tom Taylor Sent: Wednesday, September 03, 2008 5:59 AM To: megaco ietf Cc: BEHAR ALDANA RONALD Subject: [Megaco] IP 0.0.0.0 In remote descriptor For some reason the following message was bounced from the list. I am forwa= rding it on, copy the originator. Tom Taylor > ---------------------------------------------------------------------- > -- > > Subject: > IP 0.0.0.0 In remote descriptor > From: > "BEHAR ALDANA RONALD" > Date: > Tue, 2 Sep 2008 11:56:22 +0200 > To: > > > To: > > > > Hi to all > > Is IP 0.0.0.0 valid as a connection information in a remote descriptor. > > c=3D IN IP4 0.0.0.0 > > regards > > CTAC Engineer > Madrid/Spain > > -------- Original Message -------- Subject: Uncaught bounce notification Date: Tue, 02 Sep 2008 02:56:24 -0700 From: mailman-bounces@ietf.org To: megaco-owner@ietf.org The attached message was received as a bounce, but either the bounce format= was not recognized, or no member addresses could be extracted from it. Th= is mailing list has been configured to send all unrecognized bounce message= s to the list administrator(s). For more information see: https://www.ietf.org/mailman/admin/megaco/bounce "DISCLAIMER: This message is proprietary to Aricent and is intended solely = for the use of the individual to whom it is addressed. It may contain privi= leged or confidential information and should not be circulated or used for = any purpose other than for what it is intended. If you have received this m= essage in error,please notify the originator immediately. If you are not th= e intended recipient, you are notified that you are strictly prohibited fro= m using, copying, altering, or disclosing the contents of this message. Ari= cent accepts no responsibility forloss or damage arising from the use of th= e information transmitted by this email including damage from virus." _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco From megaco-bounces@ietf.org Wed Sep 3 16:57:49 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F36DD3A6C41; Wed, 3 Sep 2008 16:57:48 -0700 (PDT) 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 753DF3A6C41 for ; Wed, 3 Sep 2008 16:57:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.405 X-Spam-Level: X-Spam-Status: No, score=-1.405 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_56=0.6, 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 9e2LUZldjIHg for ; Wed, 3 Sep 2008 16:57:46 -0700 (PDT) Received: from ipmail01.adl6.internode.on.net (ipmail01.adl6.internode.on.net [203.16.214.146]) by core3.amsl.com (Postfix) with ESMTP id 26FDF3A6AB6 for ; Wed, 3 Sep 2008 16:57:45 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4AAFy+vkg7p1bo/2dsb2JhbAAIt2qBZw X-IronPort-AV: E=Sophos;i="4.32,320,1217773800"; d="scan'208";a="186333041" Received: from ppp59-167-86-232.lns2.mel6.internode.on.net (HELO [192.168.0.4]) ([59.167.86.232]) by ipmail01.adl6.internode.on.net with ESMTP; 04 Sep 2008 09:27:45 +0930 Message-ID: <48BF2478.1050705@nteczone.com> Date: Thu, 04 Sep 2008 09:57:44 +1000 From: Christian Groves User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: BEHAR ALDANA RONALD References: <48BDDA41.5090007@rogers.com> <31F873353B13F2419C80FD0833E1189513148EA880@GUREXMB01.ASIAN.AD.ARICENT.COM> <87F6BC6EF55C1942BABCB8E1AA931FB50128747D@FRMRSSMBS33.ad2.ad.alcatel.com> In-Reply-To: <87F6BC6EF55C1942BABCB8E1AA931FB50128747D@FRMRSSMBS33.ad2.ad.alcatel.com> Cc: Divij Agarwal , megaco ietf Subject: Re: [Megaco] IP 0.0.0.0 In remote descriptor X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org Hello, H.248/Megaco makes no assumption about the validity of setting the IP in = the c line to 0.0.0.0. If used by SIP/SDP to perform a particular = function then one should look at how that function is performed in = H.248. For hold moving the termination to a separate context or setting = the stream mode may be a more precise way of implementing hold rather = than relying of the MG to correctly interpret what 0.0.0.0 means. A MG = doesn't implement SIP thus its not compliant to the procedures RFC2543. Regards, Christian BEHAR ALDANA RONALD wrote: > Thanks for the comment > > This type of action was established by SIP in RFC 2543 and continues to b= e used to provide compatibility with this RFC, but Megaco has other descrip= tors to handle RTP flows. Is this connection information valid in Megaco, m= y question is because it's not a host address. > > regards = > > -----Mensaje original----- > De: Divij Agarwal [mailto:Divij.Agarwal@aricent.com] = > Enviado el: mi=E9rcoles, 03 de septiembre de 2008 14:32 > Para: Tom Taylor; megaco ietf > CC: BEHAR ALDANA RONALD > Asunto: RE: [Megaco] IP 0.0.0.0 In remote descriptor > > > Setting IP in c line to 0.0.0.0 is one of the ways of putting call on Hol= d. > > Receiving c=3DIN IP4 0.0.0.0 in remote descriptor can inform the receivin= g party that the call has been put on hold by the remote party. > > > With Regards, > > Divij Agarwal > Senior Software Engineer > A R I C E N T > > > -----Original Message----- > From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf = Of Tom Taylor > Sent: Wednesday, September 03, 2008 5:59 AM > To: megaco ietf > Cc: BEHAR ALDANA RONALD > Subject: [Megaco] IP 0.0.0.0 In remote descriptor > > For some reason the following message was bounced from the list. I am for= warding it on, copy the originator. > > Tom Taylor > > = >> ---------------------------------------------------------------------- >> -- >> >> Subject: >> IP 0.0.0.0 In remote descriptor >> From: >> "BEHAR ALDANA RONALD" >> Date: >> Tue, 2 Sep 2008 11:56:22 +0200 >> To: >> >> >> To: >> >> >> >> Hi to all >> >> Is IP 0.0.0.0 valid as a connection information in a remote descriptor. >> >> c=3D IN IP4 0.0.0.0 >> >> regards >> >> CTAC Engineer >> Madrid/Spain >> >> >> = > > > > -------- Original Message -------- > Subject: Uncaught bounce notification > Date: Tue, 02 Sep 2008 02:56:24 -0700 > From: mailman-bounces@ietf.org > To: megaco-owner@ietf.org > > The attached message was received as a bounce, but either the bounce form= at was not recognized, or no member addresses could be extracted from it. = This mailing list has been configured to send all unrecognized bounce messa= ges to the list administrator(s). > > For more information see: > https://www.ietf.org/mailman/admin/megaco/bounce > > > > "DISCLAIMER: This message is proprietary to Aricent and is intended solel= y for the use of the individual to whom it is addressed. It may contain pri= vileged or confidential information and should not be circulated or used fo= r any purpose other than for what it is intended. If you have received this= message in error,please notify the originator immediately. If you are not = the intended recipient, you are notified that you are strictly prohibited f= rom using, copying, altering, or disclosing the contents of this message. A= ricent accepts no responsibility forloss or damage arising from the use of = the information transmitted by this email including damage from virus." > _______________________________________________ > Megaco mailing list > Megaco@ietf.org > https://www.ietf.org/mailman/listinfo/megaco > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > = _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco From megaco-bounces@ietf.org Wed Sep 3 17:00:36 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 496EC3A6C85; Wed, 3 Sep 2008 17:00:36 -0700 (PDT) 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 0EE533A6C85 for ; Wed, 3 Sep 2008 17:00:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.705 X-Spam-Level: X-Spam-Status: No, score=-0.705 tagged_above=-999 required=5 tests=[AWL=-0.700, 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 HTXBS08LNcj2 for ; Wed, 3 Sep 2008 17:00:34 -0700 (PDT) Received: from ipmail01.adl6.internode.on.net (ipmail01.adl6.internode.on.net [203.16.214.146]) by core3.amsl.com (Postfix) with ESMTP id D14C63A6C41 for ; Wed, 3 Sep 2008 17:00:33 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4AAN/Bvkg7p1bo/2dsb2JhbAAIt12BZw X-IronPort-AV: E=Sophos;i="4.32,320,1217773800"; d="scan'208";a="186334571" Received: from ppp59-167-86-232.lns2.mel6.internode.on.net (HELO [192.168.0.4]) ([59.167.86.232]) by ipmail01.adl6.internode.on.net with ESMTP; 04 Sep 2008 09:30:11 +0930 Message-ID: <48BF2506.2010703@nteczone.com> Date: Thu, 04 Sep 2008 10:00:06 +1000 From: Christian Groves User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: megaco ietf Subject: [Megaco] Results of Q.3/16 Media Control Protocols Meeting X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org Hello all, Q.3/16 has recently concluded its meeting on H.248/Megaco related issues. The documents for this meeting can be found at: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0808_Gen/ The meeting report can be found at: http://ftp3.itu.int/av-arch/avc-site/2005-2008/0808_Gen/TD-15a.zip Regards, Christian _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco From megaco-bounces@ietf.org Thu Sep 4 00:48:42 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2433F3A6D4F; Thu, 4 Sep 2008 00:48:42 -0700 (PDT) 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 D76503A6D06 for ; Thu, 4 Sep 2008 00:48:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.699 X-Spam-Level: X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_12=0.6, J_CHICKENPOX_56=0.6] 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 qxGj54RfTH2T for ; Thu, 4 Sep 2008 00:48:40 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id A4F6B3A6B7D for ; Thu, 4 Sep 2008 00:48:39 -0700 (PDT) Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.ad2.ad.alcatel.com [155.132.6.77]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m847mPHT004914; Thu, 4 Sep 2008 09:48:35 +0200 Received: from FRMRSSMBS33.ad2.ad.alcatel.com ([155.132.6.16]) by FRVELSBHS05.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Thu, 4 Sep 2008 09:48:35 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 4 Sep 2008 09:48:33 +0200 Message-ID: <87F6BC6EF55C1942BABCB8E1AA931FB50128769C@FRMRSSMBS33.ad2.ad.alcatel.com> In-Reply-To: <48BF2478.1050705@nteczone.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Megaco] IP 0.0.0.0 In remote descriptor Thread-Index: AckOIOUkHMgDm4J/TC6ag4Cmtq9+wgAQZikg References: <48BDDA41.5090007@rogers.com> <31F873353B13F2419C80FD0833E1189513148EA880@GUREXMB01.ASIAN.AD.ARICENT.COM> <87F6BC6EF55C1942BABCB8E1AA931FB50128747D@FRMRSSMBS33.ad2.ad.alcatel.com> <48BF2478.1050705@nteczone.com> From: "BEHAR ALDANA RONALD" To: "Christian Groves" X-OriginalArrivalTime: 04 Sep 2008 07:48:35.0346 (UTC) FILETIME=[A28C5720:01C90E62] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Cc: Divij Agarwal , megaco ietf Subject: Re: [Megaco] IP 0.0.0.0 In remote descriptor X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org Thank you for the comments. = -----Mensaje original----- De: Christian Groves [mailto:Christian.Groves@nteczone.com] = Enviado el: jueves, 04 de septiembre de 2008 1:58 Para: BEHAR ALDANA RONALD CC: Divij Agarwal; Tom Taylor; megaco ietf Asunto: Re: [Megaco] IP 0.0.0.0 In remote descriptor Hello, H.248/Megaco makes no assumption about the validity of setting the IP in th= e c line to 0.0.0.0. If used by SIP/SDP to perform a particular function th= en one should look at how that function is performed in H.248. For hold mov= ing the termination to a separate context or setting the stream mode may be= a more precise way of implementing hold rather than relying of the MG to c= orrectly interpret what 0.0.0.0 means. A MG doesn't implement SIP thus its = not compliant to the procedures RFC2543. Regards, Christian BEHAR ALDANA RONALD wrote: > Thanks for the comment > > This type of action was established by SIP in RFC 2543 and continues to b= e used to provide compatibility with this RFC, but Megaco has other descrip= tors to handle RTP flows. Is this connection information valid in Megaco, m= y question is because it's not a host address. > > regards > > -----Mensaje original----- > De: Divij Agarwal [mailto:Divij.Agarwal@aricent.com] > Enviado el: mi=E9rcoles, 03 de septiembre de 2008 14:32 > Para: Tom Taylor; megaco ietf > CC: BEHAR ALDANA RONALD > Asunto: RE: [Megaco] IP 0.0.0.0 In remote descriptor > > > Setting IP in c line to 0.0.0.0 is one of the ways of putting call on Hol= d. > > Receiving c=3DIN IP4 0.0.0.0 in remote descriptor can inform the receivin= g party that the call has been put on hold by the remote party. > > > With Regards, > > Divij Agarwal > Senior Software Engineer > A R I C E N T > > > -----Original Message----- > From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On = > Behalf Of Tom Taylor > Sent: Wednesday, September 03, 2008 5:59 AM > To: megaco ietf > Cc: BEHAR ALDANA RONALD > Subject: [Megaco] IP 0.0.0.0 In remote descriptor > > For some reason the following message was bounced from the list. I am for= warding it on, copy the originator. > > Tom Taylor > > = >> --------------------------------------------------------------------- >> - >> -- >> >> Subject: >> IP 0.0.0.0 In remote descriptor >> From: >> "BEHAR ALDANA RONALD" >> Date: >> Tue, 2 Sep 2008 11:56:22 +0200 >> To: >> >> >> To: >> >> >> >> Hi to all >> >> Is IP 0.0.0.0 valid as a connection information in a remote descriptor. >> >> c=3D IN IP4 0.0.0.0 >> >> regards >> >> CTAC Engineer >> Madrid/Spain >> >> >> = > > > > -------- Original Message -------- > Subject: Uncaught bounce notification > Date: Tue, 02 Sep 2008 02:56:24 -0700 > From: mailman-bounces@ietf.org > To: megaco-owner@ietf.org > > The attached message was received as a bounce, but either the bounce form= at was not recognized, or no member addresses could be extracted from it. = This mailing list has been configured to send all unrecognized bounce messa= ges to the list administrator(s). > > For more information see: > https://www.ietf.org/mailman/admin/megaco/bounce > > > > "DISCLAIMER: This message is proprietary to Aricent and is intended solel= y for the use of the individual to whom it is addressed. It may contain pri= vileged or confidential information and should not be circulated or used fo= r any purpose other than for what it is intended. If you have received this= message in error,please notify the originator immediately. If you are not = the intended recipient, you are notified that you are strictly prohibited f= rom using, copying, altering, or disclosing the contents of this message. A= ricent accepts no responsibility forloss or damage arising from the use of = the information transmitted by this email including damage from virus." > _______________________________________________ > Megaco mailing list > Megaco@ietf.org > https://www.ietf.org/mailman/listinfo/megaco > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > = _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco From kwok69n@icqmail.com Thu Sep 4 21:07:25 2008 Return-Path: X-Original-To: ietfarch-megaco-archive@core3.amsl.com Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DEFF23A69C9 for ; Thu, 4 Sep 2008 21:07:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -40.199 X-Spam-Level: X-Spam-Status: No, score=-40.199 tagged_above=-999 required=5 tests=[BAYES_95=3, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.097, IP_NOT_FRIENDLY=0.334, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, SARE_FROM_DRUGS=1.666, SUBJ_ALL_CAPS=2.077, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] 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 kVXdrBJjWVgf for ; Thu, 4 Sep 2008 21:07:25 -0700 (PDT) Received: from h6.7.96.216.dynamic.ip.windstream.net (h6.7.96.216.dynamic.ip.windstream.net [216.96.7.6]) by core3.amsl.com (Postfix) with SMTP id 6A9073A69A8 for ; Thu, 4 Sep 2008 21:07:25 -0700 (PDT) Message-Id: <20080905050816.3086.qmail@h6.7.96.216.dynamic.ip.windstream.net> To: Subject: RE: SALE 89% OFF From: VIAGRA INC MIME-Version: 1.0 Content-Type: text/html Date: Thu, 4 Sep 2008 21:07:25 -0700 (PDT)

Hi all

Assuming we have two actions in a transaction, the f= irst refers to ALL contexts and the second refers to the NULL context, what= should be the correct treatment if there are no active contexts on the gat= eway? Should the second action be performed?

The standard refers to the case in which a command f= ails, but not to the case in which the action fails.

Thanks,

Nur= it Shenhar

Control an= d management Leader

&n= bsp;

Email: nurits@audiocodes.com

Tel. +972-3-9764155

Fax. +972-3-9764223

www.audiocode= s.com

This email and any files tra= nsmitted with it are confidential material. They are intended solely for th= e use of the designated individual or entity to whom they are addressed. If= the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, d= istribution or copying of this communication is strictly prohibited and may= be unlawful.

If you have received this email in error please immediately notify the send= er and delete or destroy any copy of this message
--_000_01719E4A8816F04686A988909FBFC4A4BE20BB3282aclmailboxcor_-- --_005_01719E4A8816F04686A988909FBFC4A4BE20BB3282aclmailboxcor_ Content-Type: image/gif; name="image003.gif" Content-Description: image003.gif Content-Disposition: inline; filename="image003.gif"; size=2488; creation-date="Tue, 16 Sep 2008 14:11:29 GMT"; modification-date="Tue, 16 Sep 2008 14:11:29 GMT" Content-ID: Content-Transfer-Encoding: base64 R0lGODlhkAAuAHcAMSH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAX AAAAC21zT1BNU09GRklDRTkuMEI8pPUAIf8LTVNPRkZJQ0U5LjAVAAAACXBIWXMAAA7EAAAOxAGV Kw4bACwAAAAAkAAuAIcAAAD////p6emVlZWYlpa6urjv7u7AwL5BPj2vr67r6+r39vZDQUGNjIyD goLMzMrX1tZHRkY1NDRzcXGTkpLV1dWHhoZ2dXXMyspqaWmzsrKLioq9vbtPTU2qqalcWlmnpqbp 5+VTUVChoaF3d3ejoaHS0tL5+fm4uLilo6NtbGyenp36+vpnZ2fe3d2OjY1hX11GRESpp6ZlZGRW VVX8/Pxwbm7Ozs7c29v09PTj4+NoZmVMSUlkYmH29fVUUlFMSEjm5uU1MzJYVlXX19Vsammtqqra 2tiOjYyFg4LEw8Py8vL9/f2koaDt7e1zcW+bmZbU0tI3NTJuaWOVkpFSTk3x8fCal5LJx8ZlY12m pKJvbGjk4+NcWFRWUUr7+/xqZmCEgHjLysd8eXR2dGxzcGq9u7bPzsvt7etpZFqKhnvn5eOEgnzu 7u7W1NJNRzze3ttbU0rw7+5GPi36+fmTkIliX1Xa19TOzMVVSz7j4t94cWSim5Cvq6N+dWjOy8en opjCvbiKhHS4s6mCfXDP0NNdUkPX1NHc2tX09vrl6vLX2+fM0+K4wNewu9Wcq82GmsJ0i7tMX5vv 9Pa6ytvN2OTe5O6dlotzfJFeZHVXa6FCVJQuQn0jOXIbMmcXLmYWLGgVLWsTLG8RLHU1VohRcp4A KlqWrccMNGRDY5MmSnxhgampvdGuutJCS2Byg68ZMHEZL2IWLWQYLmU1SoVkfK2XpsrIz9/4+Pr9 /v7q6eaDnr6OnL1CVYsXLWYqP3S0vdXe4uz5+vx3bF9zkbQZQHCHlrcnOm48TYGTocBkWkkhNGIZ LV8ZLl9rYlIcL1wZLWDV0cvHw7xaaZelr8j08/IbLlxQYZPs7vRygaa2rqL19PKeqsVKWYYdMFwb L1xJWYuCkbG/x9jp6vCyvNBQX42Mmbvs7vUvQW13hqtGVoQZMGAiN2k/UotOYJhLXZZMXpQyRnod MFs7THolOGRQX4ufqcLk5+5tgKg5Sn4hNWljdaOEkrUAAAAAAAAAAAAI/wADCBxIsOBAAQMIFDBw AAGCBAoMSpxIsaLFixgzatx4cQGDBAYaOHgAIYKECRQqcFzJsqXLlxktXMAgIYOGBBs4dNjg4QMI mECDCh1KMIQIDxJGDIRAooQEEydQpCBKtarVigM2MJhQsIKKER0EZlhxtazZoSxaOHVhkMILGAQC KIhh4qzduxxlbJhBQ+ICFRoiRJTRoQbew4glTkD6U+KJADYsCPwwILFlxDdIgJCAo2KFCDkCQJCg 47Lpsw1G7ODxuGIPGQJJ7DhNu6qPHziAwLaI4oPAIEJu1B4eNIEI4MIt1hhCRGAREcSju+wxwsiH IxiRJPktRIn07xqXCP+pcKEBC4wVhjAR6CAC+PcWNXTI0aOJxh51AzgRcgC+f4M7POEEfhohAcVA FPzw34ICAVHAETtgl1EBRQzkAwIYMOhfFFKcAEEPAmi0AAwRCSTDbBq+BwIQog1hwEZP9CcQEz1E kSJ4U1ARwAFVWKGRFdoRZMQVN36HABYBFJBFaBkpoMUWBFmxgg9FEsdFFwJB4cUXIqKQRWcDYVBa lbU1AYZAYUzBkQZgFECQD2KQWdsYYwhERhkcmTHGgQSdgYacp4FhhkBpqMHRGmWwUVAbbgB6GRNv wCFQHIZuJAedCxQkRmuOHsbFHEsEQEcaYXDEQh12cFHQGXd0ihgeeQj/pMcefKx0RRxxEhTEoK7i 1YcfAv3hByAr9RFHHwYFEmqvdglCbACDEFIrR4UYUodBh7TK7FmCICLQIHVMW1AiiizCSCOOPAIJ JJFEIskblRYUiECTUDKJQJVUspIllFBSWyWWDGRvQQP3O7BFlwwkAyaZPBKJJptw0oknn1QMysWh hCKKKKOI4sUeIRiEw3kBkFJKAJaY4u9Gp6CSiiqrSFTKykBRcvJEpaQiECuoGKRyAKaoQooprFCk SCuuvLIJLLHEcrEssswSyyxUV/wJLZLUYsstiuCSCxiGeFuQLroIRIkplpRCCsqn6BtAJf4CHAAr k5wiUMor3/v2Lv6m/7xLwJX8HQAlARc8ySSs7DIJv/gGHEApqqzMCt0DsWLKvaWcXMkpjv/88ypr E7QIL714EssnoYACNSi+UE1107H88gowwQgz0TBzNFqQFXgMREoqaFOCCjGoFE0KMSX7a8rxAu1i SkG7HG8K3KaUYskpMKNiSSp/m9L9JDD/XsnzAaDiNinF2P37ywShYnfxxGQfsOf+gi6QMMYcA/v+ /O+PTDKJwIgy5sArgtRgEAKrXgBSETNirI15pFBe0QRCjOetwhTk41fkgOavYhCDEqrYxS5ScYrf nUJng4teAIoxuWIMxIFvuxwHB5IznpXPeMjznNBQsbJlMIMZzQhi///6B4yNOMMQyDLIIP4kkJ8x r2UlQ14EZ7gz8p0tAC0jRjGUpzyhkYJzxSgFz1ahOFWkQm0BWEUpVhEzCq7tiivcReVQkbkZ5myG 3qNZAJ7Bx2f88IfQCKIgBXkLjlzCGfMyCCCiMZCf1XEVOmOeKor2M3qhQo5XlCQXF4g8vRWjGJMg hfauyIq1VeKTbgsADFNmiUlMr33mW6HdQohHPe6xj378oy51yQuO4EEZ0pCINJI4Q0vsUF+7QEUx VJFDPZ6yGC4LQDKFdrKXtQ0V6NPXKlShShdOYpmiDNgnCVIJbErzkzejoQsHt0xV3It+BZkGLudJ Tz5SYyN6METvDFL/jYRJRG/0CgBAL3I4gQb0oBQJmN5WgTyCDHSgE4EoRYxhDWvU86LXCEZG0OCH Nejho3pYQwhCgAixwSd+Ei0LNrLRx4q6lJ4uRQY1cHERw0RDG9oIxB3WsA05LMhxiakBN7rhjaIW 9RtITapSv2ENcIRDHBrJxbbOMg5ylGMZRs3qUZOKy2NcwxyNqMQ5bJeRLyRiHMG4BTm4EY5poKOo 6MDGVDmyCGqkQx1aNSpS5/nDdTSNHZygRTvc4Y53GBYe8OhFPOLxC2gwg48WfYY35FFUecgjgHNl yRewIY5wlGMe9DDqMyKbS2ZAw69DhN061uHYH46Wj9/wBj3QMY96NNgjs0PBxT3ORY1kmAMf0wAH MvKhD32wgx2rTa4nihsPZFxjH/zgBTfIcYtFjINLuJ1IQAAAOw== --_005_01719E4A8816F04686A988909FBFC4A4BE20BB3282aclmailboxcor_ Content-Type: image/jpeg; name="image004.jpg" Content-Description: image004.jpg Content-Disposition: inline; filename="image004.jpg"; size=2097; creation-date="Tue, 16 Sep 2008 14:11:29 GMT"; modification-date="Tue, 16 Sep 2008 14:11:29 GMT" Content-ID: Content-Transfer-Encoding: base64 /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAAXAIoDASIA AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3 ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3 uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDoNJt7 jw9ca34z8S6jfCyhu5l0+xa4fEp3sFO0nHPRR+PpXcaZqenfEPwc0sEs0CzpskEUhWW3kHbIxyDg j1H1rzbV/FM/jfxz/wAI2vhzT7xLe5kiha6klGwLw7sFYDsf5V6PFpvhv4eaRearHarZQhFNy0Jc hznAwpJ5ya7Kq0V/iexz03vb4TwHxEnivw1rs+lXmq6m0kZzG6XEmJUPRhz3/Q8VP4P1bXH8baJF c6jqRie9jDJLNJtYZ6EE819B+IbO81zw27aFqTWl48YktrmIjDcZAJx90+31rxDwx4u8Xw+OtO0n U9UvDm9SG4t7kBsc4I5HH1FdNOr7Sm9Fdf12OedNU5rV2Z9GVVtNSsb+SeO0u4J3t32TLE4Yxt6N joayvGevHw74Yur2Ib7t8Q2sYGS8z8IAPrz+FeUeElvfhz8T49I1OcvDqsKB5T0aRuQ34PuXPvXD To88W/u/U651OWSR7tRWTP4k0q28Q2+hS3O3UrhN8UOxjuXnnOMfwmqKePfDT2WoXn9pIsGnuI7l mRl2uSQFAI5OQelZckn0L5l3OkorypfG1xqvxStLbTdUmTSHsHleKSAqFcI53FWAb+6feug8P+K7 PT/B8Woaz4lt9T3ztEl1DAUMrZ4RUAyxHsK0lRlFImNSLO1rN1LxBo+jYGpapaWhPIWaZVJ/A81z uvePbGHwtrl3pkx/tHT4wGt542jkiZiFUsjAHHIPpXIfCHwzZa3Z3nibWoxqN/JctGj3P7zbgAls HuSfwxxTjR91znokJ1PeUYnqOm+IdG1kldN1Szu2HJWGZWP5da0qw18NaBpusNr8Vlb2lzHCyPMg Ea7DgksOnbrVe08eeHb25toYr1gLpyltNJC6RTsDghHIwefes3G+sE7Fp2+I6SiuA8b+PtOstH1m w0zU3TV7aLh4omZYnyPlLYKg9Rg1a8N+L7eLwpoJ1W7ludVvrbzRFFEZJZAM5bao6cdar2M+XmsL 2kb2O1ornJPHfh1LC0vEvjOl2WEMcETySNt+98gG4Y75HFOh8deGp4Y5U1aLY6hlyrDgjPpU+zn2 HzR7nlXh/SNd8P8AxSudal0lpLGS6nVmWaPIR2OGA3Z44OK9V8b+H5PFHhC+0uBwk8ih4ixwN6kM AfY4x+NFFbVajcoz6ozpwSTj0Pn0eDvG0aiNbe5VU+UKt8gAx2Hz1p+FvB3ieDxppF9fWTlI7uN5 JXuEcgA9fvEmiiuh4mTT0RgsPFNas9O8RaNceMfH9lp17byLoGmxNNIyzBTNMQMAYO4YyOeO9YHx F+GUEWlWt74bt5vtkUwV1e6ZiVPQgyNwQcd+9FFc8a0oSilsjeVOMk7kF3PrsXi3wx4tvNJeZktT Z3MKTxhvOG5SRlsYO4Hr69Kwm8H+ILnQNbuH08RypqqXxtjOhEifPuGQccZ7+9FFbe1cUml/VzP2 ab1/rQ6oG98Q/Eux1+20qWHTxpskAaSSPczFH7Bj3OKxrDwlrml+HvCupXFluGjX8s11aiZCdjOr B1OcE8dM+lFFS6ri+Ven5/5lKCau/wCtjctvC7+OfF+u65NG9to17ZfY4SzKXkbCjfgE4AK559qo eHZfEPwoa60/VNNW/wBJmk8yOe2mQMG6ZCsQcEAcHpjrRRQqjc/ZPb/IHBKPOtzob7U9X+Ifh/VN N07SWsbOa1YJc3M6bpJNwIQKpOAQDkmubm0/UPEug+GfCdvYNa3mlzI19K8ibYQgIypBJYnOeKKK SlyOSittQ5eazfUgj0zU9B0rxh4Yl06S7vdSkMttOsse2RD/ABMSwII64x1NMi0TWvDd34e8QTQ3 Js105bO6W1njWaEjPAycEZwePeiirVV6ee/3E+zWvkP1rw/YQ2Fje2VjrenSSyTTW95HdxPKJGIw GXcOGxng8d+tadnpHxX+xW+LvTVHlrxIsbMOO528miionWaitE99yo002f/Z --_005_01719E4A8816F04686A988909FBFC4A4BE20BB3282aclmailboxcor_-- --===============2061894479== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============2061894479==-- From megaco-bounces@ietf.org Tue Sep 16 13:19:44 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A59F3A680E; Tue, 16 Sep 2008 13:19:44 -0700 (PDT) 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 93C653A680E for ; Tue, 16 Sep 2008 13:19:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.089 X-Spam-Level: X-Spam-Status: No, score=-0.089 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, SARE_GIF_ATTACH=1.42] 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 Eoe+b42115N4 for ; Tue, 16 Sep 2008 13:19:42 -0700 (PDT) Received: from exchange.txpcorp.com (exchange.txpcorp.com [207.71.49.220]) by core3.amsl.com (Postfix) with ESMTP id 082933A677D for ; Tue, 16 Sep 2008 13:19:41 -0700 (PDT) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325 Content-class: urn:content-classes:message MIME-Version: 1.0 Importance: normal Priority: normal Date: Tue, 16 Sep 2008 15:19:49 -0500 Message-ID: In-Reply-To: <01719E4A8816F04686A988909FBFC4A4BE20BB3282@aclmailbox.corp.audiocodes.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Megaco] What is the correct treatment when an action fails? Thread-Index: AckX7PdCsfZHAS7dSaqzeZ/COPdSYwAS+u9g References: <01719E4A8816F04686A988909FBFC4A4BE20BB3282@aclmailbox.corp.audiocodes.com> From: "John Wainwright" To: "Nurit Shenhar" , Subject: Re: [Megaco] What is the correct treatment when an action fails? X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1995392474==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org This is a multi-part message in MIME format. --===============1995392474== Content-class: urn:content-classes:message Content-Transfer-Encoding: 7bit Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01C91839.91A9FCE5" This is a multi-part message in MIME format. ------_=_NextPart_001_01C91839.91A9FCE5 Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01C91839.91A9FCE5" ------_=_NextPart_002_01C91839.91A9FCE5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We have a classic case of this scenario with our response shown below As you see we respond to both Actions. Hope this helps John =20 =20 !/2 [w.x.y.z]:20000 T=3D284515136 { C=3D*{ O-AV=3DA1{ AT{M,E}}}, C=3D-{ O-AV=3DA1{ AT{M,E}}}} =20 MEGACO/2 [a.b.c.d]:2084 REPLY =3D 284515136 { CONTEXT =3D * { AUDITVALUE =3D A1 { ERROR =3D 435 { "Termination ID is not in specified Context" } } }, CONTEXT =3D - { AUDITVALUE =3D A1 { EVENTS =3D 84412159 { AL/ON, AL/OF { STRICT =3D STATE } }, MEDIA { TERMINATIONSTATE { SERVICESTATES =3D INSERVICE, BUFFER =3D OFF } } } } } =20 ________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Nurit Shenhar Sent: Tuesday, September 16, 2008 6:11 AM To: megaco@ietf.org Subject: [Megaco] What is the correct treatment when an action fails? =20 Hi all =20 Assuming we have two actions in a transaction, the first refers to ALL contexts and the second refers to the NULL context, what should be the correct treatment if there are no active contexts on the gateway? Should the second action be performed? =20 The standard refers to the case in which a command fails, but not to the case in which the action fails. =20 Thanks, =20 Nurit Shenhar Control and management Leader =20 =20 =20 Email: nurits@audiocodes.com Tel. +972-3-9764155 Fax. +972-3-9764223 www.audiocodes.com =20 =20 =20 =20 =20 ________________________________ This email and any files transmitted with it are confidential material. They are intended solely for the use of the designated individual or entity to whom they are addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this email in error please immediately notify the sender and delete or destroy any copy of this message **************************************** The information contained in this message may be confidential, = privileged or protected from disclosure. If you have received it by = mistake, please let us know by e-mail reply and delete it from your = system; you may not copy, disseminate or disclose the contents of this = message to anyone. ------_=_NextPart_002_01C91839.91A9FCE5 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

We have a classic case of this = scenario with our response shown below

As you see we respond to both = Actions. Hope this helps

John

!/2 [w.x.y.z]:20000 = T=3D284515136 {

C=3D*{

O-AV=3DA1{<= /p>

AT{M,E}}},<= /p>

C=3D-{

O-AV=3DA1{<= /p>

AT{M,E}}}}<= /p>

MEGACO/2 = [a.b.c.d]:2084

REPLY =3D 284515136 = {

CONTEXT =3D * = {

AUDITVALUE =3D = A1 {

= ERROR =3D 435 { "Termination ID is not in specified Context" = }

= }

= },

CONTEXT =3D - = {

AUDITVALUE =3D = A1 {

= EVENTS =3D 84412159 { AL/ON,

= &= nbsp; AL/OF { STRICT =3D STATE } },

= MEDIA {

= TERMINATIONSTATE { SERVICESTATES =3D = INSERVICE,

= &= nbsp; BUFFER =3D OFF }

= }

}

The information contained in this message may be = confidential, privileged or protected from disclosure. If you have = received it by mistake, please let us know by e-mail reply and delete it = from your system; you may not copy, disseminate or disclose the contents = of this message to anyone.

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Nurit Shenhar
Sent: Tuesday, September = 16, 2008 6:11 AM
To: megaco@ietf.org
Subject: [Megaco] What is = the correct treatment when an action fails?

Hi all

Assuming we have two actions in a transaction, the first refers to ALL contexts = and the second refers to the NULL context, what should be the correct treatment = if there are no active contexts on the gateway? Should the second = action be performed?

The standard refers to the case in which a command fails, but not to the = case in which the action fails.

Thanks,

Nurit = Shenhar

Control and management = Leader

Email: = nurits@audiocodes.com

Tel. +972-3-9764155

Fax. +972-3-9764223

www.audiocodes.com

This email and any files transmitted = with it are confidential material. They are intended solely for the use of = the designated individual or entity to whom they are addressed. If the = reader of this message is not the intended recipient, you are hereby notified that = any dissemination, use, distribution or copying of this communication is = strictly prohibited and may be unlawful.

If you have received this email in error please immediately notify the = sender and delete or destroy any copy of this message

------_=_NextPart_002_01C91839.91A9FCE5-- ------_=_NextPart_001_01C91839.91A9FCE5 Content-Type: image/gif; name="image002.gif" Content-Transfer-Encoding: base64 Content-ID: Content-Description: image002.gif Content-Location: image002.gif R0lGODlhkAAuAHcAMSH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAX AAAAC21zT1BNU09GRklDRTkuMEI8pPUAIf8LTVNPRkZJQ0U5LjAVAAAACXBIWXMAAA7EAAAOxAGV Kw4bACwAAAAAkAAuAIcAAAD////p6emVlZWYlpa6urjv7u7AwL5BPj2vr67r6+r39vZDQUGNjIyD goLMzMrX1tZHRkY1NDRzcXGTkpLV1dWHhoZ2dXXMyspqaWmzsrKLioq9vbtPTU2qqalcWlmnpqbp 5+VTUVChoaF3d3ejoaHS0tL5+fm4uLilo6NtbGyenp36+vpnZ2fe3d2OjY1hX11GRESpp6ZlZGRW VVX8/Pxwbm7Ozs7c29v09PTj4+NoZmVMSUlkYmH29fVUUlFMSEjm5uU1MzJYVlXX19Vsammtqqra 2tiOjYyFg4LEw8Py8vL9/f2koaDt7e1zcW+bmZbU0tI3NTJuaWOVkpFSTk3x8fCal5LJx8ZlY12m pKJvbGjk4+NcWFRWUUr7+/xqZmCEgHjLysd8eXR2dGxzcGq9u7bPzsvt7etpZFqKhnvn5eOEgnzu 7u7W1NJNRzze3ttbU0rw7+5GPi36+fmTkIliX1Xa19TOzMVVSz7j4t94cWSim5Cvq6N+dWjOy8en opjCvbiKhHS4s6mCfXDP0NNdUkPX1NHc2tX09vrl6vLX2+fM0+K4wNewu9Wcq82GmsJ0i7tMX5vv 9Pa6ytvN2OTe5O6dlotzfJFeZHVXa6FCVJQuQn0jOXIbMmcXLmYWLGgVLWsTLG8RLHU1VohRcp4A KlqWrccMNGRDY5MmSnxhgampvdGuutJCS2Byg68ZMHEZL2IWLWQYLmU1SoVkfK2XpsrIz9/4+Pr9 /v7q6eaDnr6OnL1CVYsXLWYqP3S0vdXe4uz5+vx3bF9zkbQZQHCHlrcnOm48TYGTocBkWkkhNGIZ LV8ZLl9rYlIcL1wZLWDV0cvHw7xaaZelr8j08/IbLlxQYZPs7vRygaa2rqL19PKeqsVKWYYdMFwb L1xJWYuCkbG/x9jp6vCyvNBQX42Mmbvs7vUvQW13hqtGVoQZMGAiN2k/UotOYJhLXZZMXpQyRnod MFs7THolOGRQX4ufqcLk5+5tgKg5Sn4hNWljdaOEkrUAAAAAAAAAAAAI/wADCBxIsOBAAQMIFDBw AAGCBAoMSpxIsaLFixgzatx4cQGDBAYaOHgAIYKECRQqcFzJsqXLlxktXMAgIYOGBBs4dNjg4QMI mECDCh1KMIQIDxJGDIRAooQEEydQpCBKtarVigM2MJhQsIKKER0EZlhxtazZoSxaOHVhkMILGAQC KIhh4qzduxxlbJhBQ+ICFRoiRJTRoQbew4glTkD6U+KJADYsCPwwILFlxDdIgJCAo2KFCDkCQJCg 47Lpsw1G7ODxuGIPGQJJ7DhNu6qPHziAwLaI4oPAIEJu1B4eNIEI4MIt1hhCRGAREcSju+wxwsiH IxiRJPktRIn07xqXCP+pcKEBC4wVhjAR6CAC+PcWNXTI0aOJxh51AzgRcgC+f4M7POEEfhohAcVA FPzw34ICAVHAETtgl1EBRQzkAwIYMOhfFFKcAEEPAmi0AAwRCSTDbBq+BwIQog1hwEZP9CcQEz1E kSJ4U1ARwAFVWKGRFdoRZMQVN36HABYBFJBFaBkpoMUWBFmxgg9FEsdFFwJB4cUXIqKQRWcDYVBa lbU1AYZAYUzBkQZgFECQD2KQWdsYYwhERhkcmTHGgQSdgYacp4FhhkBpqMHRGmWwUVAbbgB6GRNv wCFQHIZuJAedCxQkRmuOHsbFHEsEQEcaYXDEQh12cFHQGXd0ihgeeQj/pMcefKx0RRxxEhTEoK7i 1YcfAv3hByAr9RFHHwYFEmqvdglCbACDEFIrR4UYUodBh7TK7FmCICLQIHVMW1AiiizCSCOOPAIJ JJFEIskblRYUiECTUDKJQJVUspIllFBSWyWWDGRvQQP3O7BFlwwkAyaZPBKJJptw0oknn1QMysWh hCKKKKOI4sUeIRiEw3kBkFJKAJaY4u9Gp6CSiiqrSFTKykBRcvJEpaQiECuoGKRyAKaoQooprFCk SCuuvLIJLLHEcrEssswSyyxUV/wJLZLUYsstiuCSCxiGeFuQLroIRIkplpRCCsqn6BtAJf4CHAAr k5wiUMor3/v2Lv6m/7xLwJX8HQAlARc8ySSs7DIJv/gGHEApqqzMCt0DsWLKvaWcXMkpjv/88ypr E7QIL714EssnoYACNSi+UE1107H88gowwQgz0TBzNFqQFXgMREoqaFOCCjGoFE0KMSX7a8rxAu1i SkG7HG8K3KaUYskpMKNiSSp/m9L9JDD/XsnzAaDiNinF2P37ywShYnfxxGQfsOf+gi6QMMYcA/v+ /O+PTDKJwIgy5sArgtRgEAKrXgBSETNirI15pFBe0QRCjOetwhTk41fkgOavYhCDEqrYxS5ScYrf nUJng4teAIoxuWIMxIFvuxwHB5IznpXPeMjznNBQsbJlMIMZzQhi///6B4yNOMMQyDLIIP4kkJ8x r2UlQ14EZ7gz8p0tAC0jRjGUpzyhkYJzxSgFz1ahOFWkQm0BWEUpVhEzCq7tiivcReVQkbkZ5myG 3qNZAJ7Bx2f88IfQCKIgBXkLjlzCGfMyCCCiMZCf1XEVOmOeKor2M3qhQo5XlCQXF4g8vRWjGJMg hfauyIq1VeKTbgsADFNmiUlMr33mW6HdQohHPe6xj378oy51yQuO4EEZ0pCINJI4Q0vsUF+7QEUx VJFDPZ6yGC4LQDKFdrKXtQ0V6NPXKlShShdOYpmiDNgnCVIJbErzkzejoQsHt0xV3It+BZkGLudJ Tz5SYyN6METvDFL/jYRJRG/0CgBAL3I4gQb0oBQJmN5WgTyCDHSgE4EoRYxhDWvU86LXCEZG0OCH Nejho3pYQwhCgAixwSd+Ei0LNrLRx4q6lJ4uRQY1cHERw0RDG9oIxB3WsA05LMhxiakBN7rhjaIW 9RtITapSv2ENcIRDHBrJxbbOMg5ylGMZRs3qUZOKy2NcwxyNqMQ5bJeRLyRiHMG4BTm4EY5poKOo 6MDGVDmyCGqkQx1aNSpS5/nDdTSNHZygRTvc4Y53GBYe8OhFPOLxC2gwg48WfYY35FFUecgjgHNl yRewIY5wlGMe9DDqMyKbS2ZAw69DhN061uHYH46Wj9/wBj3QMY96NNgjs0PBxT3ORY1kmAMf0wAH MvKhD32wgx2rTa4nihsPZFxjH/zgBTfIcYtFjINLuJ1IQAAAOw== ------_=_NextPart_001_01C91839.91A9FCE5 Content-Type: image/jpeg; name="image001.jpg" Content-Transfer-Encoding: base64 Content-ID: Content-Description: image001.jpg Content-Location: image001.jpg /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAAXAIoDASIA AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3 ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3 uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDoNJt7 jw9ca34z8S6jfCyhu5l0+xa4fEp3sFO0nHPRR+PpXcaZqenfEPwc0sEs0CzpskEUhWW3kHbIxyDg j1H1rzbV/FM/jfxz/wAI2vhzT7xLe5kiha6klGwLw7sFYDsf5V6PFpvhv4eaRearHarZQhFNy0Jc hznAwpJ5ya7Kq0V/iexz03vb4TwHxEnivw1rs+lXmq6m0kZzG6XEmJUPRhz3/Q8VP4P1bXH8baJF c6jqRie9jDJLNJtYZ6EE819B+IbO81zw27aFqTWl48YktrmIjDcZAJx90+31rxDwx4u8Xw+OtO0n U9UvDm9SG4t7kBsc4I5HH1FdNOr7Sm9Fdf12OedNU5rV2Z9GVVtNSsb+SeO0u4J3t32TLE4Yxt6N joayvGevHw74Yur2Ib7t8Q2sYGS8z8IAPrz+FeUeElvfhz8T49I1OcvDqsKB5T0aRuQ34PuXPvXD To88W/u/U651OWSR7tRWTP4k0q28Q2+hS3O3UrhN8UOxjuXnnOMfwmqKePfDT2WoXn9pIsGnuI7l mRl2uSQFAI5OQelZckn0L5l3OkorypfG1xqvxStLbTdUmTSHsHleKSAqFcI53FWAb+6feug8P+K7 PT/B8Woaz4lt9T3ztEl1DAUMrZ4RUAyxHsK0lRlFImNSLO1rN1LxBo+jYGpapaWhPIWaZVJ/A81z uvePbGHwtrl3pkx/tHT4wGt542jkiZiFUsjAHHIPpXIfCHwzZa3Z3nibWoxqN/JctGj3P7zbgAls HuSfwxxTjR91znokJ1PeUYnqOm+IdG1kldN1Szu2HJWGZWP5da0qw18NaBpusNr8Vlb2lzHCyPMg Ea7DgksOnbrVe08eeHb25toYr1gLpyltNJC6RTsDghHIwefes3G+sE7Fp2+I6SiuA8b+PtOstH1m w0zU3TV7aLh4omZYnyPlLYKg9Rg1a8N+L7eLwpoJ1W7ludVvrbzRFFEZJZAM5bao6cdar2M+XmsL 2kb2O1ornJPHfh1LC0vEvjOl2WEMcETySNt+98gG4Y75HFOh8deGp4Y5U1aLY6hlyrDgjPpU+zn2 HzR7nlXh/SNd8P8AxSudal0lpLGS6nVmWaPIR2OGA3Z44OK9V8b+H5PFHhC+0uBwk8ih4ixwN6kM AfY4x+NFFbVajcoz6ozpwSTj0Pn0eDvG0aiNbe5VU+UKt8gAx2Hz1p+FvB3ieDxppF9fWTlI7uN5 JXuEcgA9fvEmiiuh4mTT0RgsPFNas9O8RaNceMfH9lp17byLoGmxNNIyzBTNMQMAYO4YyOeO9YHx F+GUEWlWt74bt5vtkUwV1e6ZiVPQgyNwQcd+9FFc8a0oSilsjeVOMk7kF3PrsXi3wx4tvNJeZktT Z3MKTxhvOG5SRlsYO4Hr69Kwm8H+ILnQNbuH08RypqqXxtjOhEifPuGQccZ7+9FFbe1cUml/VzP2 ab1/rQ6oG98Q/Eux1+20qWHTxpskAaSSPczFH7Bj3OKxrDwlrml+HvCupXFluGjX8s11aiZCdjOr B1OcE8dM+lFFS6ri+Ven5/5lKCau/wCtjctvC7+OfF+u65NG9to17ZfY4SzKXkbCjfgE4AK559qo eHZfEPwoa60/VNNW/wBJmk8yOe2mQMG6ZCsQcEAcHpjrRRQqjc/ZPb/IHBKPOtzob7U9X+Ifh/VN N07SWsbOa1YJc3M6bpJNwIQKpOAQDkmubm0/UPEug+GfCdvYNa3mlzI19K8ibYQgIypBJYnOeKKK SlyOSittQ5eazfUgj0zU9B0rxh4Yl06S7vdSkMttOsse2RD/ABMSwII64x1NMi0TWvDd34e8QTQ3 Js105bO6W1njWaEjPAycEZwePeiirVV6ee/3E+zWvkP1rw/YQ2Fje2VjrenSSyTTW95HdxPKJGIw GXcOGxng8d+tadnpHxX+xW+LvTVHlrxIsbMOO528miionWaitE99yo002f/Z ------_=_NextPart_001_01C91839.91A9FCE5-- --===============1995392474== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============1995392474==-- From megaco-bounces@ietf.org Wed Sep 17 00:31:52 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D26428C29A; Wed, 17 Sep 2008 00:31:52 -0700 (PDT) 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 091F328C292 for ; Wed, 17 Sep 2008 00:31:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.038 X-Spam-Level: X-Spam-Status: No, score=-5.038 tagged_above=-999 required=5 tests=[AWL=-1.210, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_GIF_ATTACH=1.42] 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 xWKQcdf4S4Qt for ; Wed, 17 Sep 2008 00:31:40 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 704673A69F3 for ; Wed, 17 Sep 2008 00:31:39 -0700 (PDT) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 2CE402071E; Wed, 17 Sep 2008 09:31:51 +0200 (CEST) X-AuditID: c1b4fb3c-ae0cebb0000015b5-61-48d0b2677d6a Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 0213920D8A; Wed, 17 Sep 2008 09:31:51 +0200 (CEST) Received: from esealmw107.eemea.ericsson.se ([153.88.200.70]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 17 Sep 2008 09:31:50 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 17 Sep 2008 09:31:49 +0200 Message-ID: In-Reply-To: <01719E4A8816F04686A988909FBFC4A4BE20BB3282@aclmailbox.corp.audiocodes.com> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: [Megaco] What is the correct treatment when an action fails? Thread-Index: AckX7PdCsfZHAS7dSaqzeZ/COPdSYwAqL8eQ References: <01719E4A8816F04686A988909FBFC4A4BE20BB3282@aclmailbox.corp.audiocodes.com> From: "Krishna Prasad Kalluri" To: "Nurit Shenhar" , X-OriginalArrivalTime: 17 Sep 2008 07:31:50.0298 (UTC) FILETIME=[72DCEFA0:01C91897] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Megaco] What is the correct treatment when an action fails? X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1252435403==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org This is a multi-part message in MIME format. --===============1252435403== Content-class: urn:content-classes:message Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01C91897.72FCA6B7" This is a multi-part message in MIME format. ------_=_NextPart_001_01C91897.72FCA6B7 Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01C91897.72FCA6B7" ------_=_NextPart_002_01C91897.72FCA6B7 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Nurit, =20 It depends on whether the first command is marked with optional flag or not. If the first command is marked with "optional" flag then you have to continue and execute the section action request. =20 Here is the description from H.248.v2 page 43 Commands may be marked as "Optional" which can override this behaviour - if a command marked as Optional results in an error, subsequent commands in the Transaction will be executed. =20 So though the "optional" indication is there at the command level it applies to the Action request. The above statement is saying subsequent commands in the "TRANSACTION". =20 Regards Krishna=20 ________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Nurit Shenhar Sent: den 16 september 2008 13:11 To: megaco@ietf.org Subject: [Megaco] What is the correct treatment when an action fails? Hi all =20 Assuming we have two actions in a transaction, the first refers to ALL contexts and the second refers to the NULL context, what should be the correct treatment if there are no active contexts on the gateway? Should the second action be performed? =20 The standard refers to the case in which a command fails, but not to the case in which the action fails. =20 Thanks, =20 Nurit Shenhar Control and management Leader =20 =20 =20 Email: nurits@audiocodes.com Tel. +972-3-9764155 Fax. +972-3-9764223 www.audiocodes.com =20 =20 =20 =20 ________________________________ This email and any files transmitted with it are confidential material. They are intended solely for the use of the designated individual or entity to whom they are addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this email in error please immediately notify the sender and delete or destroy any copy of this message ------_=_NextPart_002_01C91897.72FCA6B7 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Nurit,

It depends on whether the first command is = marked with=20 optional flag or not. If the first command is marked with "optional" = flag then=20 you have to continue and execute the section action = request.

Here is the description from H.248.v2 page=20 43

Commands may be marked = as "Optional"=20 which can override this behaviour – if a command=20 marked as Optional results in an error, subsequent commands in = the=20 Transaction will be executed.

So though the "optional" indication is there = at the=20 command level it applies to the Action request. The above statement is = saying=20 subsequent commands in the = "TRANSACTION".

Regards

Krishna

From: megaco-bounces@ietf.org=20 [mailto:megaco-bounces@ietf.org] On Behalf Of Nurit=20 Shenhar
Sent: den 16 september 2008 13:11
To:=20 megaco@ietf.org
Subject: [Megaco] What is the correct = treatment when=20 an action fails?

Hi all

Assuming we have two actions in a transaction, the = first=20 refers to ALL contexts and the second refers to the NULL context, what = should be=20 the correct treatment if there are no active contexts on the gateway?=20 Should the second action be performed?

The standard refers to the case in which a command = fails, but=20 not to the case in which the action fails.

Thanks,

Nurit=20 Shenhar

Control=20 and management Leader

Email:=20 nurits@audiocodes.com

Tel. =20 +972-3-9764155

Fax.=20 +972-3-9764223

www.audiocodes.com

This email and any files = transmitted with it=20 are confidential material. They are intended solely for the use of the=20 designated individual or entity to whom they are addressed. If the = reader of=20 this message is not the intended recipient, you are hereby notified that = any=20 dissemination, use, distribution or copying of this communication is = strictly=20 prohibited and may be unlawful.

If you have received this email = in error=20 please immediately notify the sender and delete or destroy any copy of = this=20 message
------_=_NextPart_002_01C91897.72FCA6B7-- ------_=_NextPart_001_01C91897.72FCA6B7 Content-Type: image/jpeg; name="image004.jpg" Content-Transfer-Encoding: base64 Content-ID: <577241907@17092008-0F72> Content-Description: image004.jpg Content-Location: image004.jpg /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAAXAIoDASIA AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3 ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3 uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDoNJt7 jw9ca34z8S6jfCyhu5l0+xa4fEp3sFO0nHPRR+PpXcaZqenfEPwc0sEs0CzpskEUhWW3kHbIxyDg j1H1rzbV/FM/jfxz/wAI2vhzT7xLe5kiha6klGwLw7sFYDsf5V6PFpvhv4eaRearHarZQhFNy0Jc hznAwpJ5ya7Kq0V/iexz03vb4TwHxEnivw1rs+lXmq6m0kZzG6XEmJUPRhz3/Q8VP4P1bXH8baJF c6jqRie9jDJLNJtYZ6EE819B+IbO81zw27aFqTWl48YktrmIjDcZAJx90+31rxDwx4u8Xw+OtO0n U9UvDm9SG4t7kBsc4I5HH1FdNOr7Sm9Fdf12OedNU5rV2Z9GVVtNSsb+SeO0u4J3t32TLE4Yxt6N joayvGevHw74Yur2Ib7t8Q2sYGS8z8IAPrz+FeUeElvfhz8T49I1OcvDqsKB5T0aRuQ34PuXPvXD To88W/u/U651OWSR7tRWTP4k0q28Q2+hS3O3UrhN8UOxjuXnnOMfwmqKePfDT2WoXn9pIsGnuI7l mRl2uSQFAI5OQelZckn0L5l3OkorypfG1xqvxStLbTdUmTSHsHleKSAqFcI53FWAb+6feug8P+K7 PT/B8Woaz4lt9T3ztEl1DAUMrZ4RUAyxHsK0lRlFImNSLO1rN1LxBo+jYGpapaWhPIWaZVJ/A81z uvePbGHwtrl3pkx/tHT4wGt542jkiZiFUsjAHHIPpXIfCHwzZa3Z3nibWoxqN/JctGj3P7zbgAls HuSfwxxTjR91znokJ1PeUYnqOm+IdG1kldN1Szu2HJWGZWP5da0qw18NaBpusNr8Vlb2lzHCyPMg Ea7DgksOnbrVe08eeHb25toYr1gLpyltNJC6RTsDghHIwefes3G+sE7Fp2+I6SiuA8b+PtOstH1m w0zU3TV7aLh4omZYnyPlLYKg9Rg1a8N+L7eLwpoJ1W7ludVvrbzRFFEZJZAM5bao6cdar2M+XmsL 2kb2O1ornJPHfh1LC0vEvjOl2WEMcETySNt+98gG4Y75HFOh8deGp4Y5U1aLY6hlyrDgjPpU+zn2 HzR7nlXh/SNd8P8AxSudal0lpLGS6nVmWaPIR2OGA3Z44OK9V8b+H5PFHhC+0uBwk8ih4ixwN6kM AfY4x+NFFbVajcoz6ozpwSTj0Pn0eDvG0aiNbe5VU+UKt8gAx2Hz1p+FvB3ieDxppF9fWTlI7uN5 JXuEcgA9fvEmiiuh4mTT0RgsPFNas9O8RaNceMfH9lp17byLoGmxNNIyzBTNMQMAYO4YyOeO9YHx F+GUEWlWt74bt5vtkUwV1e6ZiVPQgyNwQcd+9FFc8a0oSilsjeVOMk7kF3PrsXi3wx4tvNJeZktT Z3MKTxhvOG5SRlsYO4Hr69Kwm8H+ILnQNbuH08RypqqXxtjOhEifPuGQccZ7+9FFbe1cUml/VzP2 ab1/rQ6oG98Q/Eux1+20qWHTxpskAaSSPczFH7Bj3OKxrDwlrml+HvCupXFluGjX8s11aiZCdjOr B1OcE8dM+lFFS6ri+Ven5/5lKCau/wCtjctvC7+OfF+u65NG9to17ZfY4SzKXkbCjfgE4AK559qo eHZfEPwoa60/VNNW/wBJmk8yOe2mQMG6ZCsQcEAcHpjrRRQqjc/ZPb/IHBKPOtzob7U9X+Ifh/VN N07SWsbOa1YJc3M6bpJNwIQKpOAQDkmubm0/UPEug+GfCdvYNa3mlzI19K8ibYQgIypBJYnOeKKK SlyOSittQ5eazfUgj0zU9B0rxh4Yl06S7vdSkMttOsse2RD/ABMSwII64x1NMi0TWvDd34e8QTQ3 Js105bO6W1njWaEjPAycEZwePeiirVV6ee/3E+zWvkP1rw/YQ2Fje2VjrenSSyTTW95HdxPKJGIw GXcOGxng8d+tadnpHxX+xW+LvTVHlrxIsbMOO528miionWaitE99yo002f/Z ------_=_NextPart_001_01C91897.72FCA6B7 Content-Type: image/gif; name="image003.gif" Content-Transfer-Encoding: base64 Content-ID: <577241907@17092008-0F79> Content-Description: image003.gif Content-Location: image003.gif R0lGODlhkAAuAHcAMSH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAX AAAAC21zT1BNU09GRklDRTkuMEI8pPUAIf8LTVNPRkZJQ0U5LjAVAAAACXBIWXMAAA7EAAAOxAGV Kw4bACwAAAAAkAAuAIcAAAD////p6emVlZWYlpa6urjv7u7AwL5BPj2vr67r6+r39vZDQUGNjIyD goLMzMrX1tZHRkY1NDRzcXGTkpLV1dWHhoZ2dXXMyspqaWmzsrKLioq9vbtPTU2qqalcWlmnpqbp 5+VTUVChoaF3d3ejoaHS0tL5+fm4uLilo6NtbGyenp36+vpnZ2fe3d2OjY1hX11GRESpp6ZlZGRW VVX8/Pxwbm7Ozs7c29v09PTj4+NoZmVMSUlkYmH29fVUUlFMSEjm5uU1MzJYVlXX19Vsammtqqra 2tiOjYyFg4LEw8Py8vL9/f2koaDt7e1zcW+bmZbU0tI3NTJuaWOVkpFSTk3x8fCal5LJx8ZlY12m pKJvbGjk4+NcWFRWUUr7+/xqZmCEgHjLysd8eXR2dGxzcGq9u7bPzsvt7etpZFqKhnvn5eOEgnzu 7u7W1NJNRzze3ttbU0rw7+5GPi36+fmTkIliX1Xa19TOzMVVSz7j4t94cWSim5Cvq6N+dWjOy8en opjCvbiKhHS4s6mCfXDP0NNdUkPX1NHc2tX09vrl6vLX2+fM0+K4wNewu9Wcq82GmsJ0i7tMX5vv 9Pa6ytvN2OTe5O6dlotzfJFeZHVXa6FCVJQuQn0jOXIbMmcXLmYWLGgVLWsTLG8RLHU1VohRcp4A KlqWrccMNGRDY5MmSnxhgampvdGuutJCS2Byg68ZMHEZL2IWLWQYLmU1SoVkfK2XpsrIz9/4+Pr9 /v7q6eaDnr6OnL1CVYsXLWYqP3S0vdXe4uz5+vx3bF9zkbQZQHCHlrcnOm48TYGTocBkWkkhNGIZ LV8ZLl9rYlIcL1wZLWDV0cvHw7xaaZelr8j08/IbLlxQYZPs7vRygaa2rqL19PKeqsVKWYYdMFwb L1xJWYuCkbG/x9jp6vCyvNBQX42Mmbvs7vUvQW13hqtGVoQZMGAiN2k/UotOYJhLXZZMXpQyRnod MFs7THolOGRQX4ufqcLk5+5tgKg5Sn4hNWljdaOEkrUAAAAAAAAAAAAI/wADCBxIsOBAAQMIFDBw AAGCBAoMSpxIsaLFixgzatx4cQGDBAYaOHgAIYKECRQqcFzJsqXLlxktXMAgIYOGBBs4dNjg4QMI mECDCh1KMIQIDxJGDIRAooQEEydQpCBKtarVigM2MJhQsIKKER0EZlhxtazZoSxaOHVhkMILGAQC KIhh4qzduxxlbJhBQ+ICFRoiRJTRoQbew4glTkD6U+KJADYsCPwwILFlxDdIgJCAo2KFCDkCQJCg 47Lpsw1G7ODxuGIPGQJJ7DhNu6qPHziAwLaI4oPAIEJu1B4eNIEI4MIt1hhCRGAREcSju+wxwsiH IxiRJPktRIn07xqXCP+pcKEBC4wVhjAR6CAC+PcWNXTI0aOJxh51AzgRcgC+f4M7POEEfhohAcVA FPzw34ICAVHAETtgl1EBRQzkAwIYMOhfFFKcAEEPAmi0AAwRCSTDbBq+BwIQog1hwEZP9CcQEz1E kSJ4U1ARwAFVWKGRFdoRZMQVN36HABYBFJBFaBkpoMUWBFmxgg9FEsdFFwJB4cUXIqKQRWcDYVBa lbU1AYZAYUzBkQZgFECQD2KQWdsYYwhERhkcmTHGgQSdgYacp4FhhkBpqMHRGmWwUVAbbgB6GRNv wCFQHIZuJAedCxQkRmuOHsbFHEsEQEcaYXDEQh12cFHQGXd0ihgeeQj/pMcefKx0RRxxEhTEoK7i 1YcfAv3hByAr9RFHHwYFEmqvdglCbACDEFIrR4UYUodBh7TK7FmCICLQIHVMW1AiiizCSCOOPAIJ JJFEIskblRYUiECTUDKJQJVUspIllFBSWyWWDGRvQQP3O7BFlwwkAyaZPBKJJptw0oknn1QMysWh hCKKKKOI4sUeIRiEw3kBkFJKAJaY4u9Gp6CSiiqrSFTKykBRcvJEpaQiECuoGKRyAKaoQooprFCk SCuuvLIJLLHEcrEssswSyyxUV/wJLZLUYsstiuCSCxiGeFuQLroIRIkplpRCCsqn6BtAJf4CHAAr k5wiUMor3/v2Lv6m/7xLwJX8HQAlARc8ySSs7DIJv/gGHEApqqzMCt0DsWLKvaWcXMkpjv/88ypr E7QIL714EssnoYACNSi+UE1107H88gowwQgz0TBzNFqQFXgMREoqaFOCCjGoFE0KMSX7a8rxAu1i SkG7HG8K3KaUYskpMKNiSSp/m9L9JDD/XsnzAaDiNinF2P37ywShYnfxxGQfsOf+gi6QMMYcA/v+ /O+PTDKJwIgy5sArgtRgEAKrXgBSETNirI15pFBe0QRCjOetwhTk41fkgOavYhCDEqrYxS5ScYrf nUJng4teAIoxuWIMxIFvuxwHB5IznpXPeMjznNBQsbJlMIMZzQhi///6B4yNOMMQyDLIIP4kkJ8x r2UlQ14EZ7gz8p0tAC0jRjGUpzyhkYJzxSgFz1ahOFWkQm0BWEUpVhEzCq7tiivcReVQkbkZ5myG 3qNZAJ7Bx2f88IfQCKIgBXkLjlzCGfMyCCCiMZCf1XEVOmOeKor2M3qhQo5XlCQXF4g8vRWjGJMg hfauyIq1VeKTbgsADFNmiUlMr33mW6HdQohHPe6xj378oy51yQuO4EEZ0pCINJI4Q0vsUF+7QEUx VJFDPZ6yGC4LQDKFdrKXtQ0V6NPXKlShShdOYpmiDNgnCVIJbErzkzejoQsHt0xV3It+BZkGLudJ Tz5SYyN6METvDFL/jYRJRG/0CgBAL3I4gQb0oBQJmN5WgTyCDHSgE4EoRYxhDWvU86LXCEZG0OCH Nejho3pYQwhCgAixwSd+Ei0LNrLRx4q6lJ4uRQY1cHERw0RDG9oIxB3WsA05LMhxiakBN7rhjaIW 9RtITapSv2ENcIRDHBrJxbbOMg5ylGMZRs3qUZOKy2NcwxyNqMQ5bJeRLyRiHMG4BTm4EY5poKOo 6MDGVDmyCGqkQx1aNSpS5/nDdTSNHZygRTvc4Y53GBYe8OhFPOLxC2gwg48WfYY35FFUecgjgHNl yRewIY5wlGMe9DDqMyKbS2ZAw69DhN061uHYH46Wj9/wBj3QMY96NNgjs0PBxT3ORY1kmAMf0wAH MvKhD32wgx2rTa4nihsPZFxjH/zgBTfIcYtFjINLuJ1IQAAAOw== ------_=_NextPart_001_01C91897.72FCA6B7-- --===============1252435403== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============1252435403==-- From megaco-bounces@ietf.org Wed Sep 17 17:24:49 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E9DF3A69EA; Wed, 17 Sep 2008 17:24:49 -0700 (PDT) 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 B1E643A69EC for ; Wed, 17 Sep 2008 17:24:47 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BANNED, message contains part: multipart/mixed | application/ms-tnef,.tnef,winmail.dat X-Spam-Flag: NO X-Spam-Score: -1.677 X-Spam-Level: X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311] X-Amavis-Modified: Mail body modified (defanged) by core3.amsl.com 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 Om8rAgqli1zU for ; Wed, 17 Sep 2008 17:24:41 -0700 (PDT) Content-Type: multipart/mixed; boundary="----------=_1221697487-1176-1" Content-Transfer-Encoding: binary MIME-Version: 1.0 Received: from smtp.exchangecentral.net (onr-off.chi.us.siteprotect.com [64.41.122.5]) by core3.amsl.com (Postfix) with ESMTP id E13983A6942 for ; Wed, 17 Sep 2008 17:24:40 -0700 (PDT) Date: Wed, 17 Sep 2008 19:31:56 -0500 Message-ID: References: From: "Tom Deckert" To: Subject: Re: [Megaco] Megaco Digest, Vol 53, Issue 11 X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org This is a multi-part message in MIME format... ------------=_1221697487-1176-1 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit WARNING: contains banned part ------------=_1221697487-1176-1 Content-Type: message/rfc822; x-spam-type=original; name="message" Content-Disposition: attachment; filename="message" Content-Transfer-Encoding: 7bit Content-Description: Original message Received: from smtp.exchangecentral.net (onr-off.chi.us.siteprotect.com [64.41.122.5]) by core3.amsl.com (Postfix) with ESMTP id E13983A6942 for ; Wed, 17 Sep 2008 17:24:40 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C91925.F4C1E466" Subject: RE: Megaco Digest, Vol 53, Issue 11 Date: Wed, 17 Sep 2008 19:31:56 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Megaco Digest, Vol 53, Issue 11 Thread-Index: AckY+Kijxqbv0ZHpQBeKcc4ueUsEegALH3+H References: From: "Tom Deckert" To: This is a multi-part message in MIME format. ------_=_NextPart_001_01C91925.F4C1E466 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, >From reading this thread, my interpretation is that any action which contains only optional commands will always succeed. By definition. Thanks, Tom=20 -----Original Message----- From: megaco-bounces@ietf.org on behalf of megaco-request@ietf.org Sent: Wed 9/17/2008 2:00 PM To: megaco@ietf.org Subject: Megaco Digest, Vol 53, Issue 11 =20 Send Megaco mailing list submissions to megaco@ietf.org To subscribe or unsubscribe via the World Wide Web, visit https://www.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-owner@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: What is the correct treatment when an action fails? (Krishna Prasad Kalluri) ---------------------------------------------------------------------- Message: 1 Date: Wed, 17 Sep 2008 09:31:49 +0200 From: "Krishna Prasad Kalluri" Subject: Re: [Megaco] What is the correct treatment when an action fails? To: "Nurit Shenhar" , Message-ID: =09 Content-Type: text/plain; charset=3D"us-ascii" Hi Nurit, =20 It depends on whether the first command is marked with optional flag or not. If the first command is marked with "optional" flag then you have to continue and execute the section action request. =20 Here is the description from H.248.v2 page 43 Commands may be marked as "Optional" which can override this behaviour - if a command marked as Optional results in an error, subsequent commands in the Transaction will be executed. =20 So though the "optional" indication is there at the command level it applies to the Action request. The above statement is saying subsequent commands in the "TRANSACTION". =20 Regards Krishna=20 ________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Nurit Shenhar Sent: den 16 september 2008 13:11 To: megaco@ietf.org Subject: [Megaco] What is the correct treatment when an action fails? Hi all =20 Assuming we have two actions in a transaction, the first refers to ALL contexts and the second refers to the NULL context, what should be the correct treatment if there are no active contexts on the gateway? Should the second action be performed? =20 The standard refers to the case in which a command fails, but not to the case in which the action fails. =20 Thanks, =20 Nurit Shenhar Control and management Leader =20 =20 =20 Email: nurits@audiocodes.com Tel. +972-3-9764155 Fax. +972-3-9764223 www.audiocodes.com =20 =20 =20 =20 ________________________________ This email and any files transmitted with it are confidential material. They are intended solely for the use of the designated individual or entity to whom they are addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this email in error please immediately notify the sender and delete or destroy any copy of this message -------------- next part -------------- An HTML attachment was scrubbed... URL: = https://www.ietf.org/mailman/private/megaco/attachments/20080917/c1c3d094= /attachment.html=20 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 2097 bytes Desc: image004.jpg Url : = https://www.ietf.org/mailman/private/megaco/attachments/20080917/c1c3d094= /attachment-0001.jpeg=20 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2488 bytes Desc: image003.gif Url : = https://www.ietf.org/mailman/private/megaco/attachments/20080917/c1c3d094= /attachment-0001.gif=20 ------------------------------ _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco End of Megaco Digest, Vol 53, Issue 11 ************************************** ------_=_NextPart_001_01C91925.F4C1E466 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 eJ8+IgEAAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEAJAAAAFJFOiBNZWdhY28gRGlnZXN0 LCBWb2wgNTMsIElzc3VlIDExAJkKAQWAAwAOAAAA2AcJABEAEwAfADgAAwBmAQEggAMADgAAANgH CQARABMAHwA4AAMAZgEBCYABACEAAABBRDBFQ0VDMzkzNUY4MTQ1OTRFNTI3MjE4OEI5RUVENgBT BwEDkAYAQBEAADkAAAADACYAAAAAAAMANgAAAAAAQAA5AGbkwfQlGckBHgA9AAEAAAAFAAAAUkU6 IAAAAAACAUcAAQAAADEAAABjPVVTO2E9IDtwPVdpbmRvd3NORztsPUVYVlMwMS0wODA5MTgwMDMx NTZaLTQzMDAAAAAAHgBJAAEAAAAgAAAATWVnYWNvIERpZ2VzdCwgVm9sIDUzLCBJc3N1ZSAxMQBA AE4AAKWilvcYyQEeAFoAAQAAABgAAABtZWdhY28tYm91bmNlc0BpZXRmLm9yZwACAVsAAQAAAE0A AAAAAAAAgSsfpL6jEBmdbgDdAQ9UAgAAAABtZWdhY28tYm91bmNlc0BpZXRmLm9yZwBTTVRQAG1l Z2Fjby1ib3VuY2VzQGlldGYub3JnAAAAAAIBXAABAAAAHQAAAFNNVFA6TUVHQUNPLUJPVU5DRVNA SUVURi5PUkcAAAAAHgBdAAEAAAAYAAAAbWVnYWNvLXJlcXVlc3RAaWV0Zi5vcmcAAgFeAAEAAABN AAAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAAAbWVnYWNvLXJlcXVlc3RAaWV0Zi5vcmcAU01UUABt ZWdhY28tcmVxdWVzdEBpZXRmLm9yZwAAAAACAV8AAQAAAB0AAABTTVRQOk1FR0FDTy1SRVFVRVNU QElFVEYuT1JHAAAAAB4AZgABAAAABQAAAFNNVFAAAAAAHgBnAAEAAAAYAAAAbWVnYWNvLWJvdW5j ZXNAaWV0Zi5vcmcAHgBoAAEAAAAFAAAAU01UUAAAAAAeAGkAAQAAABgAAABtZWdhY28tcmVxdWVz dEBpZXRmLm9yZwAeAHAAAQAAACAAAABNZWdhY28gRGlnZXN0LCBWb2wgNTMsIElzc3VlIDExAAIB cQABAAAAGwAAAAHJGPioo8am79GR6UAXinHOLnlLBHoACx9/hwAeAHQAAQAAABAAAABtZWdhY29A aWV0Zi5vcmcAHgAaDAEAAAAMAAAAVG9tIERlY2tlcnQAHgAdDgEAAAAgAAAATWVnYWNvIERpZ2Vz dCwgVm9sIDUzLCBJc3N1ZSAxMQACAQkQAQAAAP0JAAD5CQAAEhUAAExaRnXqsugjAwAKAHJjcGcx MjXiMgNDdGV4BUEBAwH3/wqAAqQD5AcTAoAP8wBQBFY/CFUHshElDlEDAQIAY2jhCsBzZXQyBgAG wxEl9jMERhO3MBIsETMI7wn3tjsYHw4wNREiDGBjAFDzCwkBZDM2FlALpgrjCoBYSGksHPQc9EYD YSAJGCBhZAuAZyB0aAcEAB8BHpIsIG15IDMLgA6wcnAYIAGQdGn/AiAgAB9CIKAc9ABwH/AA0O0g s3cfIBPQIAWgAjALcesEIAIgbB/wbwUwIMEHQGsc9AWgbQOBZAQgA/BsowMgB0B3YXkEIHMa0IJj CeBkLiAgQh/wawEBC4BpILIuHYoc9FTRE+Bua3MddVQeYSd/1AotKsJPBRBnC4AHQMMF0AeQc2Fn ZSrDHeiSOh/QZWcA0G8tBuBkdW4mIHNACJAAMC4nBbAe8CDRYmUT4GxmLyNgLyAtJRggcQpQc3Rf Lgcc9AZgAjAtAFcJgCAgOS8xNy8B0DA4iCAyOjJAIFBNKQbjLQYwXnViagWQMXEroLktQiBEKzAw IR/AVgbwaCA1Mx/ASQQQClAg/jEa8wqAHOUxQTHANXUAwJ8DEB7SOSAwMCXhYm0EAfsgwR9Bbx2F AZEzjyfqNcB/OcEE8i7QI2AFwC2wPTh2VwcwHwE3IFcFsGwxwFf2aQEAMZFiH8A+wACQIWUFOwNo AkBwczovL2p3QcAuLhYvOPIDgS//OXILgAIQQoAtMxz0BbBAIv0+4GU48h/AFBA4UT7gB4F/K9Il IR8QObI1Ej3CBuBkxR/wJz8QbHAnOn8vr/08HVkIYCLQA5EekSKxPwL6cASQcyDRA4Er4B7UNyDH OXMhVkiKb3duBJBJv90dElc/EEtiC1B5HtEfwL8LUB6gFBBE0B7ABUB5CGH/BgBGpTkhNyBMUCAA BUAfMe8EYBggJeBMIGMGkA3gHPTjITEDoCJSZS0ACFAgIb8CMCNRLyA1dR7ANgIuV1DWIimvKVFk JbAnBCApYP5wDeBBgB2KJnA3MCZgVYJ/UJAgoCD0NyAFoRggRuF0/R6RdAeAAjAicVCxA5EiFTJm OQFzP1oHWmEoS9kFEHNoJBAywHJRsB6w3CBLB0AKQAUQKVefKrT/Yd9i72P/ZOwdiiulLQA3VX5E IKBa0gmAH8AyAAZRcAMycDJCMDk6MzE6YDQ5ICswMjEsaiJDXw9gEyIgPGtq5C7TIGBfoi5rYARA BnFZcLVMUS4koT40jVWCWzV0fl1a/1wPXRlN2V3aM1Ii9k4IcQVAU1ChE+FsMXTjoi51RUBhdR7A bwWg3QEAc25THXA7Ejw7XW6VGSumSURZlnfTRUY0gQ4gMUI0RUJDe2BAMDQ1QkRFDiA3ADNGOUQw QTg3EEZGMDZpgEREQw4xbcAUEAdAbXcxMPw3LgngB4BswG3XFBBulcc7Axz0VcUtVHlMIC0ANQ6y LwtTOyLQE+Q9Ivh1cy1RsFRwbCAdih1Q7wewdPIddRzlSQVAAQBMIP8k8iJTFCA/EAXAPwIm4BQA 7wVAJKVTswrAazGxRkMjxpddwAtgLoFyHPRub1dA7zbQLyCGr4e+IiPGbDCJQ48/AQOgUkFBMGF2 ZVTFfzXAIuILgDcRi3IOwAWQdf8OsD7zFBAiJCIVSUUnZRzmfwSQNyBwtXcxBQNdkx5SSMAuMjQ4 LnYUQAqw/UYRNBUwgBUkxQDAH/A9oXeH9VGwVWBPjMcihQORb/+OUHFAP7IfEy7SPsBSUixVfwaQ RZGLNpcIl7YegSXwbP9WIQuAXSKZEURiPTJJUnIR7ySmmoUDoD8CVF+QAIAiFv8lQj2hj9UmUDds NcAfEAhg/mdLxIypC4AewEtAILiS4n9wgXDki1RRkI5QAyBAdmHecAtQCJA6Yj7zQZEsWSD/PxEB oJjxJeAgkX5BchEfMR8r0FEinikkTZ/FIlRSAEFOU0FDVElP/E4ikfxVgC1ACyCfVWrW+WB/Cl+x b7JcHY4tDy4Xdls48kgAOrSPLjRwQE/tA6BCLuMc9E8vIHTrMOrzAQADoDE2RUEFMETgLtDjBcAy MzEzOjdGM180b/9v33Dvcf9drcK/g9JgAVmr3R2KQTbxOfAe4Xc3II4y/R8AdzXAIhSdRMCxoFcf wBuKmBggZkwxp+JBTEz/JEYgIQ7QBCCLcpBVAiAxwPPJuD8CTlXKYCLTDsEfwP8igL+hawAIYD9x PaE/ASRG/8BumuGlRVQRihAiA6nRyuf/INE/AragDrAloV4ldUDOk1/LuSIVPaFMIQIQcgeAZP/C q7A7qWKqASTwCxHMXUtAv1HBnWEihJsYXdMfwGKQEP/RgcChqAMkRdnLPwLB6idr/9c9KLnfPwqA uT8dxlXCA2DvJWGbg0yxqkRMHqEEkODf9+YPWiQdikU48rRgj1B1AZ8t8HbM36tHsCZhKzkBwNgt My3r8H0AMRpgHYvMYXgmYOvpMjKVlRz0P0HCdsxsQEFCQZV2zC8+/+aP8q/zv7D/9p+zHyiQHzH/ ROOPgyHSJuBRkB9BoEI58P8CQIg2UhHRUiLhJuC6wSCw/ytxAMAgMQcxJ2WpYSHxkvL/VeIBADHA TFBRkCOR1gE+8/+CkD2xinR3MSswJBD60qRiuT7AZHUrcYmW/DJ0H/C/jtEigB5hPwH9xB6wZJzh /xQQJlGKZR6SEoH/41PCRdX/HzGKEVTG/gnAcZPgp7APoO8fwI3y0VKlUmIf8IoRVIH/MbEhMvmj HsAEAcZhIKMddf//oR/ACpHAwD2QkBAgwkcR/c+gcKrzBUYkoi2wpJkMQq8iICOQXjQgYG8fIGIn EJ+XQpuDlrMtsBtwd2adEO8na4phjfYHwmXR8cuS+Of3x/Gdw1F2aSTAUfFnwSOR/wlzAoHPJkVS BRGLcibAUZD/kCFHEfAh5CEh8SHhDSIFPt9g32Tn0YDN0ZUhcuVAZR/jxfLIAEhUTc1wIKAjEP+C AMEUl3GTsTTwoUAmUFdQ8V40VVJMtGBBT0JaEBDX0fBnwUOVLx7oczIjaSBBMgFjMWMzZGkgNPUj 6S7wsG35UBs/HE8dX3JB0YFuLc3CHt8f7k7+YX5Q6VHb8Y5AOQGpoFGQz+AFgPMVwHnBL2qBADDW vGl6ZxFo0OvwmcB5kCCdn1VEk6EuhWjgNC4vAPU0dVU/YCAhHyIvIz8kT/clX4DAaOAwWpAvAibP J9//KO8p/ysPLB8tLy47TNC4lZ8vpZTQaQAwXzFlMy5BB/8yjzOfNK81vzbPN9lBAfTb/2TvOt/1 j06fT6+zKFaF+SL/xnJSANhAUQq9fUTfRepSUv/H8P8gRxX07+jwi4H/4VFlLkQAgBjhnhBW5EE1 M92eEEnGMZVgvFYqWu9b/wtcMbNqfV4QAAAAHgA1EAEAAABEAAAAPEU5MTg3NzQ0QzZBN0VFNDFB REE0RTA4MzhENjQ0NTlDMDRGQjI0QEVYVlMwMS53bmcuY2hpY2Fnby5ob3N0d2F5PgAeADkQAQAA AC0AAAA8bWFpbG1hbi41LjEyMjE2NzgwMDIuMTcyNTAubWVnYWNvQGlldGYub3JnPgAAAAAeAEcQ AQAAAA8AAABtZXNzYWdlL3JmYzgyMgAACwDyEAEAAAAfAPMQAQAAAFQAAABSAEUAJQAzAEEAIABN AGUAZwBhAGMAbwAgAEQAaQBnAGUAcwB0ACwAIABWAG8AbAAgADUAMwAsACAASQBzAHMAdQBlACAA MQAxAC4ARQBNAEwAAAALAPYQAAAAAEAABzBCFKImJRnJAUAACDA30M30JRnJAQMA3j+vbwAAAwDx PwkEAAAeAPg/AQAAAAwAAABUb20gRGVja2VydAACAfk/AQAAAG0AAAAAAAAA3KdAyMBCEBq0uQgA Ky/hggEAAAAAAAAAL089V0lORE9XU05HL09VPUZJUlNUIEFETUlOSVNUUkFUSVZFIEdST1VQL0NO PVJFQ0lQSUVOVFMvQ049VERFQ0tFUlRfRkFTVFdJUkUtR1IAAAAAHgD6PwEAAAAVAAAAU3lzdGVt IEFkbWluaXN0cmF0b3IAAAAAAgH7PwEAAAAeAAAAAAAAANynQMjAQhAatLkIACsv4YIBAAAAAAAA AC4AAAADAP0/5AQAAAMAGUAAAAAAAwAaQAAAAAADAB1AAAAAAAMAHkAAAAAAHgAwQAEAAAAVAAAA VERFQ0tFUlRfRkFTVFdJUkUtR1IAAAAAHgAxQAEAAAAVAAAAVERFQ0tFUlRfRkFTVFdJUkUtR1IA AAAAHgAyQAEAAAAYAAAAbWVnYWNvLWJvdW5jZXNAaWV0Zi5vcmcAHgAzQAEAAAAYAAAAbWVnYWNv LXJlcXVlc3RAaWV0Zi5vcmcAHgA4QAEAAAAVAAAAVERFQ0tFUlRfRkFTVFdJUkUtR1IAAAAAHgA5 QAEAAAACAAAALgAAAAMAdkD/////CwApAAAAAAALACMAAAAAAAMABhBFQgA9AwAHEHcNAAADABAQ AAAAAAMAERAAAAAAHgAIEAEAAABlAAAASEksRlJPTVJFQURJTkdUSElTVEhSRUFELE1ZSU5URVJQ UkVUQVRJT05JU1RIQVRBTllBQ1RJT05XSElDSENPTlRBSU5TT05MWU9QVElPTkFMQ09NTUFORFNX SUxMQUxXQVlTUwAAAAACAX8AAQAAAEQAAAA8RTkxODc3NDRDNkE3RUU0MUFEQTRFMDgzOEQ2NDQ1 OUMwNEZCMjRARVhWUzAxLnduZy5jaGljYWdvLmhvc3R3YXk+AH1w ------_=_NextPart_001_01C91925.F4C1E466-- ------------=_1221697487-1176-1 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco ------------=_1221697487-1176-1-- From megaco-bounces@ietf.org Thu Sep 18 03:20:08 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D393D3A687F; Thu, 18 Sep 2008 03:20:08 -0700 (PDT) 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 90DCB3A686E for ; Thu, 18 Sep 2008 03:20:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 7pgIosOeEo+y for ; Thu, 18 Sep 2008 03:20:06 -0700 (PDT) Received: from zw2-smtp1.zhone.com (zw2-smtp1.zhone.com [199.190.211.5]) by core3.amsl.com (Postfix) with ESMTP id D28773A679F for ; Thu, 18 Sep 2008 03:20:06 -0700 (PDT) Received: from priority.oak.zhone.com (priority.oak.zhone.com [172.16.1.21]) by smtp.zhone.com (8.12.1/8.12.1) with ESMTP id m8IAKJDm027884 for ; Thu, 18 Sep 2008 03:20:19 -0700 (PDT) Received: from RKUPPILI.zhone.com ([192.168.127.40]) by priority.oak.zhone.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTP id <0K7D0025WZDS10B0@priority.oak.zhone.com> for megaco@ietf.org; Thu, 18 Sep 2008 03:20:19 -0700 (PDT) Content-return: prohibited Date: Thu, 18 Sep 2008 15:50:11 +0530 From: Ramesh Babu Kuppili To: megaco@ietf.org Message-id: <0K7D0025XZDS10B0@priority.oak.zhone.com> MIME-version: 1.0 X-Mailer: Sun Outlook Connector 7.2.310.1 Subject: [Megaco] Question about port numbers being used for T.38 in megaco X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1073463331==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org --===============1073463331== Content-return: prohibited Content-type: multipart/alternative; boundary="Boundary_(ID_Xw690d+ApNAlNl4a+nRb9Q)" --Boundary_(ID_Xw690d+ApNAlNl4a+nRb9Q) Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Hello, I have a quick question about the port numbers used for T.38 in megaco. Is it a must for T.38 to have it's own port number (different from one assigned for audio). Is is possible to use the same port number for audio and T.38 stream. - ramesh --Boundary_(ID_Xw690d+ApNAlNl4a+nRb9Q) Content-type: TEXT/HTML; CHARSET=US-ASCII Content-transfer-encoding: 7BIT

Hello,

I have a quick question about the port numbers used for T.38 in megaco.

Is it a must for T.38 to have it's own port number (different from one assigned for audio). Is is possible to use the same port number for audio and T.38 stream.

- ramesh

--Boundary_(ID_Xw690d+ApNAlNl4a+nRb9Q)-- --===============1073463331== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============1073463331==-- From megaco-bounces@ietf.org Thu Sep 18 06:15:27 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0117428C0D0; Thu, 18 Sep 2008 06:15:27 -0700 (PDT) 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 B96C33A6774 for ; Thu, 18 Sep 2008 06:15:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.946 X-Spam-Level: X-Spam-Status: No, score=-5.946 tagged_above=-999 required=5 tests=[AWL=0.302, BAYES_00=-2.599, HELO_EQ_SE=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 yieTnY806W4l for ; Thu, 18 Sep 2008 06:15:19 -0700 (PDT) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 5DB9C3A63C9 for ; Thu, 18 Sep 2008 06:15:19 -0700 (PDT) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 2A2F6204CA; Thu, 18 Sep 2008 15:15:30 +0200 (CEST) X-AuditID: c1b4fb3e-a9e87bb000007a96-4b-48d254722e77 Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 01383204C2; Thu, 18 Sep 2008 15:15:30 +0200 (CEST) Received: from esealmw107.eemea.ericsson.se ([153.88.200.70]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 18 Sep 2008 15:15:23 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 18 Sep 2008 15:15:22 +0200 Message-ID: In-Reply-To: <0K7D0025XZDS10B0@priority.oak.zhone.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Megaco] Question about port numbers being used for T.38 in megaco Thread-Index: AckZeCqoxiTDAQjrQcWgrXRvd4p0kwAF69cg References: <0K7D0025XZDS10B0@priority.oak.zhone.com> From: "Krishna Prasad Kalluri" To: "Ramesh Babu Kuppili" , X-OriginalArrivalTime: 18 Sep 2008 13:15:23.0069 (UTC) FILETIME=[9B71EED0:01C91990] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Megaco] Question about port numbers being used for T.38 in megaco X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0042063299==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org This is a multi-part message in MIME format. --===============0042063299== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C91990.9B81AFF6" This is a multi-part message in MIME format. ------_=_NextPart_001_01C91990.9B81AFF6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Ramesh, =20 There is no such restriction to use different port for T38. I think at least its not specified in any standards. =20 The only important thing is to modify the media path when you are sure that remote side can also support T38. =20 Regards Krishna ________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Ramesh Babu Kuppili Sent: den 18 september 2008 12:20 To: megaco@ietf.org Subject: [Megaco] Question about port numbers being used for T.38 in megaco Hello, =20 I have a quick question about the port numbers used for T.38 in megaco. =20 Is it a must for T.38 to have it's own port number (different from one assigned for audio). Is is possible to use the same port number for audio and T.38 stream. =20 - ramesh ------_=_NextPart_001_01C91990.9B81AFF6 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Ramesh,

There is no such restriction to use different = port for T38.=20 I think at least its not specified in any standards.

The only important thing is to modify the media = path when=20 you are sure that remote side can also support T38.

Regards

Krishna

From: megaco-bounces@ietf.org=20 [mailto:megaco-bounces@ietf.org] On Behalf Of Ramesh Babu=20 Kuppili
Sent: den 18 september 2008 12:20
To:=20 megaco@ietf.org
Subject: [Megaco] Question about port numbers = being=20 used for T.38 in megaco

Hello,

I have = a quick=20 question about the port numbers used for T.38 in = megaco.

Is it = a must for=20 T.38 to have it's own port number (different from one assigned for = audio). =20 Is is possible to use the same port number for audio and T.38=20 stream.

-=20 ramesh

------_=_NextPart_001_01C91990.9B81AFF6-- --===============0042063299== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============0042063299==-- From megaco-bounces@ietf.org Thu Sep 18 22:47:55 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FDBD3A68D7; Thu, 18 Sep 2008 22:47:55 -0700 (PDT) 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 5255E3A68D7 for ; Thu, 18 Sep 2008 22:47:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.298 X-Spam-Level: X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=1.300, 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 T09YV2T78E-Y for ; Thu, 18 Sep 2008 22:47:52 -0700 (PDT) Received: from zw2-smtp1.zhone.com (zw2-smtp1.zhone.com [199.190.211.5]) by core3.amsl.com (Postfix) with ESMTP id 8648E3A67B6 for ; Thu, 18 Sep 2008 22:47:52 -0700 (PDT) Received: from priority.oak.zhone.com (priority.oak.zhone.com [172.16.1.21]) by smtp.zhone.com (8.12.1/8.12.1) with ESMTP id m8J5m7Dm017196 for ; Thu, 18 Sep 2008 22:48:07 -0700 (PDT) Received: from RKUPPILI.zhone.com ([192.168.127.40]) by priority.oak.zhone.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTP id <0K7F00JN7HG44E20@priority.oak.zhone.com> for megaco@ietf.org; Thu, 18 Sep 2008 22:48:07 -0700 (PDT) Content-return: prohibited Date: Fri, 19 Sep 2008 11:18:03 +0530 From: Ramesh Babu Kuppili To: megaco@ietf.org Message-id: <0K7F00JN8HG54E20@priority.oak.zhone.com> MIME-version: 1.0 X-Mailer: Sun Outlook Connector 7.2.310.1 Cc: Murugesh Govindaraju Subject: [Megaco] Event buffer Descriptor in H.248 X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0857475489==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org --===============0857475489== Content-return: prohibited Content-type: multipart/alternative; boundary="Boundary_(ID_pFzOQjxl6YSmvZSl+j3JeQ)" --Boundary_(ID_pFzOQjxl6YSmvZSl+j3JeQ) Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Hello Megaco Gurus, In H.248, does absence of "Event Buffer Descriptor" in a message means we should use the previous received (if any) Event Buffer Descriptor. Thanks for your time. - ramesh --Boundary_(ID_pFzOQjxl6YSmvZSl+j3JeQ) Content-type: TEXT/HTML; CHARSET=US-ASCII Content-transfer-encoding: 7BIT

Hello Megaco Gurus,

In H.248, does absence of "Event Buffer Descriptor" in a message means we should use the previous received (if any) Event Buffer Descriptor.

Thanks for your time.

- ramesh

--Boundary_(ID_pFzOQjxl6YSmvZSl+j3JeQ)-- --===============0857475489== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============0857475489==-- From megaco-bounces@ietf.org Fri Sep 19 01:34:26 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 055FE3A68BA; Fri, 19 Sep 2008 01:34:26 -0700 (PDT) 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 8D4653A6939 for ; Fri, 19 Sep 2008 01:34:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.948 X-Spam-Level: X-Spam-Status: No, score=-0.948 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 0Ye7OeaK7pQg for ; Fri, 19 Sep 2008 01:34:23 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id 146F43A688C for ; Fri, 19 Sep 2008 01:34:21 -0700 (PDT) Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com [155.132.6.75]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m8J8XoxL023855; Fri, 19 Sep 2008 10:34:29 +0200 Received: from FRVELSMBS24.ad2.ad.alcatel.com ([155.132.6.52]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Fri, 19 Sep 2008 10:34:07 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 19 Sep 2008 10:37:10 +0200 Message-ID: In-Reply-To: <0K7F00JN8HG54E20@priority.oak.zhone.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Megaco] Event buffer Descriptor in H.248 Thread-Index: AckaG1CGJNacxCopT6uPiSEvYvC1VAAFsveQ References: <0K7F00JN8HG54E20@priority.oak.zhone.com> From: "CHATURVEDI PRABUDDHA" To: "Ramesh Babu Kuppili" , X-OriginalArrivalTime: 19 Sep 2008 08:34:07.0243 (UTC) FILETIME=[7B14FDB0:01C91A32] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Subject: Re: [Megaco] Event buffer Descriptor in H.248 X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2134365428==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org This is a multi-part message in MIME format. --===============2134365428== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C91A32.7A694A64" This is a multi-part message in MIME format. ------_=_NextPart_001_01C91A32.7A694A64 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I hope your scenario fits case 1 of 7.1.9 of standard doc and you seems to be right. "The MG waits for a new Events Descriptor. While waiting for a new Events Descriptor, any events detected that appear in the EventBuffer Descriptor will be placed in the EventBuffer." your event buffer control seems to be LockStep else events in buffer would have been discarded and buffereing would have no meaning. =20 =20 Best Regards. Prabuddha C ________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Ramesh Babu Kuppili Sent: Friday, September 19, 2008 11:18 AM To: megaco@ietf.org Cc: Murugesh Govindaraju Subject: [Megaco] Event buffer Descriptor in H.248 Hello Megaco Gurus, =20 In H.248, does absence of "Event Buffer Descriptor" in a message means we should use the previous received (if any) Event Buffer Descriptor. =20 Thanks for your time. =20 - ramesh ------_=_NextPart_001_01C91A32.7A694A64 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

I hope your scenario fits case 1 of 7.1.9 of = standard doc=20 and you seems to be right.

"The MG waits for a new Events Descriptor. = While waiting=20 for a new Events Descriptor, any events detected that appear in the = EventBuffer=20 Descriptor will be placed in the EventBuffer." your=20 event buffer control seems to be LockStep else events in buffer would = have been=20 discarded and buffereing would have no = meaning.

Best Regards.

Prabuddha=20 C

From: megaco-bounces@ietf.org=20 [mailto:megaco-bounces@ietf.org] On Behalf Of Ramesh Babu=20 Kuppili
Sent: Friday, September 19, 2008 11:18 = AM
To:=20 megaco@ietf.org
Cc: Murugesh Govindaraju
Subject: = [Megaco]=20 Event buffer Descriptor in H.248

Hello = Megaco=20 Gurus,

In = H.248, does=20 absence of "Event Buffer Descriptor" in a message means we should use = the=20 previous received (if any) Event Buffer Descriptor.

Thanks = for your=20 time.

-=20 ramesh

------_=_NextPart_001_01C91A32.7A694A64-- --===============2134365428== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============2134365428==-- From megaco-bounces@ietf.org Mon Sep 22 04:03:56 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBED53A6890; Mon, 22 Sep 2008 04:03:55 -0700 (PDT) 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 8279A3A6890 for ; Mon, 22 Sep 2008 04:03:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.316 X-Spam-Level: * X-Spam-Status: No, score=1.316 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, MIME_ASCII0=1.5] 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 xs7lvQS6OkcI for ; Mon, 22 Sep 2008 04:03:53 -0700 (PDT) Received: from tparelay1.telrad.com (tparelay1.telrad.com [62.90.58.240]) by core3.amsl.com (Postfix) with ESMTP id 657603A6874 for ; Mon, 22 Sep 2008 04:03:52 -0700 (PDT) Received: from tparelay1.telrad.com (localhost.localdomain [127.0.0.1]) by tparelay1.telrad.com (8.12.11.20060308/8.12.11) with ESMTP id m8MAvs7c027024 for ; Mon, 22 Sep 2008 13:57:54 +0300 Received: from TLRD-MAIL1.Telrad.co.il ([141.226.76.177]) by tparelay1.telrad.com (8.12.11.20060308/8.12.11) with SMTP id m8MAvpcI027015 for ; Mon, 22 Sep 2008 13:57:53 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 22 Sep 2008 14:04:53 +0300 Message-ID: <6FC94336B3E3F6468408F294C14A9ECB02121C3D@TLRD-MAIL1.Telrad.co.il> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Subtract all calls Thread-Index: AckcownoHjVVYCBZTZ6wb/A5CQsXow== From: "Tamar Nemet" To: Subject: [Megaco] Subtract all calls X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1902766596==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org This is a multi-part message in MIME format. --===============1902766596== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C91CA3.0A10D9C8" This is a multi-part message in MIME format. ------_=_NextPart_001_01C91CA3.0A10D9C8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 When MG get the following message for MGC: =20 !/1 [10.100.4.28]:2944 T=3D95{C=3D*{O-W-S=3D*{AT{}}}} =20 What it should do ? I understand that it should subtract all calls, but what it should put in the reply ? all the termination that had been subtracted ? And if it has 2000 calls , how it can be sent in one reply ? =20 Thanks for your help, Tamar ------_=_NextPart_001_01C91CA3.0A10D9C8 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

Hi,

When = MG get the=20 following message for MGC:

!/1 [10.100.4.28]:2944=20 T=3D95{C=3D*{O-W-S=3D*{AT{}}}}

What = it should do ?=20 I understand that it should subtract all calls, but what it should put = in the=20 reply ? all the termination that had been subtracted ? And if it has = 2000 calls=20 , how it can be sent in one reply ?

Thanks = for your=20 help,

Tamar

=00 ------_=_NextPart_001_01C91CA3.0A10D9C8-- --===============1902766596== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============1902766596==-- From megaco-bounces@ietf.org Mon Sep 22 04:58:51 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25FAF28C0E1; Mon, 22 Sep 2008 04:58:51 -0700 (PDT) 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 8206D28C0E1 for ; Mon, 22 Sep 2008 04:58:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6] 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 OrsONMVUlbio for ; Mon, 22 Sep 2008 04:58:46 -0700 (PDT) Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by core3.amsl.com (Postfix) with ESMTP id 84CE128C0DE for ; Mon, 22 Sep 2008 04:58:44 -0700 (PDT) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by jaguar.aricent.com (8.13.8/8.13.8) with ESMTP id m8MBsVBW001118 for ; Mon, 22 Sep 2008 17:24:31 +0530 Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (8.13.8/8.13.8) with ESMTP id m8MBsUvZ001083 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Mon, 22 Sep 2008 17:24:30 +0530 Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.130]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Mon, 22 Sep 2008 17:28:01 +0530 From: Deepak Bissa To: Tamar Nemet , "megaco@ietf.org" Date: Mon, 22 Sep 2008 17:27:59 +0530 Thread-Topic: Subtract all calls Thread-Index: AckcownoHjVVYCBZTZ6wb/A5CQsXowAB0Bcw Message-ID: <31F873353B13F2419C80FD0833E118951E83717718@GUREXMB01.ASIAN.AD.ARICENT.COM> References: <6FC94336B3E3F6468408F294C14A9ECB02121C3D@TLRD-MAIL1.Telrad.co.il> In-Reply-To: <6FC94336B3E3F6468408F294C14A9ECB02121C3D@TLRD-MAIL1.Telrad.co.il> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Megaco] Subtract all calls X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1072528095==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org --===============1072528095== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_31F873353B13F2419C80FD0833E118951E83717718GUREXMB01ASIA_" --_000_31F873353B13F2419C80FD0833E118951E83717718GUREXMB01ASIA_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, This is an optional wildcarded subtract command and MGC is not interested i= n knowing the termination ids in response. If there are contexts present then MG should return !/1 [10.100.4.28]:2944 T=3D95{C=3D*{S=3D*}} Else it should return with error descriptor !/1 [10.100.4.28]:2944 T=3D95{ER=3D411{}} Please refer to mail with subject "cleaning up of contexts" dated 31/05/200= 2 With regards, Deepak Bissa Extn 5106 ________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= Tamar Nemet Sent: Monday, September 22, 2008 4:35 PM To: megaco@ietf.org Subject: [Megaco] Subtract all calls Hi, When MG get the following message for MGC: !/1 [10.100.4.28]:2944 T=3D95{C=3D*{O-W-S=3D*{AT{}}}} What it should do ? I understand that it should subtract all calls, but wha= t it should put in the reply ? all the termination that had been subtracted= ? And if it has 2000 calls , how it can be sent in one reply ? Thanks for your help, Tamar ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely = for the use of the individual to whom it is addressed. It may contain privi= leged or confidential information and should not be circulated or used for = any purpose other than for what it is intended. If you have received this m= essage in error,please notify the originator immediately. If you are not th= e intended recipient, you are notified that you are strictly prohibited fro= m using, copying, altering, or disclosing the contents of this message. Ari= cent accepts no responsibility for loss or damage arising from the use of t= he information transmitted by this email including damage from virus." --_000_31F873353B13F2419C80FD0833E118951E83717718GUREXMB01ASIA_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message

Hello,

This is an optional wildcarded subtract command and MGC = is not interested in knowing the termination ids in response.

If there are contexts present then MG = should return

!/1 [10.100.4.28]:2944 T=3D95{C=3D*{S=3D*}}

Else it should return with error descr= iptor

!/1 [10.100.4.28]:2944 T=3D95{ER=3D411{}}

Please refer to mail with subject R= 20;cleaning up of contexts” dated 31/05/2002=

With regards,

Deepak Bissa

Extn 5106

From: mega= co-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Tamar Nemet
Sent: Monday, September 22, = 2008 4:35 PM
To: megaco@ietf.org
Subject: [Megaco] Subtract a= ll calls

Hi,

When MG get the following message for MGC:=

!/1 [10.100.4.28]:2944 T=3D95{C=3D*{O-W-S=3D*{AT{}}}}

What it should do ? I understand that it should subtract= all calls, but what it should put in the reply ? all the termination that = had been subtracted ? And if it has 2000 calls , how it can be sent in one reply ?

Thanks for your help,

Tamar

Thanks=20 for your reply

-----Original Message-----
From: = Deepak Bissa=20 [mailto:deepak.bissa@aricent.com]
Sent: Monday, September = 22, 2008=20 2:58 PM
To: Tamar Nemet; megaco@ietf.org
Subject: = RE:=20 Subtract all calls

Hello,

This is an optional = wildcarded=20 subtract command and MGC is not interested in knowing the termination = ids in=20 response.

If there = are contexts=20 present then MG should return

!/1 [10.100.4.28]:2944=20 T=3D95{C=3D*{S=3D*}}

Else it = should return=20 with error descriptor

!/1 [10.100.4.28]:2944=20 T=3D95{ER=3D411{}}

Please = refer to mail=20 with subject “cleaning up of contexts” dated=20 31/05/2002

With=20 regards,

Deepak=20 Bissa

Extn=20 5106

From:=20 megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Tamar = Nemet
Sent: Monday, September 22, = 2008 4:35=20 PM
To:=20 megaco@ietf.org
Subject:=20 [Megaco] Subtract all calls

Hi,

When MG get the = following message=20 for MGC:

!/1 [10.100.4.28]:2944=20 T=3D95{C=3D*{O-W-S=3D*{AT{}}}}

What it should do ? I = understand=20 that it should subtract all calls, but what it should put in the reply = ? all=20 the termination that had been subtracted ? And if it has 2000 calls , = how it=20 can be sent in one reply ?

Thanks for your=20 help,

Tamar

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

=00 ------_=_NextPart_001_01C91CAF.657DEA34-- --===============2029367770== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============2029367770==-- From megaco-bounces@ietf.org Sun Sep 28 09:55:18 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D08083A6767; Sun, 28 Sep 2008 09:55:18 -0700 (PDT) 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 7E0CE3A6767 for ; Sun, 28 Sep 2008 09:55:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.184 X-Spam-Level: X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 XQfCY3A8vKSJ for ; Sun, 28 Sep 2008 09:55:16 -0700 (PDT) Received: from zw2-smtp1.zhone.com (zw2-smtp1.zhone.com [199.190.211.5]) by core3.amsl.com (Postfix) with ESMTP id BCB8F3A6403 for ; Sun, 28 Sep 2008 09:55:16 -0700 (PDT) Received: from priority.oak.zhone.com (priority.oak.zhone.com [172.16.1.21]) by smtp.zhone.com (8.12.1/8.12.1) with ESMTP id m8SGt3Dm009900 for ; Sun, 28 Sep 2008 09:55:03 -0700 (PDT) Received: from RKUPPILI.zhone.com ([172.16.15.101]) by priority.oak.zhone.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTP id <0K7X0069X0BOLC40@priority.oak.zhone.com> for megaco@ietf.org; Sun, 28 Sep 2008 09:55:02 -0700 (PDT) Content-return: prohibited Date: Sun, 28 Sep 2008 22:24:58 +0530 From: Ramesh Babu Kuppili To: megaco@ietf.org Message-id: <0K7X0069Z0BPLC40@priority.oak.zhone.com> MIME-version: 1.0 X-Mailer: Sun Outlook Connector 7.2.310.1 Subject: [Megaco] Megaco question about interpretation of dot in a digitmap X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1625454772==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org --===============1625454772== Content-return: prohibited Content-type: multipart/alternative; boundary="Boundary_(ID_ATwTz1tlk1IM2P3PSqK5Kg)" --Boundary_(ID_ATwTz1tlk1IM2P3PSqK5Kg) Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Hello, Megaco question about interpretation of dot in a digitmap. According the spec, the definition of "dot" is as follows: "Finally, the dot symbol "." stands for zero or more repetitions of the event selector (event, range of events, set of alternative events, or wildcard) that precedes it." What does "zero of more repetitions of the event selector that precedes it" mean. For example, if the digitmap is x., does it mean x + zero of more repetitions of x or does it mean just zero or more repetitions of x. As another example, lets say the digitmap i receive have a digitmap: "1x." and if the dialed digits as "123". What should be the timers started: (case 1) 1 - Long timer 2 - Long timer 3 - Short timer (this is x + zero or more repetitions of x) or (case 2) 1 - Long timer 2 - Short timer 3 - Short timer (this is zero or more repetitions of x) Thanks a lot for your time. - ramesh --Boundary_(ID_ATwTz1tlk1IM2P3PSqK5Kg) Content-type: TEXT/HTML; CHARSET=US-ASCII Content-transfer-encoding: 7BIT

Hello,

Megaco question about interpretation of dot in a digitmap.

According the spec, the definition of "dot" is as follows:
"Finally, the dot symbol "." stands for zero or more repetitions of the event selector (event, range of events, set of alternative events, or wildcard) that precedes it."

What does "zero of more repetitions of the event selector that precedes it" mean.

For example, if the digitmap is x., does it mean x + zero of more repetitions of x or does it mean just zero or more repetitions of x.

As another example, lets say the digitmap i receive have a digitmap: "1x." and if the dialed digits as "123". What should be the timers started:

(case 1)
1 - Long timer
2 - Long timer
3 - Short timer
(this is x + zero or more repetitions of x)

or (case 2)
1 - Long timer
2 - Short timer
3 - Short timer
(this is zero or more repetitions of x)

Thanks a lot for your time.

- ramesh

--Boundary_(ID_ATwTz1tlk1IM2P3PSqK5Kg)-- --===============1625454772== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============1625454772==-- From megaco-bounces@ietf.org Sun Sep 28 10:12:25 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 857B128C0F5; Sun, 28 Sep 2008 10:12:25 -0700 (PDT) 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 3224928C0E1 for ; Sun, 28 Sep 2008 10:12:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.184 X-Spam-Level: X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 t40EwoskazmS for ; Sun, 28 Sep 2008 10:12:23 -0700 (PDT) Received: from mail.teledata-networks.com (mail.teledata-networks.com [194.90.152.129]) by core3.amsl.com (Postfix) with SMTP id 41C2328C0EF for ; Sun, 28 Sep 2008 10:12:22 -0700 (PDT) Received: from tndcmail.Teledata.Local ([10.1.100.59]) by eSafe SMTP Relay 1221048363; Sun, 28 Sep 2008 20:09:59 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 28 Sep 2008 20:13:46 +0300 Message-ID: In-Reply-To: <0K7X0069Z0BPLC40@priority.oak.zhone.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Megaco] Megaco question about interpretation of dot in a digitmap thread-index: Ackhiy1arGdxIIQbTjuC/1VYonX3+gAAi5Zw From: "Raphael Tryster" To: "Ramesh Babu Kuppili" , X-ESAFE-STATUS: Mail clean X-ESAFE-DETAILS: Subject: Re: [Megaco] Megaco question about interpretation of dot in a digitmap X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0924590718==" Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org This is a multi-part message in MIME format. --===============0924590718== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9218D.8A873FE0" This is a multi-part message in MIME format. ------_=_NextPart_001_01C9218D.8A873FE0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Kevin Boyle answered this last year as copied below. However, I suspect not all deployed implementations comply. =20 Raphael =20 The key word here in H.248 is "repetitions". The map you provide as an example asks for "0800" followed by one or more digits between 0 and 9. That is, "08005" matches as does "08005678", but "0800" does NOT match. Kevin ________________________________ From: Bill Xiaoshaoping [mailto:xiaoshaoping@huawei.com ] Sent: Wednesday, May 16, 2007 5:02 AM To: megaco@ietf.org Subject: [Megaco] DOT in H.248 Digit map syntax =20 =20 Hello all, Given a digit plan of "0800x.", which is the real intention of the following two: 1. matching with the dialed digits starting with 0800 followed by at least 1 digit and possible more digits 2. matching with the dialed digits starting with 0800 followed by ZERO digit or more Section 7.1.14.3 DigitMap syntax/H248 v3: =2E....Finally, the dot symbol "." stands for zero or more repetitions of the event selector (event, range of events, set of alternative events, or wildcard) that precedes it.=20 Explanation in MGCP is:=20 * Position: A period (".") which matches an arbitrary number, including zero, of occurrences of the preceding construct. Does the zero repetiton in H.248 means no occurence of the previous element as in MGCP? The digit map syntaxs of both are almost the same. Any help on this appreciated. Thanks ________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Ramesh Babu Kuppili Sent: Sunday, September 28, 2008 7:55 PM To: megaco@ietf.org Subject: [Megaco] Megaco question about interpretation of dot in a digitmap Hello,=20 Megaco question about interpretation of dot in a digitmap.=20 According the spec, the definition of "dot" is as follows:=20 "Finally, the dot symbol "." stands for zero or more repetitions of the event selector (event, range of events, set of alternative events, or wildcard) that precedes it."=20 What does "zero of more repetitions of the event selector that precedes it" mean.=20 For example, if the digitmap is x., does it mean x + zero of more repetitions of x or does it mean just zero or more repetitions of x.=20 As another example, lets say the digitmap i receive have a digitmap: "1x." and if the dialed digits as "123". What should be the timers started:=20 (case 1)=20 1 - Long timer=20 2 - Long timer=20 3 - Short timer=20 (this is x + zero or more repetitions of x)=20 or (case 2)=20 1 - Long timer=20 2 - Short timer=20 3 - Short timer=20 (this is zero or more repetitions of x)=20 Thanks a lot for your time.=20 - ramesh=20 *************************************************************************= ********************* IMPORTANT: The contents of this email and any attachments are confidentia= l. They are intended for the=20 named recipient(s) only. If you have received this email in error, please notify the system manage= r or the sender immediately and do=20 not disclose the contents to anyone or make copies thereof. *** eSafe scanned this email for viruses, vandals, and malicious content.= *** *************************************************************************= ********************* ------_=_NextPart_001_01C9218D.8A873FE0 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Kevin=20 Boyle answered this last year as copied below. However, I suspect n= ot all=20 deployed implementations comply.

Raphael

The key word here in H.248 is "repetitions". The map you provide as an= =20 example asks for "0800" followed by one or more digits between 0 and 9.

That is, "08005" matches as does "08005678", but "0800" does NOT match= =2E

Kevin

________________________________

From: Bill Xiaoshaoping [mailto:xiaoshaoping@huawei.com]

Sent: Wednesday, May 16, 2007 5:02 AM

To: megaco@ietf.org

Subject: [Megaco] DOT in H.248 Digit map syntax

Hello all,

Given a digit plan of "0800x.", which is the real intention of the

following two:

1. matching with the dialed digits starting with 0800 followed by at

least 1 digit and possible more digits

2. matching with the dialed digits starting with 0800 followed by ZERO=

digit or more

Section 7.1.14.3 DigitMap syntax/H248 v3:

.....Finally, the dot symbol "." stands for zero or more repetitions o= f

the event selector (event, range of events, set of alternative events,=

or wildcard) that precedes it.

Explanation in MGCP is:

* Position: A period (".") which matches an arbitrary number,

including zero, of occurrences of the preceding

construct.

Does the zero repetiton in H.248 means no occurence of the previous

element as in MGCP? The digit map syntaxs of both are almost the same.=

Any help on this appreciated.

Thanks

From: megaco-bounces@ietf.org=20 [mailto:megaco-bounces@ietf.org] On Behalf Of Ramesh Babu=20 Kuppili
Sent: Sunday, September 28, 2008 7:55 PM
To:=20 megaco@ietf.org
Subject: [Megaco] Megaco question about interpr= etation=20 of dot in a digitmap

<= SPAN=20 class=3Dli-threaded id=3Dli3>Hello,
Megaco question about interpretation of= dot in a=20 digitmap.

According the spec, the definition of "dot" is as follo= ws:=20
"Finally, the dot symbol "." stands for zero or more repetitions of t= he=20 event selector (event, range of events, set of alternative events, or wil= dcard)=20 that precedes it."

What does "zero of more repetitions of the eve= nt=20 selector that precedes it" mean.

For example, if the digitmap is = x.,=20 does it mean x + zero of more repetitions of x or does it mean just zero = or more=20 repetitions of x.

As another example, lets say the digitmap i rec= eive=20 have a digitmap: "1x." and if the dialed digits as "123". What shou= ld be=20 the timers started:

(case 1)
1 - Long timer
2 - Long time= r
3=20 - Short timer
(this is x + zero or more repetitions of x)

or = (case=20 2)
1 - Long timer
2 - Short timer
3 - Short timer
(this i= s zero=20 or more repetitions of x)

Thanks a lot for your time.

- r= amesh=20

------_=_NextPart_001_01C9218D.8A873FE0-- --===============0924590718== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco --===============0924590718==-- From megaco-bounces@ietf.org Sun Sep 28 10:50:15 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10DB53A6AB7; Sun, 28 Sep 2008 10:50:15 -0700 (PDT) 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 2284F3A68D7 for ; Sun, 28 Sep 2008 10:50:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.185 X-Spam-Level: X-Spam-Status: No, score=-1.185 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_40=-0.185, GB_I_LETTER=-2] 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 BoSyDiEDU+r2 for ; Sun, 28 Sep 2008 10:50:12 -0700 (PDT) Received: from mail.teledata-networks.com (mail.teledata-networks.com [194.90.152.129]) by core3.amsl.com (Postfix) with SMTP id A015A3A6B08 for ; Sun, 28 Sep 2008 10:50:11 -0700 (PDT) Received: from tndcmail.Teledata.Local ([10.1.100.59]) by eSafe SMTP Relay 1221048363; Sun, 28 Sep 2008 20:47:44 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 28 Sep 2008 20:51:32 +0300 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: terminationId syntax and semantics thread-index: AcEjoM9ZwOqSK48qEdW4jAAIxyQt74/73DNw From: "Raphael Tryster" To: "megaco ietf" X-ESAFE-STATUS: Mail clean X-ESAFE-DETAILS: Subject: [Megaco] terminationId syntax and semantics X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org I think it is a safe bet that George W. Bush has spent almost his entire presidency not understanding the rules by which which Megaco termination identifiers are constructed. I have been aware of the existence of Megaco for about the same period, and don't understand them either. TerminationID = "ROOT" / pathNAME / "$" / "*" ; Total length of pathNAME must not exceed 64 chars. pathNAME = ["*"] NAME *("/" / "*"/ ALPHA / DIGIT /"_" / "$" ) ["@" pathDomainName ] ; ABNF allows two or more consecutive "." although it is meaningless in a path domain name. pathDomainName = (ALPHA / DIGIT / "*" ) *63(ALPHA / DIGIT / "-" / "*" / ".") NAME = ALPHA *63(ALPHA / DIGIT / "_" ) I have been happily building Megaco termination ids of the form term1/term2/term3, like in MGCP, and hoping the above defintions would go away. Now, 3 of the possibilities for TerminationID are simple. pathNAME is the tricky one. What would it mean if it starts with a "*"? Wildcarded first term? But since NAME has to start with a letter, "*/5" would be illegal, so "*" would have to be a prefix of the first term, not the whole first term. Then, once we have seen something like *A/5", we could then follow it with something ridiculous, like "*A/5$$$_abcd////". Why is it important that the first term start with a letter and not a digit? Why doesn't it matter for the other terms? When should a terminationID include a pathDomainName and when not? When would one want to pepper a pathDomainName with "*"s? What I am really looking for is to understand the reasoning that led to defining the syntax as above. What things was it designed to allow and what was important to forbid? Is there semantic meaning to the "/" characters to delineate terms as units of wildcarding like in MGCP, or is the stack expected to do the most general regular expression processing with whatever legal string it gets, and the "/" has no special meaning? What abou the other special characters like "$". Can they be delimiters? And so on. I would be really grateful if someone can help me understand this before I am older than either the president or the vice president of the U.S.A. Raphael Tryster ********************************************************************************************** IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email in error, please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies thereof. *** eSafe scanned this email for viruses, vandals, and malicious content. *** ********************************************************************************************** _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco From megaco-bounces@ietf.org Tue Sep 30 02:49:28 2008 Return-Path: X-Original-To: megaco-archive@megatron.ietf.org Delivered-To: ietfarch-megaco-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AA833A6AF9; Tue, 30 Sep 2008 02:49:28 -0700 (PDT) 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 C58903A6AF9 for ; Tue, 30 Sep 2008 02:49:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.76 X-Spam-Level: X-Spam-Status: No, score=-2.76 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, GB_I_LETTER=-2, 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 aoedXnsXYOdm for ; Tue, 30 Sep 2008 02:49:26 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id 7857C3A6AE3 for ; Tue, 30 Sep 2008 02:49:25 -0700 (PDT) Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com [155.132.6.76]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m8U9nITu014269; Tue, 30 Sep 2008 11:49:23 +0200 Received: from FRVELSMBS23.ad2.ad.alcatel.com ([155.132.6.54]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 30 Sep 2008 11:49:22 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 30 Sep 2008 11:49:21 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Megaco] terminationId syntax and semantics Thread-Index: AcEjoM9ZwOqSK48qEdW4jAAIxyQt74/73DNwAFQ890A= References: From: "Schwarz Albrecht" To: "Raphael Tryster" , "megaco ietf" X-OriginalArrivalTime: 30 Sep 2008 09:49:22.0337 (UTC) FILETIME=[D0D4E910:01C922E1] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Subject: Re: [Megaco] terminationId syntax and semantics X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: megaco-bounces@ietf.org Errors-To: megaco-bounces@ietf.org I don't know the rationale behind that ABNF grammar (because I wasn't involved in H.248 version 1). Anyway, the profile concept is a perfect means to address such kind of things (e.g. flexible syntax vs explicit semantic or not formal enough ABNF) IMHO. You may use the termination naming conventions in a profile to fix that issue. I'm not aware of any problems with profiled-defined termination names. Of course, may email is not answering your questions. [But I'm also not aware of any MG implementation, operating in the NoProfile mode, and using an identity management function which tries to generate unambiguous TerminationIDs solely on the basis of the Annex B ABNF grammar rules.] > -----Original Message----- > From: megaco-bounces@ietf.org > [mailto:megaco-bounces@ietf.org] On Behalf Of Raphael Tryster > Sent: Sonntag, 28. September 2008 19:52 > To: megaco ietf > Subject: [Megaco] terminationId syntax and semantics > > I think it is a safe bet that George W. Bush has spent almost > his entire presidency not understanding the rules by which > which Megaco termination identifiers are constructed. I have > been aware of the existence of Megaco for about the same > period, and don't understand them either. > > TerminationID = "ROOT" / pathNAME / "$" / "*" > > ; Total length of pathNAME must not exceed 64 chars. > pathNAME = ["*"] NAME *("/" / "*"/ ALPHA / DIGIT /"_" / "$" ) ["@" > pathDomainName ] > > ; ABNF allows two or more consecutive "." although it is > meaningless in a path domain name. > pathDomainName = (ALPHA / DIGIT / "*" ) *63(ALPHA / DIGIT / > "-" / "*" / > ".") > > NAME = ALPHA *63(ALPHA / DIGIT / "_" ) > > I have been happily building Megaco termination ids of the > form term1/term2/term3, like in MGCP, and hoping the above > defintions would go away. > > Now, 3 of the possibilities for TerminationID are simple. > pathNAME is the tricky one. What would it mean if it starts > with a "*"? Wildcarded first term? But since NAME has to > start with a letter, "*/5" would be illegal, so "*" would > have to be a prefix of the first term, not the whole first > term. Then, once we have seen something like *A/5", we could > then follow it with something ridiculous, like "*A/5$$$_abcd////". > Why is it important that the first term start with a letter > and not a digit? Why doesn't it matter for the other terms? > > When should a terminationID include a pathDomainName and when > not? When would one want to pepper a pathDomainName with "*"s? > > What I am really looking for is to understand the reasoning > that led to defining the syntax as above. What things was it > designed to allow and what was important to forbid? Is there > semantic meaning to the "/" > characters to delineate terms as units of wildcarding like in > MGCP, or is the stack expected to do the most general regular > expression processing with whatever legal string it gets, and > the "/" has no special meaning? What abou the other special > characters like "$". Can they be delimiters? And so on. > > I would be really grateful if someone can help me understand > this before I am older than either the president or the vice > president of the U.S.A. > > Raphael Tryster > ************************************************************** > ******************************** > IMPORTANT: The contents of this email and any attachments are > confidential. They are intended for the named recipient(s) only. > If you have received this email in error, please notify the > system manager or the sender immediately and do not disclose > the contents to anyone or make copies thereof. > *** eSafe scanned this email for viruses, vandals, and > malicious content. *** > ************************************************************** > ******************************** > > _______________________________________________ > Megaco mailing list > Megaco@ietf.org > https://www.ietf.org/mailman/listinfo/megaco > _______________________________________________ Megaco mailing list Megaco@ietf.org https://www.ietf.org/mailman/listinfo/megaco