From sip-admin@ietf.org  Tue Jul  1 09:13:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21326
	for <megaco-archive@lists.ietf.org>; Tue, 1 Jul 2003 09:13:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19XKwQ-000544-Kh
	for megaco-archive@lists.ietf.org; Tue, 01 Jul 2003 09:13:02 -0400
Date: Tue, 01 Jul 2003 09:13:02 -0400
Message-ID: <20030701131302.18162.43953.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: megaco-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, megaco-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for megaco-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
megaco@ietf.org                          rFKd      
https://www1.ietf.org/mailman/options/megaco/megaco-archive%40lists.ietf.org


From exim@www1.ietf.org  Tue Jul  1 13:48:18 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08436
	for <megaco-archive@odin.ietf.org>; Tue, 1 Jul 2003 13:48:18 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RIXex05366
	for megaco-archive@odin.ietf.org; Fri, 27 Jun 2003 14:33:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vy2W-0001OT-PX
	for megaco-web-archive@optimus.ietf.org; Fri, 27 Jun 2003 14:33:40 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10894
	for <megaco-web-archive@ietf.org>; Fri, 27 Jun 2003 14:33:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vy21-00015P-A7; Fri, 27 Jun 2003 14:33:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VvVM-0006FZ-Hk
	for megaco@optimus.ietf.org; Fri, 27 Jun 2003 11:51:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05101
	for <megaco@ietf.org>; Fri, 27 Jun 2003 11:50:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19VvV6-000448-00
	for megaco@ietf.org; Fri, 27 Jun 2003 11:51:00 -0400
Received: from [4.19.224.196] (helo=wench.telica.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19VvUq-00043V-00
	for megaco@ietf.org; Fri, 27 Jun 2003 11:50:44 -0400
Received: by wench.telica.com with Internet Mail Service (5.5.2653.19)
	id <NT6JF9NJ>; Fri, 27 Jun 2003 11:49:40 -0400
Message-ID: <C9AFC8E904D49C4593EB077A2E8402BA731AB9@wench.telica.com>
From: Bob Braisted <bbraisted@telica.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Fri, 27 Jun 2003 11:49:34 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Z duration modifier and Timer overrides
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>



i have 2 questions.

1. i see that in previous versions of h248v2 that the Z duration modifier
was called out in Annex B of the protocol (see below)

http://www1.ietf.org/internet-drafts/draft-ietf-megaco-h248v2-04.txt

     digitMapName        = NAME 
      digitMapValue       = ["T" COLON Timer COMMA] ["S" COLON Timer COMMA] 
                                     ["L" COLON Timer COMMA] ["Z" COLON
Timer COMMA] 
                                    digitMap  
      Timer               = 1*2DIGIT 
      ; Units are seconds for T, S, and L timers, and hundreds of  
      ; milliseconds for Z timer. Thus T, S, and L range from 1 to 99 
      ; seconds and Z from 100 ms to 9.9 s 

was this unintentionally omitted from the RFC 3525?
and if not, how would one override the provisioned value of the Z duration
modifier on a per call basis?

2. with respect to timer overrides, again referencing h248v2, i notice that
previously,  the letter "T" was a valid digitMapLetter, (used to specify
start timer override), and the latest version does not include "T" in the
digitMapLetter expression. Was this also intentionally removed? and if so,
can we assume that overriding the start digit timer would consist of
specifying   ["T" COLON Timer COMMA] in the digit map descriptor and not
within the digit map string itself.?

the older version has ...

     digitMapLetter    = DIGIT                              ;Basic event
symbols 
                  / %x41-4B / %x61-6B                     ; a-k, A-K 
                  / "L" / "S" / "T"
;Inter-event timers (long, short, start) 
                  / "Z"                                              ;Long
duration modifier 
      
the latest version removes the "T" .


Robert M. Braisted                     Tel:   508-804-8182
Telica, Inc                                  Fax: 508-460-0698 
734 Forest Street                       email:bbraisted@telica.com
Building G, Suite 500                                 
Marlboro, MA 01752
<http://www.telica.com/>



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



From exim@www1.ietf.org  Tue Jul  1 13:49:13 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09096
	for <megaco-archive@odin.ietf.org>; Tue, 1 Jul 2003 13:49:12 -0400 (EDT)
Received: (from exim@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h5RITPn32757
	for megaco-archive@odin.ietf.org; Fri, 27 Jun 2003 14:29:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vxy5-0008Tw-8U
	for megaco-web-archive@optimus.ietf.org; Fri, 27 Jun 2003 14:29:05 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10264
	for <megaco-web-archive@ietf.org>; Fri, 27 Jun 2003 14:28:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19VxxA-0007qQ-AI; Fri, 27 Jun 2003 14:28:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19Vubq-0002P9-H5
	for megaco@optimus.ietf.org; Fri, 27 Jun 2003 10:54:39 -0400
Received: from ish7.ericsson.com.au (ish7.ericsson.com.au [61.88.9.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20340
	for <megaco@ietf.org>; Fri, 27 Jun 2003 04:11:31 -0400 (EDT)
Received: from brsf10.epa.ericsson.se ([146.11.31.193])
	by ish7.ericsson.com.au (8.11.7+Sun/8.11.7) with ESMTP id h5N62Rk06597;
	Mon, 23 Jun 2003 16:02:27 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsf10.epa.ericsson.se (8.11.7+Sun/8.11.6) with ESMTP id h5N64sP18186;
	Mon, 23 Jun 2003 16:04:54 +1000 (EST)
Received: from ericsson.com.au (E0050DA878EDF [146.11.236.91]) by eaubrnt019.epa.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id LZBXWHBF; Mon, 23 Jun 2003 16:04:10 +1000
Message-ID: <3EF679AA.8070702@ericsson.com.au>
Date: Mon, 23 Jun 2003 13:53:14 +1000
From: Christian Groves <Christian.Groves@ericsson.com.au>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Aleksandr Ryabin <kengr@winphoria.com>
CC: megaco@ietf.org, Kevin Boyle <kboyle@nortelnetworks.com>,
        micael.karlberg@ericsson.com
Subject: Re: [Megaco] v2 mismatch ABNF & ASN.1 IndAudmediaParm?
References: <5.2.1.1.0.20030617201948.02d0c8a0@imap.winphoria.com> <5.2.1.1.0.20030618091318.02d8bb08@imap.winphoria.com> <5.2.1.1.0.20030620102508.02de9e50@imap.winphoria.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA20341
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hello Aleksandr,

See below.

Christian

Aleksandr Ryabin wrote:
> Hi Christian,
>=20
> I'm not sure on your usage of "whole" and "individual".
> They are complimentary: each SDP is "individual" and it is a "whole".
> I said "whole" SDP, not "whole" MediaDescriptor.
[CHG] Well no use arguing about personal interpretations maybe its the=20
difference between US english, International english and Australian engli=
sh :).

>=20
> What I'm trying to understand is:
> How can MGC do an audit to get *only* whole local (or remote) SDP and=20
> nothing else?
[CHG] No

> My understanding current ABNF syntax does not allow it.
> Do we agree on this?
[CHG] Yes

>=20
> If yes, is it useful to have such a functionality? I think yes.
> Do we agree on this?
[CHG] I don't oppose adding this if its wanted.

>=20
> If yes, does my proposal below solves the request? I think yes.
> Do we agree on this?
[CHG] Yes

>=20
> If yes, how do we go about adding it into IG/or next version?
> Opinions?
[CHG] Next version would enable the syntax change to be identified. Witho=
ut=20
breaking things.


>=20
> Thanks
>         Aleks
>=20
> At 10:22 PM 6/18/2003, Christian Groves wrote:
>=20
>> Hello Aleksandr,
>>
>> You said "whole" local or remote descriptor MediaToken allows that. It=
=20
>> does not
>> allow "individual" local and remote descriptors.
>>
>> Regards, Christian
>>
>> Aleksandr Ryabin wrote:
>> >
>> > Hi Christian,
>> >
>> > Could you please clarify on how would MGC audit individual local, or
>> > remote SDP with v1? I mean, local and remote SDPs are part of
>> > larger MediaDescriptor and the ABNF construction of auditItem
>> > only allows auditing the whole MediaDescriptor, not parts of it:
>> >
>> >        ;at-most-once, and DigitMapToken and PackagesToken are not=20
>> allowed
>> >        ;in AuditCapabilities command
>> >        auditItem            =3D ( MuxToken / ModemToken / MediaToken=
 /
>> >                                SignalsToken / EventBufferToken /
>> >                                DigitMapToken / StatsToken /=20
>> EventsToken /
>> >                                ObservedEventsToken / PackagesToken )
>> >
>> > So, if I understand it correctly, MGC can only audit the whole
>> > MediaDescriptor, not individual local, or remote SDP.
>> >
>> > Regards,
>> >          Aleks
>> >
>> > At 11:59 PM 6/17/2003, Christian Groves wrote:
>> > >Hello Aleksandr,
>> > >
>> > >Megaco does allow you to audit a whole local or remote descriptor.=20
>> This is the
>> > >audit capability v1. Individual auditing was added in v2. We didn't=
=20
>> add
>> > >individual audit of a whole descriptor as this would duplicate=20
>> functionality.
>> > >
>> > >It was decided not to allow auditing of individual segments of=20
>> local and
>> > >remote
>> > >SDP (text encoding) because no body could come up with an appropria=
te
>> > >method to
>> > >do this and didn't know what the reply looked like. For the binary=20
>> encoding it
>> > >was very easy because all parameters follow a tag length value=20
>> structure. You
>> > >request the tag and you get back the value.
>> > >
>> > >Christian
>> > >
>> > >Aleksandr Ryabin wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > While we are on topic. The following does not allow auditing for=
=20
>> the whole
>> > > > local or remote SDP in ABNF:
>> > > >          ; at-most-once
>> > > >          indAudstreamParm =3D ( indAudlocalControlDescriptor )
>> > > >          ; SDP too complex to pull out individual pieces for aud=
it,
>> > > >          ; hence no individual audit for Local and Remote
>> > > >
>> > > > The question is why? I mean why does not it allow to audit *whol=
e*
>> > > > local or remote SDP? E.g.:
>> > > >          indAudstreamParm =3D ( indAudlocalControlDescriptor /=20
>> LocalToken /
>> > > > RemoteToken)
>> > > >
>> > > > BTW ASN.1 does allow that, as well as individual pieces of SDPs.
>> > > >
>> > > > Thanks
>> > > >          Aleks
>> > > >
>> > > > PS. Small nit in indAudauditReturnParameter (two slashes at the=20
>> end):
>> > > >        indAudauditReturnParameter =3D (indAudmediaDescriptor / /
>> > > >
>> > > > At 03:30 PM 6/17/2003, Kevin Boyle wrote:
>> > > > >Aha... I see the problem now.  In binary, you can request info=20
>> about
>> > > several
>> > > > >streams at once, but you may only request info about one stream=
 in
>> > > text.  Is
>> > > > >this an accurate summary?
>> > > > >
>> > > > >Seeing as this would be a syntax change, we need to know if=20
>> anyone would
>> > > > >have major heartburn over changing the syntax to fix this.  If=20
>> not, I will
>> > > > >draft up an IG item to fix this...
>> > > > >
>> > > > >Speaking personally, I think this is a beneficial change,=20
>> because it makes
>> > > > >the syntax align between the expression of items within the med=
ia
>> > > > >descriptor, and the audit of items within the media descriptor,=
=20
>> as well as
>> > > > >making both binary and text align in capability.
>> > > > >
>> > > > >Any other comments?
>> > > > >
>> > > > >Kevin
>> > > > >
>> > > > >-----Original Message-----
>> > > > >From: Micael Karlberg [mailto:micael.karlberg@ericsson.com]
>> > > > >Sent: Tuesday, June 17, 2003 1:26 PM
>> > > > >To: Christian Groves
>> > > > >Cc: megaco@ietf.org
>> > > > >Subject: Re: [Megaco] v2 mismatch ABNF & ASN.1 IndAudmediaParm?
>> > > > >
>> > > > >
>> > > > >Hello Christian,
>> > > > >
>> > > > >Christian Groves writes:
>> > > > >  > Hello Micael,
>> > > > >  >
>> > > > >  > I don't understand what the problem is nor the comments in =
the
>> > > ASN.1 you
>> > > > >are  > referring to?
>> > > > >
>> > > > >The comment ("at-most-once per item...") is in the ABNF.
>> > > > >
>> > > > >  > If you are referring to the ::=3D SEQUENCE this is actually=
=20
>> an ASN.1  >
>> > > > >construct that says that a sequence of information elements may=
 be
>> > > encoded,
>> > > > >in  > this case "termStateDescr" & a choice of streams.
>> > > > >
>> > > > >This is how see it also.
>> > > > >
>> > > > >  > This same information is represented by the ABNF.
>> > > > >
>> > > > >This I _cannot_ find!
>> > > > >
>> > > > >The comment in the ABNF seems to indicate that it should be as =
in
>> > > > >the ASN.1 but the ABNF definition of the indAudmediaDescriptor
>> > > > >allow for only one value of indAudmediaParm.
>> > > > >
>> > > > >Therefor my _question_ if the definition should'nt really be:
>> > > > >
>> > > > >         indAudmediaDescriptor =3D MediaToken LBRKT indAudmedia=
Parm
>> > > > >                                  *(COMMA indAudmediaParm) RBRK=
T
>> > > > >
>> > > > >Also, the defintion of the mediaDescriptor strikes me as _very_=
=20
>> similar to
>> > > > >my "proposal":
>> > > > >
>> > > > >       mediaDescriptor =3D MediaToken LBRKT mediaParm
>> > > > >                         *(COMMA mediaParm) RBRKT
>> > > > >
>> > > > >       ; at-most one terminationStateDescriptor
>> > > > >       ; and either streamParm(s) or streamDescriptor(s) but=20
>> not both
>> > > > >       mediaParm =3D (streamParm / streamDescriptor /
>> > > > >                     terminationStateDescriptor)
>> > > > >
>> > > > >Regards,
>> > > > >         /BMK
>> > > > >
>> > > > >  >
>> > > > >  > Regards, Christian
>> > > > >  >
>> > > > >  > Micael Karlberg wrote:
>> > > > >  > >
>> > > > >  > > Hi,
>> > > > >  > >
>> > > > >  > > In draft-ietf-megaco-h248v2-04.txt there appear to be a
>> > > mismatch  > >
>> > > > >between the ABNF and the ASN.1 regarding=20
>> indAudmediaDescriptor.  > > My
>> > > > >question is: Should the definition of ABNF=20
>> indAudmediaDescriptor  > >
>> > > really
>> > > > >be:  > >
>> > > > >  > >       indAudmediaDescriptor   =3D MediaToken LBRKT=20
>> indAudmediaParm
>> > > > >  > >                                 *(COMMA indAudmediaParm)=20
>> RBRKT
>> > > > >  > >
>> > > > >  > > The comment for indAudmediaParm and the ASN.1
>> > > IndAudMediaDescriptor  >
>> > > > > > indicates that it should be a list. Or am I missing=20
>> something?  > >
>> > > > >  > > Also, see definition of mediaDescriptor!
>> > > > >  > >
>> > > > >  > > ABNF:
>> > > > >  > > ----
>> > > > >  > >       indAudmediaDescriptor   =3D MediaToken LBRKT=20
>> indAudmediaParm
>> > > RBRKT
>> > > > >  > >
>> > > > >  > >       ; at-most-once per item
>> > > > >  > >       ; and either streamParm or streamDescriptor but not=
=20
>> both
>> > > > >  > >       indAudmediaParm =3D (indAudstreamParm /=20
>> indAudstreamDescriptor /
>> > > > >  > >                          indAudterminationStateDescriptor=
)
>> > > > >  > >
>> > > > >  > > ASN.1:
>> > > > >  > > -----
>> > > > >  > >       IndAudMediaDescriptor ::=3D SEQUENCE
>> > > > >  > >       {
>> > > > >  > >
>> > > > >  > >          termStateDescr    IndAudTerminationStateDescript=
or
>> > > OPTIONAL,
>> > > > >  > >          streams  CHOICE
>> > > > >  > >                {
>> > > > >  > >                   oneStream      IndAudStreamParms,
>> > > > >  > >                   multiStream    SEQUENCE OF=20
>> IndAudStreamDescriptor
>> > > > >  > >                } OPTIONAL,
>> > > > >  > >          ...
>> > > > >  > >       }
>> > > > >  > >
>> > > > >  > > Regards,
>> > > > >  > >         /BMK
>> > > > >  > >
>> > > > >  > > _______________________________________________
>> > > > >  > > Megaco mailing list
>> > > > >  > > Megaco@ietf.org
>> > > > >  > > https://www1.ietf.org/mailman/listinfo/megaco
>> > > > >
>> > > > >--
>> > > > >Micael Karlberg          Ericsson AB, =C4lvsj=F6 Sweden
>> > > > >Tel:  +46 8 727 5668     EAB/UHK/KD - OTP Product Development
>> > > > >ECN:  851 5668           Mail: micael.karlberg@ericsson.com
>> > > > >Fax:  +46 8 727 5775
>> > > > >
>> > > > >_______________________________________________
>> > > > >Megaco mailing list
>> > > > >Megaco@ietf.org
>> > > > >https://www1.ietf.org/mailman/listinfo/megaco
>> > > > >
>> > > > >_______________________________________________
>> > > > >Megaco mailing list
>> > > > >Megaco@ietf.org
>> > > > >https://www1.ietf.org/mailman/listinfo/megaco
>=20
>=20




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



From mailman-admin@ietf.org  Thu Jul  3 18:48:59 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16979
	for <megaco-archive@lists.ietf.org>; Thu, 3 Jul 2003 18:48:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19YCfB-0007PB-G3
	for megaco-archive@lists.ietf.org; Thu, 03 Jul 2003 18:34:49 -0400
Date: Thu, 03 Jul 2003 18:34:49 -0400
Message-ID: <20030703223449.4508.92675.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: megaco-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

There was an error in the last monthly reminder, in that the NOTE WELL
statement (below) was not included. Therefore, the reminder is being
sent out again.

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, megaco-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

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


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

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

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

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


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for megaco-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
megaco@ietf.org                          rFKd      
https://www1.ietf.org/mailman/options/megaco/megaco-archive%40lists.ietf.org


From megaco-admin@ietf.org  Mon Jul  7 07:15:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20784
	for <megaco-archive@lists.ietf.org>; Mon, 7 Jul 2003 07:15:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZTxV-0003iw-UJ; Mon, 07 Jul 2003 07:15:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZTwk-0003iP-NO
	for megaco@optimus.ietf.org; Mon, 07 Jul 2003 07:14:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20745
	for <megaco@ietf.org>; Mon, 7 Jul 2003 07:14:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZTwk-0003FN-00
	for megaco@ietf.org; Mon, 07 Jul 2003 07:14:14 -0400
Received: from eins.siemens.at ([193.81.246.11])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZTwj-0003F6-00
	for megaco@ietf.org; Mon, 07 Jul 2003 07:14:13 -0400
Received: from scesie13.sie.siemens.at (forix [10.1.140.2])
	by eins.siemens.at (8.12.9/8.12.8) with ESMTP id h67BDfcJ018661
	for <megaco@ietf.org>; Mon, 7 Jul 2003 13:13:42 +0200
Received: from vies194a.sie.siemens.at (atws15tc.sie.siemens.at [158.226.135.41])
	by scesie13.sie.siemens.at (8.12.9/8.12.1) with ESMTP id h67BDemv026982
	for <megaco@ietf.org>; Mon, 7 Jul 2003 13:13:41 +0200 (MET DST)
Received: by vies194a.sie.siemens.at with Internet Mail Service (5.5.2653.19)
	id <33A04YND>; Mon, 7 Jul 2003 13:14:46 +0200
Message-ID: <C10F60785AE7D211B6E00800060DA3910544CB56@vieg128a.gud.siemens.at>
From: Loritz Wolfgang <wolfgang.loritz@siemens.com>
To: "'megaco'" <megaco@ietf.org>
Date: Mon, 7 Jul 2003 13:13:21 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Applicability of packages to RFC 2833?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

Dear list members,

RFC 2833 defines separate RTP payload formats for carrying DTMF, other tone
signals and telephony events in RTP packets.

Which of the various tone generation and tone detection packages are
intended for use with RFC 2833 payload formats?

Many Thanks & Best Regards.
Wolfgang Loritz


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


From exim@www1.ietf.org  Mon Jul  7 07:15:34 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20799
	for <megaco-archive@odin.ietf.org>; Mon, 7 Jul 2003 07:15:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZTxY-0003jl-Lz
	for megaco-archive@odin.ietf.org; Mon, 07 Jul 2003 07:15:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h67BF4Eq014361
	for megaco-archive@odin.ietf.org; Mon, 7 Jul 2003 07:15:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZTxY-0003jY-GW
	for megaco-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 07:15:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20770
	for <megaco-web-archive@ietf.org>; Mon, 7 Jul 2003 07:15:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZTxY-0003Fg-00
	for megaco-web-archive@ietf.org; Mon, 07 Jul 2003 07:15:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZTxX-0003Fc-00
	for megaco-web-archive@ietf.org; Mon, 07 Jul 2003 07:15:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZTxV-0003iw-UJ; Mon, 07 Jul 2003 07:15:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZTwk-0003iP-NO
	for megaco@optimus.ietf.org; Mon, 07 Jul 2003 07:14:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20745
	for <megaco@ietf.org>; Mon, 7 Jul 2003 07:14:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZTwk-0003FN-00
	for megaco@ietf.org; Mon, 07 Jul 2003 07:14:14 -0400
Received: from eins.siemens.at ([193.81.246.11])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZTwj-0003F6-00
	for megaco@ietf.org; Mon, 07 Jul 2003 07:14:13 -0400
Received: from scesie13.sie.siemens.at (forix [10.1.140.2])
	by eins.siemens.at (8.12.9/8.12.8) with ESMTP id h67BDfcJ018661
	for <megaco@ietf.org>; Mon, 7 Jul 2003 13:13:42 +0200
Received: from vies194a.sie.siemens.at (atws15tc.sie.siemens.at [158.226.135.41])
	by scesie13.sie.siemens.at (8.12.9/8.12.1) with ESMTP id h67BDemv026982
	for <megaco@ietf.org>; Mon, 7 Jul 2003 13:13:41 +0200 (MET DST)
Received: by vies194a.sie.siemens.at with Internet Mail Service (5.5.2653.19)
	id <33A04YND>; Mon, 7 Jul 2003 13:14:46 +0200
Message-ID: <C10F60785AE7D211B6E00800060DA3910544CB56@vieg128a.gud.siemens.at>
From: Loritz Wolfgang <wolfgang.loritz@siemens.com>
To: "'megaco'" <megaco@ietf.org>
Date: Mon, 7 Jul 2003 13:13:21 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Applicability of packages to RFC 2833?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

Dear list members,

RFC 2833 defines separate RTP payload formats for carrying DTMF, other tone
signals and telephony events in RTP packets.

Which of the various tone generation and tone detection packages are
intended for use with RFC 2833 payload formats?

Many Thanks & Best Regards.
Wolfgang Loritz


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



From megaco-admin@ietf.org  Tue Jul  8 16:53:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09703
	for <megaco-archive@lists.ietf.org>; Tue, 8 Jul 2003 16:53:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZzSP-0005Nw-74; Tue, 08 Jul 2003 16:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZzS8-0005NS-Pd
	for megaco@optimus.ietf.org; Tue, 08 Jul 2003 16:52:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09671
	for <megaco@ietf.org>; Tue, 8 Jul 2003 16:52:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZzS6-0006Jq-00
	for megaco@ietf.org; Tue, 08 Jul 2003 16:52:42 -0400
Received: from mail.utstar.com ([65.200.123.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZzS6-0006Jn-00
	for megaco@ietf.org; Tue, 08 Jul 2003 16:52:42 -0400
Received: from balanew (balanew [172.16.40.43])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id h68Kqrf19025
	for <megaco@ietf.org>; Tue, 8 Jul 2003 16:52:53 -0400 (EDT)
Reply-To: <bs@utstar.com>
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Date: Tue, 8 Jul 2003 16:52:41 -0400
Organization: UTStarcom Inc
Message-ID: <002201c34592$dfe870c0$2b2810ac@balanew>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0023_01C34571.58D6D0C0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Subject: [Megaco] Package for SMS & Email
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0023_01C34571.58D6D0C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello Folks,

 

Just wondering if there are any packages defined that could be used to send
SMS & Email arising from the mobile phone terminals in the MG to be passed
along to the MGC and then on to the destination?

 

Is Megaco the right protocol to be used to carry such data or are there
other protocols available for this purpose?

 

Thanks,

Bala

______________________

Bala Pitchandi

UTStarcom Inc.


------=_NextPart_000_0023_01C34571.58D6D0C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{font-family:Verdana;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D1 face=3DVerdana><span =
style=3D'font-size:9.0pt;
font-family:Verdana'>Hello Folks,</span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DVerdana><span =
style=3D'font-size:9.0pt;
font-family:Verdana'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DVerdana><span =
style=3D'font-size:9.0pt;
 font-family:Verdana'>J</span></font><font size=3D1 face=3DVerdana><span
style=3D'font-size:9.0pt;font-family:Verdana'>ust wondering if there are =
any packages
defined that could be used to send SMS &amp; Email arising from the =
mobile phone
terminals in the MG to be passed along to the MGC and then on to the
destination?</span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DVerdana><span =
style=3D'font-size:9.0pt;
font-family:Verdana'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DVerdana><span =
style=3D'font-size:9.0pt;
font-family:Verdana'>Is Megaco the right protocol to be used to carry =
such data
or are there other protocols available for this =
purpose?</span></font></p>

<p class=3DMsoAutoSig><font size=3D2 face=3DTahoma><span =
style=3D'font-size:11.0pt;
font-family:Tahoma'>&nbsp;</span></font></p>

<p class=3DMsoAutoSig><font size=3D1 face=3DVerdana><span =
style=3D'font-size:7.5pt;
font-family:Verdana'>Thanks,</span></font></p>

<p class=3DMsoAutoSig><font size=3D1 face=3DVerdana><span =
style=3D'font-size:7.5pt;
 font-family:Verdana'>Bala</span></font></p>

<p class=3DMsoAutoSig><font size=3D1 face=3DVerdana><span =
style=3D'font-size:7.5pt;
font-family:Verdana'>______________________</span></font></p>

<p class=3DMsoAutoSig><strong><b><font size=3D1 face=3DVerdana><span
 =
style=3D'font-size:7.5pt;font-family:Verdana'>Bala</span></font></b></str=
ong><strong><b><font
size=3D1 face=3DVerdana><span =
style=3D'font-size:7.5pt;font-family:Verdana'>
Pitchandi</span></font></b></strong></p>

<p class=3DMsoAutoSig><strong><b><font size=3D1 face=3DVerdana><span
style=3D'font-size:7.5pt;font-family:Verdana'>UTStarcom =
Inc.</span></font></b></strong></p>

</div>

</body>

</html>

------=_NextPart_000_0023_01C34571.58D6D0C0--


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


From exim@www1.ietf.org  Tue Jul  8 16:53:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09718
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jul 2003 16:53:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZzST-0005Oz-S3
	for megaco-archive@odin.ietf.org; Tue, 08 Jul 2003 16:53:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h68Kr5GX020764
	for megaco-archive@odin.ietf.org; Tue, 8 Jul 2003 16:53:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZzST-0005Op-LS
	for megaco-web-archive@optimus.ietf.org; Tue, 08 Jul 2003 16:53:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09688
	for <megaco-web-archive@ietf.org>; Tue, 8 Jul 2003 16:53:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZzSR-0006KM-00
	for megaco-web-archive@ietf.org; Tue, 08 Jul 2003 16:53:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZzSR-0006KI-00
	for megaco-web-archive@ietf.org; Tue, 08 Jul 2003 16:53:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZzSP-0005Nw-74; Tue, 08 Jul 2003 16:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ZzS8-0005NS-Pd
	for megaco@optimus.ietf.org; Tue, 08 Jul 2003 16:52:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09671
	for <megaco@ietf.org>; Tue, 8 Jul 2003 16:52:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZzS6-0006Jq-00
	for megaco@ietf.org; Tue, 08 Jul 2003 16:52:42 -0400
Received: from mail.utstar.com ([65.200.123.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ZzS6-0006Jn-00
	for megaco@ietf.org; Tue, 08 Jul 2003 16:52:42 -0400
Received: from balanew (balanew [172.16.40.43])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id h68Kqrf19025
	for <megaco@ietf.org>; Tue, 8 Jul 2003 16:52:53 -0400 (EDT)
Reply-To: <bs@utstar.com>
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: <megaco@ietf.org>
Date: Tue, 8 Jul 2003 16:52:41 -0400
Organization: UTStarcom Inc
Message-ID: <002201c34592$dfe870c0$2b2810ac@balanew>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0023_01C34571.58D6D0C0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Subject: [Megaco] Package for SMS & Email
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0023_01C34571.58D6D0C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello Folks,

 

Just wondering if there are any packages defined that could be used to send
SMS & Email arising from the mobile phone terminals in the MG to be passed
along to the MGC and then on to the destination?

 

Is Megaco the right protocol to be used to carry such data or are there
other protocols available for this purpose?

 

Thanks,

Bala

______________________

Bala Pitchandi

UTStarcom Inc.


------=_NextPart_000_0023_01C34571.58D6D0C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{font-family:Verdana;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D1 face=3DVerdana><span =
style=3D'font-size:9.0pt;
font-family:Verdana'>Hello Folks,</span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DVerdana><span =
style=3D'font-size:9.0pt;
font-family:Verdana'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DVerdana><span =
style=3D'font-size:9.0pt;
 font-family:Verdana'>J</span></font><font size=3D1 face=3DVerdana><span
style=3D'font-size:9.0pt;font-family:Verdana'>ust wondering if there are =
any packages
defined that could be used to send SMS &amp; Email arising from the =
mobile phone
terminals in the MG to be passed along to the MGC and then on to the
destination?</span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DVerdana><span =
style=3D'font-size:9.0pt;
font-family:Verdana'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DVerdana><span =
style=3D'font-size:9.0pt;
font-family:Verdana'>Is Megaco the right protocol to be used to carry =
such data
or are there other protocols available for this =
purpose?</span></font></p>

<p class=3DMsoAutoSig><font size=3D2 face=3DTahoma><span =
style=3D'font-size:11.0pt;
font-family:Tahoma'>&nbsp;</span></font></p>

<p class=3DMsoAutoSig><font size=3D1 face=3DVerdana><span =
style=3D'font-size:7.5pt;
font-family:Verdana'>Thanks,</span></font></p>

<p class=3DMsoAutoSig><font size=3D1 face=3DVerdana><span =
style=3D'font-size:7.5pt;
 font-family:Verdana'>Bala</span></font></p>

<p class=3DMsoAutoSig><font size=3D1 face=3DVerdana><span =
style=3D'font-size:7.5pt;
font-family:Verdana'>______________________</span></font></p>

<p class=3DMsoAutoSig><strong><b><font size=3D1 face=3DVerdana><span
 =
style=3D'font-size:7.5pt;font-family:Verdana'>Bala</span></font></b></str=
ong><strong><b><font
size=3D1 face=3DVerdana><span =
style=3D'font-size:7.5pt;font-family:Verdana'>
Pitchandi</span></font></b></strong></p>

<p class=3DMsoAutoSig><strong><b><font size=3D1 face=3DVerdana><span
style=3D'font-size:7.5pt;font-family:Verdana'>UTStarcom =
Inc.</span></font></b></strong></p>

</div>

</body>

</html>

------=_NextPart_000_0023_01C34571.58D6D0C0--


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



From megaco-admin@ietf.org  Tue Jul  8 18:08:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12928
	for <megaco-archive@lists.ietf.org>; Tue, 8 Jul 2003 18:08:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a0cz-0002iC-D0; Tue, 08 Jul 2003 18:08:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a0cX-0002ci-6B
	for megaco@optimus.ietf.org; Tue, 08 Jul 2003 18:07:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12819
	for <megaco@ietf.org>; Tue, 8 Jul 2003 18:07:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a0cU-0007Z5-00
	for megaco@ietf.org; Tue, 08 Jul 2003 18:07:30 -0400
Received: from mail.utstar.com ([65.200.123.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a0cO-0007Yt-00
	for megaco@ietf.org; Tue, 08 Jul 2003 18:07:25 -0400
Received: from balanew (balanew [172.16.40.43])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id h68M7Jf02511;
	Tue, 8 Jul 2003 18:07:19 -0400 (EDT)
Reply-To: <bs@utstar.com>
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: <megaco@ietf.org>, <P.Kotar@alcatel.de>,
        "'Anil Jangam'" <anilj@mahindrabt.com>
Subject: RE: [Megaco] Re: ISDN Package for Megaco.
Date: Tue, 8 Jul 2003 18:07:05 -0400
Organization: UTStarcom Inc
Message-ID: <003501c3459d$469d6cd0$2b2810ac@balanew>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <OF938F6C49.FC374C8F-ONC1256D51.0022A359@stgl.netd.alcatel.de>
Content-Transfer-Encoding: quoted-printable
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hello Christian & All,

Have there been any progress regarding this?

Like others, I also think there is a missing link between the ISDN Q.931
messages to corresponding Megaco messages to be sent to MGC, if the MG
decides to terminate the ISDN signaling and presents an abstract view to =
the
MGC.

Maybe a new package with a set of events/signals/properties would make =
this
link clear?
=20
Thanks,
Bala
=20

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
P.Kotar@alcatel.de
Sent: Thursday, June 26, 2003 2:30 AM
To: Anil Jangam
Cc: Christian Groves; megaco@ietf.org; megaco-admin@ietf.org
Subject: Re: [Megaco] Re: ISDN Package for Megaco.


Hello

In deed there is a kind of interworking profile missing for DSS1 <-> =
H.248.
Depending on the DSS1 messages and its content (e.g. SETUP message with =
or
without cd party nbr. digits;
with a certain bearer capability; if there is a Progress Indicator to be
sent, etc). the related H.248 messages
and their content have to be defined. This "co-operation between DSS1 =
and
H.248" should be specified
in order to allow that MG and MGCs of different manufacturers work
together.

Peter



=20

                      "Anil Jangam"

                      <anilj@mahindrab         To:      "Christian =
Groves"
<Christian.Groves@ericsson.com.au>                         =20
                      t.com>                   cc:      =
<megaco@ietf.org>

                      Sent by:                 Subject: [Megaco] Re: =
ISDN
Package for Megaco.                                         =20
                      megaco-admin@iet

                      f.org

=20

=20

                      06/25/2003 03:01

                      PM

=20

=20





Hi Christian,

yes, you are correct.

The events related to signaling (q.931) messages that an isdn terminal
would
generate, would eventually be transmitted to MGC by IUA backhualing.
As far as the bearer events on the same isdn termination is concern, I =
am
not sure how the "draft-bouwen-megaco-isdn-pack-00.txt" (though expired) =
is
applicable.

I was looking into the q.931, but could not find much except that the
beraer
events (e.g. offhook + called party number) would be communicated to the
MGC
in a single Q.931 SETUP message. In this case then what are the other
bearer
events that MEGACO is going to detect and/or report the to the MGC? What
role does megaco is going to play (if at all it plays!)?

I hope my query now makes some sense.
/anil.

----- Original Message -----
From: "Christian Groves" <Christian.Groves@ericsson.com.au>
To: "Anil Jangam" <anilj@mahindrabt.com>
Cc: <megaco@ietf.org>; "Tom-PT Taylor" <taylor@nortelnetworks.com>
Sent: Wednesday, June 25, 2003 11:25 AM
Subject: Re: ISDN Package for Megaco.

> Hello Anil,
>
> The status of the draft is that its expired so theoretically it =
doesn't
exist!?
>
> I don't think the aspects so mention below are of much interest to the
Megaco
> protocol. The backhaul interface (using IUA etc) would be something
different to
> the Megaco interface. Could you be more specific on your question 1.? =
Is
it
> events related to the ISDN signalling data (ie. the backhauled =
channel)
or
> bearer events?
>
> Regards, Christian
>
> Anil Jangam wrote:
> > Hi,
> >
> > What is the status of the document
"draft-bouwen-megaco-isdn-pack-00.txt"?
> > As it stands in the Packages supplement (rel-3) of the ITU-T, no
'Identity'
> > is defined and the 'Status' is expired.
> >
> > I would like to know following regarding an 'ISDN-Access gateway'
controlled
> > by MEGACO :
> > 1. How does the events and signaling generated out of the ISDN
interface
be
> > handled?
> > 2. Do we have to define an IUA interface in MGW to transport the
signaling
> > to MGC? In this case, how the MGW would look like?
> >
> > regards,
> > /anil.
> >
> > *********************************************************
> > Disclaimer
> >
> > This message (including any attachments) contains
> > confidential information intended for a specific
> > individual and purpose, and is protected by law.
> > If you are not the intended recipient, you should
> > delete this message and are hereby notified that
> > any disclosure, copying, or distribution of this
> > message, or the taking of any action based on it,
> > is strictly prohibited.
> >
> > *********************************************************
> > Visit us at http://www.mahindrabt.com
> >
> >
> >
>
>
>

*********************************************************
Disclaimer

This message (including any attachments) contains
confidential information intended for a specific
individual and purpose, and is protected by law.
If you are not the intended recipient, you should
delete this message and are hereby notified that
any disclosure, copying, or distribution of this
message, or the taking of any action based on it,
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com




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






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


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


From exim@www1.ietf.org  Tue Jul  8 18:08:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12947
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jul 2003 18:08:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a0d3-0002jI-0u
	for megaco-archive@odin.ietf.org; Tue, 08 Jul 2003 18:08:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h68M84xx010486
	for megaco-archive@odin.ietf.org; Tue, 8 Jul 2003 18:08:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a0d2-0002j3-Ty
	for megaco-web-archive@optimus.ietf.org; Tue, 08 Jul 2003 18:08:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12877
	for <megaco-web-archive@ietf.org>; Tue, 8 Jul 2003 18:08:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a0d0-0007Zp-00
	for megaco-web-archive@ietf.org; Tue, 08 Jul 2003 18:08:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19a0cz-0007Zm-00
	for megaco-web-archive@ietf.org; Tue, 08 Jul 2003 18:08:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a0cz-0002iC-D0; Tue, 08 Jul 2003 18:08:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a0cX-0002ci-6B
	for megaco@optimus.ietf.org; Tue, 08 Jul 2003 18:07:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12819
	for <megaco@ietf.org>; Tue, 8 Jul 2003 18:07:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a0cU-0007Z5-00
	for megaco@ietf.org; Tue, 08 Jul 2003 18:07:30 -0400
Received: from mail.utstar.com ([65.200.123.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a0cO-0007Yt-00
	for megaco@ietf.org; Tue, 08 Jul 2003 18:07:25 -0400
Received: from balanew (balanew [172.16.40.43])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id h68M7Jf02511;
	Tue, 8 Jul 2003 18:07:19 -0400 (EDT)
Reply-To: <bs@utstar.com>
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: <megaco@ietf.org>, <P.Kotar@alcatel.de>,
        "'Anil Jangam'" <anilj@mahindrabt.com>
Subject: RE: [Megaco] Re: ISDN Package for Megaco.
Date: Tue, 8 Jul 2003 18:07:05 -0400
Organization: UTStarcom Inc
Message-ID: <003501c3459d$469d6cd0$2b2810ac@balanew>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <OF938F6C49.FC374C8F-ONC1256D51.0022A359@stgl.netd.alcatel.de>
Content-Transfer-Encoding: quoted-printable
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hello Christian & All,

Have there been any progress regarding this?

Like others, I also think there is a missing link between the ISDN Q.931
messages to corresponding Megaco messages to be sent to MGC, if the MG
decides to terminate the ISDN signaling and presents an abstract view to =
the
MGC.

Maybe a new package with a set of events/signals/properties would make =
this
link clear?
=20
Thanks,
Bala
=20

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
P.Kotar@alcatel.de
Sent: Thursday, June 26, 2003 2:30 AM
To: Anil Jangam
Cc: Christian Groves; megaco@ietf.org; megaco-admin@ietf.org
Subject: Re: [Megaco] Re: ISDN Package for Megaco.


Hello

In deed there is a kind of interworking profile missing for DSS1 <-> =
H.248.
Depending on the DSS1 messages and its content (e.g. SETUP message with =
or
without cd party nbr. digits;
with a certain bearer capability; if there is a Progress Indicator to be
sent, etc). the related H.248 messages
and their content have to be defined. This "co-operation between DSS1 =
and
H.248" should be specified
in order to allow that MG and MGCs of different manufacturers work
together.

Peter



=20

                      "Anil Jangam"

                      <anilj@mahindrab         To:      "Christian =
Groves"
<Christian.Groves@ericsson.com.au>                         =20
                      t.com>                   cc:      =
<megaco@ietf.org>

                      Sent by:                 Subject: [Megaco] Re: =
ISDN
Package for Megaco.                                         =20
                      megaco-admin@iet

                      f.org

=20

=20

                      06/25/2003 03:01

                      PM

=20

=20





Hi Christian,

yes, you are correct.

The events related to signaling (q.931) messages that an isdn terminal
would
generate, would eventually be transmitted to MGC by IUA backhualing.
As far as the bearer events on the same isdn termination is concern, I =
am
not sure how the "draft-bouwen-megaco-isdn-pack-00.txt" (though expired) =
is
applicable.

I was looking into the q.931, but could not find much except that the
beraer
events (e.g. offhook + called party number) would be communicated to the
MGC
in a single Q.931 SETUP message. In this case then what are the other
bearer
events that MEGACO is going to detect and/or report the to the MGC? What
role does megaco is going to play (if at all it plays!)?

I hope my query now makes some sense.
/anil.

----- Original Message -----
From: "Christian Groves" <Christian.Groves@ericsson.com.au>
To: "Anil Jangam" <anilj@mahindrabt.com>
Cc: <megaco@ietf.org>; "Tom-PT Taylor" <taylor@nortelnetworks.com>
Sent: Wednesday, June 25, 2003 11:25 AM
Subject: Re: ISDN Package for Megaco.

> Hello Anil,
>
> The status of the draft is that its expired so theoretically it =
doesn't
exist!?
>
> I don't think the aspects so mention below are of much interest to the
Megaco
> protocol. The backhaul interface (using IUA etc) would be something
different to
> the Megaco interface. Could you be more specific on your question 1.? =
Is
it
> events related to the ISDN signalling data (ie. the backhauled =
channel)
or
> bearer events?
>
> Regards, Christian
>
> Anil Jangam wrote:
> > Hi,
> >
> > What is the status of the document
"draft-bouwen-megaco-isdn-pack-00.txt"?
> > As it stands in the Packages supplement (rel-3) of the ITU-T, no
'Identity'
> > is defined and the 'Status' is expired.
> >
> > I would like to know following regarding an 'ISDN-Access gateway'
controlled
> > by MEGACO :
> > 1. How does the events and signaling generated out of the ISDN
interface
be
> > handled?
> > 2. Do we have to define an IUA interface in MGW to transport the
signaling
> > to MGC? In this case, how the MGW would look like?
> >
> > regards,
> > /anil.
> >
> > *********************************************************
> > Disclaimer
> >
> > This message (including any attachments) contains
> > confidential information intended for a specific
> > individual and purpose, and is protected by law.
> > If you are not the intended recipient, you should
> > delete this message and are hereby notified that
> > any disclosure, copying, or distribution of this
> > message, or the taking of any action based on it,
> > is strictly prohibited.
> >
> > *********************************************************
> > Visit us at http://www.mahindrabt.com
> >
> >
> >
>
>
>

*********************************************************
Disclaimer

This message (including any attachments) contains
confidential information intended for a specific
individual and purpose, and is protected by law.
If you are not the intended recipient, you should
delete this message and are hereby notified that
any disclosure, copying, or distribution of this
message, or the taking of any action based on it,
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com




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






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


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



From megaco-admin@ietf.org  Tue Jul  8 18:34:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14170
	for <megaco-archive@lists.ietf.org>; Tue, 8 Jul 2003 18:34:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a129-0004SG-FF; Tue, 08 Jul 2003 18:34:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a11W-0004Ph-UF
	for megaco@optimus.ietf.org; Tue, 08 Jul 2003 18:33:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14147
	for <megaco@ietf.org>; Tue, 8 Jul 2003 18:33:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a11U-0000AT-00
	for megaco@ietf.org; Tue, 08 Jul 2003 18:33:20 -0400
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a11T-00009w-00
	for megaco@ietf.org; Tue, 08 Jul 2003 18:33:19 -0400
Received: from zcard307.ca.nortel.com (americasm07.nt.com [47.129.242.67])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h68MWSM13503;
	Tue, 8 Jul 2003 18:32:28 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 31QD4MBT; Tue, 8 Jul 2003 18:32:29 -0400
Received: from nortelnetworks.com (acart1d3.ca.nortel.com [47.129.129.79]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLV9J0QG; Tue, 8 Jul 2003 18:32:28 -0400
Message-ID: <3F0B467A.7030506@nortelnetworks.com>
Date: Tue, 08 Jul 2003 18:32:26 -0400
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: bs@utstar.com
CC: "'Christian Groves'" <Christian.Groves@ericsson.com.au>, megaco@ietf.org,
        P.Kotar@alcatel.de, "'Anil Jangam'" <anilj@mahindrabt.com>
Subject: Re: [Megaco] Re: ISDN Package for Megaco.
References: <003501c3459d$469d6cd0$2b2810ac@balanew>
In-Reply-To: <003501c3459d$469d6cd0$2b2810ac@balanew>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

This is out of scope for Megaco.  The IETF has defined a suite of protocols for 
specific purposes: Megaco for media gateway control, SIGTRAN IUA/SCTP for carriage 
of signalling.  If you try to substitute Megaco for the latter, you will probably 
end up with nasty surprises.

Your idea isn't new, by the way.  Ascend were proposing "Q.931+" for gateway control 
before Megaco got rolling.

Balasubramanian Pitchandi wrote:

> Hello Christian & All,
> 
> Have there been any progress regarding this?
> 
> Like others, I also think there is a missing link between the ISDN Q.931
> messages to corresponding Megaco messages to be sent to MGC, if the MG
> decides to terminate the ISDN signaling and presents an abstract view to the
> MGC.
> 
> Maybe a new package with a set of events/signals/properties would make this
> link clear?
>  
> Thanks,
> Bala
>  
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> P.Kotar@alcatel.de
> Sent: Thursday, June 26, 2003 2:30 AM
> To: Anil Jangam
> Cc: Christian Groves; megaco@ietf.org; megaco-admin@ietf.org
> Subject: Re: [Megaco] Re: ISDN Package for Megaco.
> 
> 
> Hello
> 
> In deed there is a kind of interworking profile missing for DSS1 <-> H.248.
> Depending on the DSS1 messages and its content (e.g. SETUP message with or
> without cd party nbr. digits;
> with a certain bearer capability; if there is a Progress Indicator to be
> sent, etc). the related H.248 messages
> and their content have to be defined. This "co-operation between DSS1 and
> H.248" should be specified
> in order to allow that MG and MGCs of different manufacturers work
> together.
> 
> Peter
> 
> 
> 
>  
> 
>                       "Anil Jangam"
> 
>                       <anilj@mahindrab         To:      "Christian Groves"
> <Christian.Groves@ericsson.com.au>                          
>                       t.com>                   cc:      <megaco@ietf.org>
> 
>                       Sent by:                 Subject: [Megaco] Re: ISDN
> Package for Megaco.                                          
>                       megaco-admin@iet
> 
>                       f.org
> 
>  
> 
>  
> 
>                       06/25/2003 03:01
> 
>                       PM
> 
>  
> 
>  
> 
> 
> 
> 
> 
> Hi Christian,
> 
> yes, you are correct.
> 
> The events related to signaling (q.931) messages that an isdn terminal
> would
> generate, would eventually be transmitted to MGC by IUA backhualing.
> As far as the bearer events on the same isdn termination is concern, I am
> not sure how the "draft-bouwen-megaco-isdn-pack-00.txt" (though expired) is
> applicable.
> 
> I was looking into the q.931, but could not find much except that the
> beraer
> events (e.g. offhook + called party number) would be communicated to the
> MGC
> in a single Q.931 SETUP message. In this case then what are the other
> bearer
> events that MEGACO is going to detect and/or report the to the MGC? What
> role does megaco is going to play (if at all it plays!)?
> 
> I hope my query now makes some sense.
> /anil.
> 
> ----- Original Message -----
> From: "Christian Groves" <Christian.Groves@ericsson.com.au>
> To: "Anil Jangam" <anilj@mahindrabt.com>
> Cc: <megaco@ietf.org>; "Tom-PT Taylor" <taylor@nortelnetworks.com>
> Sent: Wednesday, June 25, 2003 11:25 AM
> Subject: Re: ISDN Package for Megaco.
> 
> 
>>Hello Anil,
>>
>>The status of the draft is that its expired so theoretically it doesn't
> 
> exist!?
> 
>>I don't think the aspects so mention below are of much interest to the
> 
> Megaco
> 
>>protocol. The backhaul interface (using IUA etc) would be something
> 
> different to
> 
>>the Megaco interface. Could you be more specific on your question 1.? Is
> 
> it
> 
>>events related to the ISDN signalling data (ie. the backhauled channel)
> 
> or
> 
>>bearer events?
>>
>>Regards, Christian
>>
>>Anil Jangam wrote:
>>
>>>Hi,
>>>
>>>What is the status of the document
> 
> "draft-bouwen-megaco-isdn-pack-00.txt"?
> 
>>>As it stands in the Packages supplement (rel-3) of the ITU-T, no
> 
> 'Identity'
> 
>>>is defined and the 'Status' is expired.
>>>
>>>I would like to know following regarding an 'ISDN-Access gateway'
> 
> controlled
> 
>>>by MEGACO :
>>>1. How does the events and signaling generated out of the ISDN
> 
> interface
> be
> 
>>>handled?
>>>2. Do we have to define an IUA interface in MGW to transport the
> 
> signaling
> 
>>>to MGC? In this case, how the MGW would look like?
>>>
>>>regards,
>>>/anil.
>>>
>>>*********************************************************
>>>Disclaimer
>>>
>>>This message (including any attachments) contains
>>>confidential information intended for a specific
>>>individual and purpose, and is protected by law.
>>>If you are not the intended recipient, you should
>>>delete this message and are hereby notified that
>>>any disclosure, copying, or distribution of this
>>>message, or the taking of any action based on it,
>>>is strictly prohibited.
>>>
>>>*********************************************************
>>>Visit us at http://www.mahindrabt.com
>>>
>>>
>>>
>>
>>
>>
> 
> *********************************************************
> Disclaimer
> 
> This message (including any attachments) contains
> confidential information intended for a specific
> individual and purpose, and is protected by law.
> If you are not the intended recipient, you should
> delete this message and are hereby notified that
> any disclosure, copying, or distribution of this
> message, or the taking of any action based on it,
> is strictly prohibited.
> 
> *********************************************************
> Visit us at http://www.mahindrabt.com
> 
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 


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


From exim@www1.ietf.org  Tue Jul  8 18:34:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14188
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jul 2003 18:34:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a12C-0004XR-As
	for megaco-archive@odin.ietf.org; Tue, 08 Jul 2003 18:34:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h68MY4df017441
	for megaco-archive@odin.ietf.org; Tue, 8 Jul 2003 18:34:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a12C-0004XE-73
	for megaco-web-archive@optimus.ietf.org; Tue, 08 Jul 2003 18:34:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14159
	for <megaco-web-archive@ietf.org>; Tue, 8 Jul 2003 18:33:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a129-0000BC-00
	for megaco-web-archive@ietf.org; Tue, 08 Jul 2003 18:34:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19a128-0000B9-00
	for megaco-web-archive@ietf.org; Tue, 08 Jul 2003 18:34:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a129-0004SG-FF; Tue, 08 Jul 2003 18:34:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a11W-0004Ph-UF
	for megaco@optimus.ietf.org; Tue, 08 Jul 2003 18:33:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14147
	for <megaco@ietf.org>; Tue, 8 Jul 2003 18:33:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a11U-0000AT-00
	for megaco@ietf.org; Tue, 08 Jul 2003 18:33:20 -0400
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a11T-00009w-00
	for megaco@ietf.org; Tue, 08 Jul 2003 18:33:19 -0400
Received: from zcard307.ca.nortel.com (americasm07.nt.com [47.129.242.67])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h68MWSM13503;
	Tue, 8 Jul 2003 18:32:28 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 31QD4MBT; Tue, 8 Jul 2003 18:32:29 -0400
Received: from nortelnetworks.com (acart1d3.ca.nortel.com [47.129.129.79]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLV9J0QG; Tue, 8 Jul 2003 18:32:28 -0400
Message-ID: <3F0B467A.7030506@nortelnetworks.com>
Date: Tue, 08 Jul 2003 18:32:26 -0400
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: bs@utstar.com
CC: "'Christian Groves'" <Christian.Groves@ericsson.com.au>, megaco@ietf.org,
        P.Kotar@alcatel.de, "'Anil Jangam'" <anilj@mahindrabt.com>
Subject: Re: [Megaco] Re: ISDN Package for Megaco.
References: <003501c3459d$469d6cd0$2b2810ac@balanew>
In-Reply-To: <003501c3459d$469d6cd0$2b2810ac@balanew>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

This is out of scope for Megaco.  The IETF has defined a suite of protocols for 
specific purposes: Megaco for media gateway control, SIGTRAN IUA/SCTP for carriage 
of signalling.  If you try to substitute Megaco for the latter, you will probably 
end up with nasty surprises.

Your idea isn't new, by the way.  Ascend were proposing "Q.931+" for gateway control 
before Megaco got rolling.

Balasubramanian Pitchandi wrote:

> Hello Christian & All,
> 
> Have there been any progress regarding this?
> 
> Like others, I also think there is a missing link between the ISDN Q.931
> messages to corresponding Megaco messages to be sent to MGC, if the MG
> decides to terminate the ISDN signaling and presents an abstract view to the
> MGC.
> 
> Maybe a new package with a set of events/signals/properties would make this
> link clear?
>  
> Thanks,
> Bala
>  
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
> P.Kotar@alcatel.de
> Sent: Thursday, June 26, 2003 2:30 AM
> To: Anil Jangam
> Cc: Christian Groves; megaco@ietf.org; megaco-admin@ietf.org
> Subject: Re: [Megaco] Re: ISDN Package for Megaco.
> 
> 
> Hello
> 
> In deed there is a kind of interworking profile missing for DSS1 <-> H.248.
> Depending on the DSS1 messages and its content (e.g. SETUP message with or
> without cd party nbr. digits;
> with a certain bearer capability; if there is a Progress Indicator to be
> sent, etc). the related H.248 messages
> and their content have to be defined. This "co-operation between DSS1 and
> H.248" should be specified
> in order to allow that MG and MGCs of different manufacturers work
> together.
> 
> Peter
> 
> 
> 
>  
> 
>                       "Anil Jangam"
> 
>                       <anilj@mahindrab         To:      "Christian Groves"
> <Christian.Groves@ericsson.com.au>                          
>                       t.com>                   cc:      <megaco@ietf.org>
> 
>                       Sent by:                 Subject: [Megaco] Re: ISDN
> Package for Megaco.                                          
>                       megaco-admin@iet
> 
>                       f.org
> 
>  
> 
>  
> 
>                       06/25/2003 03:01
> 
>                       PM
> 
>  
> 
>  
> 
> 
> 
> 
> 
> Hi Christian,
> 
> yes, you are correct.
> 
> The events related to signaling (q.931) messages that an isdn terminal
> would
> generate, would eventually be transmitted to MGC by IUA backhualing.
> As far as the bearer events on the same isdn termination is concern, I am
> not sure how the "draft-bouwen-megaco-isdn-pack-00.txt" (though expired) is
> applicable.
> 
> I was looking into the q.931, but could not find much except that the
> beraer
> events (e.g. offhook + called party number) would be communicated to the
> MGC
> in a single Q.931 SETUP message. In this case then what are the other
> bearer
> events that MEGACO is going to detect and/or report the to the MGC? What
> role does megaco is going to play (if at all it plays!)?
> 
> I hope my query now makes some sense.
> /anil.
> 
> ----- Original Message -----
> From: "Christian Groves" <Christian.Groves@ericsson.com.au>
> To: "Anil Jangam" <anilj@mahindrabt.com>
> Cc: <megaco@ietf.org>; "Tom-PT Taylor" <taylor@nortelnetworks.com>
> Sent: Wednesday, June 25, 2003 11:25 AM
> Subject: Re: ISDN Package for Megaco.
> 
> 
>>Hello Anil,
>>
>>The status of the draft is that its expired so theoretically it doesn't
> 
> exist!?
> 
>>I don't think the aspects so mention below are of much interest to the
> 
> Megaco
> 
>>protocol. The backhaul interface (using IUA etc) would be something
> 
> different to
> 
>>the Megaco interface. Could you be more specific on your question 1.? Is
> 
> it
> 
>>events related to the ISDN signalling data (ie. the backhauled channel)
> 
> or
> 
>>bearer events?
>>
>>Regards, Christian
>>
>>Anil Jangam wrote:
>>
>>>Hi,
>>>
>>>What is the status of the document
> 
> "draft-bouwen-megaco-isdn-pack-00.txt"?
> 
>>>As it stands in the Packages supplement (rel-3) of the ITU-T, no
> 
> 'Identity'
> 
>>>is defined and the 'Status' is expired.
>>>
>>>I would like to know following regarding an 'ISDN-Access gateway'
> 
> controlled
> 
>>>by MEGACO :
>>>1. How does the events and signaling generated out of the ISDN
> 
> interface
> be
> 
>>>handled?
>>>2. Do we have to define an IUA interface in MGW to transport the
> 
> signaling
> 
>>>to MGC? In this case, how the MGW would look like?
>>>
>>>regards,
>>>/anil.
>>>
>>>*********************************************************
>>>Disclaimer
>>>
>>>This message (including any attachments) contains
>>>confidential information intended for a specific
>>>individual and purpose, and is protected by law.
>>>If you are not the intended recipient, you should
>>>delete this message and are hereby notified that
>>>any disclosure, copying, or distribution of this
>>>message, or the taking of any action based on it,
>>>is strictly prohibited.
>>>
>>>*********************************************************
>>>Visit us at http://www.mahindrabt.com
>>>
>>>
>>>
>>
>>
>>
> 
> *********************************************************
> Disclaimer
> 
> This message (including any attachments) contains
> confidential information intended for a specific
> individual and purpose, and is protected by law.
> If you are not the intended recipient, you should
> delete this message and are hereby notified that
> any disclosure, copying, or distribution of this
> message, or the taking of any action based on it,
> is strictly prohibited.
> 
> *********************************************************
> Visit us at http://www.mahindrabt.com
> 
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 


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



From megaco-admin@ietf.org  Tue Jul  8 22:11:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19223
	for <megaco-archive@lists.ietf.org>; Tue, 8 Jul 2003 22:11:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a4QA-0001wJ-1N; Tue, 08 Jul 2003 22:11:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a4Pa-0001w1-Sh
	for megaco@optimus.ietf.org; Tue, 08 Jul 2003 22:10:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19176
	for <megaco@ietf.org>; Tue, 8 Jul 2003 22:10:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a4PX-0002oO-00
	for megaco@ietf.org; Tue, 08 Jul 2003 22:10:23 -0400
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a4PW-0002oL-00
	for megaco@ietf.org; Tue, 08 Jul 2003 22:10:23 -0400
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h692AF1R000703
	for <megaco@ietf.org>; Wed, 9 Jul 2003 11:10:15 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h692AE8E001245
	for <megaco@ietf.org>; Wed, 9 Jul 2003 11:10:14 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h692AEeH016267
	for <megaco@ietf.org>; Wed, 9 Jul 2003 11:10:14 +0900 (JST)
Received: from imb.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id LAA09234;
	Wed, 9 Jul 2003 11:10:13 +0900 (JST)
Received: from DYNABOOK-YAMA.lab.ntt.co.jp
	by imb.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id LAA04430;
	Wed, 9 Jul 2003 11:10:13 +0900 (JST)
Message-Id: <5.1.1.9.2.20030709110017.06086e90@imb.m.ecl.ntt.co.jp>
X-Sender: sy001@imb.m.ecl.ntt.co.jp
X-Mailer: QUALCOMM Windows Eudora Version 5.1-Jr4
Date: Wed, 09 Jul 2003 11:10:22 +0900
To: megaco@ietf.org
From: "YAMAMOTO, Susumu" <yamamoto.susumu@lab.ntt.co.jp>
Cc: tsuboi.shunnichi@lab.ntt.co.jp
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] QoS package
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all,

I am looking for a MEGACO package which could configure TOS value
of RTP packets session by session with Add or Modify command. I found
draft-madhubabu-megaco-qospackage-00 at some web sites, but the
draft seems already expired.

Please let me know the current situation of standardization of the draft,
or another latest solution for TOS operation if we have. I hope the
standardization process for the draft might contiue in ITU or somewhere.

Thanks,
-Susumu



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


From exim@www1.ietf.org  Tue Jul  8 22:11:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19238
	for <megaco-archive@odin.ietf.org>; Tue, 8 Jul 2003 22:11:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a4QE-0001xg-Ga
	for megaco-archive@odin.ietf.org; Tue, 08 Jul 2003 22:11:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h692B6mp007534
	for megaco-archive@odin.ietf.org; Tue, 8 Jul 2003 22:11:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a4QE-0001xR-CT
	for megaco-web-archive@optimus.ietf.org; Tue, 08 Jul 2003 22:11:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19202
	for <megaco-web-archive@ietf.org>; Tue, 8 Jul 2003 22:11:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a4QB-0002of-00
	for megaco-web-archive@ietf.org; Tue, 08 Jul 2003 22:11:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19a4QA-0002oc-00
	for megaco-web-archive@ietf.org; Tue, 08 Jul 2003 22:11:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a4QA-0001wJ-1N; Tue, 08 Jul 2003 22:11:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a4Pa-0001w1-Sh
	for megaco@optimus.ietf.org; Tue, 08 Jul 2003 22:10:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19176
	for <megaco@ietf.org>; Tue, 8 Jul 2003 22:10:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a4PX-0002oO-00
	for megaco@ietf.org; Tue, 08 Jul 2003 22:10:23 -0400
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a4PW-0002oL-00
	for megaco@ietf.org; Tue, 08 Jul 2003 22:10:23 -0400
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h692AF1R000703
	for <megaco@ietf.org>; Wed, 9 Jul 2003 11:10:15 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h692AE8E001245
	for <megaco@ietf.org>; Wed, 9 Jul 2003 11:10:14 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h692AEeH016267
	for <megaco@ietf.org>; Wed, 9 Jul 2003 11:10:14 +0900 (JST)
Received: from imb.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id LAA09234;
	Wed, 9 Jul 2003 11:10:13 +0900 (JST)
Received: from DYNABOOK-YAMA.lab.ntt.co.jp
	by imb.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id LAA04430;
	Wed, 9 Jul 2003 11:10:13 +0900 (JST)
Message-Id: <5.1.1.9.2.20030709110017.06086e90@imb.m.ecl.ntt.co.jp>
X-Sender: sy001@imb.m.ecl.ntt.co.jp
X-Mailer: QUALCOMM Windows Eudora Version 5.1-Jr4
Date: Wed, 09 Jul 2003 11:10:22 +0900
To: megaco@ietf.org
From: "YAMAMOTO, Susumu" <yamamoto.susumu@lab.ntt.co.jp>
Cc: tsuboi.shunnichi@lab.ntt.co.jp
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] QoS package
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all,

I am looking for a MEGACO package which could configure TOS value
of RTP packets session by session with Add or Modify command. I found
draft-madhubabu-megaco-qospackage-00 at some web sites, but the
draft seems already expired.

Please let me know the current situation of standardization of the draft,
or another latest solution for TOS operation if we have. I hope the
standardization process for the draft might contiue in ITU or somewhere.

Thanks,
-Susumu



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



From megaco-admin@ietf.org  Wed Jul  9 01:23:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22612
	for <megaco-archive@lists.ietf.org>; Wed, 9 Jul 2003 01:23:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a7Pw-0006BH-S5; Wed, 09 Jul 2003 01:23:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a7PX-0006B2-Ew
	for megaco@optimus.ietf.org; Wed, 09 Jul 2003 01:22:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22605
	for <megaco@ietf.org>; Wed, 9 Jul 2003 01:22:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a7PS-0003e2-00
	for megaco@ietf.org; Wed, 09 Jul 2003 01:22:31 -0400
Received: from [210.22.146.172] (helo=asbmx.sbell.com.cn)
	by ietf-mx with esmtp (Exim 4.12)
	id 19a7PF-0003dt-00
	for megaco@ietf.org; Wed, 09 Jul 2003 01:22:28 -0400
Received: from asbwebshld.sbell.com.cn (asbwebshld [172.24.208.38])
	by asbmx.sbell.com.cn (8.12.2+Sun/8.12.3) with SMTP id h6959Qki018932
	for <megaco@ietf.org>; Wed, 9 Jul 2003 13:09:28 +0800 (CST)
Received: FROM bellnet-mail4.sbell.com.cn BY asbwebshld.sbell.com.cn ; Wed Jul 09 13:21:57 2003 +0800
Received: from bellnet-mail1.sbell.com.cn ([172.24.208.21]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 9 Jul 2003 13:21:56 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-7"
Content-Transfer-Encoding: 7bit
Date: Wed, 9 Jul 2003 13:21:56 +0800
Message-ID: <C2DB7F5BC458EA4C8EB46B7A4EFF7E764B856C@bellnet-mail1.sbell.com.cn>
Thread-Topic: question about signal descriptor in Modify's response 
Thread-Index: AcNF2gPCyCoJxHeKTjiggMUx5W76bA+AD0APQ-
From: "FND-AD Wang JuLin" <JuLin.Wang@alcatel-sbell.com.cn>
To: "Megaco (E-mail)" <megaco@ietf.org>
X-OriginalArrivalTime: 09 Jul 2003 05:21:56.0846 (UTC) FILETIME=[03FAC8E0:01C345DA]
Content-Transfer-Encoding: 7bit
Subject: [Megaco] question about signal descriptor in Modify's response
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all,
According to the protocol,signal descriptor can be modified and returned in Modify's response.Can we construct the Modify 's response whatever we want to implement our product features?Here are two examples as follows.
Example 1:
MGC---+AD4-MG
MEGACO/1 +AFs-15.8.1.10+AF0-:2944 
   Transaction +AD0- 10001 +AHs- 
       Context +AD0- - +AHs- 
           Modify +AD0- ROOT +AHs-Signals  +AHs-xxx/yyy   +AHs-k+AD0-1,
                                                     ea +AD0- 1, 
                                                     random +AD0-1224+AH0AfQ-    
           +AH0- 
       +AH0- 
   +AH0- 

MG---+AD4-MGC
MEGACO/1 +AFs-15.8.1.18+AF0-:2944 
Reply +AD0- 10001 +AHs- 
Context +AD0- - +AHs-Modify +AD0- ROOT+AHs-
Signals +AHs-xxx/yyy+AHs-key+AD0-22,
ea +AD0- 1 
+AH0AfQ-    
           +AH0- +AH0- +AH0-
Example 2: 
MGC---+AD4-MG
MEGACO/1 +AFs-15.8.1.10+AF0-:2944 
   Transaction +AD0- 10001 +AHs- 
       Context +AD0- - +AHs- 
           Modify +AD0- ROOT +AHs-Signals  +AHs-xxx/zzz   +AHs-t+AD0-1+AH0-,
                                                         xxx/yyy   +AHs-k+AD0-2,
                                                     ea +AD0- 1, 
                                                     random +AD0-1223+AH0AfQ-    
           +AH0- 
       +AH0- 
   +AH0- 
 
MG---+AD4-MGC
MEGACO/1 +AFs-15.8.1.18+AF0-:2944 
Reply +AD0- 10001 +AHs- 
Context +AD0- - +AHs-Modify +AD0- ROOT+AH0AfQ-

I wonder if the above  two examples are suitable or not when both are adopted in a scenario for gateway to implement some features.Please clear my mind.Thanks in advance+ACE-

 best  regards 
JJerry Wang 
tel:(8621)58541240 ext 9531 
MP:13621761050 
mailto:Julin.Wang+AEA-alcatel-sbell.com.cn 
Alcatel Shanghai Bell Co.LTD 

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


From exim@www1.ietf.org  Wed Jul  9 01:23:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22627
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jul 2003 01:23:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a7Py-0006Bu-U2
	for megaco-archive@odin.ietf.org; Wed, 09 Jul 2003 01:23:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h695N2vr023792
	for megaco-archive@odin.ietf.org; Wed, 9 Jul 2003 01:23:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a7Py-0006Bf-Qr
	for megaco-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 01:23:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22609
	for <megaco-web-archive@ietf.org>; Wed, 9 Jul 2003 01:23:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a7Pv-0003e8-00
	for megaco-web-archive@ietf.org; Wed, 09 Jul 2003 01:22:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19a7Pv-0003e5-00
	for megaco-web-archive@ietf.org; Wed, 09 Jul 2003 01:22:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a7Pw-0006BH-S5; Wed, 09 Jul 2003 01:23:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19a7PX-0006B2-Ew
	for megaco@optimus.ietf.org; Wed, 09 Jul 2003 01:22:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22605
	for <megaco@ietf.org>; Wed, 9 Jul 2003 01:22:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19a7PS-0003e2-00
	for megaco@ietf.org; Wed, 09 Jul 2003 01:22:31 -0400
Received: from [210.22.146.172] (helo=asbmx.sbell.com.cn)
	by ietf-mx with esmtp (Exim 4.12)
	id 19a7PF-0003dt-00
	for megaco@ietf.org; Wed, 09 Jul 2003 01:22:28 -0400
Received: from asbwebshld.sbell.com.cn (asbwebshld [172.24.208.38])
	by asbmx.sbell.com.cn (8.12.2+Sun/8.12.3) with SMTP id h6959Qki018932
	for <megaco@ietf.org>; Wed, 9 Jul 2003 13:09:28 +0800 (CST)
Received: FROM bellnet-mail4.sbell.com.cn BY asbwebshld.sbell.com.cn ; Wed Jul 09 13:21:57 2003 +0800
Received: from bellnet-mail1.sbell.com.cn ([172.24.208.21]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 9 Jul 2003 13:21:56 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-7"
Content-Transfer-Encoding: 7bit
Date: Wed, 9 Jul 2003 13:21:56 +0800
Message-ID: <C2DB7F5BC458EA4C8EB46B7A4EFF7E764B856C@bellnet-mail1.sbell.com.cn>
Thread-Topic: question about signal descriptor in Modify's response 
Thread-Index: AcNF2gPCyCoJxHeKTjiggMUx5W76bA+AD0APQ-
From: "FND-AD Wang JuLin" <JuLin.Wang@alcatel-sbell.com.cn>
To: "Megaco (E-mail)" <megaco@ietf.org>
X-OriginalArrivalTime: 09 Jul 2003 05:21:56.0846 (UTC) FILETIME=[03FAC8E0:01C345DA]
Content-Transfer-Encoding: 7bit
Subject: [Megaco] question about signal descriptor in Modify's response
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all,
According to the protocol,signal descriptor can be modified and returned in Modify's response.Can we construct the Modify 's response whatever we want to implement our product features?Here are two examples as follows.
Example 1:
MGC---+AD4-MG
MEGACO/1 +AFs-15.8.1.10+AF0-:2944 
   Transaction +AD0- 10001 +AHs- 
       Context +AD0- - +AHs- 
           Modify +AD0- ROOT +AHs-Signals  +AHs-xxx/yyy   +AHs-k+AD0-1,
                                                     ea +AD0- 1, 
                                                     random +AD0-1224+AH0AfQ-    
           +AH0- 
       +AH0- 
   +AH0- 

MG---+AD4-MGC
MEGACO/1 +AFs-15.8.1.18+AF0-:2944 
Reply +AD0- 10001 +AHs- 
Context +AD0- - +AHs-Modify +AD0- ROOT+AHs-
Signals +AHs-xxx/yyy+AHs-key+AD0-22,
ea +AD0- 1 
+AH0AfQ-    
           +AH0- +AH0- +AH0-
Example 2: 
MGC---+AD4-MG
MEGACO/1 +AFs-15.8.1.10+AF0-:2944 
   Transaction +AD0- 10001 +AHs- 
       Context +AD0- - +AHs- 
           Modify +AD0- ROOT +AHs-Signals  +AHs-xxx/zzz   +AHs-t+AD0-1+AH0-,
                                                         xxx/yyy   +AHs-k+AD0-2,
                                                     ea +AD0- 1, 
                                                     random +AD0-1223+AH0AfQ-    
           +AH0- 
       +AH0- 
   +AH0- 
 
MG---+AD4-MGC
MEGACO/1 +AFs-15.8.1.18+AF0-:2944 
Reply +AD0- 10001 +AHs- 
Context +AD0- - +AHs-Modify +AD0- ROOT+AH0AfQ-

I wonder if the above  two examples are suitable or not when both are adopted in a scenario for gateway to implement some features.Please clear my mind.Thanks in advance+ACE-

 best  regards 
JJerry Wang 
tel:(8621)58541240 ext 9531 
MP:13621761050 
mailto:Julin.Wang+AEA-alcatel-sbell.com.cn 
Alcatel Shanghai Bell Co.LTD 

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



From megaco-admin@ietf.org  Wed Jul  9 11:13:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04301
	for <megaco-archive@lists.ietf.org>; Wed, 9 Jul 2003 11:13:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aGcy-0000vx-FM; Wed, 09 Jul 2003 11:13:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aDd4-0000oG-JC
	for megaco@optimus.ietf.org; Wed, 09 Jul 2003 08:00:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28318
	for <megaco@ietf.org>; Wed, 9 Jul 2003 08:00:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aDd3-0006C5-00
	for megaco@ietf.org; Wed, 09 Jul 2003 08:00:57 -0400
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aDd3-0006C0-00
	for megaco@ietf.org; Wed, 09 Jul 2003 08:00:57 -0400
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h69BxpQ07802;
	Wed, 9 Jul 2003 07:59:51 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLVYR00M; Wed, 9 Jul 2003 07:59:51 -0400
Received: from nortelnetworks.com (acart1d3.ca.nortel.com [47.129.129.79]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3RVWPB5L; Wed, 9 Jul 2003 07:59:51 -0400
Message-ID: <3F0C0380.9010307@nortelnetworks.com>
Date: Wed, 09 Jul 2003 07:58:56 -0400
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: "YAMAMOTO, Susumu" <yamamoto.susumu@lab.ntt.co.jp>
CC: megaco@ietf.org, tsuboi.shunnichi@lab.ntt.co.jp
Subject: Re: [Megaco] QoS package
References: <5.1.1.9.2.20030709110017.06086e90@imb.m.ecl.ntt.co.jp>
In-Reply-To: <5.1.1.9.2.20030709110017.06086e90@imb.m.ecl.ntt.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

France Telecom has such a proposal into SG 11.  If you have an ITU-T TIES account,
have a look at http://ties.itu.int/u/tsg11/sg11/bicc/common/france-0304/fra105r1.zip

YAMAMOTO, Susumu wrote:

> Hi all,
> 
> I am looking for a MEGACO package which could configure TOS value
> of RTP packets session by session with Add or Modify command. I found
> draft-madhubabu-megaco-qospackage-00 at some web sites, but the
> draft seems already expired.
> 
> Please let me know the current situation of standardization of the draft,
> or another latest solution for TOS operation if we have. I hope the
> standardization process for the draft might contiue in ITU or somewhere.
> 
> Thanks,
> -Susumu
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 


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


From exim@www1.ietf.org  Wed Jul  9 11:14:05 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04843
	for <megaco-archive@odin.ietf.org>; Wed, 9 Jul 2003 11:14:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aGdR-0001T6-VE
	for megaco-archive@odin.ietf.org; Wed, 09 Jul 2003 11:13:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h69FDXlw005640
	for megaco-archive@odin.ietf.org; Wed, 9 Jul 2003 11:13:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aGdR-0001St-SK
	for megaco-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 11:13:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04227
	for <megaco-web-archive@ietf.org>; Wed, 9 Jul 2003 11:13:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aGdQ-0007Ip-00
	for megaco-web-archive@ietf.org; Wed, 09 Jul 2003 11:13:32 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19aGdP-0007Fv-00
	for megaco-web-archive@ietf.org; Wed, 09 Jul 2003 11:13:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aGcy-0000vx-FM; Wed, 09 Jul 2003 11:13:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19aDd4-0000oG-JC
	for megaco@optimus.ietf.org; Wed, 09 Jul 2003 08:00:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28318
	for <megaco@ietf.org>; Wed, 9 Jul 2003 08:00:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aDd3-0006C5-00
	for megaco@ietf.org; Wed, 09 Jul 2003 08:00:57 -0400
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 19aDd3-0006C0-00
	for megaco@ietf.org; Wed, 09 Jul 2003 08:00:57 -0400
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h69BxpQ07802;
	Wed, 9 Jul 2003 07:59:51 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLVYR00M; Wed, 9 Jul 2003 07:59:51 -0400
Received: from nortelnetworks.com (acart1d3.ca.nortel.com [47.129.129.79]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3RVWPB5L; Wed, 9 Jul 2003 07:59:51 -0400
Message-ID: <3F0C0380.9010307@nortelnetworks.com>
Date: Wed, 09 Jul 2003 07:58:56 -0400
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: "YAMAMOTO, Susumu" <yamamoto.susumu@lab.ntt.co.jp>
CC: megaco@ietf.org, tsuboi.shunnichi@lab.ntt.co.jp
Subject: Re: [Megaco] QoS package
References: <5.1.1.9.2.20030709110017.06086e90@imb.m.ecl.ntt.co.jp>
In-Reply-To: <5.1.1.9.2.20030709110017.06086e90@imb.m.ecl.ntt.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

France Telecom has such a proposal into SG 11.  If you have an ITU-T TIES account,
have a look at http://ties.itu.int/u/tsg11/sg11/bicc/common/france-0304/fra105r1.zip

YAMAMOTO, Susumu wrote:

> Hi all,
> 
> I am looking for a MEGACO package which could configure TOS value
> of RTP packets session by session with Add or Modify command. I found
> draft-madhubabu-megaco-qospackage-00 at some web sites, but the
> draft seems already expired.
> 
> Please let me know the current situation of standardization of the draft,
> or another latest solution for TOS operation if we have. I hope the
> standardization process for the draft might contiue in ITU or somewhere.
> 
> Thanks,
> -Susumu
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 


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



From megaco-admin@ietf.org  Thu Jul 10 15:37:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18811
	for <megaco-archive@lists.ietf.org>; Thu, 10 Jul 2003 15:37:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ahDx-000886-8O; Thu, 10 Jul 2003 15:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ahDO-00087S-Tn
	for megaco@optimus.ietf.org; Thu, 10 Jul 2003 15:36:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18789
	for <megaco@ietf.org>; Thu, 10 Jul 2003 15:36:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ahDN-0006YV-00
	for megaco@ietf.org; Thu, 10 Jul 2003 15:36:25 -0400
Received: from host217-45-197-114.in-addr.btopenworld.com ([217.45.197.114] helo=aegir.engineering.newport-networks.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ahDM-0006YR-00
	for megaco@ietf.org; Thu, 10 Jul 2003 15:36:24 -0400
Received: from EDLUFF ([134.22.36.66])
	(authenticated user edluff@newport-networks.com)
	by aegir.engineering.newport-networks.com
	for megaco@ietf.org;
	Thu, 10 Jul 2003 20:35:51 +0100
Reply-To: <ed.luff@newport-networks.com>
From: "Ed Luff" <ed.luff@newport-networks.com>
To: <megaco@ietf.org>
Date: Thu, 10 Jul 2003 15:36:10 -0400
Organization: Newport Networks
Message-ID: <005c01c3471a$84a4cae0$1703a8c0@EDLUFF>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_005D_01C346F8.FD932AE0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Subject: [Megaco] Megaco support for RFC 2833
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

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

All,
 
It does not appear as though a Megaco package exists to support RFC 2833
for RTP flow terminations.
 
I suppose the question would be whether the existing basic "DTMF
detection Package" should be extended, or whether a new package should
be defined.
 
A few additional questions and possible new requirements.
-          RFC 2833 defines the decimal encodings for DTMF named events
and E.182 line events.  Would a Megaco DigitMap be created, or would the
MGC and MG simply use the decimal encodings defined in RFC 2833?
-          As the RTP payload type for 'telephone-event' is established
dynamically, during the signaling between two clients (for example, two
SIP clients).  It would appear then that the RTP Payload type value
would need to be signaled from the MGC to the MG.
-          The MGC may request the MG to event notify based on the
'volume' and 'duration' of the event.
-          The MG may need to pass up the 'event', 'volume' and
'duration' values, as defined in the payload format for
'telephone-event'
 
Ed
 
Newport Networks Ltd.
www.newport-networks.com
office   (613)-591-8440
mobile (613)-864-1194
 

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

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C346F8.FC108280">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1509442077;
	mso-list-type:hybrid;
	mso-list-template-ids:168220826 960390152 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:11;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:21.0pt;
	mso-level-number-position:left;
	margin-left:21.0pt;
	text-indent:-.25in;
	font-family:Arial;
	mso-fareast-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>It does not appear as though a Megaco package exists =
to support
RFC 2833 for RTP flow terminations.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I suppose the question would be whether the existing =
basic &#8220;DTMF
detection Package&#8221; should be extended, or whether a new package =
should be
defined.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>A few additional questions and possible new =
requirements&#8230;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:21.0pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list 21.0pt'><![if !supportLists]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-family:Arial=
'><span
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>RFC 2833 defines the =
decimal
encodings for DTMF named events and E.182 line events.<span
style=3D'mso-spacerun:yes'>&nbsp; </span>Would a Megaco DigitMap be =
created, or
would the MGC and MG simply use the decimal encodings defined in RFC =
2833?<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:21.0pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list 21.0pt'><![if !supportLists]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-family:Arial=
'><span
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>As the RTP payload type for =
&#8216;telephone-event&#8217;
is established dynamically, during the signaling between two clients =
(for
example, two SIP clients).<span style=3D'mso-spacerun:yes'>&nbsp; =
</span>It would
appear then that the RTP Payload type value would need to be signaled =
from the
MGC to the MG.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:21.0pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list 21.0pt'><![if !supportLists]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-family:Arial=
'><span
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>The MGC may request the MG =
to event
notify based on the &#8216;volume&#8217; and &#8216;duration&#8217; of =
the
event.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:21.0pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list 21.0pt'><![if !supportLists]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-family:Arial=
'><span
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>The MG may need to pass up =
the &#8216;event&#8217;,
&#8216;volume&#8217; and &#8216;duration&#8217; values, as defined in =
the
payload format for =
&#8216;telephone-event&#8217;<o:p></o:p></span></font></p>

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

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;mso-no-proof:yes'>Newport Networks =
Ltd.</span></font><span
style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;mso-no-proof:yes'><a =
href=3D"http://www.newport-networks.com">www.newport-networks.com</a></sp=
an></font><span
style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;mso-no-proof:yes'>office &nbsp; =
(613)-591-8440</span></font><span
style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;mso-no-proof:yes'>mobile =
(613)-864-1194</span></font><o:p></o:p></p>

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

</div>

</body>

</html>

------=_NextPart_000_005D_01C346F8.FD932AE0--



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


From exim@www1.ietf.org  Thu Jul 10 15:37:37 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18827
	for <megaco-archive@odin.ietf.org>; Thu, 10 Jul 2003 15:37:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ahE5-00089a-Fd
	for megaco-archive@odin.ietf.org; Thu, 10 Jul 2003 15:37:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AJb9ni031342
	for megaco-archive@odin.ietf.org; Thu, 10 Jul 2003 15:37:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ahE5-00089R-2Y
	for megaco-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 15:37:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18808
	for <megaco-web-archive@ietf.org>; Thu, 10 Jul 2003 15:37:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ahE0-0006Yt-00
	for megaco-web-archive@ietf.org; Thu, 10 Jul 2003 15:37:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ahE0-0006Yp-00
	for megaco-web-archive@ietf.org; Thu, 10 Jul 2003 15:37:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ahDx-000886-8O; Thu, 10 Jul 2003 15:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ahDO-00087S-Tn
	for megaco@optimus.ietf.org; Thu, 10 Jul 2003 15:36:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18789
	for <megaco@ietf.org>; Thu, 10 Jul 2003 15:36:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ahDN-0006YV-00
	for megaco@ietf.org; Thu, 10 Jul 2003 15:36:25 -0400
Received: from host217-45-197-114.in-addr.btopenworld.com ([217.45.197.114] helo=aegir.engineering.newport-networks.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ahDM-0006YR-00
	for megaco@ietf.org; Thu, 10 Jul 2003 15:36:24 -0400
Received: from EDLUFF ([134.22.36.66])
	(authenticated user edluff@newport-networks.com)
	by aegir.engineering.newport-networks.com
	for megaco@ietf.org;
	Thu, 10 Jul 2003 20:35:51 +0100
Reply-To: <ed.luff@newport-networks.com>
From: "Ed Luff" <ed.luff@newport-networks.com>
To: <megaco@ietf.org>
Date: Thu, 10 Jul 2003 15:36:10 -0400
Organization: Newport Networks
Message-ID: <005c01c3471a$84a4cae0$1703a8c0@EDLUFF>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_005D_01C346F8.FD932AE0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Subject: [Megaco] Megaco support for RFC 2833
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

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

All,
 
It does not appear as though a Megaco package exists to support RFC 2833
for RTP flow terminations.
 
I suppose the question would be whether the existing basic "DTMF
detection Package" should be extended, or whether a new package should
be defined.
 
A few additional questions and possible new requirements.
-          RFC 2833 defines the decimal encodings for DTMF named events
and E.182 line events.  Would a Megaco DigitMap be created, or would the
MGC and MG simply use the decimal encodings defined in RFC 2833?
-          As the RTP payload type for 'telephone-event' is established
dynamically, during the signaling between two clients (for example, two
SIP clients).  It would appear then that the RTP Payload type value
would need to be signaled from the MGC to the MG.
-          The MGC may request the MG to event notify based on the
'volume' and 'duration' of the event.
-          The MG may need to pass up the 'event', 'volume' and
'duration' values, as defined in the payload format for
'telephone-event'
 
Ed
 
Newport Networks Ltd.
www.newport-networks.com
office   (613)-591-8440
mobile (613)-864-1194
 

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

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C346F8.FC108280">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1509442077;
	mso-list-type:hybrid;
	mso-list-template-ids:168220826 960390152 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:11;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:21.0pt;
	mso-level-number-position:left;
	margin-left:21.0pt;
	text-indent:-.25in;
	font-family:Arial;
	mso-fareast-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>It does not appear as though a Megaco package exists =
to support
RFC 2833 for RTP flow terminations.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I suppose the question would be whether the existing =
basic &#8220;DTMF
detection Package&#8221; should be extended, or whether a new package =
should be
defined.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>A few additional questions and possible new =
requirements&#8230;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:21.0pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list 21.0pt'><![if !supportLists]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-family:Arial=
'><span
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>RFC 2833 defines the =
decimal
encodings for DTMF named events and E.182 line events.<span
style=3D'mso-spacerun:yes'>&nbsp; </span>Would a Megaco DigitMap be =
created, or
would the MGC and MG simply use the decimal encodings defined in RFC =
2833?<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:21.0pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list 21.0pt'><![if !supportLists]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-family:Arial=
'><span
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>As the RTP payload type for =
&#8216;telephone-event&#8217;
is established dynamically, during the signaling between two clients =
(for
example, two SIP clients).<span style=3D'mso-spacerun:yes'>&nbsp; =
</span>It would
appear then that the RTP Payload type value would need to be signaled =
from the
MGC to the MG.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:21.0pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list 21.0pt'><![if !supportLists]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-family:Arial=
'><span
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>The MGC may request the MG =
to event
notify based on the &#8216;volume&#8217; and &#8216;duration&#8217; of =
the
event.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:21.0pt;text-indent:-.25in;mso-list:l0 level1 lfo1;
tab-stops:list 21.0pt'><![if !supportLists]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;mso-fareast-font-family:Arial=
'><span
style=3D'mso-list:Ignore'>-<font size=3D1 face=3D"Times New Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>The MG may need to pass up =
the &#8216;event&#8217;,
&#8216;volume&#8217; and &#8216;duration&#8217; values, as defined in =
the
payload format for =
&#8216;telephone-event&#8217;<o:p></o:p></span></font></p>

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

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;mso-no-proof:yes'>Newport Networks =
Ltd.</span></font><span
style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;mso-no-proof:yes'><a =
href=3D"http://www.newport-networks.com">www.newport-networks.com</a></sp=
an></font><span
style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;mso-no-proof:yes'>office &nbsp; =
(613)-591-8440</span></font><span
style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;mso-no-proof:yes'>mobile =
(613)-864-1194</span></font><o:p></o:p></p>

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

</div>

</body>

</html>

------=_NextPart_000_005D_01C346F8.FD932AE0--



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



From megaco-admin@ietf.org  Wed Jul 16 08:17:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27254
	for <megaco-archive@lists.ietf.org>; Wed, 16 Jul 2003 08:17:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clDR-0007Id-SM; Wed, 16 Jul 2003 08:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clCx-0007I9-Hv
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 08:16:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27231
	for <megaco@ietf.org>; Wed, 16 Jul 2003 08:16:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19clCw-0006XA-00
	for megaco@ietf.org; Wed, 16 Jul 2003 08:16:30 -0400
Received: from [4.19.224.196] (helo=wench.telica.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19clCg-0006X0-00
	for megaco@ietf.org; Wed, 16 Jul 2003 08:16:15 -0400
Received: by wench.telica.com with Internet Mail Service (5.5.2653.19)
	id <NT6J2NT6>; Wed, 16 Jul 2003 08:15:02 -0400
Message-ID: <C9AFC8E904D49C4593EB077A2E8402BA015109EF@wench.telica.com>
From: Brad Steinka <bsteinka@telica.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 16 Jul 2003 08:15:02 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Active Events
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>


When a termination is in a active Context and the MG receives a Modify for
the termination that contains an Event Descriptor
requesting the MG to detect specific events (ex.  flash / on-hook/
off-hook),  do these events REMAIN ACTIVE when
the termination is returned to the NULL context when the MG receives a
Subtract for the termination in question?

It is NOT clear in the RFC-3015 what happens to ACTIVE events / signals when
a termination is returned to the NULL context.

Thanks in advance for any clarification you can bring to this topic.




Brad Steinka
Director - Software Engineering
734 Forest Street, Building G, Suite 100
Marlboro, Ma.   01752
Tel:  508-480-0909  x154
Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
Web:   www.telica.com <http://www.telica.com>



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


From exim@www1.ietf.org  Wed Jul 16 08:17:42 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27269
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jul 2003 08:17:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clDf-0007K1-I1
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 08:17:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GCHF9D028139
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 08:17:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clDf-0007Jm-6B
	for megaco-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 08:17:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27248
	for <megaco-web-archive@ietf.org>; Wed, 16 Jul 2003 08:17:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19clDe-0006XR-00
	for megaco-web-archive@ietf.org; Wed, 16 Jul 2003 08:17:14 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19clDY-0006XL-00
	for megaco-web-archive@ietf.org; Wed, 16 Jul 2003 08:17:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clDR-0007Id-SM; Wed, 16 Jul 2003 08:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clCx-0007I9-Hv
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 08:16:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27231
	for <megaco@ietf.org>; Wed, 16 Jul 2003 08:16:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19clCw-0006XA-00
	for megaco@ietf.org; Wed, 16 Jul 2003 08:16:30 -0400
Received: from [4.19.224.196] (helo=wench.telica.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19clCg-0006X0-00
	for megaco@ietf.org; Wed, 16 Jul 2003 08:16:15 -0400
Received: by wench.telica.com with Internet Mail Service (5.5.2653.19)
	id <NT6J2NT6>; Wed, 16 Jul 2003 08:15:02 -0400
Message-ID: <C9AFC8E904D49C4593EB077A2E8402BA015109EF@wench.telica.com>
From: Brad Steinka <bsteinka@telica.com>
To: "'megaco@ietf.org'" <megaco@ietf.org>
Date: Wed, 16 Jul 2003 08:15:02 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Megaco] Active Events
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>


When a termination is in a active Context and the MG receives a Modify for
the termination that contains an Event Descriptor
requesting the MG to detect specific events (ex.  flash / on-hook/
off-hook),  do these events REMAIN ACTIVE when
the termination is returned to the NULL context when the MG receives a
Subtract for the termination in question?

It is NOT clear in the RFC-3015 what happens to ACTIVE events / signals when
a termination is returned to the NULL context.

Thanks in advance for any clarification you can bring to this topic.




Brad Steinka
Director - Software Engineering
734 Forest Street, Building G, Suite 100
Marlboro, Ma.   01752
Tel:  508-480-0909  x154
Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
Web:   www.telica.com <http://www.telica.com>



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



From megaco-admin@ietf.org  Wed Jul 16 08:24:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27416
	for <megaco-archive@lists.ietf.org>; Wed, 16 Jul 2003 08:24:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clKD-0007cA-34; Wed, 16 Jul 2003 08:24:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clJV-0007bd-Qt
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 08:23:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27373
	for <megaco@ietf.org>; Wed, 16 Jul 2003 08:23:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19clJH-0006Z8-00
	for megaco@ietf.org; Wed, 16 Jul 2003 08:23:03 -0400
Received: from [61.144.161.2] (helo=mta0.huawei.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19clJ5-0006Z3-00
	for megaco@ietf.org; Wed, 16 Jul 2003 08:22:52 -0400
Received: from z09303 (mta0.huawei.com [172.17.1.62])
 by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12
 2002)) with ESMTPA id <0HI400KFWAA633@mta0.huawei.com> for megaco@ietf.org;
 Wed, 16 Jul 2003 20:20:39 +0800 (CST)
Date: Tue, 16 Jul 2002 20:18:49 +0800
From: "Felix,Zhang" <lionking@huawei.com>
To: megaco@ietf.org
Message-id: <002101c22cc2$f61a6e00$35e5a051@ietf57.telekom.at>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <C9AFC8E904D49C4593EB077A2E8402BA015109EF@wench.telica.com>
Content-Transfer-Encoding: 7BIT
Subject: [Megaco] Looking for help.
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Sorry for trouble all of you, I'm a new comer to IETF.

Is anybody can tell me which work group  accepts comments of MGCP?

Is it be addressed in this work group?

----- Original Message ----- 
From: "Brad Steinka" <bsteinka@telica.com>
To: <megaco@ietf.org>
Sent: Wednesday, July 16, 2003 8:15 PM
Subject: [Megaco] Active Events


| 
| When a termination is in a active Context and the MG receives a Modify for
| the termination that contains an Event Descriptor
| requesting the MG to detect specific events (ex.  flash / on-hook/
| off-hook),  do these events REMAIN ACTIVE when
| the termination is returned to the NULL context when the MG receives a
| Subtract for the termination in question?
| 
| It is NOT clear in the RFC-3015 what happens to ACTIVE events / signals when
| a termination is returned to the NULL context.
| 
| Thanks in advance for any clarification you can bring to this topic.
| 
| 
| 
| 
| Brad Steinka
| Director - Software Engineering
| 734 Forest Street, Building G, Suite 100
| Marlboro, Ma.   01752
| Tel:  508-480-0909  x154
| Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
| Web:   www.telica.com <http://www.telica.com>
| 
| 
| 
| _______________________________________________
| Megaco mailing list
| Megaco@ietf.org
| https://www1.ietf.org/mailman/listinfo/megaco

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


From exim@www1.ietf.org  Wed Jul 16 08:24:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27434
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jul 2003 08:24:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clKK-0007d0-Gd
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 08:24:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GCO8eQ029316
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 08:24:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clKK-0007cl-7y
	for megaco-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 08:24:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27407
	for <megaco-web-archive@ietf.org>; Wed, 16 Jul 2003 08:24:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19clKJ-0006Zc-00
	for megaco-web-archive@ietf.org; Wed, 16 Jul 2003 08:24:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19clKD-0006ZZ-00
	for megaco-web-archive@ietf.org; Wed, 16 Jul 2003 08:24:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clKD-0007cA-34; Wed, 16 Jul 2003 08:24:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19clJV-0007bd-Qt
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 08:23:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27373
	for <megaco@ietf.org>; Wed, 16 Jul 2003 08:23:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19clJH-0006Z8-00
	for megaco@ietf.org; Wed, 16 Jul 2003 08:23:03 -0400
Received: from [61.144.161.2] (helo=mta0.huawei.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19clJ5-0006Z3-00
	for megaco@ietf.org; Wed, 16 Jul 2003 08:22:52 -0400
Received: from z09303 (mta0.huawei.com [172.17.1.62])
 by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12
 2002)) with ESMTPA id <0HI400KFWAA633@mta0.huawei.com> for megaco@ietf.org;
 Wed, 16 Jul 2003 20:20:39 +0800 (CST)
Date: Tue, 16 Jul 2002 20:18:49 +0800
From: "Felix,Zhang" <lionking@huawei.com>
To: megaco@ietf.org
Message-id: <002101c22cc2$f61a6e00$35e5a051@ietf57.telekom.at>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <C9AFC8E904D49C4593EB077A2E8402BA015109EF@wench.telica.com>
Content-Transfer-Encoding: 7BIT
Subject: [Megaco] Looking for help.
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Sorry for trouble all of you, I'm a new comer to IETF.

Is anybody can tell me which work group  accepts comments of MGCP?

Is it be addressed in this work group?

----- Original Message ----- 
From: "Brad Steinka" <bsteinka@telica.com>
To: <megaco@ietf.org>
Sent: Wednesday, July 16, 2003 8:15 PM
Subject: [Megaco] Active Events


| 
| When a termination is in a active Context and the MG receives a Modify for
| the termination that contains an Event Descriptor
| requesting the MG to detect specific events (ex.  flash / on-hook/
| off-hook),  do these events REMAIN ACTIVE when
| the termination is returned to the NULL context when the MG receives a
| Subtract for the termination in question?
| 
| It is NOT clear in the RFC-3015 what happens to ACTIVE events / signals when
| a termination is returned to the NULL context.
| 
| Thanks in advance for any clarification you can bring to this topic.
| 
| 
| 
| 
| Brad Steinka
| Director - Software Engineering
| 734 Forest Street, Building G, Suite 100
| Marlboro, Ma.   01752
| Tel:  508-480-0909  x154
| Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
| Web:   www.telica.com <http://www.telica.com>
| 
| 
| 
| _______________________________________________
| Megaco mailing list
| Megaco@ietf.org
| https://www1.ietf.org/mailman/listinfo/megaco

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



From megaco-admin@ietf.org  Wed Jul 16 09:21:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28979
	for <megaco-archive@lists.ietf.org>; Wed, 16 Jul 2003 09:21:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cmDO-00022n-PA; Wed, 16 Jul 2003 09:21:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cmD9-000229-3q
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 09:20:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28969
	for <megaco@ietf.org>; Wed, 16 Jul 2003 09:20:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmD7-0006yT-00
	for megaco@ietf.org; Wed, 16 Jul 2003 09:20:45 -0400
Received: from mail.utstar.com ([65.200.123.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmCw-0006yI-00
	for megaco@ietf.org; Wed, 16 Jul 2003 09:20:34 -0400
Received: from balanew (balanew [172.16.40.43])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id h6GDK1f25560;
	Wed, 16 Jul 2003 09:20:01 -0400 (EDT)
Reply-To: <bs@utstar.com>
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Felix,Zhang'" <lionking@huawei.com>
Cc: <megaco@ietf.org>
Subject: RE: [Megaco] Looking for help.
Date: Wed, 16 Jul 2003 09:19:51 -0400
Organization: UTStarcom Inc
Message-ID: <002b01c34b9c$f1228aa0$2b2810ac@balanew>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <002101c22cc2$f61a6e00$35e5a051@ietf57.telekom.at>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

You can send your MGCP comments to mgcp@vovida.org or
MGCP@LISTSERV.PULVER.COM

Thanks,
Bala
=20

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Felix,Zhang
Sent: Tuesday, July 16, 2002 8:19 AM
To: megaco@ietf.org
Subject: [Megaco] Looking for help.

Sorry for trouble all of you, I'm a new comer to IETF.

Is anybody can tell me which work group  accepts comments of MGCP?

Is it be addressed in this work group?

----- Original Message -----=20
From: "Brad Steinka" <bsteinka@telica.com>
To: <megaco@ietf.org>
Sent: Wednesday, July 16, 2003 8:15 PM
Subject: [Megaco] Active Events


|=20
| When a termination is in a active Context and the MG receives a Modify =
for
| the termination that contains an Event Descriptor
| requesting the MG to detect specific events (ex.  flash / on-hook/
| off-hook),  do these events REMAIN ACTIVE when
| the termination is returned to the NULL context when the MG receives a
| Subtract for the termination in question?
|=20
| It is NOT clear in the RFC-3015 what happens to ACTIVE events / =
signals
when
| a termination is returned to the NULL context.
|=20
| Thanks in advance for any clarification you can bring to this topic.
|=20
|=20
|=20
|=20
| Brad Steinka
| Director - Software Engineering
| 734 Forest Street, Building G, Suite 100
| Marlboro, Ma.   01752
| Tel:  508-480-0909  x154
| Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
| Web:   www.telica.com <http://www.telica.com>
|=20
|=20
|=20
| _______________________________________________
| Megaco mailing list
| Megaco@ietf.org
| https://www1.ietf.org/mailman/listinfo/megaco

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


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


From exim@www1.ietf.org  Wed Jul 16 09:21:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29006
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jul 2003 09:21:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cmDW-00024k-1M
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 09:21:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GDLAIC007972
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 09:21:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cmDV-00024V-UW
	for megaco-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 09:21:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28975
	for <megaco-web-archive@ietf.org>; Wed, 16 Jul 2003 09:21:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmDU-0006ya-00
	for megaco-web-archive@ietf.org; Wed, 16 Jul 2003 09:21:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmDO-0006yX-00
	for megaco-web-archive@ietf.org; Wed, 16 Jul 2003 09:21:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cmDO-00022n-PA; Wed, 16 Jul 2003 09:21:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cmD9-000229-3q
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 09:20:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28969
	for <megaco@ietf.org>; Wed, 16 Jul 2003 09:20:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmD7-0006yT-00
	for megaco@ietf.org; Wed, 16 Jul 2003 09:20:45 -0400
Received: from mail.utstar.com ([65.200.123.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cmCw-0006yI-00
	for megaco@ietf.org; Wed, 16 Jul 2003 09:20:34 -0400
Received: from balanew (balanew [172.16.40.43])
	by mail.utstar.com (8.11.3/8.11.3) with ESMTP id h6GDK1f25560;
	Wed, 16 Jul 2003 09:20:01 -0400 (EDT)
Reply-To: <bs@utstar.com>
From: "Balasubramanian Pitchandi" <bs@utstar.com>
To: "'Felix,Zhang'" <lionking@huawei.com>
Cc: <megaco@ietf.org>
Subject: RE: [Megaco] Looking for help.
Date: Wed, 16 Jul 2003 09:19:51 -0400
Organization: UTStarcom Inc
Message-ID: <002b01c34b9c$f1228aa0$2b2810ac@balanew>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <002101c22cc2$f61a6e00$35e5a051@ietf57.telekom.at>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

You can send your MGCP comments to mgcp@vovida.org or
MGCP@LISTSERV.PULVER.COM

Thanks,
Bala
=20

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On Behalf Of
Felix,Zhang
Sent: Tuesday, July 16, 2002 8:19 AM
To: megaco@ietf.org
Subject: [Megaco] Looking for help.

Sorry for trouble all of you, I'm a new comer to IETF.

Is anybody can tell me which work group  accepts comments of MGCP?

Is it be addressed in this work group?

----- Original Message -----=20
From: "Brad Steinka" <bsteinka@telica.com>
To: <megaco@ietf.org>
Sent: Wednesday, July 16, 2003 8:15 PM
Subject: [Megaco] Active Events


|=20
| When a termination is in a active Context and the MG receives a Modify =
for
| the termination that contains an Event Descriptor
| requesting the MG to detect specific events (ex.  flash / on-hook/
| off-hook),  do these events REMAIN ACTIVE when
| the termination is returned to the NULL context when the MG receives a
| Subtract for the termination in question?
|=20
| It is NOT clear in the RFC-3015 what happens to ACTIVE events / =
signals
when
| a termination is returned to the NULL context.
|=20
| Thanks in advance for any clarification you can bring to this topic.
|=20
|=20
|=20
|=20
| Brad Steinka
| Director - Software Engineering
| 734 Forest Street, Building G, Suite 100
| Marlboro, Ma.   01752
| Tel:  508-480-0909  x154
| Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
| Web:   www.telica.com <http://www.telica.com>
|=20
|=20
|=20
| _______________________________________________
| Megaco mailing list
| Megaco@ietf.org
| https://www1.ietf.org/mailman/listinfo/megaco

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


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



From megaco-admin@ietf.org  Wed Jul 16 10:36:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03944
	for <megaco-archive@lists.ietf.org>; Wed, 16 Jul 2003 10:36:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnNw-0006oA-LJ; Wed, 16 Jul 2003 10:36:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnNG-0006kZ-4A
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 10:35:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03860
	for <megaco@ietf.org>; Wed, 16 Jul 2003 10:35:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cnNB-0007nc-00
	for megaco@ietf.org; Wed, 16 Jul 2003 10:35:13 -0400
Received: from [202.41.72.121] (helo=ws9.cdotb.ernet.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cnMx-0007kd-00
	for megaco@ietf.org; Wed, 16 Jul 2003 10:35:01 -0400
Received: from cdotb.ernet.in ([192.168.51.214])
	by ws9.cdotb.ernet.in (8.9.3/8.9.3) with ESMTP id TAA07973
	for <megaco@ietf.org>; Wed, 16 Jul 2003 19:37:48 +0500 (GMT+0500)
Message-ID: <3F155FB2.3010803@cdotb.ernet.in>
Date: Wed, 16 Jul 2003 19:52:42 +0530
From: Titty Thomas <titty@cdotb.ernet.in>
Reply-To: titty@cdotb.ernet.in
Organization: Centre for Development of Telematics
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Subtract before Add reply
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,
      
       Can the MGC subtract a termination after issuing an add command

       but before it got the add reply.

       If so, what should be the context id and the termination id (if 
MGC has added
     
       an ephemeral termination) to be used in the subtract command.

Warm regards,
-- Titty

-- 
Two roads diverged in a wood, and I took the one less traveled by,
And that has made all the difference.



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


From exim@www1.ietf.org  Wed Jul 16 10:37:02 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04007
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jul 2003 10:37:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnOR-0006rD-VY
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 10:36:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GEaVmJ026353
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 10:36:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnOR-0006qy-QN
	for megaco-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 10:36:31 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03945
	for <megaco-web-archive@ietf.org>; Wed, 16 Jul 2003 10:36:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnNw-0006oA-LJ; Wed, 16 Jul 2003 10:36:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnNG-0006kZ-4A
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 10:35:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03860
	for <megaco@ietf.org>; Wed, 16 Jul 2003 10:35:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cnNB-0007nc-00
	for megaco@ietf.org; Wed, 16 Jul 2003 10:35:13 -0400
Received: from [202.41.72.121] (helo=ws9.cdotb.ernet.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cnMx-0007kd-00
	for megaco@ietf.org; Wed, 16 Jul 2003 10:35:01 -0400
Received: from cdotb.ernet.in ([192.168.51.214])
	by ws9.cdotb.ernet.in (8.9.3/8.9.3) with ESMTP id TAA07973
	for <megaco@ietf.org>; Wed, 16 Jul 2003 19:37:48 +0500 (GMT+0500)
Message-ID: <3F155FB2.3010803@cdotb.ernet.in>
Date: Wed, 16 Jul 2003 19:52:42 +0530
From: Titty Thomas <titty@cdotb.ernet.in>
Reply-To: titty@cdotb.ernet.in
Organization: Centre for Development of Telematics
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Subtract before Add reply
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,
      
       Can the MGC subtract a termination after issuing an add command

       but before it got the add reply.

       If so, what should be the context id and the termination id (if 
MGC has added
     
       an ephemeral termination) to be used in the subtract command.

Warm regards,
-- Titty

-- 
Two roads diverged in a wood, and I took the one less traveled by,
And that has made all the difference.



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



From megaco-admin@ietf.org  Wed Jul 16 10:44:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04424
	for <megaco-archive@lists.ietf.org>; Wed, 16 Jul 2003 10:44:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnVh-0007Sl-GU; Wed, 16 Jul 2003 10:44:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnV9-0007Qg-5s
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 10:43:27 -0400
Received: from zrtps06s.nortelnetworks.com (zrtps06s.nortelnetworks.com [47.140.48.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04370
	for <megaco@ietf.org>; Wed, 16 Jul 2003 10:43:21 -0400 (EDT)
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6GEgg214498
	for <megaco@ietf.org>; Wed, 16 Jul 2003 10:42:42 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NQAZASPQ>; Wed, 16 Jul 2003 10:42:39 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C0A6AF06F@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "Felix,Zhang" <lionking@huawei.com>, megaco@ietf.org
Subject: RE: [Megaco] Looking for help.
Date: Wed, 16 Jul 2003 10:42:36 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

MGCP is not the product of an IETF Working Group, therefore, there is no WG
that would take comments on it.  I believe others have posted the address of
the appropriate mailing list for MGCP.

Kevin

-----Original Message-----
From: Felix,Zhang [mailto:lionking@huawei.com] 
Sent: Tuesday, July 16, 2002 8:19 AM
To: megaco@ietf.org
Subject: [Megaco] Looking for help.


Sorry for trouble all of you, I'm a new comer to IETF.

Is anybody can tell me which work group  accepts comments of MGCP?

Is it be addressed in this work group?

----- Original Message ----- 
From: "Brad Steinka" <bsteinka@telica.com>
To: <megaco@ietf.org>
Sent: Wednesday, July 16, 2003 8:15 PM
Subject: [Megaco] Active Events


| 
| When a termination is in a active Context and the MG receives a Modify 
| for the termination that contains an Event Descriptor requesting the 
| MG to detect specific events (ex.  flash / on-hook/ off-hook),  do 
| these events REMAIN ACTIVE when the termination is returned to the 
| NULL context when the MG receives a Subtract for the termination in 
| question?
| 
| It is NOT clear in the RFC-3015 what happens to ACTIVE events / 
| signals when a termination is returned to the NULL context.
| 
| Thanks in advance for any clarification you can bring to this topic.
| 
| 
| 
| 
| Brad Steinka
| Director - Software Engineering
| 734 Forest Street, Building G, Suite 100
| Marlboro, Ma.   01752
| Tel:  508-480-0909  x154
| Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
| Web:   www.telica.com <http://www.telica.com>
| 
| 
| 
| _______________________________________________
| Megaco mailing list
| Megaco@ietf.org
| https://www1.ietf.org/mailman/listinfo/megaco

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

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


From exim@www1.ietf.org  Wed Jul 16 10:44:57 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04480
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jul 2003 10:44:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnWC-0007ZD-WE
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 10:44:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GEiW4x029081
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 10:44:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnWC-0007Yy-Pt
	for megaco-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 10:44:32 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04426
	for <megaco-web-archive@ietf.org>; Wed, 16 Jul 2003 10:44:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnVh-0007Sl-GU; Wed, 16 Jul 2003 10:44:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cnV9-0007Qg-5s
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 10:43:27 -0400
Received: from zrtps06s.nortelnetworks.com (zrtps06s.nortelnetworks.com [47.140.48.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04370
	for <megaco@ietf.org>; Wed, 16 Jul 2003 10:43:21 -0400 (EDT)
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6GEgg214498
	for <megaco@ietf.org>; Wed, 16 Jul 2003 10:42:42 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NQAZASPQ>; Wed, 16 Jul 2003 10:42:39 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C0A6AF06F@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: "Felix,Zhang" <lionking@huawei.com>, megaco@ietf.org
Subject: RE: [Megaco] Looking for help.
Date: Wed, 16 Jul 2003 10:42:36 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

MGCP is not the product of an IETF Working Group, therefore, there is no WG
that would take comments on it.  I believe others have posted the address of
the appropriate mailing list for MGCP.

Kevin

-----Original Message-----
From: Felix,Zhang [mailto:lionking@huawei.com] 
Sent: Tuesday, July 16, 2002 8:19 AM
To: megaco@ietf.org
Subject: [Megaco] Looking for help.


Sorry for trouble all of you, I'm a new comer to IETF.

Is anybody can tell me which work group  accepts comments of MGCP?

Is it be addressed in this work group?

----- Original Message ----- 
From: "Brad Steinka" <bsteinka@telica.com>
To: <megaco@ietf.org>
Sent: Wednesday, July 16, 2003 8:15 PM
Subject: [Megaco] Active Events


| 
| When a termination is in a active Context and the MG receives a Modify 
| for the termination that contains an Event Descriptor requesting the 
| MG to detect specific events (ex.  flash / on-hook/ off-hook),  do 
| these events REMAIN ACTIVE when the termination is returned to the 
| NULL context when the MG receives a Subtract for the termination in 
| question?
| 
| It is NOT clear in the RFC-3015 what happens to ACTIVE events / 
| signals when a termination is returned to the NULL context.
| 
| Thanks in advance for any clarification you can bring to this topic.
| 
| 
| 
| 
| Brad Steinka
| Director - Software Engineering
| 734 Forest Street, Building G, Suite 100
| Marlboro, Ma.   01752
| Tel:  508-480-0909  x154
| Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
| Web:   www.telica.com <http://www.telica.com>
| 
| 
| 
| _______________________________________________
| Megaco mailing list
| Megaco@ietf.org
| https://www1.ietf.org/mailman/listinfo/megaco

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

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



From megaco-admin@ietf.org  Wed Jul 16 13:31:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09473
	for <megaco-archive@lists.ietf.org>; Wed, 16 Jul 2003 13:31:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cq7J-0000CQ-9P; Wed, 16 Jul 2003 13:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cq70-0000BV-Ow
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 13:30:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09431
	for <megaco@ietf.org>; Wed, 16 Jul 2003 13:30:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cq6y-0001Rq-00
	for megaco@ietf.org; Wed, 16 Jul 2003 13:30:40 -0400
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cq6n-0001RJ-00
	for megaco@ietf.org; Wed, 16 Jul 2003 13:30:29 -0400
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6GHTVi28078;
	Wed, 16 Jul 2003 13:29:31 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLVYVN7W; Wed, 16 Jul 2003 13:29:32 -0400
Received: from nortelnetworks.com (acart3zr.ca.nortel.com [47.129.49.95]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3RVWP1HK; Wed, 16 Jul 2003 13:29:30 -0400
Message-ID: <3F158B79.2000805@nortelnetworks.com>
Date: Wed, 16 Jul 2003 19:29:29 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: Brad Steinka <bsteinka@telica.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Active Events
References: <C9AFC8E904D49C4593EB077A2E8402BA015109EF@wench.telica.com>
In-Reply-To: <C9AFC8E904D49C4593EB077A2E8402BA015109EF@wench.telica.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Afraid not.  You have to do the modification after the subtract.  I'm a bit busy to 
look up the reference, but it's early in section 6.

Brad Steinka wrote:

> When a termination is in a active Context and the MG receives a Modify for
> the termination that contains an Event Descriptor
> requesting the MG to detect specific events (ex.  flash / on-hook/
> off-hook),  do these events REMAIN ACTIVE when
> the termination is returned to the NULL context when the MG receives a
> Subtract for the termination in question?
> 
> It is NOT clear in the RFC-3015 what happens to ACTIVE events / signals when
> a termination is returned to the NULL context.
> 
> Thanks in advance for any clarification you can bring to this topic.
> 
> 
> 
> 
> Brad Steinka
> Director - Software Engineering
> 734 Forest Street, Building G, Suite 100
> Marlboro, Ma.   01752
> Tel:  508-480-0909  x154
> Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
> Web:   www.telica.com <http://www.telica.com>
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 


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


From exim@www1.ietf.org  Wed Jul 16 13:31:55 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09510
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jul 2003 13:31:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cq7k-0000MS-JM
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 13:31:28 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GHVSkD001382
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 13:31:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cq7k-0000MD-Eu
	for megaco-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 13:31:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09468
	for <megaco-web-archive@ietf.org>; Wed, 16 Jul 2003 13:31:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cq7d-0001SE-00
	for megaco-web-archive@ietf.org; Wed, 16 Jul 2003 13:31:21 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cq7I-0001S2-00
	for megaco-web-archive@ietf.org; Wed, 16 Jul 2003 13:31:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cq7J-0000CQ-9P; Wed, 16 Jul 2003 13:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cq70-0000BV-Ow
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 13:30:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09431
	for <megaco@ietf.org>; Wed, 16 Jul 2003 13:30:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cq6y-0001Rq-00
	for megaco@ietf.org; Wed, 16 Jul 2003 13:30:40 -0400
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cq6n-0001RJ-00
	for megaco@ietf.org; Wed, 16 Jul 2003 13:30:29 -0400
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6GHTVi28078;
	Wed, 16 Jul 2003 13:29:31 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLVYVN7W; Wed, 16 Jul 2003 13:29:32 -0400
Received: from nortelnetworks.com (acart3zr.ca.nortel.com [47.129.49.95]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3RVWP1HK; Wed, 16 Jul 2003 13:29:30 -0400
Message-ID: <3F158B79.2000805@nortelnetworks.com>
Date: Wed, 16 Jul 2003 19:29:29 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: Brad Steinka <bsteinka@telica.com>
CC: "'megaco@ietf.org'" <megaco@ietf.org>
Subject: Re: [Megaco] Active Events
References: <C9AFC8E904D49C4593EB077A2E8402BA015109EF@wench.telica.com>
In-Reply-To: <C9AFC8E904D49C4593EB077A2E8402BA015109EF@wench.telica.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Afraid not.  You have to do the modification after the subtract.  I'm a bit busy to 
look up the reference, but it's early in section 6.

Brad Steinka wrote:

> When a termination is in a active Context and the MG receives a Modify for
> the termination that contains an Event Descriptor
> requesting the MG to detect specific events (ex.  flash / on-hook/
> off-hook),  do these events REMAIN ACTIVE when
> the termination is returned to the NULL context when the MG receives a
> Subtract for the termination in question?
> 
> It is NOT clear in the RFC-3015 what happens to ACTIVE events / signals when
> a termination is returned to the NULL context.
> 
> Thanks in advance for any clarification you can bring to this topic.
> 
> 
> 
> 
> Brad Steinka
> Director - Software Engineering
> 734 Forest Street, Building G, Suite 100
> Marlboro, Ma.   01752
> Tel:  508-480-0909  x154
> Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
> Web:   www.telica.com <http://www.telica.com>
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 


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



From megaco-admin@ietf.org  Wed Jul 16 14:38:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11878
	for <megaco-archive@lists.ietf.org>; Wed, 16 Jul 2003 14:38:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19crAA-0004qW-29; Wed, 16 Jul 2003 14:38:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cr9s-0004kl-3K
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 14:37:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11852
	for <megaco@ietf.org>; Wed, 16 Jul 2003 14:37:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cr9p-000226-00
	for megaco@ietf.org; Wed, 16 Jul 2003 14:37:41 -0400
Received: from amethyst.syndeocorp.com ([4.21.34.131] helo=syndeocorp.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cr9e-00021S-00
	for megaco@ietf.org; Wed, 16 Jul 2003 14:37:30 -0400
Received: from madhupc (madhu-pc.syndeocorp.com [4.21.35.182])
	by syndeocorp.com (Switch-2.0.1/Switch-2.0.1) with SMTP id h6GIZL908489;
	Wed, 16 Jul 2003 11:35:21 -0700 (PDT)
Reply-To: <madhu@syndeocorp.com>
From: "Madhu Babu Brahmanapally" <madhu@syndeocorp.com>
To: "'Tom Taylor'" <taylor@nortelnetworks.com>,
        "'Brad Steinka'" <bsteinka@telica.com>
Cc: <megaco@ietf.org>
Subject: RE: [Megaco] Active Events
Date: Wed, 16 Jul 2003 11:38:03 -0700
Message-ID: <03aa01c34bc9$64f31db0$b6231504@madhupc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300
In-Reply-To: <3F158B79.2000805@nortelnetworks.com>
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi All,
I think that the Subtract on a termination is enough to make the event
descriptor empty. Section 6.2.4 indicates "If not provisioned otherwise, all
descriptors except TerminationState and LocalControl default to   empty/"no
value" when a Termination is first created or returned to   the null
Context.".
Regards
Madhubabu Brahmanapally.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Tom Taylor
Sent: Wednesday, July 16, 2003 10:29 AM
To: Brad Steinka
Cc: 'megaco@ietf.org'
Subject: Re: [Megaco] Active Events


Afraid not.  You have to do the modification after the subtract.  I'm a bit
busy to
look up the reference, but it's early in section 6.

Brad Steinka wrote:

> When a termination is in a active Context and the MG receives a Modify for
> the termination that contains an Event Descriptor
> requesting the MG to detect specific events (ex.  flash / on-hook/
> off-hook),  do these events REMAIN ACTIVE when
> the termination is returned to the NULL context when the MG receives a
> Subtract for the termination in question?
>
> It is NOT clear in the RFC-3015 what happens to ACTIVE events / signals
when
> a termination is returned to the NULL context.
>
> Thanks in advance for any clarification you can bring to this topic.
>
>
>
>
> Brad Steinka
> Director - Software Engineering
> 734 Forest Street, Building G, Suite 100
> Marlboro, Ma.   01752
> Tel:  508-480-0909  x154
> Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
> Web:   www.telica.com <http://www.telica.com>
>
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>


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


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


From exim@www1.ietf.org  Wed Jul 16 14:38:59 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11934
	for <megaco-archive@odin.ietf.org>; Wed, 16 Jul 2003 14:38:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19crAf-0004v5-99
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 14:38:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GIcXjO018907
	for megaco-archive@odin.ietf.org; Wed, 16 Jul 2003 14:38:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19crAf-0004us-6A
	for megaco-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 14:38:33 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11879
	for <megaco-web-archive@ietf.org>; Wed, 16 Jul 2003 14:38:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19crAA-0004qW-29; Wed, 16 Jul 2003 14:38:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19cr9s-0004kl-3K
	for megaco@optimus.ietf.org; Wed, 16 Jul 2003 14:37:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11852
	for <megaco@ietf.org>; Wed, 16 Jul 2003 14:37:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19cr9p-000226-00
	for megaco@ietf.org; Wed, 16 Jul 2003 14:37:41 -0400
Received: from amethyst.syndeocorp.com ([4.21.34.131] helo=syndeocorp.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19cr9e-00021S-00
	for megaco@ietf.org; Wed, 16 Jul 2003 14:37:30 -0400
Received: from madhupc (madhu-pc.syndeocorp.com [4.21.35.182])
	by syndeocorp.com (Switch-2.0.1/Switch-2.0.1) with SMTP id h6GIZL908489;
	Wed, 16 Jul 2003 11:35:21 -0700 (PDT)
Reply-To: <madhu@syndeocorp.com>
From: "Madhu Babu Brahmanapally" <madhu@syndeocorp.com>
To: "'Tom Taylor'" <taylor@nortelnetworks.com>,
        "'Brad Steinka'" <bsteinka@telica.com>
Cc: <megaco@ietf.org>
Subject: RE: [Megaco] Active Events
Date: Wed, 16 Jul 2003 11:38:03 -0700
Message-ID: <03aa01c34bc9$64f31db0$b6231504@madhupc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300
In-Reply-To: <3F158B79.2000805@nortelnetworks.com>
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi All,
I think that the Subtract on a termination is enough to make the event
descriptor empty. Section 6.2.4 indicates "If not provisioned otherwise, all
descriptors except TerminationState and LocalControl default to   empty/"no
value" when a Termination is first created or returned to   the null
Context.".
Regards
Madhubabu Brahmanapally.

-----Original Message-----
From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
Tom Taylor
Sent: Wednesday, July 16, 2003 10:29 AM
To: Brad Steinka
Cc: 'megaco@ietf.org'
Subject: Re: [Megaco] Active Events


Afraid not.  You have to do the modification after the subtract.  I'm a bit
busy to
look up the reference, but it's early in section 6.

Brad Steinka wrote:

> When a termination is in a active Context and the MG receives a Modify for
> the termination that contains an Event Descriptor
> requesting the MG to detect specific events (ex.  flash / on-hook/
> off-hook),  do these events REMAIN ACTIVE when
> the termination is returned to the NULL context when the MG receives a
> Subtract for the termination in question?
>
> It is NOT clear in the RFC-3015 what happens to ACTIVE events / signals
when
> a termination is returned to the NULL context.
>
> Thanks in advance for any clarification you can bring to this topic.
>
>
>
>
> Brad Steinka
> Director - Software Engineering
> 734 Forest Street, Building G, Suite 100
> Marlboro, Ma.   01752
> Tel:  508-480-0909  x154
> Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
> Web:   www.telica.com <http://www.telica.com>
>
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>


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


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



From megaco-admin@ietf.org  Thu Jul 17 02:42:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18096
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 02:42:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2Sm-0004qZ-S6; Thu, 17 Jul 2003 02:42:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2Rp-0004p7-AW
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 02:41:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17994
	for <megaco@ietf.org>; Thu, 17 Jul 2003 02:40:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d2Rl-0001iW-00
	for megaco@ietf.org; Thu, 17 Jul 2003 02:40:57 -0400
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d2Ra-0001i6-00
	for megaco@ietf.org; Thu, 17 Jul 2003 02:40:46 -0400
Received: from zcard307.ca.nortel.com (americasm01.nt.com [47.129.242.67])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6H6dWh01316;
	Thu, 17 Jul 2003 02:39:32 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 31Q1HS6F; Thu, 17 Jul 2003 02:39:32 -0400
Received: from nortelnetworks.com (acart3xf.ca.nortel.com [47.129.49.20]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3RVWP1NF; Thu, 17 Jul 2003 02:39:32 -0400
Message-ID: <3F1644A0.1010804@nortelnetworks.com>
Date: Thu, 17 Jul 2003 08:39:28 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: madhu@syndeocorp.com
CC: "'Brad Steinka'" <bsteinka@telica.com>, megaco@ietf.org
Subject: Re: [Megaco] Active Events
References: <03aa01c34bc9$64f31db0$b6231504@madhupc>
In-Reply-To: <03aa01c34bc9$64f31db0$b6231504@madhupc>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

That's the one.  We deliberately did it that way on the basis of the principle of 
least surprise.  It makes it easy for the MGC to restore terminations to a known 
state when it has to.

Madhu Babu Brahmanapally wrote:

> Hi All,
> I think that the Subtract on a termination is enough to make the event
> descriptor empty. Section 6.2.4 indicates "If not provisioned otherwise, all
> descriptors except TerminationState and LocalControl default to   empty/"no
> value" when a Termination is first created or returned to   the null
> Context.".
> Regards
> Madhubabu Brahmanapally.
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Tom Taylor
> Sent: Wednesday, July 16, 2003 10:29 AM
> To: Brad Steinka
> Cc: 'megaco@ietf.org'
> Subject: Re: [Megaco] Active Events
> 
> 
> Afraid not.  You have to do the modification after the subtract.  I'm a bit
> busy to
> look up the reference, but it's early in section 6.
> 
> Brad Steinka wrote:
> 
> 
>>When a termination is in a active Context and the MG receives a Modify for
>>the termination that contains an Event Descriptor
>>requesting the MG to detect specific events (ex.  flash / on-hook/
>>off-hook),  do these events REMAIN ACTIVE when
>>the termination is returned to the NULL context when the MG receives a
>>Subtract for the termination in question?
>>
>>It is NOT clear in the RFC-3015 what happens to ACTIVE events / signals
> 
> when
> 
>>a termination is returned to the NULL context.
>>
>>Thanks in advance for any clarification you can bring to this topic.
>>
>>
>>
>>
>>Brad Steinka
>>Director - Software Engineering
>>734 Forest Street, Building G, Suite 100
>>Marlboro, Ma.   01752
>>Tel:  508-480-0909  x154
>>Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
>>Web:   www.telica.com <http://www.telica.com>
>>
>>
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 


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


From exim@www1.ietf.org  Thu Jul 17 02:42:34 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18135
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 02:42:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2Su-0004rr-Gs
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 02:42:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6H6g88h018707
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 02:42:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2Su-0004re-3c
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 02:42:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18089
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 02:42:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d2Sq-0001jN-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 02:42:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d2Sk-0001jK-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 02:41:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2Sm-0004qZ-S6; Thu, 17 Jul 2003 02:42:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2Rp-0004p7-AW
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 02:41:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17994
	for <megaco@ietf.org>; Thu, 17 Jul 2003 02:40:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d2Rl-0001iW-00
	for megaco@ietf.org; Thu, 17 Jul 2003 02:40:57 -0400
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d2Ra-0001i6-00
	for megaco@ietf.org; Thu, 17 Jul 2003 02:40:46 -0400
Received: from zcard307.ca.nortel.com (americasm01.nt.com [47.129.242.67])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6H6dWh01316;
	Thu, 17 Jul 2003 02:39:32 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 31Q1HS6F; Thu, 17 Jul 2003 02:39:32 -0400
Received: from nortelnetworks.com (acart3xf.ca.nortel.com [47.129.49.20]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3RVWP1NF; Thu, 17 Jul 2003 02:39:32 -0400
Message-ID: <3F1644A0.1010804@nortelnetworks.com>
Date: Thu, 17 Jul 2003 08:39:28 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: madhu@syndeocorp.com
CC: "'Brad Steinka'" <bsteinka@telica.com>, megaco@ietf.org
Subject: Re: [Megaco] Active Events
References: <03aa01c34bc9$64f31db0$b6231504@madhupc>
In-Reply-To: <03aa01c34bc9$64f31db0$b6231504@madhupc>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

That's the one.  We deliberately did it that way on the basis of the principle of 
least surprise.  It makes it easy for the MGC to restore terminations to a known 
state when it has to.

Madhu Babu Brahmanapally wrote:

> Hi All,
> I think that the Subtract on a termination is enough to make the event
> descriptor empty. Section 6.2.4 indicates "If not provisioned otherwise, all
> descriptors except TerminationState and LocalControl default to   empty/"no
> value" when a Termination is first created or returned to   the null
> Context.".
> Regards
> Madhubabu Brahmanapally.
> 
> -----Original Message-----
> From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org]On Behalf Of
> Tom Taylor
> Sent: Wednesday, July 16, 2003 10:29 AM
> To: Brad Steinka
> Cc: 'megaco@ietf.org'
> Subject: Re: [Megaco] Active Events
> 
> 
> Afraid not.  You have to do the modification after the subtract.  I'm a bit
> busy to
> look up the reference, but it's early in section 6.
> 
> Brad Steinka wrote:
> 
> 
>>When a termination is in a active Context and the MG receives a Modify for
>>the termination that contains an Event Descriptor
>>requesting the MG to detect specific events (ex.  flash / on-hook/
>>off-hook),  do these events REMAIN ACTIVE when
>>the termination is returned to the NULL context when the MG receives a
>>Subtract for the termination in question?
>>
>>It is NOT clear in the RFC-3015 what happens to ACTIVE events / signals
> 
> when
> 
>>a termination is returned to the NULL context.
>>
>>Thanks in advance for any clarification you can bring to this topic.
>>
>>
>>
>>
>>Brad Steinka
>>Director - Software Engineering
>>734 Forest Street, Building G, Suite 100
>>Marlboro, Ma.   01752
>>Tel:  508-480-0909  x154
>>Email: bsteinka@telica.com <mailto:bsteinka@telica.com>
>>Web:   www.telica.com <http://www.telica.com>
>>
>>
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
> 
> 
> 
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
> 
> 


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



From megaco-admin@ietf.org  Thu Jul 17 02:48:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18545
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 02:48:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2Yb-0005Mv-9O; Thu, 17 Jul 2003 02:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2YD-0005MO-WC
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 02:47:38 -0400
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18491
	for <megaco@ietf.org>; Thu, 17 Jul 2003 02:47:33 -0400 (EDT)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6H6fFA05867;
	Thu, 17 Jul 2003 02:41:15 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLVYVVY0; Thu, 17 Jul 2003 02:41:15 -0400
Received: from nortelnetworks.com (acart3xf.ca.nortel.com [47.129.49.20]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3RVWP1NH; Thu, 17 Jul 2003 02:41:15 -0400
Message-ID: <3F164507.60309@nortelnetworks.com>
Date: Thu, 17 Jul 2003 08:41:11 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: titty@cdotb.ernet.in
CC: megaco@ietf.org
Subject: Re: [Megaco] Subtract before Add reply
References: <3F155FB2.3010803@cdotb.ernet.in>
In-Reply-To: <3F155FB2.3010803@cdotb.ernet.in>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I think you've answered your own question -- though I suppose a wildcard subtract 
covering all contexts and terminations might do the job if it lost the race with the 
add.

Titty Thomas wrote:

> Hi,
>            Can the MGC subtract a termination after issuing an add command
> 
>       but before it got the add reply.
> 
>       If so, what should be the context id and the termination id (if 
> MGC has added
>           an ephemeral termination) to be used in the subtract command.
> 
> Warm regards,
> -- Titty
> 


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


From exim@www1.ietf.org  Thu Jul 17 02:48:58 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18597
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 02:48:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2Z6-0005TX-Gy
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 02:48:32 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6H6mW3r021041
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 02:48:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2Z6-0005TI-1w
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 02:48:32 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18546
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 02:48:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2Yb-0005Mv-9O; Thu, 17 Jul 2003 02:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d2YD-0005MO-WC
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 02:47:38 -0400
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18491
	for <megaco@ietf.org>; Thu, 17 Jul 2003 02:47:33 -0400 (EDT)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6H6fFA05867;
	Thu, 17 Jul 2003 02:41:15 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id NLVYVVY0; Thu, 17 Jul 2003 02:41:15 -0400
Received: from nortelnetworks.com (acart3xf.ca.nortel.com [47.129.49.20]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 3RVWP1NH; Thu, 17 Jul 2003 02:41:15 -0400
Message-ID: <3F164507.60309@nortelnetworks.com>
Date: Thu, 17 Jul 2003 08:41:11 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: titty@cdotb.ernet.in
CC: megaco@ietf.org
Subject: Re: [Megaco] Subtract before Add reply
References: <3F155FB2.3010803@cdotb.ernet.in>
In-Reply-To: <3F155FB2.3010803@cdotb.ernet.in>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I think you've answered your own question -- though I suppose a wildcard subtract 
covering all contexts and terminations might do the job if it lost the race with the 
add.

Titty Thomas wrote:

> Hi,
>            Can the MGC subtract a termination after issuing an add command
> 
>       but before it got the add reply.
> 
>       If so, what should be the context id and the termination id (if 
> MGC has added
>           an ephemeral termination) to be used in the subtract command.
> 
> Warm regards,
> -- Titty
> 


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



From megaco-admin@ietf.org  Thu Jul 17 05:42:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26940
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 05:42:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d5Gz-0003CW-P5; Thu, 17 Jul 2003 05:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d5G9-0003Bt-LV
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 05:41:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26916
	for <megaco@ietf.org>; Thu, 17 Jul 2003 05:41:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d5G6-00040H-00
	for megaco@ietf.org; Thu, 17 Jul 2003 05:41:06 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49] helo=albatross.tn.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d5Fv-00040C-00
	for megaco@ietf.org; Thu, 17 Jul 2003 05:40:55 -0400
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h6H9eoIi025739
	for <megaco@ietf.org>; Thu, 17 Jul 2003 11:40:50 +0200 (MEST)
Received: from super.du.uab.ericsson.se ([134.138.176.16]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id 3S6JQ428; Thu, 17 Jul 2003 11:43:44 +0200
Received: from bifur.du.uab.ericsson.se (root@bifur [134.138.177.75])
	by super.du.uab.ericsson.se (8.10.1/8.10.1/erix-1.8) with ESMTP id h6H9enn23370
	for <megaco@ietf.org>; Thu, 17 Jul 2003 11:40:49 +0200 (MET DST)
Received: (from bmk@localhost)
	by bifur.du.uab.ericsson.se (8.11.6+Sun/8.9.1/client-1.0) id h6H9Vl903225;
	Thu, 17 Jul 2003 11:31:47 +0200 (MEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16150.27894.389089.986520@gargle.gargle.HOWL>
Date: Thu, 17 Jul 2003 11:31:34 +0200
From: Micael Karlberg <micael.karlberg@ericsson.com>
Reply-To: micael.karlberg@ericsson.com
Organization: Ericsson AB (EAB/UKH/KD)
To: megaco@ietf.org
X-Mailer: VM 7.07 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Ambiguous definition of auditReturnParameter in v2 ABNF
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

The 'auditReturnParameter' appears to be ambiguously defined in version 2
of the ABNF.

An example. If the 'auditReturnParameter' contains the following 
sequence of tokens:

   "EB { hobbes }"

i.e.

    EventBufferToken LBRKT pkgdName RBRKT

then it may be an 'auditItem' (see 'indAudeventBufferDescriptor') or an 
'eventBufferDescriptor'

What is the intention here? Should this sequence of tokens be
interpreted as an 'auditItem' or an 'eventBufferDescriptor?

As a parser implementor I need a well defined, unambiguous grammar to
rely on.

The grammar looks like this (a little bit simplified):

  auditReturnParameter        = eventBufferDescriptor / auditItem

  eventBufferDescriptor       = EventBufferToken 
                                [ LBRKT eventSpec *(COMMA eventSpec) RBRKT]

  eventSpec                   = pkgdName  
                                [ LBRKT eventSpecParameter 
                                        *(COMMA eventSpecParameter) RBRKT]

  auditItem                   = indAudterminationAudit 

  indAudterminationAudit      = indAudauditReturnParameter
                                *(COMMA insAudauditReturnParameter)

  indAudauditReturnParameter  = indAudeventBufferDescriptor

  indAudeventBufferDescriptor = EventBufferToken LBRKT indAudeventSpec RBRKT

  indAudeventSpec             = pkgdName 
                                [ LBRKT indAudeventSpecParameter RBRKT ]


Regards,
	/BMK

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


From exim@www1.ietf.org  Thu Jul 17 05:43:00 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27018
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 05:43:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d5HX-0003J9-12
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 05:42:35 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6H9gY7Z012714
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 05:42:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d5HV-0003Iq-NY
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 05:42:33 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26941
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 05:42:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d5Gz-0003CW-P5; Thu, 17 Jul 2003 05:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d5G9-0003Bt-LV
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 05:41:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26916
	for <megaco@ietf.org>; Thu, 17 Jul 2003 05:41:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d5G6-00040H-00
	for megaco@ietf.org; Thu, 17 Jul 2003 05:41:06 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49] helo=albatross.tn.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d5Fv-00040C-00
	for megaco@ietf.org; Thu, 17 Jul 2003 05:40:55 -0400
Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h6H9eoIi025739
	for <megaco@ietf.org>; Thu, 17 Jul 2003 11:40:50 +0200 (MEST)
Received: from super.du.uab.ericsson.se ([134.138.176.16]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id 3S6JQ428; Thu, 17 Jul 2003 11:43:44 +0200
Received: from bifur.du.uab.ericsson.se (root@bifur [134.138.177.75])
	by super.du.uab.ericsson.se (8.10.1/8.10.1/erix-1.8) with ESMTP id h6H9enn23370
	for <megaco@ietf.org>; Thu, 17 Jul 2003 11:40:49 +0200 (MET DST)
Received: (from bmk@localhost)
	by bifur.du.uab.ericsson.se (8.11.6+Sun/8.9.1/client-1.0) id h6H9Vl903225;
	Thu, 17 Jul 2003 11:31:47 +0200 (MEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16150.27894.389089.986520@gargle.gargle.HOWL>
Date: Thu, 17 Jul 2003 11:31:34 +0200
From: Micael Karlberg <micael.karlberg@ericsson.com>
Reply-To: micael.karlberg@ericsson.com
Organization: Ericsson AB (EAB/UKH/KD)
To: megaco@ietf.org
X-Mailer: VM 7.07 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Ambiguous definition of auditReturnParameter in v2 ABNF
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

The 'auditReturnParameter' appears to be ambiguously defined in version 2
of the ABNF.

An example. If the 'auditReturnParameter' contains the following 
sequence of tokens:

   "EB { hobbes }"

i.e.

    EventBufferToken LBRKT pkgdName RBRKT

then it may be an 'auditItem' (see 'indAudeventBufferDescriptor') or an 
'eventBufferDescriptor'

What is the intention here? Should this sequence of tokens be
interpreted as an 'auditItem' or an 'eventBufferDescriptor?

As a parser implementor I need a well defined, unambiguous grammar to
rely on.

The grammar looks like this (a little bit simplified):

  auditReturnParameter        = eventBufferDescriptor / auditItem

  eventBufferDescriptor       = EventBufferToken 
                                [ LBRKT eventSpec *(COMMA eventSpec) RBRKT]

  eventSpec                   = pkgdName  
                                [ LBRKT eventSpecParameter 
                                        *(COMMA eventSpecParameter) RBRKT]

  auditItem                   = indAudterminationAudit 

  indAudterminationAudit      = indAudauditReturnParameter
                                *(COMMA insAudauditReturnParameter)

  indAudauditReturnParameter  = indAudeventBufferDescriptor

  indAudeventBufferDescriptor = EventBufferToken LBRKT indAudeventSpec RBRKT

  indAudeventSpec             = pkgdName 
                                [ LBRKT indAudeventSpecParameter RBRKT ]


Regards,
	/BMK

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



From megaco-admin@ietf.org  Thu Jul 17 07:41:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01219
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 07:41:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d788-00032Y-HS; Thu, 17 Jul 2003 07:41:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d77L-00030X-V5
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 07:40:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01145
	for <megaco@ietf.org>; Thu, 17 Jul 2003 07:40:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d77L-0005IO-00
	for megaco@ietf.org; Thu, 17 Jul 2003 07:40:11 -0400
Received: from shardagate2.mahindrabt.com ([203.124.158.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d778-0005Hr-00
	for megaco@ietf.org; Thu, 17 Jul 2003 07:39:59 -0400
Received: from thisdomain (mailscan.sharda.mahindrabt.com [10.5.0.97])
	by shardagate2.mahindrabt.com (8.12.9/8.12.9) with ESMTP id h6HBZIeX014111
	for <megaco@ietf.org>; Thu, 17 Jul 2003 17:05:24 +0530
Received: from intranet.sharda.mahindrabt.com by mahindrabt.com ; Thu, 17 Jul 2003 16:52:33 +0530
Date: Thu, 17 Jul 2003 16:52:33 +0530
X-Originating-IP: 10.5.0.15
X-Auth-User: anilj@mahindrabt.com
Received: from dscp00986 ([10.5.13.76])
	by intranet.sharda.mahindrabt.com (8.9.3/8.9.3) with SMTP id RAA13051;
	Thu, 17 Jul 2003 17:09:11 +0530
Message-ID: <00e301c34c58$c21b2de0$4c0d050a@mahindrabt.com>
From: "Anil Jangam" <anilj@mahindrabt.com>
To: <micael.karlberg@ericsson.com>, <megaco@ietf.org>
Cc: "Tom-PT Taylor" <taylor@nortelnetworks.com>,
        "Kevin Boyle" <kboyle@nortelnetworks.com>
References: <16150.27894.389089.986520@gargle.gargle.HOWL>
Subject: Re: [Megaco] Ambiguous definition of auditReturnParameter in v2 ABNF
Date: Thu, 17 Jul 2003 17:14:18 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

This particular question has been repeated for a number of times so far.
Even I had the same doubt for which Tom has replied as follows: (Marked with
####>).
I think we need to fix this now.

####> STARTS
----- Original Message -----
From: Tom-PT Taylor
To: 'Anil Jangam' ; Kevin Boyle
Sent: Wednesday, January 22, 2003 10:40 PM
Subject: RE: [Megaco] auditReturnParameter in AmmsReply


I suppose as the guy who concocted this syntax I should answer the question.
You return the auditItem.  That was my shortcut for returning descriptor
name only.

Apparently there is a parsing problem with this syntax, but we never seem to
have taken the step of resolving it.
####> ENDS

----- Original Message -----
From: "Micael Karlberg" <micael.karlberg@ericsson.com>
To: <megaco@ietf.org>
Sent: Thursday, July 17, 2003 3:16 PM
Subject: [Megaco] Ambiguous definition of auditReturnParameter in v2 ABNF


> Hi,
>
> The 'auditReturnParameter' appears to be ambiguously defined in version 2
> of the ABNF.
>
> An example. If the 'auditReturnParameter' contains the following
> sequence of tokens:
>
>    "EB { hobbes }"
>
> i.e.
>
>     EventBufferToken LBRKT pkgdName RBRKT
>
> then it may be an 'auditItem' (see 'indAudeventBufferDescriptor') or an
> 'eventBufferDescriptor'
>
> What is the intention here? Should this sequence of tokens be
> interpreted as an 'auditItem' or an 'eventBufferDescriptor?
>
> As a parser implementor I need a well defined, unambiguous grammar to
> rely on.
>
> The grammar looks like this (a little bit simplified):
>
>   auditReturnParameter        = eventBufferDescriptor / auditItem
>
>   eventBufferDescriptor       = EventBufferToken
>                                 [ LBRKT eventSpec *(COMMA eventSpec)
RBRKT]
>
>   eventSpec                   = pkgdName
>                                 [ LBRKT eventSpecParameter
>                                         *(COMMA eventSpecParameter) RBRKT]
>
>   auditItem                   = indAudterminationAudit
>
>   indAudterminationAudit      = indAudauditReturnParameter
>                                 *(COMMA insAudauditReturnParameter)
>
>   indAudauditReturnParameter  = indAudeventBufferDescriptor
>
>   indAudeventBufferDescriptor = EventBufferToken LBRKT indAudeventSpec
RBRKT
>
>   indAudeventSpec             = pkgdName
>                                 [ LBRKT indAudeventSpecParameter RBRKT ]
>
>
> Regards,
> /BMK
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>



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


From exim@www1.ietf.org  Thu Jul 17 07:42:00 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01260
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 07:42:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d78e-00036C-EJ
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 07:41:32 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HBfW41011906
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 07:41:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d78e-00035x-6Y
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 07:41:32 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01218
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 07:41:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d788-00032Y-HS; Thu, 17 Jul 2003 07:41:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d77L-00030X-V5
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 07:40:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01145
	for <megaco@ietf.org>; Thu, 17 Jul 2003 07:40:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d77L-0005IO-00
	for megaco@ietf.org; Thu, 17 Jul 2003 07:40:11 -0400
Received: from shardagate2.mahindrabt.com ([203.124.158.3])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d778-0005Hr-00
	for megaco@ietf.org; Thu, 17 Jul 2003 07:39:59 -0400
Received: from thisdomain (mailscan.sharda.mahindrabt.com [10.5.0.97])
	by shardagate2.mahindrabt.com (8.12.9/8.12.9) with ESMTP id h6HBZIeX014111
	for <megaco@ietf.org>; Thu, 17 Jul 2003 17:05:24 +0530
Received: from intranet.sharda.mahindrabt.com by mahindrabt.com ; Thu, 17 Jul 2003 16:52:33 +0530
Date: Thu, 17 Jul 2003 16:52:33 +0530
X-Originating-IP: 10.5.0.15
X-Auth-User: anilj@mahindrabt.com
Received: from dscp00986 ([10.5.13.76])
	by intranet.sharda.mahindrabt.com (8.9.3/8.9.3) with SMTP id RAA13051;
	Thu, 17 Jul 2003 17:09:11 +0530
Message-ID: <00e301c34c58$c21b2de0$4c0d050a@mahindrabt.com>
From: "Anil Jangam" <anilj@mahindrabt.com>
To: <micael.karlberg@ericsson.com>, <megaco@ietf.org>
Cc: "Tom-PT Taylor" <taylor@nortelnetworks.com>,
        "Kevin Boyle" <kboyle@nortelnetworks.com>
References: <16150.27894.389089.986520@gargle.gargle.HOWL>
Subject: Re: [Megaco] Ambiguous definition of auditReturnParameter in v2 ABNF
Date: Thu, 17 Jul 2003 17:14:18 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

This particular question has been repeated for a number of times so far.
Even I had the same doubt for which Tom has replied as follows: (Marked with
####>).
I think we need to fix this now.

####> STARTS
----- Original Message -----
From: Tom-PT Taylor
To: 'Anil Jangam' ; Kevin Boyle
Sent: Wednesday, January 22, 2003 10:40 PM
Subject: RE: [Megaco] auditReturnParameter in AmmsReply


I suppose as the guy who concocted this syntax I should answer the question.
You return the auditItem.  That was my shortcut for returning descriptor
name only.

Apparently there is a parsing problem with this syntax, but we never seem to
have taken the step of resolving it.
####> ENDS

----- Original Message -----
From: "Micael Karlberg" <micael.karlberg@ericsson.com>
To: <megaco@ietf.org>
Sent: Thursday, July 17, 2003 3:16 PM
Subject: [Megaco] Ambiguous definition of auditReturnParameter in v2 ABNF


> Hi,
>
> The 'auditReturnParameter' appears to be ambiguously defined in version 2
> of the ABNF.
>
> An example. If the 'auditReturnParameter' contains the following
> sequence of tokens:
>
>    "EB { hobbes }"
>
> i.e.
>
>     EventBufferToken LBRKT pkgdName RBRKT
>
> then it may be an 'auditItem' (see 'indAudeventBufferDescriptor') or an
> 'eventBufferDescriptor'
>
> What is the intention here? Should this sequence of tokens be
> interpreted as an 'auditItem' or an 'eventBufferDescriptor?
>
> As a parser implementor I need a well defined, unambiguous grammar to
> rely on.
>
> The grammar looks like this (a little bit simplified):
>
>   auditReturnParameter        = eventBufferDescriptor / auditItem
>
>   eventBufferDescriptor       = EventBufferToken
>                                 [ LBRKT eventSpec *(COMMA eventSpec)
RBRKT]
>
>   eventSpec                   = pkgdName
>                                 [ LBRKT eventSpecParameter
>                                         *(COMMA eventSpecParameter) RBRKT]
>
>   auditItem                   = indAudterminationAudit
>
>   indAudterminationAudit      = indAudauditReturnParameter
>                                 *(COMMA insAudauditReturnParameter)
>
>   indAudauditReturnParameter  = indAudeventBufferDescriptor
>
>   indAudeventBufferDescriptor = EventBufferToken LBRKT indAudeventSpec
RBRKT
>
>   indAudeventSpec             = pkgdName
>                                 [ LBRKT indAudeventSpecParameter RBRKT ]
>
>
> Regards,
> /BMK
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco
>



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



From megaco-admin@ietf.org  Thu Jul 17 08:53:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04348
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 08:53:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d8Fp-0007Pb-OQ; Thu, 17 Jul 2003 08:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d8Fj-0007PG-F4
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 08:52:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04317
	for <megaco@ietf.org>; Thu, 17 Jul 2003 08:52:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d8Fi-000631-00
	for megaco@ietf.org; Thu, 17 Jul 2003 08:52:54 -0400
Received: from [202.41.72.121] (helo=ws9.cdotb.ernet.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d8FT-00061b-00
	for megaco@ietf.org; Thu, 17 Jul 2003 08:52:41 -0400
Received: from cdotb.ernet.in ([192.168.51.243])
	by ws9.cdotb.ernet.in (8.9.3/8.9.3) with ESMTP id RAA05710;
	Thu, 17 Jul 2003 17:56:11 +0500 (GMT+0500)
Message-ID: <3F172EFC.2010802@cdotb.ernet.in>
Date: Thu, 17 Jul 2003 18:19:24 -0500
From: Krishnamurthy V <krish@cdotb.ernet.in>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020827
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom Taylor <taylor@nortelnetworks.com>
CC: titty@cdotb.ernet.in, megaco@ietf.org
Subject: Re: [Megaco] Subtract before Add reply
References: <3F155FB2.3010803@cdotb.ernet.in> <3F164507.60309@nortelnetworks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Tom,

one small clarification:

if the add is the first addition to the context (i.e. new context
creation), then that might be the solution.

but if the add is to the existing context, then mgc might know
the contextid to be used.  in that case, only terminationid
needs to be wildcarded (may be partially) in order
to minimize the casualities.

am i correct?

thank you.
krish.


Tom Taylor wrote:

> I think you've answered your own question -- though I suppose a 
> wildcard subtract covering all contexts and terminations might do the 
> job if it lost the race with the add.
>
> Titty Thomas wrote:
>
>> Hi,
>>            Can the MGC subtract a termination after issuing an add 
>> command
>>
>>       but before it got the add reply.
>>
>>       If so, what should be the context id and the termination id (if 
>> MGC has added
>>           an ephemeral termination) to be used in the subtract command.
>>
>> Warm regards,
>> -- Titty
>>
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco



-- 
-------------------------------------------------------------------------
V Krishnamurthy			Phone (O): 080-2263399 Ext:255
Internet Telephony,		      (R): 080-3339368
C-DoT, 71/1, Miller Road,
Bangalore - 560052
-------------------------------------------------------------------------
The very strength that protects the heart from injury is the strength
that prevents the heart from enlarging to its intended greatness within.
-Kahlil Gibran.
-------------------------------------------------------------------------



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


From exim@www1.ietf.org  Thu Jul 17 08:53:43 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04365
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 08:53:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d8G4-0007Qn-DB
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 08:53:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HCrG9O028560
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 08:53:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d8G4-0007QZ-AA
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 08:53:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04345
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 08:53:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d8G2-00063R-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 08:53:15 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d8Fx-00063M-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 08:53:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d8Fp-0007Pb-OQ; Thu, 17 Jul 2003 08:53:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d8Fj-0007PG-F4
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 08:52:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04317
	for <megaco@ietf.org>; Thu, 17 Jul 2003 08:52:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d8Fi-000631-00
	for megaco@ietf.org; Thu, 17 Jul 2003 08:52:54 -0400
Received: from [202.41.72.121] (helo=ws9.cdotb.ernet.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d8FT-00061b-00
	for megaco@ietf.org; Thu, 17 Jul 2003 08:52:41 -0400
Received: from cdotb.ernet.in ([192.168.51.243])
	by ws9.cdotb.ernet.in (8.9.3/8.9.3) with ESMTP id RAA05710;
	Thu, 17 Jul 2003 17:56:11 +0500 (GMT+0500)
Message-ID: <3F172EFC.2010802@cdotb.ernet.in>
Date: Thu, 17 Jul 2003 18:19:24 -0500
From: Krishnamurthy V <krish@cdotb.ernet.in>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020827
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom Taylor <taylor@nortelnetworks.com>
CC: titty@cdotb.ernet.in, megaco@ietf.org
Subject: Re: [Megaco] Subtract before Add reply
References: <3F155FB2.3010803@cdotb.ernet.in> <3F164507.60309@nortelnetworks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Tom,

one small clarification:

if the add is the first addition to the context (i.e. new context
creation), then that might be the solution.

but if the add is to the existing context, then mgc might know
the contextid to be used.  in that case, only terminationid
needs to be wildcarded (may be partially) in order
to minimize the casualities.

am i correct?

thank you.
krish.


Tom Taylor wrote:

> I think you've answered your own question -- though I suppose a 
> wildcard subtract covering all contexts and terminations might do the 
> job if it lost the race with the add.
>
> Titty Thomas wrote:
>
>> Hi,
>>            Can the MGC subtract a termination after issuing an add 
>> command
>>
>>       but before it got the add reply.
>>
>>       If so, what should be the context id and the termination id (if 
>> MGC has added
>>           an ephemeral termination) to be used in the subtract command.
>>
>> Warm regards,
>> -- Titty
>>
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco



-- 
-------------------------------------------------------------------------
V Krishnamurthy			Phone (O): 080-2263399 Ext:255
Internet Telephony,		      (R): 080-3339368
C-DoT, 71/1, Miller Road,
Bangalore - 560052
-------------------------------------------------------------------------
The very strength that protects the heart from injury is the strength
that prevents the heart from enlarging to its intended greatness within.
-Kahlil Gibran.
-------------------------------------------------------------------------



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



From megaco-admin@ietf.org  Thu Jul 17 10:07:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07357
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 10:07:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d9PS-0002z7-Db; Thu, 17 Jul 2003 10:07:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d9Ot-0002yB-CE
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 10:06:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07210
	for <megaco@ietf.org>; Thu, 17 Jul 2003 10:06:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d9Or-0006e2-00
	for megaco@ietf.org; Thu, 17 Jul 2003 10:06:25 -0400
Received: from motgate2.mot.com ([136.182.1.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d9Og-0006de-00
	for megaco@ietf.org; Thu, 17 Jul 2003 10:06:14 -0400
Received: from az33exr03.mot.com (pobox3.mot.com [10.64.251.242])
	by motgate2.mot.com (Motorola/Motgate2) with ESMTP id h6HE5hvG011056
	for <megaco@ietf.org>; Thu, 17 Jul 2003 07:05:43 -0700 (MST)
Received: from bos-exch01.winphoria.com ([10.14.25.166])
	by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id h6HE5egr020657
	for <megaco@ietf.org>; Thu, 17 Jul 2003 09:05:41 -0500
Received: from smilevm.winphoria.com ([10.14.25.162]) by bos-exch01.winphoria.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 17 Jul 2003 10:04:09 -0400
Message-Id: <5.2.1.1.0.20030717095733.02969228@imap.winphoria.com>
X-Sender: kengr@imap.winphoria.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 17 Jul 2003 10:01:42 -0400
To: "Anil Jangam"<anilj@mahindrabt.com>, <micael.karlberg@ericsson.com>,
        <megaco@ietf.org>
From: Aleksandr Ryabin <kengr@winphoria.com>
Subject: Re: [Megaco] Ambiguous definition of auditReturnParameter in
  v2 ABNF
In-Reply-To: <00e301c34c58$c21b2de0$4c0d050a@mahindrabt.com>
References: <16150.27894.389089.986520@gargle.gargle.HOWL>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 17 Jul 2003 14:04:09.0710 (UTC) FILETIME=[4B2068E0:01C34C6C]
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>


>Date: Thu, 05 Jun 2003 12:36:31 -0400
>To: Troy Cauble <troy@bell-labs.com>, "Jay H Kim" <jayhkim@xener.com>,
>    "Anil Jangam" <anilj@mahindrabt.com>, megaco@ietf.org
>From: Aleksandr Ryabin <kengr@winphoria.com>
>Subject: Re: [Megaco] EventsToken in auditItem of teminationAudit or
>   empty eventsDescriptor
>
>See "6.3 Empty Descriptor Syntax" in IG.
>http://standard.pictel.com/ftp/avc-site/0305_Gen/H.248_IG.zip
>         Aleks
...


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


From exim@www1.ietf.org  Thu Jul 17 10:07:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07383
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 10:07:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d9PZ-00032a-MU
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 10:07:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HE79rk011682
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 10:07:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d9PZ-00032L-II
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 10:07:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07309
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 10:07:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d9PX-0006eT-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 10:07:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19d9PR-0006eQ-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 10:07:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d9PS-0002z7-Db; Thu, 17 Jul 2003 10:07:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19d9Ot-0002yB-CE
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 10:06:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07210
	for <megaco@ietf.org>; Thu, 17 Jul 2003 10:06:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d9Or-0006e2-00
	for megaco@ietf.org; Thu, 17 Jul 2003 10:06:25 -0400
Received: from motgate2.mot.com ([136.182.1.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 19d9Og-0006de-00
	for megaco@ietf.org; Thu, 17 Jul 2003 10:06:14 -0400
Received: from az33exr03.mot.com (pobox3.mot.com [10.64.251.242])
	by motgate2.mot.com (Motorola/Motgate2) with ESMTP id h6HE5hvG011056
	for <megaco@ietf.org>; Thu, 17 Jul 2003 07:05:43 -0700 (MST)
Received: from bos-exch01.winphoria.com ([10.14.25.166])
	by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id h6HE5egr020657
	for <megaco@ietf.org>; Thu, 17 Jul 2003 09:05:41 -0500
Received: from smilevm.winphoria.com ([10.14.25.162]) by bos-exch01.winphoria.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 17 Jul 2003 10:04:09 -0400
Message-Id: <5.2.1.1.0.20030717095733.02969228@imap.winphoria.com>
X-Sender: kengr@imap.winphoria.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 17 Jul 2003 10:01:42 -0400
To: "Anil Jangam"<anilj@mahindrabt.com>, <micael.karlberg@ericsson.com>,
        <megaco@ietf.org>
From: Aleksandr Ryabin <kengr@winphoria.com>
Subject: Re: [Megaco] Ambiguous definition of auditReturnParameter in
  v2 ABNF
In-Reply-To: <00e301c34c58$c21b2de0$4c0d050a@mahindrabt.com>
References: <16150.27894.389089.986520@gargle.gargle.HOWL>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 17 Jul 2003 14:04:09.0710 (UTC) FILETIME=[4B2068E0:01C34C6C]
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>


>Date: Thu, 05 Jun 2003 12:36:31 -0400
>To: Troy Cauble <troy@bell-labs.com>, "Jay H Kim" <jayhkim@xener.com>,
>    "Anil Jangam" <anilj@mahindrabt.com>, megaco@ietf.org
>From: Aleksandr Ryabin <kengr@winphoria.com>
>Subject: Re: [Megaco] EventsToken in auditItem of teminationAudit or
>   empty eventsDescriptor
>
>See "6.3 Empty Descriptor Syntax" in IG.
>http://standard.pictel.com/ftp/avc-site/0305_Gen/H.248_IG.zip
>         Aleks
...


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



From megaco-admin@ietf.org  Thu Jul 17 12:25:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13012
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 12:25:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dBYz-0003M8-HE; Thu, 17 Jul 2003 12:25:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dBYm-0003Li-72
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 12:24:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12980
	for <megaco@ietf.org>; Thu, 17 Jul 2003 12:24:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dBYk-0007YT-00
	for megaco@ietf.org; Thu, 17 Jul 2003 12:24:46 -0400
Received: from mailrelay2.alcatel.de ([194.113.59.71] helo=mailrelay1.alcatel.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dBYZ-0007Y3-00
	for megaco@ietf.org; Thu, 17 Jul 2003 12:24:36 -0400
Received: from ks.sel.alcatel.de (slsv0d.stgl.sel.alcatel.de [149.204.14.10])
	by mailrelay1.alcatel.de (8.9.3/8.9.3) with ESMTP id SAA16586
	for <megaco@ietf.org>; Thu, 17 Jul 2003 18:23:10 +0200 (MET DST)
Received: from slssiv ([149.204.245.89] helo=slsdtk.stgl.sel.alcatel.de) by ks.sel.alcatel.de with esmtp (Exim 3.31) id 19dBXa-0006wG-00; Thu, 17 Jul 2003 18:23:34 +0200
Received: from slsufnt ([149.204.245.33] helo=alcatel.de) by slsdtk.stgl.sel.alcatel.de with esmtp (Exim 3.31) id 19dBXa-0004dY-00; Thu, 17 Jul 2003 18:23:34 +0200
Message-ID: <3F16CD86.3F240D16@alcatel.de>
Date: Thu, 17 Jul 2003 18:23:34 +0200
From: Juergen Stoetzer <J.Stoetzer@alcatel.de>
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Alcanet-MTA-scanned-and-authorized: yes
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Start and End Tone Detected Events in DTMF Detection Pkg
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello,

Since the DTMF Detection Package extends the
Tone Detection Package an MGC could subscribe
for a start tone or long tone detected event with
a tone id list parameter containing a certain DTMF digit and,
at the same time, subscribe for that DTMF digit
as an event of its own.

Thus, from the protocol's point of view the following
Events descriptor in an Add or Modify command is
perfectly valid, isn't it?

Events = 1 {
    dd/d3,
    dd/ltd {tl=[d3]}
}

However, does such a combination actually make sense
from the MGC's point of view?
Are there any conceivable "real world" applications
which might use such a combination of events?

Thank you very much in advance!

Kind Regards,
Juergen Stoetzer

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


From exim@www1.ietf.org  Thu Jul 17 12:25:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13027
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 12:25:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dBZ7-0003NX-7V
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 12:25:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HGP9jF012981
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 12:25:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dBZ7-0003NI-36
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 12:25:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13003
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 12:25:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dBZ5-0007Yo-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 12:25:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dBYz-0007Yl-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 12:25:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dBYz-0003M8-HE; Thu, 17 Jul 2003 12:25:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dBYm-0003Li-72
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 12:24:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12980
	for <megaco@ietf.org>; Thu, 17 Jul 2003 12:24:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dBYk-0007YT-00
	for megaco@ietf.org; Thu, 17 Jul 2003 12:24:46 -0400
Received: from mailrelay2.alcatel.de ([194.113.59.71] helo=mailrelay1.alcatel.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dBYZ-0007Y3-00
	for megaco@ietf.org; Thu, 17 Jul 2003 12:24:36 -0400
Received: from ks.sel.alcatel.de (slsv0d.stgl.sel.alcatel.de [149.204.14.10])
	by mailrelay1.alcatel.de (8.9.3/8.9.3) with ESMTP id SAA16586
	for <megaco@ietf.org>; Thu, 17 Jul 2003 18:23:10 +0200 (MET DST)
Received: from slssiv ([149.204.245.89] helo=slsdtk.stgl.sel.alcatel.de) by ks.sel.alcatel.de with esmtp (Exim 3.31) id 19dBXa-0006wG-00; Thu, 17 Jul 2003 18:23:34 +0200
Received: from slsufnt ([149.204.245.33] helo=alcatel.de) by slsdtk.stgl.sel.alcatel.de with esmtp (Exim 3.31) id 19dBXa-0004dY-00; Thu, 17 Jul 2003 18:23:34 +0200
Message-ID: <3F16CD86.3F240D16@alcatel.de>
Date: Thu, 17 Jul 2003 18:23:34 +0200
From: Juergen Stoetzer <J.Stoetzer@alcatel.de>
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: megaco@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Alcanet-MTA-scanned-and-authorized: yes
Content-Transfer-Encoding: 7bit
Subject: [Megaco] Start and End Tone Detected Events in DTMF Detection Pkg
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello,

Since the DTMF Detection Package extends the
Tone Detection Package an MGC could subscribe
for a start tone or long tone detected event with
a tone id list parameter containing a certain DTMF digit and,
at the same time, subscribe for that DTMF digit
as an event of its own.

Thus, from the protocol's point of view the following
Events descriptor in an Add or Modify command is
perfectly valid, isn't it?

Events = 1 {
    dd/d3,
    dd/ltd {tl=[d3]}
}

However, does such a combination actually make sense
from the MGC's point of view?
Are there any conceivable "real world" applications
which might use such a combination of events?

Thank you very much in advance!

Kind Regards,
Juergen Stoetzer

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



From megaco-admin@ietf.org  Thu Jul 17 14:12:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16189
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 14:12:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDEY-0000Dg-2O; Thu, 17 Jul 2003 14:12:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDEH-0000DM-Ie
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 14:11:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16148
	for <megaco@ietf.org>; Thu, 17 Jul 2003 14:11:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dDEF-0000O2-00
	for megaco@ietf.org; Thu, 17 Jul 2003 14:11:43 -0400
Received: from [4.19.224.196] (helo=wench.telica.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dDDz-0000Nn-00
	for megaco@ietf.org; Thu, 17 Jul 2003 14:11:27 -0400
Received: by wench.telica.com with Internet Mail Service (5.5.2653.19)
	id <NT6J24N4>; Thu, 17 Jul 2003 14:10:13 -0400
Message-ID: <C9AFC8E904D49C4593EB077A2E8402BA731B19@wench.telica.com>
From: Bob Braisted <bbraisted@telica.com>
To: "'Juergen Stoetzer'" <J.Stoetzer@alcatel.de>, megaco@ietf.org
Subject: RE: [Megaco] Start and End Tone Detected Events in DTMF Detection
	 Pkg
Date: Thu, 17 Jul 2003 14:10:12 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>


as i understand it, the DTMF package extends the possible values for tone Id
in the 
"start tone detected"   (0x0001),
"end tone detected"     (0x0002),
and "long tone detected" (0x0003)  events.
(The only valid tone id defined from the base tone detection package was the
wildcard tone id.)

dd/d3 is therefore not really a valid pkgId/evtId to be included in an Event
descriptor. but rather d3 is just another tone id which could be included in
the tone id list as you indicated in the example of the subsequent long tone
detected event... dd/ltd {tl=[d3]).  

DTMF detection package also extends the tone detection package by defining
one additional event, dd/ce (0x0004) digit completion event. so the only
valid events related to DTMF detection package would be  dd/std, dd/etd,
dd/ltd, and dd/ce.

for what it's worth?

thanks
bob

-----Original Message-----
From: Juergen Stoetzer [mailto:J.Stoetzer@alcatel.de]
Sent: Thursday, July 17, 2003 12:24 PM
To: megaco@ietf.org
Subject: [Megaco] Start and End Tone Detected Events in DTMF Detection
Pkg


Hello,

Since the DTMF Detection Package extends the
Tone Detection Package an MGC could subscribe
for a start tone or long tone detected event with
a tone id list parameter containing a certain DTMF digit and,
at the same time, subscribe for that DTMF digit
as an event of its own.

Thus, from the protocol's point of view the following
Events descriptor in an Add or Modify command is
perfectly valid, isn't it?

Events = 1 {
    dd/d3,
    dd/ltd {tl=[d3]}
}

However, does such a combination actually make sense
from the MGC's point of view?
Are there any conceivable "real world" applications
which might use such a combination of events?

Thank you very much in advance!

Kind Regards,
Juergen Stoetzer

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

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


From exim@www1.ietf.org  Thu Jul 17 14:13:00 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16221
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 14:12:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDF3-0000J2-Nm
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 14:12:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HICXJb001172
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 14:12:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDF3-0000Ip-JA
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 14:12:33 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16182
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 14:12:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDEY-0000Dg-2O; Thu, 17 Jul 2003 14:12:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDEH-0000DM-Ie
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 14:11:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16148
	for <megaco@ietf.org>; Thu, 17 Jul 2003 14:11:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dDEF-0000O2-00
	for megaco@ietf.org; Thu, 17 Jul 2003 14:11:43 -0400
Received: from [4.19.224.196] (helo=wench.telica.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dDDz-0000Nn-00
	for megaco@ietf.org; Thu, 17 Jul 2003 14:11:27 -0400
Received: by wench.telica.com with Internet Mail Service (5.5.2653.19)
	id <NT6J24N4>; Thu, 17 Jul 2003 14:10:13 -0400
Message-ID: <C9AFC8E904D49C4593EB077A2E8402BA731B19@wench.telica.com>
From: Bob Braisted <bbraisted@telica.com>
To: "'Juergen Stoetzer'" <J.Stoetzer@alcatel.de>, megaco@ietf.org
Subject: RE: [Megaco] Start and End Tone Detected Events in DTMF Detection
	 Pkg
Date: Thu, 17 Jul 2003 14:10:12 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>


as i understand it, the DTMF package extends the possible values for tone Id
in the 
"start tone detected"   (0x0001),
"end tone detected"     (0x0002),
and "long tone detected" (0x0003)  events.
(The only valid tone id defined from the base tone detection package was the
wildcard tone id.)

dd/d3 is therefore not really a valid pkgId/evtId to be included in an Event
descriptor. but rather d3 is just another tone id which could be included in
the tone id list as you indicated in the example of the subsequent long tone
detected event... dd/ltd {tl=[d3]).  

DTMF detection package also extends the tone detection package by defining
one additional event, dd/ce (0x0004) digit completion event. so the only
valid events related to DTMF detection package would be  dd/std, dd/etd,
dd/ltd, and dd/ce.

for what it's worth?

thanks
bob

-----Original Message-----
From: Juergen Stoetzer [mailto:J.Stoetzer@alcatel.de]
Sent: Thursday, July 17, 2003 12:24 PM
To: megaco@ietf.org
Subject: [Megaco] Start and End Tone Detected Events in DTMF Detection
Pkg


Hello,

Since the DTMF Detection Package extends the
Tone Detection Package an MGC could subscribe
for a start tone or long tone detected event with
a tone id list parameter containing a certain DTMF digit and,
at the same time, subscribe for that DTMF digit
as an event of its own.

Thus, from the protocol's point of view the following
Events descriptor in an Add or Modify command is
perfectly valid, isn't it?

Events = 1 {
    dd/d3,
    dd/ltd {tl=[d3]}
}

However, does such a combination actually make sense
from the MGC's point of view?
Are there any conceivable "real world" applications
which might use such a combination of events?

Thank you very much in advance!

Kind Regards,
Juergen Stoetzer

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

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



From megaco-admin@ietf.org  Thu Jul 17 14:47:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17431
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 14:47:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDmO-0002Fd-Uq; Thu, 17 Jul 2003 14:47:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDlt-0002CQ-3Y
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 14:46:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17366
	for <megaco@ietf.org>; Thu, 17 Jul 2003 14:46:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dDlq-0000dY-00
	for megaco@ietf.org; Thu, 17 Jul 2003 14:46:26 -0400
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dDlf-0000cy-00
	for megaco@ietf.org; Thu, 17 Jul 2003 14:46:15 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate4.mot.com (Motorola/Motgate4) with ESMTP id h6HIj6UZ028960
	for <megaco@ietf.org>; Thu, 17 Jul 2003 11:45:06 -0700 (MST)
Received: from bos-exch01.winphoria.com ([10.14.25.166])
	by az33exr02.mot.com (Motorola/az33exr02) with ESMTP id h6HIj3lf006718
	for <megaco@ietf.org>; Thu, 17 Jul 2003 13:45:04 -0500
Received: from smilevm.winphoria.com ([10.14.25.162]) by bos-exch01.winphoria.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 17 Jul 2003 14:43:30 -0400
Message-Id: <5.2.1.1.0.20030717141606.05098c48@imap.winphoria.com>
X-Sender: kengr@imap.winphoria.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 17 Jul 2003 14:41:56 -0400
To: Bob Braisted<bbraisted@telica.com>,
        "'Juergen Stoetzer'"<J.Stoetzer@alcatel.de>, <megaco@ietf.org>
From: Aleksandr Ryabin <kengr@winphoria.com>
Subject: RE: [Megaco] Start and End Tone Detected Events in DTMF
  Detection Pkg
In-Reply-To: <C9AFC8E904D49C4593EB077A2E8402BA731B19@wench.telica.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 17 Jul 2003 18:43:30.0762 (UTC) FILETIME=[517DFAA0:01C34C93]
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

No, dd package defines DTMF digits as events (see RFC 3525, E.6.2 Events).
Thus dd/d3 is a valid event.

As for original question:
Suppose MGC wants to detect "regular" brief d3 and "long" (say 2 sec) d3, then
I guess it could ask for something like { dd/d3, dd/ltd { tl = d3, dur = 
2000 }}
Then if d3 was short it would only get Notify with dd/d3, otherwise if d3
lasted for 2 sec it would get Notify for dd/d3 and dd/ltd

Although to avoid extra Notify I think more appropriate would be to ask for
dd/etd { tl = d3 } and then on receipt of Notify check observed event's "dur"
parameter to determine ether it was "short" or "long" digit.

But again, nothing precludes MGC from using former form.

Regards,
         Aleks

At 02:10 PM 7/17/2003, Bob Braisted wrote:

>as i understand it, the DTMF package extends the possible values for tone Id
>in the
>"start tone detected"   (0x0001),
>"end tone detected"     (0x0002),
>and "long tone detected" (0x0003)  events.
>(The only valid tone id defined from the base tone detection package was the
>wildcard tone id.)
>
>dd/d3 is therefore not really a valid pkgId/evtId to be included in an Event
>descriptor. but rather d3 is just another tone id which could be included in
>the tone id list as you indicated in the example of the subsequent long tone
>detected event... dd/ltd {tl=[d3]).
>
>DTMF detection package also extends the tone detection package by defining
>one additional event, dd/ce (0x0004) digit completion event. so the only
>valid events related to DTMF detection package would be  dd/std, dd/etd,
>dd/ltd, and dd/ce.
>
>for what it's worth?
>
>thanks
>bob
>
>-----Original Message-----
>From: Juergen Stoetzer [mailto:J.Stoetzer@alcatel.de]
>Sent: Thursday, July 17, 2003 12:24 PM
>To: megaco@ietf.org
>Subject: [Megaco] Start and End Tone Detected Events in DTMF Detection
>Pkg
>
>
>Hello,
>
>Since the DTMF Detection Package extends the
>Tone Detection Package an MGC could subscribe
>for a start tone or long tone detected event with
>a tone id list parameter containing a certain DTMF digit and,
>at the same time, subscribe for that DTMF digit
>as an event of its own.
>
>Thus, from the protocol's point of view the following
>Events descriptor in an Add or Modify command is
>perfectly valid, isn't it?
>
>Events = 1 {
>     dd/d3,
>     dd/ltd {tl=[d3]}
>}
>
>However, does such a combination actually make sense
>from the MGC's point of view?
>Are there any conceivable "real world" applications
>which might use such a combination of events?
>
>Thank you very much in advance!
>
>Kind Regards,
>Juergen Stoetzer
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco


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


From exim@www1.ietf.org  Thu Jul 17 14:47:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17449
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 14:47:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDmX-0002Hi-Ec
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 14:47:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HIl9i3008781
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 14:47:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDmV-0002Gk-Uz
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 14:47:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17414
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 14:47:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dDmT-0000dy-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 14:47:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dDmN-0000dv-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 14:46:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDmO-0002Fd-Uq; Thu, 17 Jul 2003 14:47:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dDlt-0002CQ-3Y
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 14:46:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17366
	for <megaco@ietf.org>; Thu, 17 Jul 2003 14:46:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dDlq-0000dY-00
	for megaco@ietf.org; Thu, 17 Jul 2003 14:46:26 -0400
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dDlf-0000cy-00
	for megaco@ietf.org; Thu, 17 Jul 2003 14:46:15 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate4.mot.com (Motorola/Motgate4) with ESMTP id h6HIj6UZ028960
	for <megaco@ietf.org>; Thu, 17 Jul 2003 11:45:06 -0700 (MST)
Received: from bos-exch01.winphoria.com ([10.14.25.166])
	by az33exr02.mot.com (Motorola/az33exr02) with ESMTP id h6HIj3lf006718
	for <megaco@ietf.org>; Thu, 17 Jul 2003 13:45:04 -0500
Received: from smilevm.winphoria.com ([10.14.25.162]) by bos-exch01.winphoria.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 17 Jul 2003 14:43:30 -0400
Message-Id: <5.2.1.1.0.20030717141606.05098c48@imap.winphoria.com>
X-Sender: kengr@imap.winphoria.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 17 Jul 2003 14:41:56 -0400
To: Bob Braisted<bbraisted@telica.com>,
        "'Juergen Stoetzer'"<J.Stoetzer@alcatel.de>, <megaco@ietf.org>
From: Aleksandr Ryabin <kengr@winphoria.com>
Subject: RE: [Megaco] Start and End Tone Detected Events in DTMF
  Detection Pkg
In-Reply-To: <C9AFC8E904D49C4593EB077A2E8402BA731B19@wench.telica.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 17 Jul 2003 18:43:30.0762 (UTC) FILETIME=[517DFAA0:01C34C93]
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

No, dd package defines DTMF digits as events (see RFC 3525, E.6.2 Events).
Thus dd/d3 is a valid event.

As for original question:
Suppose MGC wants to detect "regular" brief d3 and "long" (say 2 sec) d3, then
I guess it could ask for something like { dd/d3, dd/ltd { tl = d3, dur = 
2000 }}
Then if d3 was short it would only get Notify with dd/d3, otherwise if d3
lasted for 2 sec it would get Notify for dd/d3 and dd/ltd

Although to avoid extra Notify I think more appropriate would be to ask for
dd/etd { tl = d3 } and then on receipt of Notify check observed event's "dur"
parameter to determine ether it was "short" or "long" digit.

But again, nothing precludes MGC from using former form.

Regards,
         Aleks

At 02:10 PM 7/17/2003, Bob Braisted wrote:

>as i understand it, the DTMF package extends the possible values for tone Id
>in the
>"start tone detected"   (0x0001),
>"end tone detected"     (0x0002),
>and "long tone detected" (0x0003)  events.
>(The only valid tone id defined from the base tone detection package was the
>wildcard tone id.)
>
>dd/d3 is therefore not really a valid pkgId/evtId to be included in an Event
>descriptor. but rather d3 is just another tone id which could be included in
>the tone id list as you indicated in the example of the subsequent long tone
>detected event... dd/ltd {tl=[d3]).
>
>DTMF detection package also extends the tone detection package by defining
>one additional event, dd/ce (0x0004) digit completion event. so the only
>valid events related to DTMF detection package would be  dd/std, dd/etd,
>dd/ltd, and dd/ce.
>
>for what it's worth?
>
>thanks
>bob
>
>-----Original Message-----
>From: Juergen Stoetzer [mailto:J.Stoetzer@alcatel.de]
>Sent: Thursday, July 17, 2003 12:24 PM
>To: megaco@ietf.org
>Subject: [Megaco] Start and End Tone Detected Events in DTMF Detection
>Pkg
>
>
>Hello,
>
>Since the DTMF Detection Package extends the
>Tone Detection Package an MGC could subscribe
>for a start tone or long tone detected event with
>a tone id list parameter containing a certain DTMF digit and,
>at the same time, subscribe for that DTMF digit
>as an event of its own.
>
>Thus, from the protocol's point of view the following
>Events descriptor in an Add or Modify command is
>perfectly valid, isn't it?
>
>Events = 1 {
>     dd/d3,
>     dd/ltd {tl=[d3]}
>}
>
>However, does such a combination actually make sense
>from the MGC's point of view?
>Are there any conceivable "real world" applications
>which might use such a combination of events?
>
>Thank you very much in advance!
>
>Kind Regards,
>Juergen Stoetzer
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco


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



From megaco-admin@ietf.org  Thu Jul 17 23:21:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01951
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 23:21:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dLnp-0004Na-8L; Thu, 17 Jul 2003 23:21:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dLnO-0004NC-N7
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 23:20:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01922
	for <megaco@ietf.org>; Thu, 17 Jul 2003 23:20:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dLnM-0003wE-00
	for megaco@ietf.org; Thu, 17 Jul 2003 23:20:32 -0400
Received: from [210.22.146.172] (helo=asbmx.sbell.com.cn)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dLn9-0003vt-00
	for megaco@ietf.org; Thu, 17 Jul 2003 23:20:20 -0400
Received: from asbwebshld.sbell.com.cn (asbwebshld [172.24.208.38])
	by asbmx.sbell.com.cn (8.12.2+Sun/8.12.3) with SMTP id h6I3INPV021023
	for <megaco@ietf.org>; Fri, 18 Jul 2003 11:18:25 +0800 (CST)
Received: FROM bellnet-mail4.sbell.com.cn BY asbwebshld.sbell.com.cn ; Fri Jul 18 11:19:26 2003 +0800
Received: from bellnet-mail1.sbell.com.cn ([172.24.208.21]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 18 Jul 2003 11:19:24 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-7"
Content-Transfer-Encoding: 7bit
Date: Fri, 18 Jul 2003 11:19:23 +0800
Message-ID: <C2DB7F5BC458EA4C8EB46B7A4EFF7E764DB1C4@bellnet-mail1.sbell.com.cn>
Thread-Topic: question about signal descriptor in Modify's response 
Thread-Index: =?utf-7?Q?AcNF2gPCyCoJxHeKTjiggMUx5W76bA+AD0APA-?=
	=?utf-7?Q?+Nv9PbAA9-?=
From: "FND-AD Wang JuLin" <JuLin.Wang@alcatel-sbell.com.cn>
To: "Megaco (E-mail)" <megaco@ietf.org>
X-OriginalArrivalTime: 18 Jul 2003 03:19:24.0194 (UTC) FILETIME=[632CE020:01C34CDB]
Content-Transfer-Encoding: 7bit
Subject: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in Modify's response
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,List,
Can anybody help me on this item which i had posted before? Thanks a lot+ACE-

Jerry

+AD4------Original Message-----
+AD4-From: FND-AD Wang JuLin 
+AD4-Sent: Wednesday, July 09, 2003 1:22 PM
+AD4-To: Megaco (E-mail)
+AD4-Subject: +AFs-Megaco+AF0- question about signal descriptor in Modify's response
+AD4-
+AD4-
+AD4-Hi all,
+AD4-According to the protocol,signal descriptor can be modified 
+AD4-and returned in Modify's response.Can we construct the Modify 
+AD4-'s response whatever we want to implement our product 
+AD4-features?Here are two examples as follows.
+AD4-Example 1:
+AD4-MGC---+AD4-MG
+AD4-MEGACO/1 +AFs-15.8.1.10+AF0-:2944 
+AD4-   Transaction +AD0- 10001 +AHs- 
+AD4-       Context +AD0- - +AHs- 
+AD4-           Modify +AD0- ROOT +AHs-Signals  +AHs-xxx/yyy   +AHs-k+AD0-1,
+AD4-                                                     ea +AD0- 1, 
+AD4-                                                     random +AD0-1224+AH0AfQ-    
+AD4-           +AH0- 
+AD4-       +AH0- 
+AD4-   +AH0- 
+AD4-
+AD4-MG---+AD4-MGC
+AD4-MEGACO/1 +AFs-15.8.1.18+AF0-:2944 
+AD4-Reply +AD0- 10001 +AHs- 
+AD4-Context +AD0- - +AHs-Modify +AD0- ROOT+AHs-
+AD4-Signals +AHs-xxx/yyy+AHs-key+AD0-22,
+AD4-ea +AD0- 1 
+AD4AfQB9-    
+AD4-           +AH0- +AH0- +AH0-
+AD4-Example 2: 
+AD4-MGC---+AD4-MG
+AD4-MEGACO/1 +AFs-15.8.1.10+AF0-:2944 
+AD4-   Transaction +AD0- 10001 +AHs- 
+AD4-       Context +AD0- - +AHs- 
+AD4-           Modify +AD0- ROOT +AHs-Signals  +AHs-xxx/zzz   +AHs-t+AD0-1+AH0-,
+AD4-                                                         
+AD4-xxx/yyy   +AHs-k+AD0-2,
+AD4-                                                     ea +AD0- 1, 
+AD4-                                                     random +AD0-1223+AH0AfQ-    
+AD4-           +AH0- 
+AD4-       +AH0- 
+AD4-   +AH0- 
+AD4- 
+AD4-MG---+AD4-MGC
+AD4-MEGACO/1 +AFs-15.8.1.18+AF0-:2944 
+AD4-Reply +AD0- 10001 +AHs- 
+AD4-Context +AD0- - +AHs-Modify +AD0- ROOT+AH0AfQ-
+AD4-
+AD4-I wonder if the above  two examples are suitable or not when 
+AD4-both are adopted in a scenario for gateway to implement some 
+AD4-features.Please clear my mind.Thanks in advance+ACE-
+AD4-
+AD4- best  regards 
+AD4-JJerry Wang 
+AD4-tel:(8621)58541240 ext 9531 
+AD4-MP:13621761050 
+AD4-mailto:Julin.Wang+AEA-alcatel-sbell.com.cn 
+AD4-Alcatel Shanghai Bell Co.LTD 
+AD4-
+AD4AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBf-
+AD4-Megaco mailing list
+AD4-Megaco+AEA-ietf.org
+AD4-https://www1.ietf.org/mailman/listinfo/megaco
+AD4-

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


From exim@www1.ietf.org  Thu Jul 17 23:21:38 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01966
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 23:21:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dLnz-0004Ov-J3
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 23:21:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I3LBia016913
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 23:21:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dLnx-0004Oi-ME
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 23:21:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01934
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 23:21:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dLnv-0003wZ-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 23:21:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dLnp-0003wW-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 23:21:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dLnp-0004Na-8L; Thu, 17 Jul 2003 23:21:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dLnO-0004NC-N7
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 23:20:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01922
	for <megaco@ietf.org>; Thu, 17 Jul 2003 23:20:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dLnM-0003wE-00
	for megaco@ietf.org; Thu, 17 Jul 2003 23:20:32 -0400
Received: from [210.22.146.172] (helo=asbmx.sbell.com.cn)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dLn9-0003vt-00
	for megaco@ietf.org; Thu, 17 Jul 2003 23:20:20 -0400
Received: from asbwebshld.sbell.com.cn (asbwebshld [172.24.208.38])
	by asbmx.sbell.com.cn (8.12.2+Sun/8.12.3) with SMTP id h6I3INPV021023
	for <megaco@ietf.org>; Fri, 18 Jul 2003 11:18:25 +0800 (CST)
Received: FROM bellnet-mail4.sbell.com.cn BY asbwebshld.sbell.com.cn ; Fri Jul 18 11:19:26 2003 +0800
Received: from bellnet-mail1.sbell.com.cn ([172.24.208.21]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 18 Jul 2003 11:19:24 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-7"
Content-Transfer-Encoding: 7bit
Date: Fri, 18 Jul 2003 11:19:23 +0800
Message-ID: <C2DB7F5BC458EA4C8EB46B7A4EFF7E764DB1C4@bellnet-mail1.sbell.com.cn>
Thread-Topic: question about signal descriptor in Modify's response 
Thread-Index: =?utf-7?Q?AcNF2gPCyCoJxHeKTjiggMUx5W76bA+AD0APA-?=
	=?utf-7?Q?+Nv9PbAA9-?=
From: "FND-AD Wang JuLin" <JuLin.Wang@alcatel-sbell.com.cn>
To: "Megaco (E-mail)" <megaco@ietf.org>
X-OriginalArrivalTime: 18 Jul 2003 03:19:24.0194 (UTC) FILETIME=[632CE020:01C34CDB]
Content-Transfer-Encoding: 7bit
Subject: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in Modify's response
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,List,
Can anybody help me on this item which i had posted before? Thanks a lot+ACE-

Jerry

+AD4------Original Message-----
+AD4-From: FND-AD Wang JuLin 
+AD4-Sent: Wednesday, July 09, 2003 1:22 PM
+AD4-To: Megaco (E-mail)
+AD4-Subject: +AFs-Megaco+AF0- question about signal descriptor in Modify's response
+AD4-
+AD4-
+AD4-Hi all,
+AD4-According to the protocol,signal descriptor can be modified 
+AD4-and returned in Modify's response.Can we construct the Modify 
+AD4-'s response whatever we want to implement our product 
+AD4-features?Here are two examples as follows.
+AD4-Example 1:
+AD4-MGC---+AD4-MG
+AD4-MEGACO/1 +AFs-15.8.1.10+AF0-:2944 
+AD4-   Transaction +AD0- 10001 +AHs- 
+AD4-       Context +AD0- - +AHs- 
+AD4-           Modify +AD0- ROOT +AHs-Signals  +AHs-xxx/yyy   +AHs-k+AD0-1,
+AD4-                                                     ea +AD0- 1, 
+AD4-                                                     random +AD0-1224+AH0AfQ-    
+AD4-           +AH0- 
+AD4-       +AH0- 
+AD4-   +AH0- 
+AD4-
+AD4-MG---+AD4-MGC
+AD4-MEGACO/1 +AFs-15.8.1.18+AF0-:2944 
+AD4-Reply +AD0- 10001 +AHs- 
+AD4-Context +AD0- - +AHs-Modify +AD0- ROOT+AHs-
+AD4-Signals +AHs-xxx/yyy+AHs-key+AD0-22,
+AD4-ea +AD0- 1 
+AD4AfQB9-    
+AD4-           +AH0- +AH0- +AH0-
+AD4-Example 2: 
+AD4-MGC---+AD4-MG
+AD4-MEGACO/1 +AFs-15.8.1.10+AF0-:2944 
+AD4-   Transaction +AD0- 10001 +AHs- 
+AD4-       Context +AD0- - +AHs- 
+AD4-           Modify +AD0- ROOT +AHs-Signals  +AHs-xxx/zzz   +AHs-t+AD0-1+AH0-,
+AD4-                                                         
+AD4-xxx/yyy   +AHs-k+AD0-2,
+AD4-                                                     ea +AD0- 1, 
+AD4-                                                     random +AD0-1223+AH0AfQ-    
+AD4-           +AH0- 
+AD4-       +AH0- 
+AD4-   +AH0- 
+AD4- 
+AD4-MG---+AD4-MGC
+AD4-MEGACO/1 +AFs-15.8.1.18+AF0-:2944 
+AD4-Reply +AD0- 10001 +AHs- 
+AD4-Context +AD0- - +AHs-Modify +AD0- ROOT+AH0AfQ-
+AD4-
+AD4-I wonder if the above  two examples are suitable or not when 
+AD4-both are adopted in a scenario for gateway to implement some 
+AD4-features.Please clear my mind.Thanks in advance+ACE-
+AD4-
+AD4- best  regards 
+AD4-JJerry Wang 
+AD4-tel:(8621)58541240 ext 9531 
+AD4-MP:13621761050 
+AD4-mailto:Julin.Wang+AEA-alcatel-sbell.com.cn 
+AD4-Alcatel Shanghai Bell Co.LTD 
+AD4-
+AD4AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBfAF8AXwBf-
+AD4-Megaco mailing list
+AD4-Megaco+AEA-ietf.org
+AD4-https://www1.ietf.org/mailman/listinfo/megaco
+AD4-

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



From megaco-admin@ietf.org  Thu Jul 17 23:37:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02442
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 23:37:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dM3J-0004oC-45; Thu, 17 Jul 2003 23:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dM2P-0004nY-U9
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 23:36:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02400
	for <megaco@ietf.org>; Thu, 17 Jul 2003 23:36:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dM2N-00045W-00
	for megaco@ietf.org; Thu, 17 Jul 2003 23:36:03 -0400
Received: from zrtps06s.nortelnetworks.com ([47.140.48.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dM2C-00044S-00
	for megaco@ietf.org; Thu, 17 Jul 2003 23:35:52 -0400
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6I3Yi608900
	for <megaco@ietf.org>; Thu, 17 Jul 2003 23:34:44 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NQAZBT41>; Thu, 17 Jul 2003 23:34:38 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C0A736CDE@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: FND-AD Wang JuLin <JuLin.Wang@alcatel-sbell.com.cn>,
        "Megaco (E-mail)"
	 <megaco@ietf.org>
Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
	 Modify's response
Date: Thu, 17 Jul 2003 23:34:37 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

Uhhh... Where, exactly, does the spec indicate that the MG can modify a
signal applied by the MGC?  That is not how I read the spec.

Example 1 is not correct.  Example 2 is.

Kevin

-----Original Message-----
From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] 
Sent: Thursday, July 17, 2003 11:19 PM
To: Megaco (E-mail)
Subject: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
Modify's response


Hi,List,
Can anybody help me on this item which i had posted before? Thanks a lot!

Jerry

>-----Original Message-----
>From: FND-AD Wang JuLin
>Sent: Wednesday, July 09, 2003 1:22 PM
>To: Megaco (E-mail)
>Subject: [Megaco] question about signal descriptor in Modify's response
>
>
>Hi all,
>According to the protocol,signal descriptor can be modified
>and returned in Modify's response.Can we construct the Modify 
>'s response whatever we want to implement our product 
>features?Here are two examples as follows.
>Example 1:
>MGC--->MG
>MEGACO/1 [15.8.1.10]:2944 
>   Transaction = 10001 { 
>       Context = - { 
>           Modify = ROOT {Signals  {xxx/yyy   {k=1,
>                                                     ea = 1, 
>                                                     random =1224}}    
>           } 
>       } 
>   }
>
>MG--->MGC
>MEGACO/1 [15.8.1.18]:2944
>Reply = 10001 { 
>Context = - {Modify = ROOT{
>Signals {xxx/yyy{key=22,
>ea = 1 
>}}    
>           } } }
>Example 2: 
>MGC--->MG
>MEGACO/1 [15.8.1.10]:2944 
>   Transaction = 10001 { 
>       Context = - { 
>           Modify = ROOT {Signals  {xxx/zzz   {t=1},
>                                                         
>xxx/yyy   {k=2,
>                                                     ea = 1, 
>                                                     random =1223}}    
>           } 
>       } 
>   }
> 
>MG--->MGC
>MEGACO/1 [15.8.1.18]:2944
>Reply = 10001 { 
>Context = - {Modify = ROOT}}
>
>I wonder if the above  two examples are suitable or not when
>both are adopted in a scenario for gateway to implement some 
>features.Please clear my mind.Thanks in advance!
>
> best  regards
>JJerry Wang 
>tel:(8621)58541240 ext 9531 
>MP:13621761050 
>mailto:Julin.Wang@alcatel-sbell.com.cn 
>Alcatel Shanghai Bell Co.LTD 
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>

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

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


From exim@www1.ietf.org  Thu Jul 17 23:37:34 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02457
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 23:37:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dM3Q-0004rZ-Ta
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 23:37:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I3b8wh018679
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 23:37:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dM3Q-0004rC-NE
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 23:37:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02432
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 23:37:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dM3O-00046C-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 23:37:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dM3I-000469-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 23:37:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dM3J-0004oC-45; Thu, 17 Jul 2003 23:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dM2P-0004nY-U9
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 23:36:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02400
	for <megaco@ietf.org>; Thu, 17 Jul 2003 23:36:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dM2N-00045W-00
	for megaco@ietf.org; Thu, 17 Jul 2003 23:36:03 -0400
Received: from zrtps06s.nortelnetworks.com ([47.140.48.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dM2C-00044S-00
	for megaco@ietf.org; Thu, 17 Jul 2003 23:35:52 -0400
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6I3Yi608900
	for <megaco@ietf.org>; Thu, 17 Jul 2003 23:34:44 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NQAZBT41>; Thu, 17 Jul 2003 23:34:38 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C0A736CDE@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: FND-AD Wang JuLin <JuLin.Wang@alcatel-sbell.com.cn>,
        "Megaco (E-mail)"
	 <megaco@ietf.org>
Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
	 Modify's response
Date: Thu, 17 Jul 2003 23:34:37 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

Uhhh... Where, exactly, does the spec indicate that the MG can modify a
signal applied by the MGC?  That is not how I read the spec.

Example 1 is not correct.  Example 2 is.

Kevin

-----Original Message-----
From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] 
Sent: Thursday, July 17, 2003 11:19 PM
To: Megaco (E-mail)
Subject: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
Modify's response


Hi,List,
Can anybody help me on this item which i had posted before? Thanks a lot!

Jerry

>-----Original Message-----
>From: FND-AD Wang JuLin
>Sent: Wednesday, July 09, 2003 1:22 PM
>To: Megaco (E-mail)
>Subject: [Megaco] question about signal descriptor in Modify's response
>
>
>Hi all,
>According to the protocol,signal descriptor can be modified
>and returned in Modify's response.Can we construct the Modify 
>'s response whatever we want to implement our product 
>features?Here are two examples as follows.
>Example 1:
>MGC--->MG
>MEGACO/1 [15.8.1.10]:2944 
>   Transaction = 10001 { 
>       Context = - { 
>           Modify = ROOT {Signals  {xxx/yyy   {k=1,
>                                                     ea = 1, 
>                                                     random =1224}}    
>           } 
>       } 
>   }
>
>MG--->MGC
>MEGACO/1 [15.8.1.18]:2944
>Reply = 10001 { 
>Context = - {Modify = ROOT{
>Signals {xxx/yyy{key=22,
>ea = 1 
>}}    
>           } } }
>Example 2: 
>MGC--->MG
>MEGACO/1 [15.8.1.10]:2944 
>   Transaction = 10001 { 
>       Context = - { 
>           Modify = ROOT {Signals  {xxx/zzz   {t=1},
>                                                         
>xxx/yyy   {k=2,
>                                                     ea = 1, 
>                                                     random =1223}}    
>           } 
>       } 
>   }
> 
>MG--->MGC
>MEGACO/1 [15.8.1.18]:2944
>Reply = 10001 { 
>Context = - {Modify = ROOT}}
>
>I wonder if the above  two examples are suitable or not when
>both are adopted in a scenario for gateway to implement some 
>features.Please clear my mind.Thanks in advance!
>
> best  regards
>JJerry Wang 
>tel:(8621)58541240 ext 9531 
>MP:13621761050 
>mailto:Julin.Wang@alcatel-sbell.com.cn 
>Alcatel Shanghai Bell Co.LTD 
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>

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

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



From megaco-admin@ietf.org  Thu Jul 17 23:47:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02756
	for <megaco-archive@lists.ietf.org>; Thu, 17 Jul 2003 23:47:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dMCz-0005KA-PQ; Thu, 17 Jul 2003 23:47:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dMCb-0005JD-O8
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 23:46:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02727
	for <Megaco@ietf.org>; Thu, 17 Jul 2003 23:46:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dMCZ-0004Cf-00
	for Megaco@ietf.org; Thu, 17 Jul 2003 23:46:35 -0400
Received: from [219.140.167.39] (helo=zg.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19dMCO-0004CB-00
	for Megaco@ietf.org; Thu, 17 Jul 2003 23:46:24 -0400
Received: (qmail 7960 invoked from network); 18 Jul 2003 03:46:25 -0000
Received: from unknown (HELO wangfei) (172.16.6.36)
  by 172.16.3.1 with SMTP; 18 Jul 2003 03:46:25 -0000
From: "wangfei" <wangfei@wri.com.cn>
Reply-To: wangfei@wri.com.cn
To: "Megaco@ietf.org" <Megaco@ietf.org>
Subject: Re: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor inModify's response
X-mailer: Foxmail 4.2 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Fri, 18 Jul 2003 11:47:51 +0800
Message-Id: <E19dMCO-0004CB-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


 Seriously agree!!!

>Uhhh... Where, exactly, does the spec indicate that the MG can modify a
>signal applied by the MGC?  That is not how I read the spec.
>
>Example 1 is not correct.  Example 2 is.
>
>Kevin
>
>-----Original Message-----
>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] 
>Sent: Thursday, July 17, 2003 11:19 PM
>To: Megaco (E-mail)
>Subject: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
>Modify's response
>
>
>Hi,List,
>Can anybody help me on this item which i had posted before? Thanks a lot!
>
>Jerry
>
>>-----Original Message-----
>>From: FND-AD Wang JuLin
>>Sent: Wednesday, July 09, 2003 1:22 PM
>>To: Megaco (E-mail)
>>Subject: [Megaco] question about signal descriptor in Modify's response
>>
>>
>>Hi all,
>>According to the protocol,signal descriptor can be modified
>>and returned in Modify's response.Can we construct the Modify 
>>'s response whatever we want to implement our product 
>>features?Here are two examples as follows.
>>Example 1:
>>MGC--->MG
>>MEGACO/1 [15.8.1.10]:2944 
>>   Transaction = 10001 { 
>>       Context = - { 
>>           Modify = ROOT {Signals  {xxx/yyy   {k=1,
>>                                                     ea = 1, 
>>                                                     random =1224}}    
>>           } 
>>       } 
>>   }
>>
>>MG--->MGC
>>MEGACO/1 [15.8.1.18]:2944
>>Reply = 10001 { 
>>Context = - {Modify = ROOT{
>>Signals {xxx/yyy{key=22,
>>ea = 1 
>>}}    
>>           } } }
>>Example 2: 
>>MGC--->MG
>>MEGACO/1 [15.8.1.10]:2944 
>>   Transaction = 10001 { 
>>       Context = - { 
>>           Modify = ROOT {Signals  {xxx/zzz   {t=1},
>>                                                         
>>xxx/yyy   {k=2,
>>                                                     ea = 1, 
>>                                                     random =1223}}    
>>           } 
>>       } 
>>   }
>> 
>>MG--->MGC
>>MEGACO/1 [15.8.1.18]:2944
>>Reply = 10001 { 
>>Context = - {Modify = ROOT}}
>>
>>I wonder if the above  two examples are suitable or not when
>>both are adopted in a scenario for gateway to implement some 
>>features.Please clear my mind.Thanks in advance!
>>
>> best  regards
>>JJerry Wang 
>>tel:(8621)58541240 ext 9531 
>>MP:13621761050 
>>mailto:Julin.Wang@alcatel-sbell.com.cn 
>>Alcatel Shanghai Bell Co.LTD 
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>.




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


From exim@www1.ietf.org  Thu Jul 17 23:47:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02771
	for <megaco-archive@odin.ietf.org>; Thu, 17 Jul 2003 23:47:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dMD7-0005LW-0A
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 23:47:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I3l86h020544
	for megaco-archive@odin.ietf.org; Thu, 17 Jul 2003 23:47:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dMD6-0005LH-SB
	for megaco-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 23:47:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02746
	for <megaco-web-archive@ietf.org>; Thu, 17 Jul 2003 23:47:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dMD4-0004DH-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 23:47:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dMCz-0004DE-00
	for megaco-web-archive@ietf.org; Thu, 17 Jul 2003 23:47:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dMCz-0005KA-PQ; Thu, 17 Jul 2003 23:47:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dMCb-0005JD-O8
	for megaco@optimus.ietf.org; Thu, 17 Jul 2003 23:46:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02727
	for <Megaco@ietf.org>; Thu, 17 Jul 2003 23:46:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dMCZ-0004Cf-00
	for Megaco@ietf.org; Thu, 17 Jul 2003 23:46:35 -0400
Received: from [219.140.167.39] (helo=zg.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19dMCO-0004CB-00
	for Megaco@ietf.org; Thu, 17 Jul 2003 23:46:24 -0400
Received: (qmail 7960 invoked from network); 18 Jul 2003 03:46:25 -0000
Received: from unknown (HELO wangfei) (172.16.6.36)
  by 172.16.3.1 with SMTP; 18 Jul 2003 03:46:25 -0000
From: "wangfei" <wangfei@wri.com.cn>
Reply-To: wangfei@wri.com.cn
To: "Megaco@ietf.org" <Megaco@ietf.org>
Subject: Re: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor inModify's response
X-mailer: Foxmail 4.2 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Fri, 18 Jul 2003 11:47:51 +0800
Message-Id: <E19dMCO-0004CB-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


 Seriously agree!!!

>Uhhh... Where, exactly, does the spec indicate that the MG can modify a
>signal applied by the MGC?  That is not how I read the spec.
>
>Example 1 is not correct.  Example 2 is.
>
>Kevin
>
>-----Original Message-----
>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] 
>Sent: Thursday, July 17, 2003 11:19 PM
>To: Megaco (E-mail)
>Subject: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
>Modify's response
>
>
>Hi,List,
>Can anybody help me on this item which i had posted before? Thanks a lot!
>
>Jerry
>
>>-----Original Message-----
>>From: FND-AD Wang JuLin
>>Sent: Wednesday, July 09, 2003 1:22 PM
>>To: Megaco (E-mail)
>>Subject: [Megaco] question about signal descriptor in Modify's response
>>
>>
>>Hi all,
>>According to the protocol,signal descriptor can be modified
>>and returned in Modify's response.Can we construct the Modify 
>>'s response whatever we want to implement our product 
>>features?Here are two examples as follows.
>>Example 1:
>>MGC--->MG
>>MEGACO/1 [15.8.1.10]:2944 
>>   Transaction = 10001 { 
>>       Context = - { 
>>           Modify = ROOT {Signals  {xxx/yyy   {k=1,
>>                                                     ea = 1, 
>>                                                     random =1224}}    
>>           } 
>>       } 
>>   }
>>
>>MG--->MGC
>>MEGACO/1 [15.8.1.18]:2944
>>Reply = 10001 { 
>>Context = - {Modify = ROOT{
>>Signals {xxx/yyy{key=22,
>>ea = 1 
>>}}    
>>           } } }
>>Example 2: 
>>MGC--->MG
>>MEGACO/1 [15.8.1.10]:2944 
>>   Transaction = 10001 { 
>>       Context = - { 
>>           Modify = ROOT {Signals  {xxx/zzz   {t=1},
>>                                                         
>>xxx/yyy   {k=2,
>>                                                     ea = 1, 
>>                                                     random =1223}}    
>>           } 
>>       } 
>>   }
>> 
>>MG--->MGC
>>MEGACO/1 [15.8.1.18]:2944
>>Reply = 10001 { 
>>Context = - {Modify = ROOT}}
>>
>>I wonder if the above  two examples are suitable or not when
>>both are adopted in a scenario for gateway to implement some 
>>features.Please clear my mind.Thanks in advance!
>>
>> best  regards
>>JJerry Wang 
>>tel:(8621)58541240 ext 9531 
>>MP:13621761050 
>>mailto:Julin.Wang@alcatel-sbell.com.cn 
>>Alcatel Shanghai Bell Co.LTD 
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>.




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



From megaco-admin@ietf.org  Fri Jul 18 05:02:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23779
	for <megaco-archive@lists.ietf.org>; Fri, 18 Jul 2003 05:02:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dR7p-0003KC-Uu; Fri, 18 Jul 2003 05:02:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dR7J-0003It-BV
	for megaco@optimus.ietf.org; Fri, 18 Jul 2003 05:01:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23756
	for <Megaco@ietf.org>; Fri, 18 Jul 2003 05:01:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dR7G-0006hj-00
	for Megaco@ietf.org; Fri, 18 Jul 2003 05:01:26 -0400
Received: from [219.140.167.39] (helo=zg.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19dR75-0006h8-00
	for Megaco@ietf.org; Fri, 18 Jul 2003 05:01:15 -0400
Received: (qmail 18759 invoked from network); 18 Jul 2003 09:00:58 -0000
Received: from unknown (HELO wangfei) (172.16.6.36)
  by 172.16.3.1 with SMTP; 18 Jul 2003 09:00:58 -0000
From: "wangfei" <wangfei@wri.com.cn>
Reply-To: wangfei@wri.com.cn
To: "Megaco@ietf.org" <Megaco@ietf.org>
Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in Modify's response
X-mailer: Foxmail 4.2 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Fri, 18 Jul 2003 17:2:22 +0800
Message-Id: <E19dR75-0006h8-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Wang JuLin

    I think Signal descriptor can be modified, but only by MGC. So...

	It's just my opinion. If i'm wrong, Plz tell me. Thanks! 


>Hi, Kevin,
>In chapter Add command, it was written:
>All descriptors that can be modified could be returned by MG if a parameter was underspecified or overspecified.  ObservedEvents, Statistics, and Packages, and the EventBuffer Descriptors are returned only if requested in the AuditDescriptor.
>I wonder the Signal descriptor can be modified or not. In what case can the gateway send Add/Modify/Subtract command reply with signal descriptor?  
>Please correct me if i misunderstood the protocol.
>
>>-----Original Message-----
>>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
>>Sent: Friday, July 18, 2003 11:35 AM
>>To: FND-AD Wang JuLin; Megaco (E-mail)
>>Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor
>>in Modify's response
>>
>>
>>Uhhh... Where, exactly, does the spec indicate that the MG can modify a
>>signal applied by the MGC?  That is not how I read the spec.
>>
>>Example 1 is not correct.  Example 2 is.
>>
>>Kevin
>>
>>-----Original Message-----
>>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] 
>>Sent: Thursday, July 17, 2003 11:19 PM
>>To: Megaco (E-mail)
>>Subject: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
>>Modify's response
>>
>>
>>Hi,List,
>>Can anybody help me on this item which i had posted before? 
>>Thanks a lot!
>>
>>Jerry
>>
>>>-----Original Message-----
>>>From: FND-AD Wang JuLin
>>>Sent: Wednesday, July 09, 2003 1:22 PM
>>>To: Megaco (E-mail)
>>>Subject: [Megaco] question about signal descriptor in 
>>Modify's response
>>>
>>>
>>>Hi all,
>>>According to the protocol,signal descriptor can be modified
>>>and returned in Modify's response.Can we construct the Modify 
>>>'s response whatever we want to implement our product 
>>>features?Here are two examples as follows.
>>>Example 1:
>>>MGC--->MG
>>>MEGACO/1 [15.8.1.10]:2944 
>>>   Transaction = 10001 { 
>>>       Context = - { 
>>>           Modify = ROOT {Signals  {xxx/yyy   {k=1,
>>>                                                     ea = 1, 
>>>                                                     random 
>>=1224}}    
>>>           } 
>>>       } 
>>>   }
>>>
>>>MG--->MGC
>>>MEGACO/1 [15.8.1.18]:2944
>>>Reply = 10001 { 
>>>Context = - {Modify = ROOT{
>>>Signals {xxx/yyy{key=22,
>>>ea = 1 
>>>}}    
>>>           } } }
>>>Example 2: 
>>>MGC--->MG
>>>MEGACO/1 [15.8.1.10]:2944 
>>>   Transaction = 10001 { 
>>>       Context = - { 
>>>           Modify = ROOT {Signals  {xxx/zzz   {t=1},
>>>                                                         
>>>xxx/yyy   {k=2,
>>>                                                     ea = 1, 
>>>                                                     random 
>>=1223}}    
>>>           } 
>>>       } 
>>>   }
>>> 
>>>MG--->MGC
>>>MEGACO/1 [15.8.1.18]:2944
>>>Reply = 10001 { 
>>>Context = - {Modify = ROOT}}
>>>
>>>I wonder if the above  two examples are suitable or not when
>>>both are adopted in a scenario for gateway to implement some 
>>>features.Please clear my mind.Thanks in advance!
>>>
>>> best  regards
>>>JJerry Wang 
>>>tel:(8621)58541240 ext 9531 
>>>MP:13621761050 
>>>mailto:Julin.Wang@alcatel-sbell.com.cn 
>>>Alcatel Shanghai Bell Co.LTD 
>>>
>>>_______________________________________________
>>>Megaco mailing list
>>>Megaco@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/megaco
>>>
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>.




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


From exim@www1.ietf.org  Fri Jul 18 05:02:39 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23825
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jul 2003 05:02:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dR7x-0003PU-Bf
	for megaco-archive@odin.ietf.org; Fri, 18 Jul 2003 05:02:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I929MZ013102
	for megaco-archive@odin.ietf.org; Fri, 18 Jul 2003 05:02:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dR7x-0003PF-7e
	for megaco-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 05:02:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23765
	for <megaco-web-archive@ietf.org>; Fri, 18 Jul 2003 05:02:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dR7u-0006iH-00
	for megaco-web-archive@ietf.org; Fri, 18 Jul 2003 05:02:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dR7o-0006iE-00
	for megaco-web-archive@ietf.org; Fri, 18 Jul 2003 05:02:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dR7p-0003KC-Uu; Fri, 18 Jul 2003 05:02:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dR7J-0003It-BV
	for megaco@optimus.ietf.org; Fri, 18 Jul 2003 05:01:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23756
	for <Megaco@ietf.org>; Fri, 18 Jul 2003 05:01:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dR7G-0006hj-00
	for Megaco@ietf.org; Fri, 18 Jul 2003 05:01:26 -0400
Received: from [219.140.167.39] (helo=zg.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19dR75-0006h8-00
	for Megaco@ietf.org; Fri, 18 Jul 2003 05:01:15 -0400
Received: (qmail 18759 invoked from network); 18 Jul 2003 09:00:58 -0000
Received: from unknown (HELO wangfei) (172.16.6.36)
  by 172.16.3.1 with SMTP; 18 Jul 2003 09:00:58 -0000
From: "wangfei" <wangfei@wri.com.cn>
Reply-To: wangfei@wri.com.cn
To: "Megaco@ietf.org" <Megaco@ietf.org>
Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in Modify's response
X-mailer: Foxmail 4.2 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Fri, 18 Jul 2003 17:2:22 +0800
Message-Id: <E19dR75-0006h8-00@ietf-mx>
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Wang JuLin

    I think Signal descriptor can be modified, but only by MGC. So...

	It's just my opinion. If i'm wrong, Plz tell me. Thanks! 


>Hi, Kevin,
>In chapter Add command, it was written:
>All descriptors that can be modified could be returned by MG if a parameter was underspecified or overspecified.  ObservedEvents, Statistics, and Packages, and the EventBuffer Descriptors are returned only if requested in the AuditDescriptor.
>I wonder the Signal descriptor can be modified or not. In what case can the gateway send Add/Modify/Subtract command reply with signal descriptor?  
>Please correct me if i misunderstood the protocol.
>
>>-----Original Message-----
>>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
>>Sent: Friday, July 18, 2003 11:35 AM
>>To: FND-AD Wang JuLin; Megaco (E-mail)
>>Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor
>>in Modify's response
>>
>>
>>Uhhh... Where, exactly, does the spec indicate that the MG can modify a
>>signal applied by the MGC?  That is not how I read the spec.
>>
>>Example 1 is not correct.  Example 2 is.
>>
>>Kevin
>>
>>-----Original Message-----
>>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] 
>>Sent: Thursday, July 17, 2003 11:19 PM
>>To: Megaco (E-mail)
>>Subject: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
>>Modify's response
>>
>>
>>Hi,List,
>>Can anybody help me on this item which i had posted before? 
>>Thanks a lot!
>>
>>Jerry
>>
>>>-----Original Message-----
>>>From: FND-AD Wang JuLin
>>>Sent: Wednesday, July 09, 2003 1:22 PM
>>>To: Megaco (E-mail)
>>>Subject: [Megaco] question about signal descriptor in 
>>Modify's response
>>>
>>>
>>>Hi all,
>>>According to the protocol,signal descriptor can be modified
>>>and returned in Modify's response.Can we construct the Modify 
>>>'s response whatever we want to implement our product 
>>>features?Here are two examples as follows.
>>>Example 1:
>>>MGC--->MG
>>>MEGACO/1 [15.8.1.10]:2944 
>>>   Transaction = 10001 { 
>>>       Context = - { 
>>>           Modify = ROOT {Signals  {xxx/yyy   {k=1,
>>>                                                     ea = 1, 
>>>                                                     random 
>>=1224}}    
>>>           } 
>>>       } 
>>>   }
>>>
>>>MG--->MGC
>>>MEGACO/1 [15.8.1.18]:2944
>>>Reply = 10001 { 
>>>Context = - {Modify = ROOT{
>>>Signals {xxx/yyy{key=22,
>>>ea = 1 
>>>}}    
>>>           } } }
>>>Example 2: 
>>>MGC--->MG
>>>MEGACO/1 [15.8.1.10]:2944 
>>>   Transaction = 10001 { 
>>>       Context = - { 
>>>           Modify = ROOT {Signals  {xxx/zzz   {t=1},
>>>                                                         
>>>xxx/yyy   {k=2,
>>>                                                     ea = 1, 
>>>                                                     random 
>>=1223}}    
>>>           } 
>>>       } 
>>>   }
>>> 
>>>MG--->MGC
>>>MEGACO/1 [15.8.1.18]:2944
>>>Reply = 10001 { 
>>>Context = - {Modify = ROOT}}
>>>
>>>I wonder if the above  two examples are suitable or not when
>>>both are adopted in a scenario for gateway to implement some 
>>>features.Please clear my mind.Thanks in advance!
>>>
>>> best  regards
>>>JJerry Wang 
>>>tel:(8621)58541240 ext 9531 
>>>MP:13621761050 
>>>mailto:Julin.Wang@alcatel-sbell.com.cn 
>>>Alcatel Shanghai Bell Co.LTD 
>>>
>>>_______________________________________________
>>>Megaco mailing list
>>>Megaco@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/megaco
>>>
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>.




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



From megaco-admin@ietf.org  Fri Jul 18 05:23:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24286
	for <megaco-archive@lists.ietf.org>; Fri, 18 Jul 2003 05:23:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dRS9-0004S3-D1; Fri, 18 Jul 2003 05:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dRRt-0004RN-Uf
	for megaco@optimus.ietf.org; Fri, 18 Jul 2003 05:22:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24271
	for <megaco@ietf.org>; Fri, 18 Jul 2003 05:22:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dRRl-0006vd-00
	for megaco@ietf.org; Fri, 18 Jul 2003 05:22:37 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49] helo=albatross.tn.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dRRa-0006vE-00
	for megaco@ietf.org; Fri, 18 Jul 2003 05:22:27 -0400
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h6I9M2Ii020119;
	Fri, 18 Jul 2003 11:22:02 +0200 (MEST)
Received: from super.du.uab.ericsson.se ([134.138.176.16]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id NW4XJZ7Q; Fri, 18 Jul 2003 11:21:32 +0200
Received: from bifur.du.uab.ericsson.se (daemon@bifur [134.138.177.75])
	by super.du.uab.ericsson.se (8.10.1/8.10.1/erix-1.8) with ESMTP id h6I9LVD29283;
	Fri, 18 Jul 2003 11:21:32 +0200 (MET DST)
Received: (from bmk@localhost)
	by bifur.du.uab.ericsson.se (8.11.6+Sun/8.9.1/client-1.0) id h6I9LV405083;
	Fri, 18 Jul 2003 11:21:31 +0200 (MEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-ID: <16151.48138.771516.776631@gargle.gargle.HOWL>
Date: Fri, 18 Jul 2003 11:21:14 +0200
From: Micael Karlberg <micael.karlberg@ericsson.com>
Reply-To: micael.karlberg@ericsson.com
Organization: Ericsson AB (EAB/UKH/KD)
To: "Anil Jangam" <anilj@mahindrabt.com>
Cc: <megaco@ietf.org>, "Tom-PT Taylor" <taylor@nortelnetworks.com>,
        "Kevin Boyle" <kboyle@nortelnetworks.com>
Subject: Re: [Megaco] Ambiguous definition of auditReturnParameter in v2 ABNF
In-Reply-To: <00e301c34c58$c21b2de0$4c0d050a@mahindrabt.com>
References: <16150.27894.389089.986520@gargle.gargle.HOWL>
	<00e301c34c58$c21b2de0$4c0d050a@mahindrabt.com>
X-Mailer: VM 7.07 under Emacs 21.1.1
Content-Transfer-Encoding: quoted-printable
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

So, now we have yet another parse conflict regarding 'EventBufferToken'=
?

We three rules:

1) auditItem                   -> 'EventBufferToken'
2) eventBufferDescriptor       -> 'EventBufferToken'=20
                                  [ LBRKT eventSpec *(COMMA eventSpec) =
RBRKT ]
3) indAudeventBufferDescriptor -> 'EventBufferToken'=20
                                  LBRKT indAudeventSpec RBRKT

One conflict between rule 1) and 2) and now another conflict
between rule 2) and 3)

So, depending on the number of tokens after the 'EventBufferToken', we =
get:
 - Zero        -> auditItem
 - One         -> indAudeventBufferDescriptor
 - Two or more -> eventBufferDescriptor

Is this correct?

Regards,
=09/BMK

Anil Jangam writes:
 > This particular question has been repeated for a number of times so =
far.
 > Even I had the same doubt for which Tom has replied as follows: (Mar=
ked with
 > ####>).
 > I think we need to fix this now.
 >=20
 > ####> STARTS
 > ----- Original Message -----
 > From: Tom-PT Taylor
 > To: 'Anil Jangam' ; Kevin Boyle
 > Sent: Wednesday, January 22, 2003 10:40 PM
 > Subject: RE: [Megaco] auditReturnParameter in AmmsReply
 >=20
 >=20
 > I suppose as the guy who concocted this syntax I should answer the q=
uestion.
 > You return the auditItem.  That was my shortcut for returning descri=
ptor
 > name only.
 >=20
 > Apparently there is a parsing problem with this syntax, but we never=
 seem to
 > have taken the step of resolving it.
 > ####> ENDS
 >=20
 > ----- Original Message -----
 > From: "Micael Karlberg" <micael.karlberg@ericsson.com>
 > To: <megaco@ietf.org>
 > Sent: Thursday, July 17, 2003 3:16 PM
 > Subject: [Megaco] Ambiguous definition of auditReturnParameter in v2=
 ABNF
 >=20
 >=20
 > > Hi,
 > >
 > > The 'auditReturnParameter' appears to be ambiguously defined in ve=
rsion 2
 > > of the ABNF.
 > >
 > > An example. If the 'auditReturnParameter' contains the following
 > > sequence of tokens:
 > >
 > >    "EB { hobbes }"
 > >
 > > i.e.
 > >
 > >     EventBufferToken LBRKT pkgdName RBRKT
 > >
 > > then it may be an 'auditItem' (see 'indAudeventBufferDescriptor') =
or an
 > > 'eventBufferDescriptor'
 > >
 > > What is the intention here? Should this sequence of tokens be
 > > interpreted as an 'auditItem' or an 'eventBufferDescriptor?
 > >
 > > As a parser implementor I need a well defined, unambiguous grammar=
 to
 > > rely on.
 > >
 > > The grammar looks like this (a little bit simplified):
 > >
 > >   auditReturnParameter        =3D eventBufferDescriptor / auditIte=
m
 > >
 > >   eventBufferDescriptor       =3D EventBufferToken
 > >                                 [ LBRKT eventSpec *(COMMA eventSpe=
c)
 > RBRKT]
 > >
 > >   eventSpec                   =3D pkgdName
 > >                                 [ LBRKT eventSpecParameter
 > >                                         *(COMMA eventSpecParameter=
) RBRKT]
 > >
 > >   auditItem                   =3D indAudterminationAudit
 > >
 > >   indAudterminationAudit      =3D indAudauditReturnParameter
 > >                                 *(COMMA insAudauditReturnParameter=
)
 > >
 > >   indAudauditReturnParameter  =3D indAudeventBufferDescriptor
 > >
 > >   indAudeventBufferDescriptor =3D EventBufferToken LBRKT indAudeve=
ntSpec
 > RBRKT
 > >
 > >   indAudeventSpec             =3D pkgdName
 > >                                 [ LBRKT indAudeventSpecParameter R=
BRKT ]
 > >
 > >
 > > Regards,
 > > /BMK
 > >
 > > _______________________________________________
 > > Megaco mailing list
 > > Megaco@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/megaco
 > >

--=20
Micael Karlberg          Ericsson AB, =C4lvsj=F6 Sweden
Tel:  +46 8 727 5668     EAB/UHK/KD - OTP Product Development
ECN:  851 5668           Mail: micael.karlberg@ericsson.com
Fax:  +46 8 727 5775   =20

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


From exim@www1.ietf.org  Fri Jul 18 05:23:38 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24301
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jul 2003 05:23:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dRSG-0004Uv-Lf
	for megaco-archive@odin.ietf.org; Fri, 18 Jul 2003 05:23:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I9N8JN017283
	for megaco-archive@odin.ietf.org; Fri, 18 Jul 2003 05:23:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dRSG-0004Ug-HS
	for megaco-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 05:23:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24280
	for <megaco-web-archive@ietf.org>; Fri, 18 Jul 2003 05:23:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dRSD-0006vy-00
	for megaco-web-archive@ietf.org; Fri, 18 Jul 2003 05:23:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dRS7-0006vv-00
	for megaco-web-archive@ietf.org; Fri, 18 Jul 2003 05:22:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dRS9-0004S3-D1; Fri, 18 Jul 2003 05:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dRRt-0004RN-Uf
	for megaco@optimus.ietf.org; Fri, 18 Jul 2003 05:22:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24271
	for <megaco@ietf.org>; Fri, 18 Jul 2003 05:22:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dRRl-0006vd-00
	for megaco@ietf.org; Fri, 18 Jul 2003 05:22:37 -0400
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49] helo=albatross.tn.sw.ericsson.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dRRa-0006vE-00
	for megaco@ietf.org; Fri, 18 Jul 2003 05:22:27 -0400
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118])
	by albatross.tn.sw.ericsson.se (8.12.9/8.12.9/WIREfire-1.6b) with ESMTP id h6I9M2Ii020119;
	Fri, 18 Jul 2003 11:22:02 +0200 (MEST)
Received: from super.du.uab.ericsson.se ([134.138.176.16]) by esealnt612.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55)
	id NW4XJZ7Q; Fri, 18 Jul 2003 11:21:32 +0200
Received: from bifur.du.uab.ericsson.se (daemon@bifur [134.138.177.75])
	by super.du.uab.ericsson.se (8.10.1/8.10.1/erix-1.8) with ESMTP id h6I9LVD29283;
	Fri, 18 Jul 2003 11:21:32 +0200 (MET DST)
Received: (from bmk@localhost)
	by bifur.du.uab.ericsson.se (8.11.6+Sun/8.9.1/client-1.0) id h6I9LV405083;
	Fri, 18 Jul 2003 11:21:31 +0200 (MEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-ID: <16151.48138.771516.776631@gargle.gargle.HOWL>
Date: Fri, 18 Jul 2003 11:21:14 +0200
From: Micael Karlberg <micael.karlberg@ericsson.com>
Reply-To: micael.karlberg@ericsson.com
Organization: Ericsson AB (EAB/UKH/KD)
To: "Anil Jangam" <anilj@mahindrabt.com>
Cc: <megaco@ietf.org>, "Tom-PT Taylor" <taylor@nortelnetworks.com>,
        "Kevin Boyle" <kboyle@nortelnetworks.com>
Subject: Re: [Megaco] Ambiguous definition of auditReturnParameter in v2 ABNF
In-Reply-To: <00e301c34c58$c21b2de0$4c0d050a@mahindrabt.com>
References: <16150.27894.389089.986520@gargle.gargle.HOWL>
	<00e301c34c58$c21b2de0$4c0d050a@mahindrabt.com>
X-Mailer: VM 7.07 under Emacs 21.1.1
Content-Transfer-Encoding: quoted-printable
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

So, now we have yet another parse conflict regarding 'EventBufferToken'=
?

We three rules:

1) auditItem                   -> 'EventBufferToken'
2) eventBufferDescriptor       -> 'EventBufferToken'=20
                                  [ LBRKT eventSpec *(COMMA eventSpec) =
RBRKT ]
3) indAudeventBufferDescriptor -> 'EventBufferToken'=20
                                  LBRKT indAudeventSpec RBRKT

One conflict between rule 1) and 2) and now another conflict
between rule 2) and 3)

So, depending on the number of tokens after the 'EventBufferToken', we =
get:
 - Zero        -> auditItem
 - One         -> indAudeventBufferDescriptor
 - Two or more -> eventBufferDescriptor

Is this correct?

Regards,
=09/BMK

Anil Jangam writes:
 > This particular question has been repeated for a number of times so =
far.
 > Even I had the same doubt for which Tom has replied as follows: (Mar=
ked with
 > ####>).
 > I think we need to fix this now.
 >=20
 > ####> STARTS
 > ----- Original Message -----
 > From: Tom-PT Taylor
 > To: 'Anil Jangam' ; Kevin Boyle
 > Sent: Wednesday, January 22, 2003 10:40 PM
 > Subject: RE: [Megaco] auditReturnParameter in AmmsReply
 >=20
 >=20
 > I suppose as the guy who concocted this syntax I should answer the q=
uestion.
 > You return the auditItem.  That was my shortcut for returning descri=
ptor
 > name only.
 >=20
 > Apparently there is a parsing problem with this syntax, but we never=
 seem to
 > have taken the step of resolving it.
 > ####> ENDS
 >=20
 > ----- Original Message -----
 > From: "Micael Karlberg" <micael.karlberg@ericsson.com>
 > To: <megaco@ietf.org>
 > Sent: Thursday, July 17, 2003 3:16 PM
 > Subject: [Megaco] Ambiguous definition of auditReturnParameter in v2=
 ABNF
 >=20
 >=20
 > > Hi,
 > >
 > > The 'auditReturnParameter' appears to be ambiguously defined in ve=
rsion 2
 > > of the ABNF.
 > >
 > > An example. If the 'auditReturnParameter' contains the following
 > > sequence of tokens:
 > >
 > >    "EB { hobbes }"
 > >
 > > i.e.
 > >
 > >     EventBufferToken LBRKT pkgdName RBRKT
 > >
 > > then it may be an 'auditItem' (see 'indAudeventBufferDescriptor') =
or an
 > > 'eventBufferDescriptor'
 > >
 > > What is the intention here? Should this sequence of tokens be
 > > interpreted as an 'auditItem' or an 'eventBufferDescriptor?
 > >
 > > As a parser implementor I need a well defined, unambiguous grammar=
 to
 > > rely on.
 > >
 > > The grammar looks like this (a little bit simplified):
 > >
 > >   auditReturnParameter        =3D eventBufferDescriptor / auditIte=
m
 > >
 > >   eventBufferDescriptor       =3D EventBufferToken
 > >                                 [ LBRKT eventSpec *(COMMA eventSpe=
c)
 > RBRKT]
 > >
 > >   eventSpec                   =3D pkgdName
 > >                                 [ LBRKT eventSpecParameter
 > >                                         *(COMMA eventSpecParameter=
) RBRKT]
 > >
 > >   auditItem                   =3D indAudterminationAudit
 > >
 > >   indAudterminationAudit      =3D indAudauditReturnParameter
 > >                                 *(COMMA insAudauditReturnParameter=
)
 > >
 > >   indAudauditReturnParameter  =3D indAudeventBufferDescriptor
 > >
 > >   indAudeventBufferDescriptor =3D EventBufferToken LBRKT indAudeve=
ntSpec
 > RBRKT
 > >
 > >   indAudeventSpec             =3D pkgdName
 > >                                 [ LBRKT indAudeventSpecParameter R=
BRKT ]
 > >
 > >
 > > Regards,
 > > /BMK
 > >
 > > _______________________________________________
 > > Megaco mailing list
 > > Megaco@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/megaco
 > >

--=20
Micael Karlberg          Ericsson AB, =C4lvsj=F6 Sweden
Tel:  +46 8 727 5668     EAB/UHK/KD - OTP Product Development
ECN:  851 5668           Mail: micael.karlberg@ericsson.com
Fax:  +46 8 727 5775   =20

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



From megaco-admin@ietf.org  Fri Jul 18 07:57:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27769
	for <megaco-archive@lists.ietf.org>; Fri, 18 Jul 2003 07:57:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dTrC-00034J-2Y; Fri, 18 Jul 2003 07:57:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dTqd-00033b-LZ
	for megaco@optimus.ietf.org; Fri, 18 Jul 2003 07:56:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27723
	for <megaco@ietf.org>; Fri, 18 Jul 2003 07:56:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dTqc-0000Hs-00
	for megaco@ietf.org; Fri, 18 Jul 2003 07:56:26 -0400
Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dTqR-0000HS-00
	for megaco@ietf.org; Fri, 18 Jul 2003 07:56:15 -0400
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6IBtIs28764
	for <megaco@ietf.org>; Fri, 18 Jul 2003 07:55:19 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NQAZB4YN>; Fri, 18 Jul 2003 07:55:12 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C0A736DAC@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: FND-AD Wang JuLin <JuLin.Wang@alcatel-sbell.com.cn>,
        "Megaco (E-mail)"
	 <megaco@ietf.org>, wangfei@wri.com.cn
Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
	 Modify's response
Date: Fri, 18 Jul 2003 07:55:10 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

The Signals descriptor cannot be underspecified, or overspecified.
Therefore, it cannot be modified.

The only way an MG would be able to respond with the Signals descriptor is
if it were audited.

Kevin

-----Original Message-----
From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] 
Sent: Friday, July 18, 2003 4:39 AM
To: Boyle, Kevin [NCRTP:3Z40:EXCH]; Megaco (E-mail); wangfei@wri.com.cn
Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
Modify's response


Hi, Kevin,
In chapter Add command, it was written:
All descriptors that can be modified could be returned by MG if a parameter
was underspecified or overspecified.  ObservedEvents, Statistics, and
Packages, and the EventBuffer Descriptors are returned only if requested in
the AuditDescriptor. I wonder the Signal descriptor can be modified or not.
In what case can the gateway send Add/Modify/Subtract command reply with
signal descriptor?  
Please correct me if i misunderstood the protocol.

>-----Original Message-----
>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
>Sent: Friday, July 18, 2003 11:35 AM
>To: FND-AD Wang JuLin; Megaco (E-mail)
>Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor 
>in Modify's response
>
>
>Uhhh... Where, exactly, does the spec indicate that the MG can modify a 
>signal applied by the MGC?  That is not how I read the spec.
>
>Example 1 is not correct.  Example 2 is.
>
>Kevin
>
>-----Original Message-----
>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn]
>Sent: Thursday, July 17, 2003 11:19 PM
>To: Megaco (E-mail)
>Subject: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
>Modify's response
>
>
>Hi,List,
>Can anybody help me on this item which i had posted before?
>Thanks a lot!
>
>Jerry
>
>>-----Original Message-----
>>From: FND-AD Wang JuLin
>>Sent: Wednesday, July 09, 2003 1:22 PM
>>To: Megaco (E-mail)
>>Subject: [Megaco] question about signal descriptor in
>Modify's response
>>
>>
>>Hi all,
>>According to the protocol,signal descriptor can be modified and 
>>returned in Modify's response.Can we construct the Modify 's response 
>>whatever we want to implement our product features?Here are two 
>>examples as follows. Example 1:
>>MGC--->MG
>>MEGACO/1 [15.8.1.10]:2944 
>>   Transaction = 10001 { 
>>       Context = - { 
>>           Modify = ROOT {Signals  {xxx/yyy   {k=1,
>>                                                     ea = 1, 
>>                                                     random
>=1224}}    
>>           } 
>>       } 
>>   }
>>
>>MG--->MGC
>>MEGACO/1 [15.8.1.18]:2944
>>Reply = 10001 {
>>Context = - {Modify = ROOT{
>>Signals {xxx/yyy{key=22,
>>ea = 1 
>>}}    
>>           } } }
>>Example 2: 
>>MGC--->MG
>>MEGACO/1 [15.8.1.10]:2944 
>>   Transaction = 10001 { 
>>       Context = - { 
>>           Modify = ROOT {Signals  {xxx/zzz   {t=1},
>>                                                         
>>xxx/yyy   {k=2,
>>                                                     ea = 1, 
>>                                                     random
>=1223}}    
>>           } 
>>       } 
>>   }
>> 
>>MG--->MGC
>>MEGACO/1 [15.8.1.18]:2944
>>Reply = 10001 {
>>Context = - {Modify = ROOT}}
>>
>>I wonder if the above  two examples are suitable or not when both are 
>>adopted in a scenario for gateway to implement some features.Please 
>>clear my mind.Thanks in advance!
>>
>> best  regards
>>JJerry Wang
>>tel:(8621)58541240 ext 9531 
>>MP:13621761050 
>>mailto:Julin.Wang@alcatel-sbell.com.cn 
>>Alcatel Shanghai Bell Co.LTD 
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>

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


From exim@www1.ietf.org  Fri Jul 18 07:57:39 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27788
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jul 2003 07:57:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dTrK-00035i-G8
	for megaco-archive@odin.ietf.org; Fri, 18 Jul 2003 07:57:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6IBvAZA011876
	for megaco-archive@odin.ietf.org; Fri, 18 Jul 2003 07:57:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dTrJ-00035S-0F
	for megaco-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 07:57:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27743
	for <megaco-web-archive@ietf.org>; Fri, 18 Jul 2003 07:57:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dTrI-0000IK-00
	for megaco-web-archive@ietf.org; Fri, 18 Jul 2003 07:57:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dTrC-0000IH-00
	for megaco-web-archive@ietf.org; Fri, 18 Jul 2003 07:57:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dTrC-00034J-2Y; Fri, 18 Jul 2003 07:57:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dTqd-00033b-LZ
	for megaco@optimus.ietf.org; Fri, 18 Jul 2003 07:56:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27723
	for <megaco@ietf.org>; Fri, 18 Jul 2003 07:56:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dTqc-0000Hs-00
	for megaco@ietf.org; Fri, 18 Jul 2003 07:56:26 -0400
Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dTqR-0000HS-00
	for megaco@ietf.org; Fri, 18 Jul 2003 07:56:15 -0400
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6IBtIs28764
	for <megaco@ietf.org>; Fri, 18 Jul 2003 07:55:19 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NQAZB4YN>; Fri, 18 Jul 2003 07:55:12 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C0A736DAC@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: FND-AD Wang JuLin <JuLin.Wang@alcatel-sbell.com.cn>,
        "Megaco (E-mail)"
	 <megaco@ietf.org>, wangfei@wri.com.cn
Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
	 Modify's response
Date: Fri, 18 Jul 2003 07:55:10 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

The Signals descriptor cannot be underspecified, or overspecified.
Therefore, it cannot be modified.

The only way an MG would be able to respond with the Signals descriptor is
if it were audited.

Kevin

-----Original Message-----
From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn] 
Sent: Friday, July 18, 2003 4:39 AM
To: Boyle, Kevin [NCRTP:3Z40:EXCH]; Megaco (E-mail); wangfei@wri.com.cn
Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
Modify's response


Hi, Kevin,
In chapter Add command, it was written:
All descriptors that can be modified could be returned by MG if a parameter
was underspecified or overspecified.  ObservedEvents, Statistics, and
Packages, and the EventBuffer Descriptors are returned only if requested in
the AuditDescriptor. I wonder the Signal descriptor can be modified or not.
In what case can the gateway send Add/Modify/Subtract command reply with
signal descriptor?  
Please correct me if i misunderstood the protocol.

>-----Original Message-----
>From: Kevin Boyle [mailto:kboyle@nortelnetworks.com]
>Sent: Friday, July 18, 2003 11:35 AM
>To: FND-AD Wang JuLin; Megaco (E-mail)
>Subject: RE: [Megaco] +AFs-Megaco+AF0- question about signal descriptor 
>in Modify's response
>
>
>Uhhh... Where, exactly, does the spec indicate that the MG can modify a 
>signal applied by the MGC?  That is not how I read the spec.
>
>Example 1 is not correct.  Example 2 is.
>
>Kevin
>
>-----Original Message-----
>From: FND-AD Wang JuLin [mailto:JuLin.Wang@alcatel-sbell.com.cn]
>Sent: Thursday, July 17, 2003 11:19 PM
>To: Megaco (E-mail)
>Subject: [Megaco] +AFs-Megaco+AF0- question about signal descriptor in
>Modify's response
>
>
>Hi,List,
>Can anybody help me on this item which i had posted before?
>Thanks a lot!
>
>Jerry
>
>>-----Original Message-----
>>From: FND-AD Wang JuLin
>>Sent: Wednesday, July 09, 2003 1:22 PM
>>To: Megaco (E-mail)
>>Subject: [Megaco] question about signal descriptor in
>Modify's response
>>
>>
>>Hi all,
>>According to the protocol,signal descriptor can be modified and 
>>returned in Modify's response.Can we construct the Modify 's response 
>>whatever we want to implement our product features?Here are two 
>>examples as follows. Example 1:
>>MGC--->MG
>>MEGACO/1 [15.8.1.10]:2944 
>>   Transaction = 10001 { 
>>       Context = - { 
>>           Modify = ROOT {Signals  {xxx/yyy   {k=1,
>>                                                     ea = 1, 
>>                                                     random
>=1224}}    
>>           } 
>>       } 
>>   }
>>
>>MG--->MGC
>>MEGACO/1 [15.8.1.18]:2944
>>Reply = 10001 {
>>Context = - {Modify = ROOT{
>>Signals {xxx/yyy{key=22,
>>ea = 1 
>>}}    
>>           } } }
>>Example 2: 
>>MGC--->MG
>>MEGACO/1 [15.8.1.10]:2944 
>>   Transaction = 10001 { 
>>       Context = - { 
>>           Modify = ROOT {Signals  {xxx/zzz   {t=1},
>>                                                         
>>xxx/yyy   {k=2,
>>                                                     ea = 1, 
>>                                                     random
>=1223}}    
>>           } 
>>       } 
>>   }
>> 
>>MG--->MGC
>>MEGACO/1 [15.8.1.18]:2944
>>Reply = 10001 {
>>Context = - {Modify = ROOT}}
>>
>>I wonder if the above  two examples are suitable or not when both are 
>>adopted in a scenario for gateway to implement some features.Please 
>>clear my mind.Thanks in advance!
>>
>> best  regards
>>JJerry Wang
>>tel:(8621)58541240 ext 9531 
>>MP:13621761050 
>>mailto:Julin.Wang@alcatel-sbell.com.cn 
>>Alcatel Shanghai Bell Co.LTD 
>>
>>_______________________________________________
>>Megaco mailing list
>>Megaco@ietf.org
>>https://www1.ietf.org/mailman/listinfo/megaco
>>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>

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



From megaco-admin@ietf.org  Fri Jul 18 09:37:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29856
	for <megaco-archive@lists.ietf.org>; Fri, 18 Jul 2003 09:37:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dVPx-0006R9-Ff; Fri, 18 Jul 2003 09:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dVPl-0006QV-SZ
	for megaco@optimus.ietf.org; Fri, 18 Jul 2003 09:36:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29830
	for <megaco@ietf.org>; Fri, 18 Jul 2003 09:36:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dVPk-00011u-00
	for megaco@ietf.org; Fri, 18 Jul 2003 09:36:48 -0400
Received: from [202.41.72.121] (helo=ws9.cdotb.ernet.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dVPJ-00010q-00
	for megaco@ietf.org; Fri, 18 Jul 2003 09:36:37 -0400
Received: from cdotb.ernet.in ([192.168.51.243])
	by ws9.cdotb.ernet.in (8.9.3/8.9.3) with ESMTP id SAA11880;
	Fri, 18 Jul 2003 18:33:01 +0500 (GMT+0500)
Message-ID: <3F18891D.4000003@cdotb.ernet.in>
Date: Fri, 18 Jul 2003 18:56:13 -0500
From: Krishnamurthy V <krish@cdotb.ernet.in>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020827
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom Taylor <taylor@nortelnetworks.com>
CC: titty@cdotb.ernet.in, megaco@ietf.org
Subject: Re: [Megaco] Subtract before Add reply
References: <3F155FB2.3010803@cdotb.ernet.in> <3F164507.60309@nortelnetworks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Tom,

one small clarification:

if the add is the first addition to the context (i.e. new context
creation), then that might be the solution.

but if the add is to the existing context, then mgc might know
the contextid to be used.  in that case, only terminationid
needs to be wildcarded (may be partially) in order
to minimize the casualities.

am i correct?

thank you.
krish.

Tom Taylor wrote:

> I think you've answered your own question -- though I suppose a 
> wildcard subtract covering all contexts and terminations might do the 
> job if it lost the race with the add.
>
> Titty Thomas wrote:
>
>> Hi,
>>            Can the MGC subtract a termination after issuing an add 
>> command
>>
>>       but before it got the add reply.
>>
>>       If so, what should be the context id and the termination id (if 
>> MGC has added
>>           an ephemeral termination) to be used in the subtract command.
>>
>> Warm regards,
>> -- Titty
>>
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco



-- 
-------------------------------------------------------------------------
V Krishnamurthy			Phone (O): 080-2263399 Ext:255
Internet Telephony,		      (R): 080-3339368
C-DoT, 71/1, Miller Road,
Bangalore - 560052
-------------------------------------------------------------------------
The very strength that protects the heart from injury is the strength
that prevents the heart from enlarging to its intended greatness within.
-Kahlil Gibran.
-------------------------------------------------------------------------



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


From exim@www1.ietf.org  Fri Jul 18 09:37:42 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29875
	for <megaco-archive@odin.ietf.org>; Fri, 18 Jul 2003 09:37:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dVQB-0006XP-8K
	for megaco-archive@odin.ietf.org; Fri, 18 Jul 2003 09:37:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6IDbFZm025125
	for megaco-archive@odin.ietf.org; Fri, 18 Jul 2003 09:37:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dVQB-0006X2-40
	for megaco-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 09:37:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29842
	for <megaco-web-archive@ietf.org>; Fri, 18 Jul 2003 09:37:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dVQ9-000128-00
	for megaco-web-archive@ietf.org; Fri, 18 Jul 2003 09:37:13 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dVQ3-000124-00
	for megaco-web-archive@ietf.org; Fri, 18 Jul 2003 09:37:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dVPx-0006R9-Ff; Fri, 18 Jul 2003 09:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19dVPl-0006QV-SZ
	for megaco@optimus.ietf.org; Fri, 18 Jul 2003 09:36:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29830
	for <megaco@ietf.org>; Fri, 18 Jul 2003 09:36:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19dVPk-00011u-00
	for megaco@ietf.org; Fri, 18 Jul 2003 09:36:48 -0400
Received: from [202.41.72.121] (helo=ws9.cdotb.ernet.in)
	by ietf-mx with esmtp (Exim 4.12)
	id 19dVPJ-00010q-00
	for megaco@ietf.org; Fri, 18 Jul 2003 09:36:37 -0400
Received: from cdotb.ernet.in ([192.168.51.243])
	by ws9.cdotb.ernet.in (8.9.3/8.9.3) with ESMTP id SAA11880;
	Fri, 18 Jul 2003 18:33:01 +0500 (GMT+0500)
Message-ID: <3F18891D.4000003@cdotb.ernet.in>
Date: Fri, 18 Jul 2003 18:56:13 -0500
From: Krishnamurthy V <krish@cdotb.ernet.in>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020827
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom Taylor <taylor@nortelnetworks.com>
CC: titty@cdotb.ernet.in, megaco@ietf.org
Subject: Re: [Megaco] Subtract before Add reply
References: <3F155FB2.3010803@cdotb.ernet.in> <3F164507.60309@nortelnetworks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Tom,

one small clarification:

if the add is the first addition to the context (i.e. new context
creation), then that might be the solution.

but if the add is to the existing context, then mgc might know
the contextid to be used.  in that case, only terminationid
needs to be wildcarded (may be partially) in order
to minimize the casualities.

am i correct?

thank you.
krish.

Tom Taylor wrote:

> I think you've answered your own question -- though I suppose a 
> wildcard subtract covering all contexts and terminations might do the 
> job if it lost the race with the add.
>
> Titty Thomas wrote:
>
>> Hi,
>>            Can the MGC subtract a termination after issuing an add 
>> command
>>
>>       but before it got the add reply.
>>
>>       If so, what should be the context id and the termination id (if 
>> MGC has added
>>           an ephemeral termination) to be used in the subtract command.
>>
>> Warm regards,
>> -- Titty
>>
>
>
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www1.ietf.org/mailman/listinfo/megaco



-- 
-------------------------------------------------------------------------
V Krishnamurthy			Phone (O): 080-2263399 Ext:255
Internet Telephony,		      (R): 080-3339368
C-DoT, 71/1, Miller Road,
Bangalore - 560052
-------------------------------------------------------------------------
The very strength that protects the heart from injury is the strength
that prevents the heart from enlarging to its intended greatness within.
-Kahlil Gibran.
-------------------------------------------------------------------------



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



From megaco-admin@ietf.org  Tue Jul 22 08:50:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11536
	for <megaco-archive@lists.ietf.org>; Tue, 22 Jul 2003 08:50:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ewah-0005b4-2M; Tue, 22 Jul 2003 08:50:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ewaF-0005ZL-6j
	for megaco@optimus.ietf.org; Tue, 22 Jul 2003 08:49:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11511
	for <megaco@ietf.org>; Tue, 22 Jul 2003 08:49:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ewaD-0004Ek-00
	for megaco@ietf.org; Tue, 22 Jul 2003 08:49:33 -0400
Received: from [211.206.122.239] (helo=mail.mailwave.co.kr)
	by ietf-mx with smtp (Exim 4.12)
	id 19ewa3-0004Ee-00
	for megaco@ietf.org; Tue, 22 Jul 2003 08:49:23 -0400
Received: from unknown[203.233.7.254] (envelope sender: <jayhkim@xener.com>)
          by 211.206.122.239 (TERRACE MAILCENTER) with ESMTP
          for <megaco@ietf.org>; Tue, 22 Jul 2003 21:53:23 KST +0900
From: "Jay H Kim" <jayhkim@xener.com>
To: <megaco@ietf.org>
Subject: [Megaco] At-Most-Once functionality and MId
Date: Tue, 22 Jul 2003 21:52:53 +0900
Message-ID: <AAEHIKDKKDOAFGKBJCMPOEKKDAAA.jayhkim@xener.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001B_01C3509B.9A4CC020"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C3509B.9A4CC020
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: base64

SGkgQWxsLA0KIA0KSWYgSSByZWNldmUgYSBNc2cxICBhbmQgcmVjZWl2ZSBhIE1zZzIgbGF0ZXIg
bGlrZSB0aGlzIDoNCiANCk1zZzEgICBtSWQoYS5iLmMuZDoxMjM0KSBUcnNSZXE6dHJhbnNhY3Rp
b25JRD0xMDAwICAgd2l0aCBzb3VyY2UgSVAgQWRkcmVzcyBhbmQgcG9ydCAobC5tLm4ucDoxMjM0
KQ0KTXNnMiAgIG1JZChhLmIuYy5kOjEyMzQpIFRyc1JlcTp0cmFuc2FjdGlvbklEPTEwMDAgICB3
aXRoIHNvdXJjZSBJUCBBZGRyZXNzIGFuZCBwb3J0IChwLnEuci5zOjEyMzQpDQogICAgICAgICAg
ICAoICBsLm0ubi5wICE9IHAucS5yLnMpDQogDQppcyB0aGUgTXNnMiAgcmV0cmFuc21pdHRlZCB0
cmFuc2FjdGlvbiBvZiBNc2cxIG9yIG5vdD8NCkkgdGhpbmsgTXNnMiBpcyBOb3QgdGhlIHJldHJh
bnNtaXR0ZWQgdHJhbnNhY2lvbiBvZiBNc2cxIGJlY2F1c2UgdGhlIHNvdXJjZSBJUCBBZGRyZXNz
IGFuZCBwb3J0IGlzIGRpZmZlcmVudCwgDQphbHRob3VnaCB0aGUgbUlkcyBhcmUgc2FtZS4NCg0K
QnV0LC4uLi4uLi4NCnJmYzM1MjUgYW5kIGRyYWZ0LWlldGYtbWVnYWNvLWgyNDh2Mi0wNCBBbm5l
eHQgRDEuMS4xIHNheXMgOg0KcmV0cmFuc21paXRlZCB0cmFuc2FjdGlvbnMgYXJlIGRldGVjdGVk
IGFzIGZvbGxvd2luZyBzY2hlbWUgOg0KIlRoZSB0cmFuc2FjdGlvbiAgaWRlbnRpZmllciBvZiBl
YWNoIGluY29taW5nIG1lc3NhZ2UgaXMgY29tcGFyZWQgdG8gdGhlIHRyYW5zYWN0aW9uDQogICBp
ZGVudGlmaWVycyBvZiB0aGUgcmVjZW50IHJlc3BvbnNlcyBzZW50IHRvIHRoZSBzYW1lIE1JZC4i
DQogDQogDQpDb3VsZCBhbnlib2R5IGdpdmUgbWUgYSBjbGFyaWZpY2F0aW9uPw0KRydEYXkNCg0K
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQpKYXkgSCBLaW0NClImRCBDZW50ZXIgIFhFTkVSIFN5c3RlbXMgSW5jLg0KT2ZmaWNlOiArODIt
Mi0zNDgyLTQ5MDAuIGV4dC40MTENCkZheDogKzgyLTItMzQ4My00OTAyDQorbWFpbHRvOmpheWhr
aW1AeGVuZXIuY29tDQpIb21lcGFnZTogd3d3LnhlbmVyLmNvbQ0KLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gDQoNCg==

------=_NextPart_000_001B_01C3509B.9A4CC020
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXVz
LWFzY2lpIiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA1
LjAwLjMzMTUuMjg3MCIgbmFtZT1HRU5FUkFUT1I+PC9IRUFEPg0KPEJPRFk+DQo8RElWPg0KPERJ
Vj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiBjbGFzcz05NjcwOTMwMTItMjIwNzIwMDM+
SGkgDQpBbGwsPC9TUEFOPjwvRk9OVD48L0RJVj4NCjxESVY+PFNQQU4gY2xhc3M9OTY3MDkzMDEy
LTIyMDcyMDAzPjwvU1BBTj48Rk9OVCBmYWNlPUFyaWFsIA0Kc2l6ZT0yPiZuYnNwOzwvRk9OVD48
L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PFNQQU4gY2xhc3M9OTY3MDkzMDEy
LTIyMDcyMDAzPklmIEkgcmVjZXZlJm5ic3A7YSANCk1zZzEmbmJzcDsgYW5kIHJlY2VpdmUgYSBN
c2cyIGxhdGVyIGxpa2UgdGhpcyA6PC9TUEFOPjwvRk9OVD48L0RJVj4NCjxESVY+PFNQQU4gY2xh
c3M9OTY3MDkzMDEyLTIyMDcyMDAzPjwvU1BBTj48Rk9OVCBmYWNlPUFyaWFsIA0Kc2l6ZT0yPiZu
YnNwOzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PFNQQU4gY2xh
c3M9OTY3MDkzMDEyLTIyMDcyMDAzPk1zZzEmbmJzcDsmbmJzcDsgDQptSWQoYS5iLmMuZDoxMjM0
KSBUcnNSZXE6dHJhbnNhY3Rpb25JRD0xMDAwJm5ic3A7Jm5ic3A7IHdpdGggc291cmNlIElQIEFk
ZHJlc3MgDQphbmQgcG9ydCAobC5tLm4ucDoxMjM0KTwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjxTUEFOIGNsYXNzPTk2NzA5MzAxMi0yMjA3MjAwMz5N
c2cyJm5ic3A7Jm5ic3A7IA0KbUlkKGEuYi5jLmQ6MTIzNCkgVHJzUmVxOnRyYW5zYWN0aW9uSUQ9
MTAwMCZuYnNwOyZuYnNwOyB3aXRoIHNvdXJjZSBJUCBBZGRyZXNzIA0KYW5kIHBvcnQgKHAucS5y
LnM6MTIzNCk8L1NQQU4+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9
Mj48U1BBTiANCmNsYXNzPTk2NzA5MzAxMi0yMjA3MjAwMz4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgDQooJm5ic3A7IGwu
bS5uLnAgIT0gcC5xLnIucyk8L1NQQU4+PC9GT05UPjwvRElWPg0KPERJVj48U1BBTiBjbGFzcz05
NjcwOTMwMTItMjIwNzIwMDM+PC9TUEFOPjxGT05UIGZhY2U9QXJpYWwgDQpzaXplPTI+Jm5ic3A7
PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiBjbGFzcz05
NjcwOTMwMTItMjIwNzIwMDM+aXMgdGhlIE1zZzImbmJzcDsgDQpyZXRyYW5zbWl0dGVkIHRyYW5z
YWN0aW9uIG9mIE1zZzEgb3Igbm90PzwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZh
Y2U9QXJpYWwgc2l6ZT0yPjxTUEFOIGNsYXNzPTk2NzA5MzAxMi0yMjA3MjAwMz5JIHRoaW5rIE1z
ZzIgaXMgTm90IA0KdGhlIHJldHJhbnNtaXR0ZWQgdHJhbnNhY2lvbiBvZiBNc2cxIGJlY2F1c2Ug
dGhlIHNvdXJjZSBJUCBBZGRyZXNzIGFuZCBwb3J0IGlzIA0KZGlmZmVyZW50LCA8L1NQQU4+PC9G
T05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiBjbGFzcz05Njcw
OTMwMTItMjIwNzIwMDM+YWx0aG91Z2ggdGhlIG1JZHMgDQphcmUgc2FtZS48L1NQQU4+PC9GT05U
PjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+
PFNQQU4gDQpjbGFzcz05NjcwOTMwMTItMjIwNzIwMDM+QnV0LC4uLi4uLi48L1NQQU4+PC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiBjbGFzcz05NjcwOTMw
MTItMjIwNzIwMDM+cmZjMzUyNSBhbmQgDQpkcmFmdC1pZXRmLW1lZ2Fjby1oMjQ4djItMDQgQW5u
ZXh0IEQxLjEuMSBzYXlzIDo8L1NQQU4+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFy
aWFsIHNpemU9Mj48U1BBTiBjbGFzcz05NjcwOTMwMTItMjIwNzIwMDM+cmV0cmFuc21paXRlZCAN
CnRyYW5zYWN0aW9ucyBhcmUgZGV0ZWN0ZWQgYXMgZm9sbG93aW5nIHNjaGVtZSA6PC9TUEFOPjwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PFNQQU4gY2xhc3M9OTY3
MDkzMDEyLTIyMDcyMDAzPiJUaGUgDQp0cmFuc2FjdGlvbiZuYnNwOyBpZGVudGlmaWVyIG9mIGVh
Y2ggaW5jb21pbmcgbWVzc2FnZSBpcyBjb21wYXJlZCB0byB0aGUgDQp0cmFuc2FjdGlvbjxCUj4m
bmJzcDsmbmJzcDsgaWRlbnRpZmllcnMgb2YgdGhlIHJlY2VudCByZXNwb25zZXMgc2VudCB0byB0
aGUgc2FtZSANCk1JZC4iPC9TUEFOPjwvRk9OVD48L0RJVj4NCjxESVY+PFNQQU4gY2xhc3M9OTY3
MDkzMDEyLTIyMDcyMDAzPjwvU1BBTj48Rk9OVCBmYWNlPUFyaWFsIA0Kc2l6ZT0yPiZuYnNwOzwv
Rk9OVD48L0RJVj4NCjxESVY+PFNQQU4gY2xhc3M9OTY3MDkzMDEyLTIyMDcyMDAzPjwvU1BBTj48
Rk9OVCBmYWNlPUFyaWFsIA0Kc2l6ZT0yPiZuYnNwOzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQg
ZmFjZT1BcmlhbCBzaXplPTI+PFNQQU4gY2xhc3M9OTY3MDkzMDEyLTIyMDcyMDAzPkNvdWxkIGFu
eWJvZHkgZ2l2ZSANCm1lIGEgY2xhcmlmaWNhdGlvbj88L1NQQU4+PC9GT05UPjwvRElWPg0KPERJ
Vj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiANCmNsYXNzPTk2NzA5MzAxMi0yMjA3MjAw
Mz5HJ0RheTwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxTUEFOIGNsYXNzPTk2NzA5MzAxMi0y
MjA3MjAwMz48L1NQQU4+Jm5ic3A7PC9ESVY+DQo8RElWPjxTUEFOIGNsYXNzPTk2NzA5MzAxMi0y
MjA3MjAwMz48L1NQQU4+PEZPTlQgDQpzaXplPTI+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPEJSPjxGT05UIA0KZmFjZT0iTW9ub3R5cGUg
Q29yc2l2YSI+SmF5IEggS2ltPEJSPjwvRk9OVD5SJmFtcDtEIENlbnRlciZuYnNwOyBYRU5FUiBT
eXN0ZW1zIA0KSW5jLjxCUj5PZmZpY2U6ICs4Mi0yLTM0ODItNDkwMC4gZXh0LjQxMTxCUj5GYXg6
ICs4Mi0yLTM0ODMtNDkwMjxCUj4rPC9GT05UPjxBIA0KaHJlZj0ibWFpbHRvOmpheWhraW1AeGVu
ZXIuY29tIj48Rk9OVCANCnNpemU9Mj5tYWlsdG86amF5aGtpbUB4ZW5lci5jb208L0ZPTlQ+PC9B
PjxCUj48Rk9OVCBzaXplPTI+SG9tZXBhZ2U6IA0Kd3d3LnhlbmVyLmNvbTxCUj4tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSANCjwvRk9OVD48
L0RJVj48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_001B_01C3509B.9A4CC020--


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


From exim@www1.ietf.org  Tue Jul 22 08:50:44 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11589
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jul 2003 08:50:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ewau-0005eX-Py
	for megaco-archive@odin.ietf.org; Tue, 22 Jul 2003 08:50:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MCoG2T021725
	for megaco-archive@odin.ietf.org; Tue, 22 Jul 2003 08:50:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ewau-0005eK-K6
	for megaco-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 08:50:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11532
	for <megaco-web-archive@ietf.org>; Tue, 22 Jul 2003 08:50:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ewat-0004FO-00
	for megaco-web-archive@ietf.org; Tue, 22 Jul 2003 08:50:15 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19ewan-0004F7-00
	for megaco-web-archive@ietf.org; Tue, 22 Jul 2003 08:50:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ewah-0005b4-2M; Tue, 22 Jul 2003 08:50:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19ewaF-0005ZL-6j
	for megaco@optimus.ietf.org; Tue, 22 Jul 2003 08:49:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11511
	for <megaco@ietf.org>; Tue, 22 Jul 2003 08:49:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19ewaD-0004Ek-00
	for megaco@ietf.org; Tue, 22 Jul 2003 08:49:33 -0400
Received: from [211.206.122.239] (helo=mail.mailwave.co.kr)
	by ietf-mx with smtp (Exim 4.12)
	id 19ewa3-0004Ee-00
	for megaco@ietf.org; Tue, 22 Jul 2003 08:49:23 -0400
Received: from unknown[203.233.7.254] (envelope sender: <jayhkim@xener.com>)
          by 211.206.122.239 (TERRACE MAILCENTER) with ESMTP
          for <megaco@ietf.org>; Tue, 22 Jul 2003 21:53:23 KST +0900
From: "Jay H Kim" <jayhkim@xener.com>
To: <megaco@ietf.org>
Subject: [Megaco] At-Most-Once functionality and MId
Date: Tue, 22 Jul 2003 21:52:53 +0900
Message-ID: <AAEHIKDKKDOAFGKBJCMPOEKKDAAA.jayhkim@xener.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001B_01C3509B.9A4CC020"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C3509B.9A4CC020
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: base64

SGkgQWxsLA0KIA0KSWYgSSByZWNldmUgYSBNc2cxICBhbmQgcmVjZWl2ZSBhIE1zZzIgbGF0ZXIg
bGlrZSB0aGlzIDoNCiANCk1zZzEgICBtSWQoYS5iLmMuZDoxMjM0KSBUcnNSZXE6dHJhbnNhY3Rp
b25JRD0xMDAwICAgd2l0aCBzb3VyY2UgSVAgQWRkcmVzcyBhbmQgcG9ydCAobC5tLm4ucDoxMjM0
KQ0KTXNnMiAgIG1JZChhLmIuYy5kOjEyMzQpIFRyc1JlcTp0cmFuc2FjdGlvbklEPTEwMDAgICB3
aXRoIHNvdXJjZSBJUCBBZGRyZXNzIGFuZCBwb3J0IChwLnEuci5zOjEyMzQpDQogICAgICAgICAg
ICAoICBsLm0ubi5wICE9IHAucS5yLnMpDQogDQppcyB0aGUgTXNnMiAgcmV0cmFuc21pdHRlZCB0
cmFuc2FjdGlvbiBvZiBNc2cxIG9yIG5vdD8NCkkgdGhpbmsgTXNnMiBpcyBOb3QgdGhlIHJldHJh
bnNtaXR0ZWQgdHJhbnNhY2lvbiBvZiBNc2cxIGJlY2F1c2UgdGhlIHNvdXJjZSBJUCBBZGRyZXNz
IGFuZCBwb3J0IGlzIGRpZmZlcmVudCwgDQphbHRob3VnaCB0aGUgbUlkcyBhcmUgc2FtZS4NCg0K
QnV0LC4uLi4uLi4NCnJmYzM1MjUgYW5kIGRyYWZ0LWlldGYtbWVnYWNvLWgyNDh2Mi0wNCBBbm5l
eHQgRDEuMS4xIHNheXMgOg0KcmV0cmFuc21paXRlZCB0cmFuc2FjdGlvbnMgYXJlIGRldGVjdGVk
IGFzIGZvbGxvd2luZyBzY2hlbWUgOg0KIlRoZSB0cmFuc2FjdGlvbiAgaWRlbnRpZmllciBvZiBl
YWNoIGluY29taW5nIG1lc3NhZ2UgaXMgY29tcGFyZWQgdG8gdGhlIHRyYW5zYWN0aW9uDQogICBp
ZGVudGlmaWVycyBvZiB0aGUgcmVjZW50IHJlc3BvbnNlcyBzZW50IHRvIHRoZSBzYW1lIE1JZC4i
DQogDQogDQpDb3VsZCBhbnlib2R5IGdpdmUgbWUgYSBjbGFyaWZpY2F0aW9uPw0KRydEYXkNCg0K
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQpKYXkgSCBLaW0NClImRCBDZW50ZXIgIFhFTkVSIFN5c3RlbXMgSW5jLg0KT2ZmaWNlOiArODIt
Mi0zNDgyLTQ5MDAuIGV4dC40MTENCkZheDogKzgyLTItMzQ4My00OTAyDQorbWFpbHRvOmpheWhr
aW1AeGVuZXIuY29tDQpIb21lcGFnZTogd3d3LnhlbmVyLmNvbQ0KLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gDQoNCg==

------=_NextPart_000_001B_01C3509B.9A4CC020
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXVz
LWFzY2lpIiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA1
LjAwLjMzMTUuMjg3MCIgbmFtZT1HRU5FUkFUT1I+PC9IRUFEPg0KPEJPRFk+DQo8RElWPg0KPERJ
Vj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiBjbGFzcz05NjcwOTMwMTItMjIwNzIwMDM+
SGkgDQpBbGwsPC9TUEFOPjwvRk9OVD48L0RJVj4NCjxESVY+PFNQQU4gY2xhc3M9OTY3MDkzMDEy
LTIyMDcyMDAzPjwvU1BBTj48Rk9OVCBmYWNlPUFyaWFsIA0Kc2l6ZT0yPiZuYnNwOzwvRk9OVD48
L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PFNQQU4gY2xhc3M9OTY3MDkzMDEy
LTIyMDcyMDAzPklmIEkgcmVjZXZlJm5ic3A7YSANCk1zZzEmbmJzcDsgYW5kIHJlY2VpdmUgYSBN
c2cyIGxhdGVyIGxpa2UgdGhpcyA6PC9TUEFOPjwvRk9OVD48L0RJVj4NCjxESVY+PFNQQU4gY2xh
c3M9OTY3MDkzMDEyLTIyMDcyMDAzPjwvU1BBTj48Rk9OVCBmYWNlPUFyaWFsIA0Kc2l6ZT0yPiZu
YnNwOzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PFNQQU4gY2xh
c3M9OTY3MDkzMDEyLTIyMDcyMDAzPk1zZzEmbmJzcDsmbmJzcDsgDQptSWQoYS5iLmMuZDoxMjM0
KSBUcnNSZXE6dHJhbnNhY3Rpb25JRD0xMDAwJm5ic3A7Jm5ic3A7IHdpdGggc291cmNlIElQIEFk
ZHJlc3MgDQphbmQgcG9ydCAobC5tLm4ucDoxMjM0KTwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjxTUEFOIGNsYXNzPTk2NzA5MzAxMi0yMjA3MjAwMz5N
c2cyJm5ic3A7Jm5ic3A7IA0KbUlkKGEuYi5jLmQ6MTIzNCkgVHJzUmVxOnRyYW5zYWN0aW9uSUQ9
MTAwMCZuYnNwOyZuYnNwOyB3aXRoIHNvdXJjZSBJUCBBZGRyZXNzIA0KYW5kIHBvcnQgKHAucS5y
LnM6MTIzNCk8L1NQQU4+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9
Mj48U1BBTiANCmNsYXNzPTk2NzA5MzAxMi0yMjA3MjAwMz4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgDQooJm5ic3A7IGwu
bS5uLnAgIT0gcC5xLnIucyk8L1NQQU4+PC9GT05UPjwvRElWPg0KPERJVj48U1BBTiBjbGFzcz05
NjcwOTMwMTItMjIwNzIwMDM+PC9TUEFOPjxGT05UIGZhY2U9QXJpYWwgDQpzaXplPTI+Jm5ic3A7
PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiBjbGFzcz05
NjcwOTMwMTItMjIwNzIwMDM+aXMgdGhlIE1zZzImbmJzcDsgDQpyZXRyYW5zbWl0dGVkIHRyYW5z
YWN0aW9uIG9mIE1zZzEgb3Igbm90PzwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZh
Y2U9QXJpYWwgc2l6ZT0yPjxTUEFOIGNsYXNzPTk2NzA5MzAxMi0yMjA3MjAwMz5JIHRoaW5rIE1z
ZzIgaXMgTm90IA0KdGhlIHJldHJhbnNtaXR0ZWQgdHJhbnNhY2lvbiBvZiBNc2cxIGJlY2F1c2Ug
dGhlIHNvdXJjZSBJUCBBZGRyZXNzIGFuZCBwb3J0IGlzIA0KZGlmZmVyZW50LCA8L1NQQU4+PC9G
T05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiBjbGFzcz05Njcw
OTMwMTItMjIwNzIwMDM+YWx0aG91Z2ggdGhlIG1JZHMgDQphcmUgc2FtZS48L1NQQU4+PC9GT05U
PjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+
PFNQQU4gDQpjbGFzcz05NjcwOTMwMTItMjIwNzIwMDM+QnV0LC4uLi4uLi48L1NQQU4+PC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiBjbGFzcz05NjcwOTMw
MTItMjIwNzIwMDM+cmZjMzUyNSBhbmQgDQpkcmFmdC1pZXRmLW1lZ2Fjby1oMjQ4djItMDQgQW5u
ZXh0IEQxLjEuMSBzYXlzIDo8L1NQQU4+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFy
aWFsIHNpemU9Mj48U1BBTiBjbGFzcz05NjcwOTMwMTItMjIwNzIwMDM+cmV0cmFuc21paXRlZCAN
CnRyYW5zYWN0aW9ucyBhcmUgZGV0ZWN0ZWQgYXMgZm9sbG93aW5nIHNjaGVtZSA6PC9TUEFOPjwv
Rk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PFNQQU4gY2xhc3M9OTY3
MDkzMDEyLTIyMDcyMDAzPiJUaGUgDQp0cmFuc2FjdGlvbiZuYnNwOyBpZGVudGlmaWVyIG9mIGVh
Y2ggaW5jb21pbmcgbWVzc2FnZSBpcyBjb21wYXJlZCB0byB0aGUgDQp0cmFuc2FjdGlvbjxCUj4m
bmJzcDsmbmJzcDsgaWRlbnRpZmllcnMgb2YgdGhlIHJlY2VudCByZXNwb25zZXMgc2VudCB0byB0
aGUgc2FtZSANCk1JZC4iPC9TUEFOPjwvRk9OVD48L0RJVj4NCjxESVY+PFNQQU4gY2xhc3M9OTY3
MDkzMDEyLTIyMDcyMDAzPjwvU1BBTj48Rk9OVCBmYWNlPUFyaWFsIA0Kc2l6ZT0yPiZuYnNwOzwv
Rk9OVD48L0RJVj4NCjxESVY+PFNQQU4gY2xhc3M9OTY3MDkzMDEyLTIyMDcyMDAzPjwvU1BBTj48
Rk9OVCBmYWNlPUFyaWFsIA0Kc2l6ZT0yPiZuYnNwOzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQg
ZmFjZT1BcmlhbCBzaXplPTI+PFNQQU4gY2xhc3M9OTY3MDkzMDEyLTIyMDcyMDAzPkNvdWxkIGFu
eWJvZHkgZ2l2ZSANCm1lIGEgY2xhcmlmaWNhdGlvbj88L1NQQU4+PC9GT05UPjwvRElWPg0KPERJ
Vj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiANCmNsYXNzPTk2NzA5MzAxMi0yMjA3MjAw
Mz5HJ0RheTwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxTUEFOIGNsYXNzPTk2NzA5MzAxMi0y
MjA3MjAwMz48L1NQQU4+Jm5ic3A7PC9ESVY+DQo8RElWPjxTUEFOIGNsYXNzPTk2NzA5MzAxMi0y
MjA3MjAwMz48L1NQQU4+PEZPTlQgDQpzaXplPTI+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPEJSPjxGT05UIA0KZmFjZT0iTW9ub3R5cGUg
Q29yc2l2YSI+SmF5IEggS2ltPEJSPjwvRk9OVD5SJmFtcDtEIENlbnRlciZuYnNwOyBYRU5FUiBT
eXN0ZW1zIA0KSW5jLjxCUj5PZmZpY2U6ICs4Mi0yLTM0ODItNDkwMC4gZXh0LjQxMTxCUj5GYXg6
ICs4Mi0yLTM0ODMtNDkwMjxCUj4rPC9GT05UPjxBIA0KaHJlZj0ibWFpbHRvOmpheWhraW1AeGVu
ZXIuY29tIj48Rk9OVCANCnNpemU9Mj5tYWlsdG86amF5aGtpbUB4ZW5lci5jb208L0ZPTlQ+PC9B
PjxCUj48Rk9OVCBzaXplPTI+SG9tZXBhZ2U6IA0Kd3d3LnhlbmVyLmNvbTxCUj4tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSANCjwvRk9OVD48
L0RJVj48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_001B_01C3509B.9A4CC020--


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



From megaco-admin@ietf.org  Tue Jul 22 21:10:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02637
	for <megaco-archive@lists.ietf.org>; Tue, 22 Jul 2003 21:10:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19f88n-0008Sm-Px; Tue, 22 Jul 2003 21:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19f88S-0008S9-Ku
	for megaco@optimus.ietf.org; Tue, 22 Jul 2003 21:09:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02629
	for <megaco@ietf.org>; Tue, 22 Jul 2003 21:09:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19f88Q-0000jG-00
	for megaco@ietf.org; Tue, 22 Jul 2003 21:09:38 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19f88F-0000jC-00
	for megaco@ietf.org; Tue, 22 Jul 2003 21:09:27 -0400
Received: from [172.16.1.210] (helo=CCPU00204)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19f87c-0003N5-U5; Tue, 22 Jul 2003 18:08:48 -0700
From: "Rashim Anand" <ranand@ccpu.com>
To: <megaco@ietf.org>
Subject: [Megaco] StreamIds in SCTP as transport
Date: Tue, 22 Jul 2003 18:10:33 -0700
Message-ID: <LLEMKHPJAECAPBFPABPNMEODCBAA.ranand@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

In H.248 annex H (transport over SCTP), section H.7, a recommendation is
given -

It is recommended that transactions related to one context are transported
over the same stream.

Now suppose the following sequence of messages is exchanged ->


   MGC  ------STR 1-----------> MG
          T=1 { C=$ ... }

   MGC  <---------------------- MG
          Reply=1 { C=5 ... }

   MGC  ------STR 2-----------> MG
          T=2 { C=5 ... }

   MGC  ------STR 2-----------> MG
          T=3 { C=5 ... }

   MGC  ------STR 2-----------> MG
          T=4 { C=5 ... }


where, "T=[0-9]* { C=... }" refers to transaction requests while,
"Reply=[0-9]* { C=... }" refers to transaction replies,
"C" stands for ContextId and
STR1, STR2 refer to the outgoing stream identifiers used by the MGC.


The question is - does having STR2 different from STR1 violate the
philosophy behind the H.7 recommendation?

IMHO, it does not since the context id 5 becomes known to the MGC only after
getting a reply from the MG. Without the assigned context id, the MGC can
not send any transactions related to that context and so can not cause any
head of line blocking to transactions related to other contexts.

Please let me know your opinion?

Thanks,
Rashim Anand




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


From exim@www1.ietf.org  Tue Jul 22 21:10:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02661
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jul 2003 21:10:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19f88v-0008UL-AT
	for megaco-archive@odin.ietf.org; Tue, 22 Jul 2003 21:10:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6N1A9ew032624
	for megaco-archive@odin.ietf.org; Tue, 22 Jul 2003 21:10:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19f88v-0008U7-6a
	for megaco-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 21:10:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02634
	for <megaco-web-archive@ietf.org>; Tue, 22 Jul 2003 21:10:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19f88s-0000jP-00
	for megaco-web-archive@ietf.org; Tue, 22 Jul 2003 21:10:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19f88n-0000jM-00
	for megaco-web-archive@ietf.org; Tue, 22 Jul 2003 21:10:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19f88n-0008Sm-Px; Tue, 22 Jul 2003 21:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19f88S-0008S9-Ku
	for megaco@optimus.ietf.org; Tue, 22 Jul 2003 21:09:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02629
	for <megaco@ietf.org>; Tue, 22 Jul 2003 21:09:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19f88Q-0000jG-00
	for megaco@ietf.org; Tue, 22 Jul 2003 21:09:38 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19f88F-0000jC-00
	for megaco@ietf.org; Tue, 22 Jul 2003 21:09:27 -0400
Received: from [172.16.1.210] (helo=CCPU00204)
	by smtp.ccpu.com with smtp (Exim 4.20 #1 (Debian))
	id 19f87c-0003N5-U5; Tue, 22 Jul 2003 18:08:48 -0700
From: "Rashim Anand" <ranand@ccpu.com>
To: <megaco@ietf.org>
Subject: [Megaco] StreamIds in SCTP as transport
Date: Tue, 22 Jul 2003 18:10:33 -0700
Message-ID: <LLEMKHPJAECAPBFPABPNMEODCBAA.ranand@ccpu.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

In H.248 annex H (transport over SCTP), section H.7, a recommendation is
given -

It is recommended that transactions related to one context are transported
over the same stream.

Now suppose the following sequence of messages is exchanged ->


   MGC  ------STR 1-----------> MG
          T=1 { C=$ ... }

   MGC  <---------------------- MG
          Reply=1 { C=5 ... }

   MGC  ------STR 2-----------> MG
          T=2 { C=5 ... }

   MGC  ------STR 2-----------> MG
          T=3 { C=5 ... }

   MGC  ------STR 2-----------> MG
          T=4 { C=5 ... }


where, "T=[0-9]* { C=... }" refers to transaction requests while,
"Reply=[0-9]* { C=... }" refers to transaction replies,
"C" stands for ContextId and
STR1, STR2 refer to the outgoing stream identifiers used by the MGC.


The question is - does having STR2 different from STR1 violate the
philosophy behind the H.7 recommendation?

IMHO, it does not since the context id 5 becomes known to the MGC only after
getting a reply from the MG. Without the assigned context id, the MGC can
not send any transactions related to that context and so can not cause any
head of line blocking to transactions related to other contexts.

Please let me know your opinion?

Thanks,
Rashim Anand




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



From megaco-admin@ietf.org  Tue Jul 22 23:39:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04479
	for <megaco-archive@lists.ietf.org>; Tue, 22 Jul 2003 23:39:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fASz-0003zN-NA; Tue, 22 Jul 2003 23:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fASt-0003zA-Nz
	for megaco@optimus.ietf.org; Tue, 22 Jul 2003 23:38:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04469
	for <megaco@ietf.org>; Tue, 22 Jul 2003 23:38:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fASr-0001Kr-00
	for megaco@ietf.org; Tue, 22 Jul 2003 23:38:53 -0400
Received: from [61.144.161.2] (helo=mta0.huawei.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19fASg-0001Kc-00
	for megaco@ietf.org; Tue, 22 Jul 2003 23:38:43 -0400
Received: from z26452 (mta0.huawei.com [172.17.1.62])
 by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12
 2002)) with ESMTPA id <0HIG00DJHKONTX@mta0.huawei.com> for megaco@ietf.org;
 Wed, 23 Jul 2003 11:36:24 +0800 (CST)
Date: Wed, 23 Jul 2003 11:36:23 +0800
From: zhangtao <zhangtao_hw@huawei.com>
Subject: Re: [Megaco] At-Most-Once functionality and MId
To: Jay H Kim <jayhkim@xener.com>
Cc: megaco@ietf.org
Message-id: <000c01c350cb$96f92780$97390b0a@huawei.com.cn>
Organization: huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
Content-type: multipart/alternative;
 boundary="Boundary_(ID_Zq0SghkaXsv7gVmKW+gnHQ)"
X-Priority: 3
X-MSMail-priority: Normal
References: <AAEHIKDKKDOAFGKBJCMPOEKKDAAA.jayhkim@xener.com>
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

--Boundary_(ID_Zq0SghkaXsv7gVmKW+gnHQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

MSG2 is a retransmitted message.
Because  one MID(namely MG or MGC) maybe have many IP ADDRESS or port.
  ----- Original Message ----- 
  From: Jay H Kim 
  To: megaco@ietf.org 
  Sent: Tuesday, July 22, 2003 8:52 PM
  Subject: [Megaco] At-Most-Once functionality and MId


  Hi All,
   
  If I receve a Msg1  and receive a Msg2 later like this :
   
  Msg1   mId(a.b.c.d:1234) TrsReq:transactionID=1000   with source IP Address and port (l.m.n.p:1234)
  Msg2   mId(a.b.c.d:1234) TrsReq:transactionID=1000   with source IP Address and port (p.q.r.s:1234)
              (  l.m.n.p != p.q.r.s)
   
  is the Msg2  retransmitted transaction of Msg1 or not?
  I think Msg2 is Not the retransmitted transacion of Msg1 because the source IP Address and port is different, 
  although the mIds are same.

  But,.......
  rfc3525 and draft-ietf-megaco-h248v2-04 Annext D1.1.1 says :
  retransmiited transactions are detected as following scheme :
  "The transaction  identifier of each incoming message is compared to the transaction
     identifiers of the recent responses sent to the same MId."
   
   
  Could anybody give me a clarification?
  G'Day
   
  ---------------------------------------------------------
  Jay H Kim
  R&D Center  XENER Systems Inc.
  Office: +82-2-3482-4900. ext.411
  Fax: +82-2-3483-4902
  +mailto:jayhkim@xener.com
  Homepage: www.xener.com
  -------------------------------------------------------- 


--Boundary_(ID_Zq0SghkaXsv7gVmKW+gnHQ)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.2919.6307" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=&#23435;&#20307; size=2>MSG2 is a retransmitted message.</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2>Because&nbsp; one MID(namely MG or MGC) maybe have 
many IP ADDRESS or port.</FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style="FONT: 9pt &#23435;&#20307;">----- Original Message ----- </DIV>
  <DIV style="BACKGROUND: #e4e4e4; FONT: 9pt &#23435;&#20307;; font-color: black"><B>From:</B> 
  <A href="mailto:jayhkim@xener.com" title=jayhkim@xener.com>Jay H Kim</A> 
</DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>To:</B> <A href="mailto:megaco@ietf.org" 
  title=megaco@ietf.org>megaco@ietf.org</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Sent:</B> Tuesday, July 22, 2003 8:52 PM</DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Subject:</B> [Megaco] At-Most-Once functionality 
  and MId</DIV>
  <DIV><BR></DIV>
  <DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>Hi 
  All,</SPAN></FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT face=Arial 
  size=2>&nbsp;</FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>If I receve&nbsp;a 
  Msg1&nbsp; and receive a Msg2 later like this :</SPAN></FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT face=Arial 
  size=2>&nbsp;</FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>Msg1&nbsp;&nbsp; 
  mId(a.b.c.d:1234) TrsReq:transactionID=1000&nbsp;&nbsp; with source IP Address 
  and port (l.m.n.p:1234)</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>Msg2&nbsp;&nbsp; 
  mId(a.b.c.d:1234) TrsReq:transactionID=1000&nbsp;&nbsp; with source IP Address 
  and port (p.q.r.s:1234)</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=967093012-22072003>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  (&nbsp; l.m.n.p != p.q.r.s)</SPAN></FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT face=Arial 
  size=2>&nbsp;</FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>is the Msg2&nbsp; 
  retransmitted transaction of Msg1 or not?</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>I think Msg2 is 
  Not the retransmitted transacion of Msg1 because the source IP Address and 
  port is different, </SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>although the mIds 
  are same.</SPAN></FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=967093012-22072003>But,.......</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>rfc3525 and 
  draft-ietf-megaco-h248v2-04 Annext D1.1.1 says :</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>retransmiited 
  transactions are detected as following scheme :</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>"The 
  transaction&nbsp; identifier of each incoming message is compared to the 
  transaction<BR>&nbsp;&nbsp; identifiers of the recent responses sent to the 
  same MId."</SPAN></FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT face=Arial 
  size=2>&nbsp;</FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT face=Arial 
  size=2>&nbsp;</FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>Could anybody give 
  me a clarification?</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=967093012-22072003>G'Day</SPAN></FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT 
  size=2>---------------------------------------------------------<BR><FONT 
  face="Monotype Corsiva">Jay H Kim<BR></FONT>R&amp;D Center&nbsp; XENER Systems 
  Inc.<BR>Office: +82-2-3482-4900. ext.411<BR>Fax: +82-2-3483-4902<BR>+</FONT><A 
  href="mailto:jayhkim@xener.com"><FONT 
  size=2>mailto:jayhkim@xener.com</FONT></A><BR><FONT size=2>Homepage: 
  www.xener.com<BR>-------------------------------------------------------- 
  </FONT></DIV></DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_Zq0SghkaXsv7gVmKW+gnHQ)--

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


From exim@www1.ietf.org  Tue Jul 22 23:39:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04501
	for <megaco-archive@odin.ietf.org>; Tue, 22 Jul 2003 23:39:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fAT6-000404-Ns
	for megaco-archive@odin.ietf.org; Tue, 22 Jul 2003 23:39:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6N3d84B015377
	for megaco-archive@odin.ietf.org; Tue, 22 Jul 2003 23:39:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fAT6-0003zw-HT
	for megaco-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 23:39:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04473
	for <megaco-web-archive@ietf.org>; Tue, 22 Jul 2003 23:39:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fAT4-0001Kz-00
	for megaco-web-archive@ietf.org; Tue, 22 Jul 2003 23:39:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19fASy-0001Kw-00
	for megaco-web-archive@ietf.org; Tue, 22 Jul 2003 23:39:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fASz-0003zN-NA; Tue, 22 Jul 2003 23:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fASt-0003zA-Nz
	for megaco@optimus.ietf.org; Tue, 22 Jul 2003 23:38:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04469
	for <megaco@ietf.org>; Tue, 22 Jul 2003 23:38:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fASr-0001Kr-00
	for megaco@ietf.org; Tue, 22 Jul 2003 23:38:53 -0400
Received: from [61.144.161.2] (helo=mta0.huawei.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19fASg-0001Kc-00
	for megaco@ietf.org; Tue, 22 Jul 2003 23:38:43 -0400
Received: from z26452 (mta0.huawei.com [172.17.1.62])
 by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12
 2002)) with ESMTPA id <0HIG00DJHKONTX@mta0.huawei.com> for megaco@ietf.org;
 Wed, 23 Jul 2003 11:36:24 +0800 (CST)
Date: Wed, 23 Jul 2003 11:36:23 +0800
From: zhangtao <zhangtao_hw@huawei.com>
Subject: Re: [Megaco] At-Most-Once functionality and MId
To: Jay H Kim <jayhkim@xener.com>
Cc: megaco@ietf.org
Message-id: <000c01c350cb$96f92780$97390b0a@huawei.com.cn>
Organization: huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
Content-type: multipart/alternative;
 boundary="Boundary_(ID_Zq0SghkaXsv7gVmKW+gnHQ)"
X-Priority: 3
X-MSMail-priority: Normal
References: <AAEHIKDKKDOAFGKBJCMPOEKKDAAA.jayhkim@xener.com>
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

--Boundary_(ID_Zq0SghkaXsv7gVmKW+gnHQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

MSG2 is a retransmitted message.
Because  one MID(namely MG or MGC) maybe have many IP ADDRESS or port.
  ----- Original Message ----- 
  From: Jay H Kim 
  To: megaco@ietf.org 
  Sent: Tuesday, July 22, 2003 8:52 PM
  Subject: [Megaco] At-Most-Once functionality and MId


  Hi All,
   
  If I receve a Msg1  and receive a Msg2 later like this :
   
  Msg1   mId(a.b.c.d:1234) TrsReq:transactionID=1000   with source IP Address and port (l.m.n.p:1234)
  Msg2   mId(a.b.c.d:1234) TrsReq:transactionID=1000   with source IP Address and port (p.q.r.s:1234)
              (  l.m.n.p != p.q.r.s)
   
  is the Msg2  retransmitted transaction of Msg1 or not?
  I think Msg2 is Not the retransmitted transacion of Msg1 because the source IP Address and port is different, 
  although the mIds are same.

  But,.......
  rfc3525 and draft-ietf-megaco-h248v2-04 Annext D1.1.1 says :
  retransmiited transactions are detected as following scheme :
  "The transaction  identifier of each incoming message is compared to the transaction
     identifiers of the recent responses sent to the same MId."
   
   
  Could anybody give me a clarification?
  G'Day
   
  ---------------------------------------------------------
  Jay H Kim
  R&D Center  XENER Systems Inc.
  Office: +82-2-3482-4900. ext.411
  Fax: +82-2-3483-4902
  +mailto:jayhkim@xener.com
  Homepage: www.xener.com
  -------------------------------------------------------- 


--Boundary_(ID_Zq0SghkaXsv7gVmKW+gnHQ)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.2919.6307" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=&#23435;&#20307; size=2>MSG2 is a retransmitted message.</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2>Because&nbsp; one MID(namely MG or MGC) maybe have 
many IP ADDRESS or port.</FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style="FONT: 9pt &#23435;&#20307;">----- Original Message ----- </DIV>
  <DIV style="BACKGROUND: #e4e4e4; FONT: 9pt &#23435;&#20307;; font-color: black"><B>From:</B> 
  <A href="mailto:jayhkim@xener.com" title=jayhkim@xener.com>Jay H Kim</A> 
</DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>To:</B> <A href="mailto:megaco@ietf.org" 
  title=megaco@ietf.org>megaco@ietf.org</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Sent:</B> Tuesday, July 22, 2003 8:52 PM</DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Subject:</B> [Megaco] At-Most-Once functionality 
  and MId</DIV>
  <DIV><BR></DIV>
  <DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>Hi 
  All,</SPAN></FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT face=Arial 
  size=2>&nbsp;</FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>If I receve&nbsp;a 
  Msg1&nbsp; and receive a Msg2 later like this :</SPAN></FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT face=Arial 
  size=2>&nbsp;</FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>Msg1&nbsp;&nbsp; 
  mId(a.b.c.d:1234) TrsReq:transactionID=1000&nbsp;&nbsp; with source IP Address 
  and port (l.m.n.p:1234)</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>Msg2&nbsp;&nbsp; 
  mId(a.b.c.d:1234) TrsReq:transactionID=1000&nbsp;&nbsp; with source IP Address 
  and port (p.q.r.s:1234)</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=967093012-22072003>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  (&nbsp; l.m.n.p != p.q.r.s)</SPAN></FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT face=Arial 
  size=2>&nbsp;</FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>is the Msg2&nbsp; 
  retransmitted transaction of Msg1 or not?</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>I think Msg2 is 
  Not the retransmitted transacion of Msg1 because the source IP Address and 
  port is different, </SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>although the mIds 
  are same.</SPAN></FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=967093012-22072003>But,.......</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>rfc3525 and 
  draft-ietf-megaco-h248v2-04 Annext D1.1.1 says :</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>retransmiited 
  transactions are detected as following scheme :</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>"The 
  transaction&nbsp; identifier of each incoming message is compared to the 
  transaction<BR>&nbsp;&nbsp; identifiers of the recent responses sent to the 
  same MId."</SPAN></FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT face=Arial 
  size=2>&nbsp;</FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT face=Arial 
  size=2>&nbsp;</FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN class=967093012-22072003>Could anybody give 
  me a clarification?</SPAN></FONT></DIV>
  <DIV><FONT face=Arial size=2><SPAN 
  class=967093012-22072003>G'Day</SPAN></FONT></DIV>
  <DIV><SPAN class=967093012-22072003></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=967093012-22072003></SPAN><FONT 
  size=2>---------------------------------------------------------<BR><FONT 
  face="Monotype Corsiva">Jay H Kim<BR></FONT>R&amp;D Center&nbsp; XENER Systems 
  Inc.<BR>Office: +82-2-3482-4900. ext.411<BR>Fax: +82-2-3483-4902<BR>+</FONT><A 
  href="mailto:jayhkim@xener.com"><FONT 
  size=2>mailto:jayhkim@xener.com</FONT></A><BR><FONT size=2>Homepage: 
  www.xener.com<BR>-------------------------------------------------------- 
  </FONT></DIV></DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_Zq0SghkaXsv7gVmKW+gnHQ)--

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



From megaco-admin@ietf.org  Wed Jul 23 00:02:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05008
	for <megaco-archive@lists.ietf.org>; Wed, 23 Jul 2003 00:02:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fApG-0004tg-1Z; Wed, 23 Jul 2003 00:02:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fAoH-0004rk-2U
	for megaco@optimus.ietf.org; Wed, 23 Jul 2003 00:01:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04978
	for <megaco@ietf.org>; Wed, 23 Jul 2003 00:00:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fAoE-0001Rx-00
	for megaco@ietf.org; Wed, 23 Jul 2003 00:00:58 -0400
Received: from wiprom2mx1.wipro.com ([203.197.164.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fAo1-0001Rd-00
	for megaco@ietf.org; Wed, 23 Jul 2003 00:00:47 -0400
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx1.wipro.com (8.12.9/8.12.9) with SMTP id h6N3xfxX028157
	for <megaco@ietf.org>; Wed, 23 Jul 2003 09:29:46 +0530 (IST)
Received: from blr-ec-msg01.wipro.com ([10.200.50.99]) by blr-ec-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 23 Jul 2003 09:29:40 +0530
Received: from RANJITHEC ([10.200.8.116]) by blr-ec-msg01.wipro.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 23 Jul 2003 09:29:40 +0530
Reply-To: <ranjith.mukundan@wipro.com>
From: "Ranjith Mukundan" <ranjith.mukundan@wipro.com>
To: "'Rashim Anand'" <ranand@ccpu.com>, <megaco@ietf.org>
Subject: RE: [Megaco] StreamIds in SCTP as transport
Date: Wed, 23 Jul 2003 09:29:44 +0530
Organization: Wipro Technologies
Message-ID: <001901c350ce$da0b6210$7408c80a@RANJITHEC>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <LLEMKHPJAECAPBFPABPNMEODCBAA.ranand@ccpu.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
X-OriginalArrivalTime: 23 Jul 2003 03:59:40.0271 (UTC) FILETIME=[D755B7F0:01C350CE]
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

rashim, 

i guess you are refering to section H.8 (& not H.7) - atleast thats the
way it is numbered in the (latest?) annex  that i am seeing; anyways:

there are two parts to this recommendation:

1- unrelated transactions to be transmitted on different streams
2- transactions related to one context should be transported over the
same stream.

In your e.g., though you are compliant to 2; you are not exactly
complaint to 1 as T1 and T2-4 are related to certain extent as both have
C5 as the common link. Non-compliance to this could result in a new
*unrelated* transaction queued behind T2-4 (in STR2) to be blocked
(perhaps owing to some issues in C5 related processing/transactions);
you are better off having this C5 affect an unrelated transaction on
STR-1  rather than (probalistically) "spread" the "C5 effect" across
other streams (in this case STR-2).

-- ranjith..

>-----Original Message-----
>From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On 
>Behalf Of Rashim Anand
>Sent: Wednesday, July 23, 2003 6:41 AM
>To: megaco@ietf.org
>Subject: [Megaco] StreamIds in SCTP as transport
>
>
>Hi,
>
>In H.248 annex H (transport over SCTP), section H.7, a 
>recommendation is given -
>
>It is recommended that transactions related to one context are 
>transported over the same stream.
>
>Now suppose the following sequence of messages is exchanged ->
>
>
>   MGC  ------STR 1-----------> MG
>          T=1 { C=$ ... }
>
>   MGC  <---------------------- MG
>          Reply=1 { C=5 ... }
>
>   MGC  ------STR 2-----------> MG
>          T=2 { C=5 ... }
>
>   MGC  ------STR 2-----------> MG
>          T=3 { C=5 ... }
>
>   MGC  ------STR 2-----------> MG
>          T=4 { C=5 ... }
>
>
>where, "T=[0-9]* { C=... }" refers to transaction requests while,
>"Reply=[0-9]* { C=... }" refers to transaction replies,
>"C" stands for ContextId and
>STR1, STR2 refer to the outgoing stream identifiers used by the MGC.
>
>
>The question is - does having STR2 different from STR1 violate 
>the philosophy behind the H.7 recommendation?
>
>IMHO, it does not since the context id 5 becomes known to the 
>MGC only after getting a reply from the MG. Without the 
>assigned context id, the MGC can not send any transactions 
>related to that context and so can not cause any head of line 
>blocking to transactions related to other contexts.
>
>Please let me know your opinion?
>
>Thanks,
>Rashim Anand
>
>
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>


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


From exim@www1.ietf.org  Wed Jul 23 00:02:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05023
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jul 2003 00:02:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fApM-0004v7-MY
	for megaco-archive@odin.ietf.org; Wed, 23 Jul 2003 00:02:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6N4282t018909
	for megaco-archive@odin.ietf.org; Wed, 23 Jul 2003 00:02:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fApM-0004uu-JS
	for megaco-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 00:02:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05001
	for <megaco-web-archive@ietf.org>; Wed, 23 Jul 2003 00:02:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fApK-0001SI-00
	for megaco-web-archive@ietf.org; Wed, 23 Jul 2003 00:02:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19fApE-0001SF-00
	for megaco-web-archive@ietf.org; Wed, 23 Jul 2003 00:02:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fApG-0004tg-1Z; Wed, 23 Jul 2003 00:02:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fAoH-0004rk-2U
	for megaco@optimus.ietf.org; Wed, 23 Jul 2003 00:01:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04978
	for <megaco@ietf.org>; Wed, 23 Jul 2003 00:00:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fAoE-0001Rx-00
	for megaco@ietf.org; Wed, 23 Jul 2003 00:00:58 -0400
Received: from wiprom2mx1.wipro.com ([203.197.164.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fAo1-0001Rd-00
	for megaco@ietf.org; Wed, 23 Jul 2003 00:00:47 -0400
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx1.wipro.com (8.12.9/8.12.9) with SMTP id h6N3xfxX028157
	for <megaco@ietf.org>; Wed, 23 Jul 2003 09:29:46 +0530 (IST)
Received: from blr-ec-msg01.wipro.com ([10.200.50.99]) by blr-ec-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 23 Jul 2003 09:29:40 +0530
Received: from RANJITHEC ([10.200.8.116]) by blr-ec-msg01.wipro.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 23 Jul 2003 09:29:40 +0530
Reply-To: <ranjith.mukundan@wipro.com>
From: "Ranjith Mukundan" <ranjith.mukundan@wipro.com>
To: "'Rashim Anand'" <ranand@ccpu.com>, <megaco@ietf.org>
Subject: RE: [Megaco] StreamIds in SCTP as transport
Date: Wed, 23 Jul 2003 09:29:44 +0530
Organization: Wipro Technologies
Message-ID: <001901c350ce$da0b6210$7408c80a@RANJITHEC>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <LLEMKHPJAECAPBFPABPNMEODCBAA.ranand@ccpu.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
X-OriginalArrivalTime: 23 Jul 2003 03:59:40.0271 (UTC) FILETIME=[D755B7F0:01C350CE]
Content-Transfer-Encoding: 7bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

rashim, 

i guess you are refering to section H.8 (& not H.7) - atleast thats the
way it is numbered in the (latest?) annex  that i am seeing; anyways:

there are two parts to this recommendation:

1- unrelated transactions to be transmitted on different streams
2- transactions related to one context should be transported over the
same stream.

In your e.g., though you are compliant to 2; you are not exactly
complaint to 1 as T1 and T2-4 are related to certain extent as both have
C5 as the common link. Non-compliance to this could result in a new
*unrelated* transaction queued behind T2-4 (in STR2) to be blocked
(perhaps owing to some issues in C5 related processing/transactions);
you are better off having this C5 affect an unrelated transaction on
STR-1  rather than (probalistically) "spread" the "C5 effect" across
other streams (in this case STR-2).

-- ranjith..

>-----Original Message-----
>From: megaco-admin@ietf.org [mailto:megaco-admin@ietf.org] On 
>Behalf Of Rashim Anand
>Sent: Wednesday, July 23, 2003 6:41 AM
>To: megaco@ietf.org
>Subject: [Megaco] StreamIds in SCTP as transport
>
>
>Hi,
>
>In H.248 annex H (transport over SCTP), section H.7, a 
>recommendation is given -
>
>It is recommended that transactions related to one context are 
>transported over the same stream.
>
>Now suppose the following sequence of messages is exchanged ->
>
>
>   MGC  ------STR 1-----------> MG
>          T=1 { C=$ ... }
>
>   MGC  <---------------------- MG
>          Reply=1 { C=5 ... }
>
>   MGC  ------STR 2-----------> MG
>          T=2 { C=5 ... }
>
>   MGC  ------STR 2-----------> MG
>          T=3 { C=5 ... }
>
>   MGC  ------STR 2-----------> MG
>          T=4 { C=5 ... }
>
>
>where, "T=[0-9]* { C=... }" refers to transaction requests while,
>"Reply=[0-9]* { C=... }" refers to transaction replies,
>"C" stands for ContextId and
>STR1, STR2 refer to the outgoing stream identifiers used by the MGC.
>
>
>The question is - does having STR2 different from STR1 violate 
>the philosophy behind the H.7 recommendation?
>
>IMHO, it does not since the context id 5 becomes known to the 
>MGC only after getting a reply from the MG. Without the 
>assigned context id, the MGC can not send any transactions 
>related to that context and so can not cause any head of line 
>blocking to transactions related to other contexts.
>
>Please let me know your opinion?
>
>Thanks,
>Rashim Anand
>
>
>
>
>_______________________________________________
>Megaco mailing list
>Megaco@ietf.org
>https://www1.ietf.org/mailman/listinfo/megaco
>


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



From megaco-admin@ietf.org  Wed Jul 23 10:06:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13532
	for <megaco-archive@lists.ietf.org>; Wed, 23 Jul 2003 10:06:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fKFl-0002zk-Pq; Wed, 23 Jul 2003 10:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fKF6-0002xG-B8
	for megaco@optimus.ietf.org; Wed, 23 Jul 2003 10:05:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13376
	for <megaco@ietf.org>; Wed, 23 Jul 2003 10:05:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fKF4-0004us-00
	for megaco@ietf.org; Wed, 23 Jul 2003 10:05:18 -0400
Received: from zrtps06s.nortelnetworks.com ([47.140.48.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fKEt-0004uL-00
	for megaco@ietf.org; Wed, 23 Jul 2003 10:05:07 -0400
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6NE4AE13766
	for <megaco@ietf.org>; Wed, 23 Jul 2003 10:04:10 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NQAZD4KM>; Wed, 23 Jul 2003 10:04:11 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C0A882609@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: zhangtao <zhangtao_hw@huawei.com>, Jay H Kim <jayhkim@xener.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] At-Most-Once functionality and MId
Date: Wed, 23 Jul 2003 10:04:06 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

Actually, that would depend upon the length of time between the messages.
If the messages come more than 30 seconds apart, the second message could be
considered a new transaction.
 
The use of many IP addresses and ports with a single mId opens a denial of
service attack hole, and is ill-advised.  For determining the identity of
the sender, the receiver should confirm the source IP address independent of
the mId.
 
Kevin

-----Original Message-----
From: zhangtao [mailto:zhangtao_hw@huawei.com] 
Sent: Tuesday, July 22, 2003 11:36 PM
To: Jay H Kim
Cc: megaco@ietf.org
Subject: Re: [Megaco] At-Most-Once functionality and MId


MSG2 is a retransmitted message.
Because  one MID(namely MG or MGC) maybe have many IP ADDRESS or port.

----- Original Message ----- 
From: Jay H Kim <mailto:jayhkim@xener.com>  
To: megaco@ietf.org <mailto:megaco@ietf.org>  
Sent: Tuesday, July 22, 2003 8:52 PM
Subject: [Megaco] At-Most-Once functionality and MId

Hi All,
 
If I receve a Msg1  and receive a Msg2 later like this :
 
Msg1   mId(a.b.c.d:1234) TrsReq:transactionID=1000   with source IP Address
and port (l.m.n.p:1234)
Msg2   mId(a.b.c.d:1234) TrsReq:transactionID=1000   with source IP Address
and port (p.q.r.s:1234)
            (  l.m.n.p != p.q.r.s)
 
is the Msg2  retransmitted transaction of Msg1 or not?
I think Msg2 is Not the retransmitted transacion of Msg1 because the source
IP Address and port is different, 
although the mIds are same.
 
But,.......
rfc3525 and draft-ietf-megaco-h248v2-04 Annext D1.1.1 says :
retransmiited transactions are detected as following scheme :
"The transaction  identifier of each incoming message is compared to the
transaction
   identifiers of the recent responses sent to the same MId."
 
 
Could anybody give me a clarification?
G'Day
 
---------------------------------------------------------
Jay H Kim
R&D Center  XENER Systems Inc.
Office: +82-2-3482-4900. ext.411
Fax: +82-2-3483-4902
+ <mailto:jayhkim@xener.com> mailto:jayhkim@xener.com
Homepage: www.xener.com
-------------------------------------------------------- 
 


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


From exim@www1.ietf.org  Wed Jul 23 10:06:42 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13565
	for <megaco-archive@odin.ietf.org>; Wed, 23 Jul 2003 10:06:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fKFy-000320-NX
	for megaco-archive@odin.ietf.org; Wed, 23 Jul 2003 10:06:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6NE6EHj011646
	for megaco-archive@odin.ietf.org; Wed, 23 Jul 2003 10:06:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fKFy-00031l-KU
	for megaco-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 10:06:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13492
	for <megaco-web-archive@ietf.org>; Wed, 23 Jul 2003 10:06:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fKFw-0004vR-00
	for megaco-web-archive@ietf.org; Wed, 23 Jul 2003 10:06:12 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19fKFq-0004vG-00
	for megaco-web-archive@ietf.org; Wed, 23 Jul 2003 10:06:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fKFl-0002zk-Pq; Wed, 23 Jul 2003 10:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19fKF6-0002xG-B8
	for megaco@optimus.ietf.org; Wed, 23 Jul 2003 10:05:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13376
	for <megaco@ietf.org>; Wed, 23 Jul 2003 10:05:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fKF4-0004us-00
	for megaco@ietf.org; Wed, 23 Jul 2003 10:05:18 -0400
Received: from zrtps06s.nortelnetworks.com ([47.140.48.50])
	by ietf-mx with esmtp (Exim 4.12)
	id 19fKEt-0004uL-00
	for megaco@ietf.org; Wed, 23 Jul 2003 10:05:07 -0400
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h6NE4AE13766
	for <megaco@ietf.org>; Wed, 23 Jul 2003 10:04:10 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NQAZD4KM>; Wed, 23 Jul 2003 10:04:11 -0400
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C0A882609@zrtpd0jq.us.nortel.com>
From: "Kevin Boyle" <kboyle@nortelnetworks.com>
To: zhangtao <zhangtao_hw@huawei.com>, Jay H Kim <jayhkim@xener.com>
Cc: megaco@ietf.org
Subject: RE: [Megaco] At-Most-Once functionality and MId
Date: Wed, 23 Jul 2003 10:04:06 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>

Actually, that would depend upon the length of time between the messages.
If the messages come more than 30 seconds apart, the second message could be
considered a new transaction.
 
The use of many IP addresses and ports with a single mId opens a denial of
service attack hole, and is ill-advised.  For determining the identity of
the sender, the receiver should confirm the source IP address independent of
the mId.
 
Kevin

-----Original Message-----
From: zhangtao [mailto:zhangtao_hw@huawei.com] 
Sent: Tuesday, July 22, 2003 11:36 PM
To: Jay H Kim
Cc: megaco@ietf.org
Subject: Re: [Megaco] At-Most-Once functionality and MId


MSG2 is a retransmitted message.
Because  one MID(namely MG or MGC) maybe have many IP ADDRESS or port.

----- Original Message ----- 
From: Jay H Kim <mailto:jayhkim@xener.com>  
To: megaco@ietf.org <mailto:megaco@ietf.org>  
Sent: Tuesday, July 22, 2003 8:52 PM
Subject: [Megaco] At-Most-Once functionality and MId

Hi All,
 
If I receve a Msg1  and receive a Msg2 later like this :
 
Msg1   mId(a.b.c.d:1234) TrsReq:transactionID=1000   with source IP Address
and port (l.m.n.p:1234)
Msg2   mId(a.b.c.d:1234) TrsReq:transactionID=1000   with source IP Address
and port (p.q.r.s:1234)
            (  l.m.n.p != p.q.r.s)
 
is the Msg2  retransmitted transaction of Msg1 or not?
I think Msg2 is Not the retransmitted transacion of Msg1 because the source
IP Address and port is different, 
although the mIds are same.
 
But,.......
rfc3525 and draft-ietf-megaco-h248v2-04 Annext D1.1.1 says :
retransmiited transactions are detected as following scheme :
"The transaction  identifier of each incoming message is compared to the
transaction
   identifiers of the recent responses sent to the same MId."
 
 
Could anybody give me a clarification?
G'Day
 
---------------------------------------------------------
Jay H Kim
R&D Center  XENER Systems Inc.
Office: +82-2-3482-4900. ext.411
Fax: +82-2-3483-4902
+ <mailto:jayhkim@xener.com> mailto:jayhkim@xener.com
Homepage: www.xener.com
-------------------------------------------------------- 
 


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



From megaco-admin@ietf.org  Mon Jul 28 01:41:34 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06570
	for <megaco-archive@lists.ietf.org>; Mon, 28 Jul 2003 01:41:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19h0ko-0005Vu-Ko; Mon, 28 Jul 2003 01:41:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19h0kC-0005VG-UR
	for megaco@optimus.ietf.org; Mon, 28 Jul 2003 01:40:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06534
	for <megaco@ietf.org>; Mon, 28 Jul 2003 01:40:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19h0k9-0004as-00
	for megaco@ietf.org; Mon, 28 Jul 2003 01:40:21 -0400
Received: from mxc.rambler.ru ([81.19.66.31])
	by ietf-mx with esmtp (Exim 4.12)
	id 19h0k8-0004ap-00
	for megaco@ietf.org; Mon, 28 Jul 2003 01:40:21 -0400
Received: from mail5.rambler.ru (mail5.rambler.ru [81.19.66.7])
	by mxc.rambler.ru (Postfix) with ESMTP id 769FEB4CA
	for <megaco@ietf.org>; Mon, 28 Jul 2003 09:57:43 +0400 (MSD)
	(envelope-from fhuval@rambler.ru)
Received: from [81.19.66.146] (account <fhuval@rambler.ru>)
  by mail5.rambler.ru (CommuniGate Pro WebUser 4.0.6)
  with HTTP id 3345346 for <megaco@ietf.org>; Mon, 28 Jul 2003 09:39:32 +0400
From: "Fhuval Hittay" <fhuval@rambler.ru>
To: megaco@ietf.org
X-Mailer: CommuniGate Pro Web Mailer v.4.0.6
Date: Mon, 28 Jul 2003 09:39:32 +0400
Message-ID: <web-3345346@mail5.rambler.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1251"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Megaco] Basic CAS Addressing Package
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hello all!
According to H.248.26 "Basic CAS Packages", there is 'bcasaddr' 
package
with 'bcasaddr/addr' event. It has ObservedEventsDescriptor parameter 
- 'ds':
Description: The string of collected digits that matched all or part 
of the sequence specified in the digit map.

My question is: how passed that digit map?
If by 'dd/ce' package, then why collected digits must be returned by 
'bcasaddr/addr' package, and not by 'dd/ce' package?

Thanks in advance.

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


From exim@www1.ietf.org  Mon Jul 28 01:41:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06585
	for <megaco-archive@odin.ietf.org>; Mon, 28 Jul 2003 01:41:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19h0kv-0005Wi-1L
	for megaco-archive@odin.ietf.org; Mon, 28 Jul 2003 01:41:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h6S5f9V8021238
	for megaco-archive@odin.ietf.org; Mon, 28 Jul 2003 01:41:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19h0ku-0005WT-TR
	for megaco-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 01:41:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06558
	for <megaco-web-archive@ietf.org>; Mon, 28 Jul 2003 01:41:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19h0kr-0004bR-00
	for megaco-web-archive@ietf.org; Mon, 28 Jul 2003 01:41:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19h0kr-0004bN-00
	for megaco-web-archive@ietf.org; Mon, 28 Jul 2003 01:41:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19h0ko-0005Vu-Ko; Mon, 28 Jul 2003 01:41:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19h0kC-0005VG-UR
	for megaco@optimus.ietf.org; Mon, 28 Jul 2003 01:40:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06534
	for <megaco@ietf.org>; Mon, 28 Jul 2003 01:40:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19h0k9-0004as-00
	for megaco@ietf.org; Mon, 28 Jul 2003 01:40:21 -0400
Received: from mxc.rambler.ru ([81.19.66.31])
	by ietf-mx with esmtp (Exim 4.12)
	id 19h0k8-0004ap-00
	for megaco@ietf.org; Mon, 28 Jul 2003 01:40:21 -0400
Received: from mail5.rambler.ru (mail5.rambler.ru [81.19.66.7])
	by mxc.rambler.ru (Postfix) with ESMTP id 769FEB4CA
	for <megaco@ietf.org>; Mon, 28 Jul 2003 09:57:43 +0400 (MSD)
	(envelope-from fhuval@rambler.ru)
Received: from [81.19.66.146] (account <fhuval@rambler.ru>)
  by mail5.rambler.ru (CommuniGate Pro WebUser 4.0.6)
  with HTTP id 3345346 for <megaco@ietf.org>; Mon, 28 Jul 2003 09:39:32 +0400
From: "Fhuval Hittay" <fhuval@rambler.ru>
To: megaco@ietf.org
X-Mailer: CommuniGate Pro Web Mailer v.4.0.6
Date: Mon, 28 Jul 2003 09:39:32 +0400
Message-ID: <web-3345346@mail5.rambler.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1251"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Megaco] Basic CAS Addressing Package
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>,
	<mailto:megaco-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hello all!
According to H.248.26 "Basic CAS Packages", there is 'bcasaddr' 
package
with 'bcasaddr/addr' event. It has ObservedEventsDescriptor parameter 
- 'ds':
Description: The string of collected digits that matched all or part 
of the sequence specified in the digit map.

My question is: how passed that digit map?
If by 'dd/ce' package, then why collected digits must be returned by 
'bcasaddr/addr' package, and not by 'dd/ce' package?

Thanks in advance.

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