From albrecht.schwarz@alcatel-lucent.com Mon Feb 20 08:59:28 2012 Return-Path: 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 B32C621F86EB for ; Mon, 20 Feb 2012 08:59:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.131 X-Spam-Level: X-Spam-Status: No, score=-6.131 tagged_above=-999 required=5 tests=[AWL=4.118, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 YTCNgax55DrE for ; Mon, 20 Feb 2012 08:59:24 -0800 (PST) Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 7332F21F85B1 for ; Mon, 20 Feb 2012 08:59:23 -0800 (PST) Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q1KGxJb2022604 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 20 Feb 2012 17:59:20 +0100 Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Mon, 20 Feb 2012 17:59:20 +0100 From: "Schwarz, Albrecht (Albrecht)" To: Wayne Cutler Date: Mon, 20 Feb 2012 17:59:22 +0100 Thread-Topic: i3F WP on QOS & H248 Progress Thread-Index: AcyiwIAcq7QZzv4RQAKmZ+vlZh6VghNL3eYw Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621625F97BC@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> References: <0F361ECB01704E7BA0008560144E52E5@UserPC> <5F7BCCF5541B7444830A2288ABBEBC9621615E3B22@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <1BA76847A49542908A476593DB8FFB89@UserPC> <5F7BCCF5541B7444830A2288ABBEBC9621615E46DD@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <161DFF8270B7459E8B44A70F3ABFB389@UserPC> In-Reply-To: <161DFF8270B7459E8B44A70F3ABFB389@UserPC> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE, en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84 Cc: "msf-technical@msforum.org" , "megaco@ietf.org" Subject: Re: [Megaco] i3F WP on QOS & H248 Progress X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2012 16:59:28 -0000 Hello Wayne, just noticed the MSF contributions on RTCP-based QoS measurements & i3 Foru= m for this weeks TC meeting. There's in parallel the ITU-T WP2/16 meeting this week in Geneva: http://wftp3.itu.int/av-arch/avc-site/2009-2012/1202_Gen/1202_Gen.html As mentioned last year, we've submitted some material to start a framework = on RTCP-based measurements. Such a framework should be preferrably document= ed as profile specification guidelines. Like to draw your attention on following documents: 1st RTCP subject: AVD-4177 Proposed new H.248.RTCPPROF work item: Profile specification guide= lines for H.248-based Performance Monitoring in RTP networks =09 AVD-4178 H.248.RTCPPROF: Network monitoring architectural requirements vs H= .248 gateway types AVD-4179 H.248.RTCPPROF - Skeleton for Draft Recommendation 2nd Loopback topic: AVD-4172 H.248.LOOPB: Use cases in H.248.48 environments Best regards, Albrecht= From Abhijit.Dutta@radisys.com Wed Feb 22 11:07:19 2012 Return-Path: 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 7790621F86CE for ; Wed, 22 Feb 2012 11:07:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, 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 U8KmK050THHg for ; Wed, 22 Feb 2012 11:07:19 -0800 (PST) Received: from mail4.radisys.com (mail4.radisys.com [207.189.106.90]) by ietfa.amsl.com (Postfix) with ESMTP id EEB7B21F8637 for ; Wed, 22 Feb 2012 11:07:18 -0800 (PST) Received: from INMAIL.ccpu.com (10.1.101.36) by OREXCHANGE03.radisys.com (10.1.101.33) with Microsoft SMTP Server (TLS) id 14.1.289.1; Wed, 22 Feb 2012 11:07:18 -0800 Received: from INEXCHANGE.ccpu.com ([172.25.0.65]) by INMAIL.ccpu.com ([::1]) with mapi; Thu, 23 Feb 2012 00:38:21 +0530 From: Abhijit Dutta To: "megaco@ietf.org" Date: Thu, 23 Feb 2012 00:38:19 +0530 Thread-Topic: Local and Remote Descriptor IP type Thread-Index: AczxlQYrjdmvQwyDTgW2uwfUVI5xFg== Message-ID: <9085F06114A8A44EB121CE1B1ADAE03618E9DCE29C@INEXCHANGE> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_9085F06114A8A44EB121CE1B1ADAE03618E9DCE29CINEXCHANGE_" MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 23 Feb 2012 10:17:57 -0800 Subject: [Megaco] Local and Remote Descriptor IP type X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2012 19:08:16 -0000 --_000_9085F06114A8A44EB121CE1B1ADAE03618E9DCE29CINEXCHANGE_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Sorry for this na=EFve question - I am posting it since there is no clear = indication in the RFC. Can local and remote descriptor contain differ IP address types - one say = IPv4 and another IPv6. If not, what should the MGC return (error code) in r= eply during such situations. ~Thanx Abhijit --_000_9085F06114A8A44EB121CE1B1ADAE03618E9DCE29CINEXCHANGE_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

 

Sorry for = this na=EFve question -=A0 I am posting it since there is no clear indicati= on in the RFC.

 

Can local and remote descriptor contain differ IP address = types -=A0 one say IPv4 and another IPv6. If not, what should the MGC retur= n (error code) in reply during such situations.

 

~Thanx
Abhijit

= --_000_9085F06114A8A44EB121CE1B1ADAE03618E9DCE29CINEXCHANGE_-- From arora.kapila@gmail.com Wed Feb 22 19:44:59 2012 Return-Path: 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 C4A0511E8085 for ; Wed, 22 Feb 2012 19:44:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] 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 CnrkfjaplmRx for ; Wed, 22 Feb 2012 19:44:59 -0800 (PST) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id D39EA11E807F for ; Wed, 22 Feb 2012 19:44:58 -0800 (PST) Received: by wibhm9 with SMTP id hm9so562613wib.31 for ; Wed, 22 Feb 2012 19:44:58 -0800 (PST) Received-SPF: pass (google.com: domain of arora.kapila@gmail.com designates 10.180.81.66 as permitted sender) client-ip=10.180.81.66; Authentication-Results: mr.google.com; spf=pass (google.com: domain of arora.kapila@gmail.com designates 10.180.81.66 as permitted sender) smtp.mail=arora.kapila@gmail.com; dkim=pass header.i=arora.kapila@gmail.com Received: from mr.google.com ([10.180.81.66]) by 10.180.81.66 with SMTP id y2mr132233wix.20.1329968698011 (num_hops = 1); Wed, 22 Feb 2012 19:44:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=m7JdLnSMQ1TtCFffstLPzk6TH4oGx5+ad2xkjCzpRIU=; b=FYGUEks4EYaelICm+woQ9uj16JAl3VsPci1LuvMzcFIDIbtbGzOCtZxSqFkn1ckbDB ER6+1HbroazLqcO1K1piT8VvqfYL+tQpBAINo+3hr64V3K76tIF6uiUzkx0cBsUe5Qu7 zWOSmsB28psm8lXyYYwqgSIaXCT61bl6RM+v8= MIME-Version: 1.0 Received: by 10.180.81.66 with SMTP id y2mr105016wix.20.1329968697973; Wed, 22 Feb 2012 19:44:57 -0800 (PST) Received: by 10.180.83.33 with HTTP; Wed, 22 Feb 2012 19:44:57 -0800 (PST) Date: Thu, 23 Feb 2012 12:44:57 +0900 Message-ID: From: Kapila Arora To: megaco@ietf.org Content-Type: multipart/alternative; boundary=f46d04428d2cce1a0104b99977bc X-Mailman-Approved-At: Thu, 23 Feb 2012 10:17:57 -0800 Subject: [Megaco] Query regarding individual digit reporting X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2012 03:48:39 -0000 --f46d04428d2cce1a0104b99977bc Content-Type: text/plain; charset=ISO-8859-1 Hi all, for some king of application I need individual digits to be reported to the softswitch from the media server. I want to know what should be the format of megaco request for this. Please provide me with an example of the same Thanks Kapila --f46d04428d2cce1a0104b99977bc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,

