Re: [Megaco] Question on using signal parameters for stimal/stedsig signal

"Bhattacharjee, Arindam (Arindam)" <arindam.bhattacharjee@alcatel-lucent.com> Tue, 03 September 2013 17:28 UTC

Return-Path: <arindam.bhattacharjee@alcatel-lucent.com>
X-Original-To: megaco@ietfa.amsl.com
Delivered-To: megaco@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A781C11E80E7 for <megaco@ietfa.amsl.com>; Tue, 3 Sep 2013 10:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4pV7G+4UJRV for <megaco@ietfa.amsl.com>; Tue, 3 Sep 2013 10:28:13 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 645B421F9D53 for <megaco@ietf.org>; Tue, 3 Sep 2013 10:28:08 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r83HS5uZ026551 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 3 Sep 2013 12:28:05 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id r83HS3Xh015100 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Sep 2013 13:28:04 -0400
Received: from US70UWXCHMBA01.zam.alcatel-lucent.com ([169.254.7.67]) by US70UWXCHHUB02.zam.alcatel-lucent.com ([135.5.2.49]) with mapi id 14.02.0247.003; Tue, 3 Sep 2013 13:28:03 -0400
From: "Bhattacharjee, Arindam (Arindam)" <arindam.bhattacharjee@alcatel-lucent.com>
To: Murugesh Govindaraju <MGovindaraju@zhone.com>, "megaco@ietf.org" <megaco@ietf.org>
Thread-Topic: [Megaco] Question on using signal parameters for stimal/stedsig signal
Thread-Index: AQHOqI5cMEcYiweNAky+oqkYisDLA5m0QqMw
Date: Tue, 03 Sep 2013 17:28:02 +0000
Message-ID: <7DE39EC55B99FC47A3DEB6179256D99176F44D0C@US70UWXCHMBA01.zam.alcatel-lucent.com>
References: <5225B672.8000604@zhone.com>
In-Reply-To: <5225B672.8000604@zhone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.16]
Content-Type: multipart/alternative; boundary="_000_7DE39EC55B99FC47A3DEB6179256D99176F44D0CUS70UWXCHMBA01z_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: Ramesh Kuppili <RKuppili@zhone.com>
Subject: Re: [Megaco] Question on using signal parameters for stimal/stedsig signal
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Media Gateway Control <megaco.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/megaco>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2013 17:28:26 -0000

Hi Murugesh,

Signal Type: OnOff is default type in the specification. If SignalType= timeout is specified in the message then default type OnOff is overridden.

In your case MG should apply the signal with timeout of Duration=15.


In section 7.1.11 of H248.1
If a signal of default type other than TO has its type overridden to type TO in the Signals Descriptor, the duration parameter must be present.

-Arindam

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Murugesh Govindaraju
Sent: Tuesday, September 03, 2013 6:14 AM
To: megaco@ietf.org
Cc: Ramesh Kuppili
Subject: [Megaco] Question on using signal parameters for stimal/stedsig signal

Hi All,
Stimulus analogue line package (H.248.34) has a signal "Steady Signal" defined in it.

Following is the definition of this signal from this package:
6.3.2 Steady Signal
Signal name: Steady Signal
Signal ID: stedsig (0x0002)
Description: Used by the MGC to instruct the MG to apply a steady signal.
Signal Type: OnOff
Duration: not applicable

This signal has only one parameter called "sig".

What if we receive the following request from switch, which contains the signal parameters signalType and Duration:

MEGACO/1 Transaction = 387699 {Context = 48 {

    Modify = AL3{Media{LocalControl {   Mode = SendReceive

        }},

      Signals {

        stimal/stedsig {

          SignalType = timeOut,

          Duration = 15,

          sig = reversePolarity

        }

      },

      Events = 2527 {

        al/on,

        al/of,

        al/fl

      }

    }

  }

}
Here is my question:
Though the signal definition in package says that the steady signal is of type "OnOff", but the switch says as "timeOut" and duration as not application, but the switch says as "15" sec.
What should be the behavior of the MG in this case?
--
Thanks,
Murugesh G