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

Murugesh Govindaraju <MGovindaraju@zhone.com> Tue, 03 September 2013 10:14 UTC

Return-Path: <MGovindaraju@zhone.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 6471521E80FD for <megaco@ietfa.amsl.com>; Tue, 3 Sep 2013 03:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.669
X-Spam-Level:
X-Spam-Status: No, score=-1.669 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ZaB5q1uPlkhi for <megaco@ietfa.amsl.com>; Tue, 3 Sep 2013 03:14:14 -0700 (PDT)
Received: from zw2-smtp1.zhone.com (zw2-smtp1.zhone.com [199.190.211.5]) by ietfa.amsl.com (Postfix) with ESMTP id 02E4A21E80EE for <megaco@ietf.org>; Tue, 3 Sep 2013 03:14:12 -0700 (PDT)
Received: from priority.oak.zhone.com (priority.oak.zhone.com [172.16.1.21]) by smtp.zhone.com (8.12.1/8.12.1) with ESMTP id r83B9s7J002137 for <megaco@ietf.org>; Tue, 3 Sep 2013 04:09:54 -0700 (PDT)
Received: from [172.16.14.26] (dhcp-vpn-26.oak.zhone.com [172.16.14.26]) by priority.oak.zhone.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0MSJ00C3QOFMAJ00@priority.oak.zhone.com> for megaco@ietf.org; Tue, 03 Sep 2013 03:14:12 -0700 (PDT)
Date: Tue, 03 Sep 2013 15:44:10 +0530
From: Murugesh Govindaraju <MGovindaraju@zhone.com>
To: megaco@ietf.org
Message-id: <5225B672.8000604@zhone.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_IJtU7IcyGj3Rtmoh3dh8yg)"
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
Cc: Ramesh Kuppili <RKuppili@zhone.com>
Subject: [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 10:14:19 -0000

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 *"OnOf**f"*, 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 *