From priyadav@cisco.com Thu Jan 28 01:14:51 2010 Return-Path: X-Original-To: megaco@core3.amsl.com Delivered-To: megaco@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA53D3A67FA for ; Thu, 28 Jan 2010 01:14:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.998 X-Spam-Level: X-Spam-Status: No, score=-7.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QfRoA6W0KPmp for ; Thu, 28 Jan 2010 01:14:50 -0800 (PST) Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id ADDD23A67E1 for ; Thu, 28 Jan 2010 01:14:50 -0800 (PST) Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAGPkYEurRN+J/2dsb2JhbADAUpc1hDwEgwk X-IronPort-AV: E=Sophos;i="4.49,359,1262563200"; d="scan'208,217";a="82627084" Received: from sj-core-3.cisco.com ([171.68.223.137]) by rtp-iport-2.cisco.com with ESMTP; 28 Jan 2010 09:15:07 +0000 Received: from sj-webmail-3.cisco.com (sj-webmail-3.cisco.com [171.70.156.8]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o0S9F6N5001751 for ; Thu, 28 Jan 2010 09:15:07 GMT Received: from sj-webmail-3.cisco.com (localhost.localdomain [127.0.0.1]) by sj-webmail-3.cisco.com (8.13.1/8.13.1) with ESMTP id o0S9F6Ar025077 for ; Thu, 28 Jan 2010 01:15:06 -0800 Received: from sj-webmail-3 (root@localhost) by sj-webmail-3.cisco.com (8.13.1/8.13.1/Submit) with ESMTP id o0S9F6LH025076 for ; Thu, 28 Jan 2010 01:15:06 -0800 Received: from priyadavwxp01 ( [10.78.164.133]) by sj-webmail-3 (Scalix SMTP Relay 10.0.5.3) via ESMTP; Thu, 28 Jan 2010 01:15:06 -0800 (PST) Date: Thu, 28 Jan 2010 14:47:23 +0530 From: "Priyanka Yadav" To: Message-ID: <003f01ca9ffa$b4565e80$85a44e0a@priyadavwxp01> x-scalix-Hops: 1 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acqf+rMl1cGXytORTZOGdSBFpbjn/g== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0040_01CAA028.CE0E9A80" Subject: [Megaco] dd/etd X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2010 09:14:52 -0000 ------=_NextPart_000_0040_01CAA028.CE0E9A80 Content-Type: text/plain; charset="US-ASCII" Content-Disposition: inline Hi All I have a query regarding Digit Detection applied in event descriptor. If we get the following message from MGC :- Context = 83 { Modify = ds/1/1/1 { Events = 1 {dd/etd {tl=d1,tl=d2,tl=da} } } Here 3 digits are specified for detection. I have two questions:- 1:Is this format allowed ? 2:If this is allowed,notification for all the three digits should be sent to MGC ? Thanks Priyanka ------=_NextPart_000_0040_01CAA028.CE0E9A80 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

Hi=20 All

I have a= query=20 regarding Digit Detection applied in event=20 descriptor.

If we g= et the=20 following message from MGC :-

Context= =3D 83=20 {
Modify =3D ds/1/1/1 {
Events =3D 1 {dd/etd {tl=3Dd1,tl=3D= d2,tl=3Dda}=20 }
}

Here 3 d= igits are=20 specified for detection.

I have t= wo=20 questions:-

1:Is this=20 format allowed ?

2:If this is=20 allowed,notification for all the three digits should be sent to MGC=20 ?

Thanks=20

Priyank= a

------=_NextPart_000_0040_01CAA028.CE0E9A80--