for some king of application I ne= ed individual digits to be reported to the softswitch from the media server= . I want to know what should be the format of megaco request for this. Plea= se provide me with an example of the same

Thanks
Kapila


--f46d04428d2cce1a0104b99977bc-- From arindam.bhattacharjee@alcatel-lucent.com Thu Feb 23 10:29:57 2012 Return-Path: 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 C840221F86A7 for ; Thu, 23 Feb 2012 10:29:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.449 X-Spam-Level: X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 uH0Bc4vfr-AZ for ; Thu, 23 Feb 2012 10:29:56 -0800 (PST) Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 9FA2E21F8692 for ; Thu, 23 Feb 2012 10:29:56 -0800 (PST) Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id q1NITqE3008672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Feb 2012 12:29:52 -0600 (CST) Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q1NITqbi017038 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 23 Feb 2012 12:29:52 -0600 Received: from USNAVSXCHMBSA2.ndc.alcatel-lucent.com ([135.3.39.124]) by USNAVSXCHHUB03.ndc.alcatel-lucent.com ([135.3.39.112]) with mapi; Thu, 23 Feb 2012 12:29:52 -0600 From: "Bhattacharjee, Arindam (Arindam)" To: Kapila Arora , "megaco@ietf.org" Date: Thu, 23 Feb 2012 12:29:50 -0600 Thread-Topic: [Megaco] Query regarding individual digit reporting Thread-Index: AczyV4B9ttBbGtizRNiyU2dcsNCLZQAAUCBg Message-ID: <703C56B521385C4C9091299BE82357B7F03795F9@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_703C56B521385C4C9091299BE82357B7F03795F9USNAVSXCHMBSA2n_" MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39 X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12 Subject: Re: [Megaco] Query regarding individual digit reporting X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2012 18:29:58 -0000 --_000_703C56B521385C4C9091299BE82357B7F03795F9USNAVSXCHMBSA2n_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Please refer to Appendix I in H248.1. It has the call flow and megaco messages and procedure for collecting and n= otifying digits to MGC. -Arindam From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= Kapila Arora Sent: Wednesday, February 22, 2012 10:45 PM To: megaco@ietf.org Subject: [Megaco] Query regarding individual digit reporting Hi all, for some king of application I need individual digits to be reported to the= softswitch from the media server. I want to know what should be the format= of megaco request for this. Please provide me with an example of the same Thanks Kapila --_000_703C56B521385C4C9091299BE82357B7F03795F9USNAVSXCHMBSA2n_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Please refer to  Appendix I in H248.1.

