[Megaco] EBCP Flag ON-OFF transition

bvswamy@hss.hns.com Mon, 30 June 2003 11:29 UTC

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 HAA10281 for <megaco-archive@lists.ietf.org>; Mon, 30 Jun 2003 07:29: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 19WwqD-0000Vc-3T; Mon, 30 Jun 2003 07:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Wwpx-0000U3-W2 for megaco@optimus.ietf.org; Mon, 30 Jun 2003 07:28: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 HAA10221 for <megaco@ietf.org>; Mon, 30 Jun 2003 07:28:45 -0400 (EDT)
From: bvswamy@hss.hns.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Wwpx-0005u8-00 for megaco@ietf.org; Mon, 30 Jun 2003 07:28:45 -0400
Received: from hindon.hss.co.in ([202.54.26.202]) by ietf-mx with esmtp (Exim 4.12) id 19Wwpl-0005tg-00 for megaco@ietf.org; Mon, 30 Jun 2003 07:28:34 -0400
Received: from hindon.hss.co.in (localhost [127.0.0.1]) by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5UBPAD28190 for <megaco@ietf.org>; Mon, 30 Jun 2003 16:55:10 +0530 (IST)
Received: from ultra.hss.co.in (ultra [192.168.100.5]) by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id h5UBP9O28183 for <megaco@ietf.org>; Mon, 30 Jun 2003 16:55:09 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1]) by ultra.hss.co.in (8.10.0/8.10.0) with ESMTP id h5UBSlp29258 for <megaco@ietf.org>; Mon, 30 Jun 2003 16:58:47 +0530 (IST)
To: megaco@ietf.org
Date: Mon, 30 Jun 2003 16:53:42 +0530
Message-ID: <OF02200F87.3F4BDF4C-ON65256D55.003D7435@hss.hns.com>
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26, 2002) at 30/06/2003 04:52:29 PM
MIME-Version: 1.0
Content-type: text/plain; charset="US-ASCII"
Subject: [Megaco] EBCP Flag ON-OFF transition
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>





Hi All
      Needed a clarification on the behaviour of MG wrt to the EBCP flag
transition from ON to OFF.
The scenario is as follows:

1) Modify
TermId = T10
CtxId = null
Media
{
TerminationState { Buffer = LockStep}
},
Events = 1 { dd/d0,dd/d1,dd/d2,al/hf},
EventBuffer { dd/d4, dd/d5, dd/d6, dd/d7 }

2) After the  notification of any event in the event descriptor,
eventbuffer descriptor is activated and buffering is done by MG.

3) MGC modifies the EBCP flag to OFF.
Modify
TermId = T10
CtxId = null
Media
{
TerminationState { Buffer = OFF}
}
      Now according to the protocol, the events that are buffered shall be
discarded,
(draft-ietf-megaco-3015corr-01>>
" If the MG receives a command instructing it to set the value of
EventBufferControl to Off, all events in the EventBuffer SHALL be
   discarded"
)

however there is no mention whether the old event  descriptor shall get
activated or not. That is if any event in the old event
descriptor is detected then whether it should be reported to MGC  or
whether it should be discarded.

Regards
Venkat
www.hssworld.com
Hughes Software Systems



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


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