It has the call flow and megaco messages and procedure for c= ollecting and notifying digits to MGC.

-Arindam

 

 

From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Kapila Arora
Sent: Wednesday, February 22, 2012 10:45 PM
To: megaco@ietf.org
Subject: [Megaco] Query regarding individual digit reporting

 

Hi all,

 

for some king of application I need individual digits = to be reported to the softswitch from the media server. I want to know what shoul= d be the format of megaco request for this. Please provide me with an example of= the same

 

Thanks

Kapila

 

 

--_000_703C56B521385C4C9091299BE82357B7F03795F9USNAVSXCHMBSA2n_-- From deepak.bissa@aricent.com Thu Feb 23 19:32:29 2012 Return-Path: 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 16B1E11E80AB for ; Thu, 23 Feb 2012 19:32:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 kRCfOd9REPTl for ; Thu, 23 Feb 2012 19:32:27 -0800 (PST) Received: from jaguar.aricent.com (jaguar.aricent.com [180.151.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id B5DD411E80A3 for ; Thu, 23 Feb 2012 19:32:21 -0800 (PST) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id EBA8336B3C; Fri, 24 Feb 2012 09:00:51 +0530 (IST) Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com [10.203.171.138]) by jaguar.aricent.com (Postfix) with ESMTP id D574236B24; Fri, 24 Feb 2012 09:00:51 +0530 (IST) Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi; Fri, 24 Feb 2012 09:01:12 +0530 From: Deepak Bissa To: Kapila Arora , "megaco@ietf.org" Date: Fri, 24 Feb 2012 09:01:11 +0530 Thread-Topic: [Megaco] Query regarding individual digit reporting Thread-Index: AczyV4B9ttBbGtizRNiyU2dcsNCLZQAAUCBgABK68SA= Message-ID: <54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D43@GUREXMB01.ASIAN.AD.ARICENT.COM> References: <703C56B521385C4C9091299BE82357B7F03795F9@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> In-Reply-To: <703C56B521385C4C9091299BE82357B7F03795F9@USNAVSXCHMBSA2.ndc.alcatel-lucent.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D43GUREXMB01ASIA_" MIME-Version: 1.0 Subject: Re: [Megaco] Query regarding individual digit reporting X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2012 03:32:29 -0000 --_000_54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D43GUREXMB01ASIA_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, MGC can use events dd/d0,dd/d1... etc to enable individual digit detection = and MG can then send Notify for each digit detected at its end. There are some MGCs which use dd/std{ tl=3D*} rather than applying individu= al digits events and MG then send detected digit as dd/std{tid=3Dd0} (if di= git 0 is dialed) Regards, Deepak Bissa From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= Bhattacharjee, Arindam (Arindam) Sent: Friday, February 24, 2012 12:00 AM To: Kapila Arora; megaco@ietf.org Subject: Re: [Megaco] Query regarding individual digit reporting Please refer to Appendix I in H248.1. It has the call flow and megaco messages and procedure for collecting and n= otifying digits to MGC. -Arindam From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= Kapila Arora Sent: Wednesday, February 22, 2012 10:45 PM To: megaco@ietf.org Subject: [Megaco] Query regarding individual digit reporting Hi all, for some king of application I need individual digits to be reported to the= softswitch from the media server. I want to know what should be the format= of megaco request for this. Please provide me with an example of the same Thanks Kapila =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D --_000_54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D43GUREXMB01ASIA_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

MGC can use events dd/d0,dd/d1… etc to enable individu= al digit detection and MG can then send Notify for each digit detected at i= ts end.

There are some MGCs which use dd/std{ tl=3D*} rather than ap= plying individual digits events and MG then send detected digit as dd/std{t= id=3Dd0} (if digit 0 is dialed)

 

Regards,

Deepak Bissa

 

From: megaco-b= ounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Bhattacharjee, Arindam (Arindam)
Sent: Friday, February 24, 2012 12:00 AM
To: Kapila Arora; megaco@ietf.org
Subject: Re: [Megaco] Query regarding individual digit reporting

 

Please refer to  Appendix I in H248.1.

It has the call flow and megaco messages and procedure for c= ollecting and notifying digits to MGC.

-Arindam

 

 

From: megaco-b= ounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Kapila Arora
Sent: Wednesday, February 22, 2012 10:45 PM
To: megaco@ietf.org
Subject: [Megaco] Query regarding individual digit reporting

 

Hi all,

 

for some king of application I need individual digit= s to be reported to the softswitch from the media server. I want to know wh= at should be the format of megaco request for this. Please provide me with = an example of the same

 

Thanks

Kapila

 

 





=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D
 --_000_54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D43GUREXMB01ASIA_-- From deepak.bissa@aricent.com Thu Feb 23 19:49:52 2012 Return-Path: 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 9FAB511E8072 for ; Thu, 23 Feb 2012 19:49:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 UB+rpz9u9iYe for ; Thu, 23 Feb 2012 19:49:51 -0800 (PST) Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11]) by ietfa.amsl.com (Postfix) with ESMTP id 5806B11E8087 for ; Thu, 23 Feb 2012 19:49:43 -0800 (PST) Received: from jaguar.aricent.com (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 03D1436B37; Fri, 24 Feb 2012 09:18:15 +0530 (IST) Received: from GUREXHT01.ASIAN.AD.ARICENT.COM (gurexht01.asian.ad.aricent.com [10.203.171.136]) by jaguar.aricent.com (Postfix) with ESMTP id E1BE936B36; Fri, 24 Feb 2012 09:18:14 +0530 (IST) Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.134]) by GUREXHT01.ASIAN.AD.ARICENT.COM ([10.203.171.137]) with mapi; Fri, 24 Feb 2012 09:19:39 +0530 From: Deepak Bissa To: Abhijit Dutta , "megaco@ietf.org" Date: Fri, 24 Feb 2012 09:19:29 +0530 Thread-Topic: Local and Remote Descriptor IP type Thread-Index: AczxlQYrjdmvQwyDTgW2uwfUVI5xFgBD9U9w Message-ID: <54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D53@GUREXMB01.ASIAN.AD.ARICENT.COM> References: <9085F06114A8A44EB121CE1B1ADAE03618E9DCE29C@INEXCHANGE> In-Reply-To: <9085F06114A8A44EB121CE1B1ADAE03618E9DCE29C@INEXCHANGE> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-cr-hashedpuzzle: QYI= WzA= EfMg FyFp GQMD G8+S HRYs HgG5 IIHN JNrc KPdH LgPg Q4O6 RYkb UeNi Xd5l; 2; YQBiAGgAaQBqAGkAdAAuAGQAdQB0AHQAYQBAAHIAYQBkAGkAcwB5AHMALgBjAG8AbQA7AG0AZQBnAGEAYwBvAEAAaQBlAHQAZgAuAG8AcgBnAA==; Sosha1_v1; 7; {AF14973B-568B-4167-9DB6-E60CE4862E2D}; ZABlAGUAcABhAGsALgBiAGkAcwBzAGEAQABhAHIAaQBjAGUAbgB0AC4AYwBvAG0A; Fri, 24 Feb 2012 03:49:29 GMT; UgBFADoAIABMAG8AYwBhAGwAIABhAG4AZAAgAFIAZQBtAG8AdABlACAARABlAHMAYwByAGkAcAB0AG8AcgAgAEkAUAAgAHQAeQBwAGUA x-cr-puzzleid: {AF14973B-568B-4167-9DB6-E60CE4862E2D} acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D53GUREXMB01ASIA_" MIME-Version: 1.0 Subject: Re: [Megaco] Local and Remote Descriptor IP type X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2012 03:49:52 -0000 --_000_54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D53GUREXMB01ASIA_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Megaco protocol does not impose such restrictions on SDP internals and it i= s possible to have such situation. MGCs "might not" look into these details and just tunnel it to respective M= Gs and then MG has to apply or reject such media connection. H.248.8 provides list of error codes that can be exchanged between MG and M= GC. "Not Implemented" could be one of the candidate. Regards, Deepak Bissa From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= Abhijit Dutta Sent: Thursday, February 23, 2012 12:38 AM To: megaco@ietf.org Subject: [Megaco] Local and Remote Descriptor IP type Hi, Sorry for this na=EFve question - I am posting it since there is no clear = indication in the RFC. Can local and remote descriptor contain differ IP address types - one say = IPv4 and another IPv6. If not, what should the MGC return (error code) in r= eply during such situations. ~Thanx Abhijit =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D --_000_54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D53GUREXMB01ASIA_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,<= /p>

Megaco protocol does n= ot impose such restrictions on SDP internals and it is possible to have suc= h situation.

MGCs “might not&= #8221; look into these details and just tunnel it to respective MGs and the= n MG has to apply or reject such media connection.

 

H.248.8 provides list = of error codes that can be exchanged between MG and MGC.  “Not I= mplemented” could be one of the candidate.

 

Regards,

Deepak Bissa

 

From: megaco-b= ounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Abhijit Dutta
Sent: Thursday, February 23, 2012 12:38 AM
To: megaco@ietf.org
Subject: [Megaco] Local and Remote Descriptor IP type

 

Hi,

 

Sorry for this na=EFve question= -  I am posting it since there is no clear indication in the RFC.

 

Can local and remote descriptor= contain differ IP address types -  one say IPv4 and another IPv6. If = not, what should the MGC return (error code) in reply during such situation= s.

 

~Thanx
Abhijit





=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D
 --_000_54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D53GUREXMB01ASIA_-- From albrecht.schwarz@alcatel-lucent.com Fri Feb 24 00:47:02 2012 Return-Path: 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 39D1F21F87CD for ; Fri, 24 Feb 2012 00:47:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.954 X-Spam-Level: X-Spam-Status: No, score=-4.954 tagged_above=-999 required=5 tests=[AWL=1.294, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 gLl10yHGOhF2 for ; Fri, 24 Feb 2012 00:47:01 -0800 (PST) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by ietfa.amsl.com (Postfix) with ESMTP id 10FF821F87C9 for ; Fri, 24 Feb 2012 00:47:00 -0800 (PST) Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q1O8klRC022753 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 24 Feb 2012 09:46:58 +0100 Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.50]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Fri, 24 Feb 2012 09:46:56 +0100 From: "Schwarz, Albrecht (Albrecht)" To: Abhijit Dutta , "megaco@ietf.org" Date: Fri, 24 Feb 2012 09:47:05 +0100 Thread-Topic: Local and Remote Descriptor IP type Thread-Index: AczxlQYrjdmvQwyDTgW2uwfUVI5xFgBD9U9wAArUovA= Message-ID: <5F7BCCF5541B7444830A2288ABBEBC9621625F9D34@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> References: <9085F06114A8A44EB121CE1B1ADAE03618E9DCE29C@INEXCHANGE> <54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D53@GUREXMB01.ASIAN.AD.ARICENT.COM> In-Reply-To: <54EB4D88B3CAC74B816D6B3B65528CA42E02EB3D53@GUREXMB01.ASIAN.AD.ARICENT.COM> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE, en-US Content-Type: multipart/alternative; boundary="_000_5F7BCCF5541B7444830A2288ABBEBC9621625F9D34FRMRSSXCHMBSD_" MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13 Subject: Re: [Megaco] Local and Remote Descriptor IP type X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2012 08:47:02 -0000 --_000_5F7BCCF5541B7444830A2288ABBEBC9621625F9D34FRMRSSXCHMBSD_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Abhijit, 1st: there isn't any RFC, you got to use the ITU-T H.248.x-series of Recomm= endations concerning MEGACO protocol. 2nd: the H.248 stream is fundamentally a bidirectional construct, i.e., cov= ering two unidirectional media (or control) flows. However, each traffic direction may be different than the reverse direction= , sometimes called asymmetrical media (flows). Thus, it's definetely not a failure situation per se your use case. You may= use different IP protocol versions for each traffic direction! You may also use different media formats (e.g. different video or audio cod= ecs) for each traffic direction. Etc. -Albrecht ________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= Deepak Bissa Sent: Freitag, 24. Februar 2012 04:49 To: Abhijit Dutta; megaco@ietf.org Subject: Re: [Megaco] Local and Remote Descriptor IP type Hi, Megaco protocol does not impose such restrictions on SDP internals and it i= s possible to have such situation. MGCs "might not" look into these details and just tunnel it to respective M= Gs and then MG has to apply or reject such media connection. H.248.8 provides list of error codes that can be exchanged between MG and M= GC. "Not Implemented" could be one of the candidate. Regards, Deepak Bissa From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= Abhijit Dutta Sent: Thursday, February 23, 2012 12:38 AM To: megaco@ietf.org Subject: [Megaco] Local and Remote Descriptor IP type Hi, Sorry for this na=EFve question - I am posting it since there is no clear = indication in the RFC. Can local and remote descriptor contain differ IP address types - one say = IPv4 and another IPv6. If not, what should the MGC return (error code) in r= eply during such situations. ~Thanx Abhijit =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D --_000_5F7BCCF5541B7444830A2288ABBEBC9621625F9D34FRMRSSXCHMBSD_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Abhijit,
 
1st: there isn't any RFC, you got to use the ITU-T= =20 H.248.x-series of Recommendations concerning MEGACO=20 protocol.
 
2nd: the H.248 stream is fundamentally a bidirecti= onal=20 construct, i.e., covering two unidirectional media (or control)=20 flows.
However, each traffic direction may be different t= han the=20 reverse direction, sometimes called asymmetrical media=20 (flows).
 
Thus, it's definetely not a failure situation per = se your=20 use case. You may use different IP protocol versions for each traffic= =20 direction!
You may also use different media formats (e.g. dif= ferent=20 video or audio codecs) for each traffic direction. Etc.
 
-Albrecht
 
 

From: megaco-bounces@ietf.org=20 [mailto:megaco-bounces@ietf.org] On Behalf Of Deepak=20 Bissa
Sent: Freitag, 24. Februar 2012 04:49
To: Abhij= it=20 Dutta; megaco@ietf.org
Subject: Re: [Megaco] Local and Remote=20 Descriptor IP type

Hi,=

Megaco protocol does = not=20 impose such restrictions on SDP internals and it is possible to have such= =20 situation.

MGCs =93might not=94 = look into=20 these details and just tunnel it to respective MGs and then MG has to app= ly or=20 reject such media connection.

 

H.248.8 provides list= of error=20 codes that can be exchanged between MG and MGC.  =93Not Implemented= =94 could=20 be one of the candidate.

 

Regards,

Deepak=20 Bissa

 

From:=20 megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= =20 Abhijit Dutta
Sent: Thursday, February 23, 2012 12:38=20 AM
To: megaco@ietf.org
Subject: [Megaco] Local and Re= mote=20 Descriptor IP type

 

Hi,

 

Sorry for this na=EFve question -=   I am=20 posting it since there is no clear indication in the=20 RFC.

 

Can local and remote descriptor c= ontain=20 differ IP address types -  one say IPv4 and another IPv6. If not, wh= at=20 should the MGC return (error code) in reply during such=20 situations.

 

~Thanx
Abhijit





=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Please=20 refer to http://www.aricent.com/legal/email_disclaimer.html
for import= ant=20 disclosures regarding this electronic=20 communication.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 --_000_5F7BCCF5541B7444830A2288ABBEBC9621625F9D34FRMRSSXCHMBSD_-- From manoska@gmail.com Sat Feb 25 13:28:03 2012 Return-Path: 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 ED54721F8548 for ; Sat, 25 Feb 2012 13:28:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] 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 1GwPyvU8mv76 for ; Sat, 25 Feb 2012 13:28:02 -0800 (PST) Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5761B21F8522 for ; Sat, 25 Feb 2012 13:28:02 -0800 (PST) Received: by eeke51 with SMTP id e51so305191eek.31 for ; Sat, 25 Feb 2012 13:28:01 -0800 (PST) Received-SPF: pass (google.com: domain of manoska@gmail.com designates 10.14.47.68 as permitted sender) client-ip=10.14.47.68; Authentication-Results: mr.google.com; spf=pass (google.com: domain of manoska@gmail.com designates 10.14.47.68 as permitted sender) smtp.mail=manoska@gmail.com; dkim=pass header.i=manoska@gmail.com Received: from mr.google.com ([10.14.47.68]) by 10.14.47.68 with SMTP id s44mr4427170eeb.11.1330205281647 (num_hops = 1); Sat, 25 Feb 2012 13:28:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=lUx21ln1sS1HxMaTW/EOuv+ti5kHT2EKHMO1fvvrlu4=; b=ELQXCUc9DBb7cxDxkyQiY4iSdYrc9H3d399AXY//NUq3Py3WFO5Spx3jFgRYL3yFvm JJb6S8hT15qqF/0bR+sFMRu1I6f/g2GzxGlL4VxmIDOCwMx/yzAuwvDsNczndTjnZD+A N4ttYUBvW6dUfVmDvIclzMvyMleBj57LZFznE= Received: by 10.14.47.68 with SMTP id s44mr3337564eeb.11.1330205281561; Sat, 25 Feb 2012 13:28:01 -0800 (PST) Received: from manoscardio (adsl-52.109.242.170.tellas.gr. [109.242.170.52]) by mx.google.com with ESMTPS id a58sm36318063eeb.8.2012.02.25.13.27.59 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 25 Feb 2012 13:28:00 -0800 (PST) From: "Manolis Katsidoniotis" To: Date: Sat, 25 Feb 2012 23:27:46 +0200 Message-ID: <000c01ccf404$53985340$fac8f9c0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01CCF415.1729AEC0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Acz0A4gCbk/lXT+NTOKdoJyowjWAGA== Content-Language: el Subject: Re: [Megaco] Query regarding individual digit reporting (Deepak Bissa) X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2012 21:28:04 -0000 This is a multipart message in MIME format. ------=_NextPart_000_000D_01CCF415.1729AEC0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello Given this opportunity I would like to ask if there is any way or package that allows to send a group of digits instead of one by one. Thanks Manolis ------=_NextPart_000_000D_01CCF415.1729AEC0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello

 

Given this opportunity I would like to ask if there is any = way or package that allows to send a group of digits instead of one by = one.

 

Thanks

Manolis

------=_NextPart_000_000D_01CCF415.1729AEC0-- From Raphael.Tryster@Teledata-Networks.com Sat Feb 25 22:15:17 2012 Return-Path: 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 1990521F8598 for ; Sat, 25 Feb 2012 22:15:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.714 X-Spam-Level: ** X-Spam-Status: No, score=2.714 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_MISMATCH_COM=0.553, MIME_QP_LONG_LINE=1.396, SARE_RECV_BEZEQINT_B=0.763, UNPARSEABLE_RELAY=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 maVLvAZJlLR7 for ; Sat, 25 Feb 2012 22:15:16 -0800 (PST) Received: from teledata-networks.com (mail.teledata-networks.COM [81.218.12.242]) by ietfa.amsl.com (Postfix) with ESMTP id F02BC21F8542 for ; Sat, 25 Feb 2012 22:15:14 -0800 (PST) Received: from Internal Mail-Server by Mail-SeCure (envelope-from Raphael.Tryster@Teledata-Networks.com) with SMTP; 26 Feb 2012 08:57:00 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 26 Feb 2012 08:15:29 +0200 Message-ID: In-Reply-To: <000c01ccf404$53985340$fac8f9c0$@gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Megaco] Query regarding individual digit reporting (DeepakBissa) Thread-Index: Acz0A4gCbk/lXT+NTOKdoJyowjWAGAASg4gg References: <000c01ccf404$53985340$fac8f9c0$@gmail.com> From: "Raphael Tryster" To: "Manolis Katsidoniotis" , Subject: Re: [Megaco] Query regarding individual digit reporting (DeepakBissa) X-BeenThere: megaco@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Media Gateway Control List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2012 06:15:17 -0000 This is what digit maps are for. You can read about them in H.248.1 section 7.1.14. For an example, see section I.1.2 Collecting originator digits and initiating termination, steps 8 to 11. ________________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Manolis Katsidoniotis Sent: Saturday, 25 February 2012 11:28 PM To: megaco@ietf.org Subject: Re: [Megaco] Query regarding individual digit reporting (DeepakBissa) Hello Given this opportunity I would like to ask if there is any way or package that allows to send a group of digits instead of one by one. Thanks Manolis NOTICE: This email and any files transmitted with it are Enablence and Teledata-Networks confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains Enablence and Teledata-Networks confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.