=A0

thanks a lot.

=A0

Best Regards,

Kapi= l

--e89a8ff1cc642459f204c2523499-- From albrecht.schwarz@alcatel-lucent.com Wed Jun 13 00:01:47 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 3148121F8551 for ; Wed, 13 Jun 2012 00:01:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.248 X-Spam-Level: X-Spam-Status: No, score=-10.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 AryWYYe0jaLj for ; Wed, 13 Jun 2012 00:01:46 -0700 (PDT) Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 5D2E121F854A for ; Wed, 13 Jun 2012 00:01:45 -0700 (PDT) Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q5D71Xjg001021 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 13 Jun 2012 09:01:42 +0200 Received: from FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com ([135.120.45.53]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Wed, 13 Jun 2012 09:01:35 +0200 From: "Schwarz, Albrecht (Albrecht)" To: Kapil gupta , "megaco@ietf.org" Date: Wed, 13 Jun 2012 09:01:34 +0200 Thread-Topic: [Megaco] MEGACO Message Termination-Id mapping to SS7 TDM channel Thread-Index: Ac1JFOF2wDUzeeXuSZiyGQ3x6tZKUgAHSYcA Message-ID: <5F7BCCF5541B7444830A2288ABBEBC962189F4827C@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> References: In-Reply-To: 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_5F7BCCF5541B7444830A2288ABBEBC962189F4827CFRMRSSXCHMBSD_" MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83 Subject: Re: [Megaco] MEGACO Message Termination-Id mapping to SS7 TDM channel 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, 13 Jun 2012 07:01:47 -0000 --_000_5F7BCCF5541B7444830A2288ABBEBC962189F4827CFRMRSSXCHMBSD_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable See e.g. H.248 profile specification from ETSI: TS 183 002 for access gateways ES 283 024 for trunking gateways =3D> sections on termination names ________________________________ From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of= Kapil gupta Sent: Mittwoch, 13. Juni 2012 05:30 To: megaco@ietf.org Subject: [Megaco] MEGACO Message Termination-Id mapping to SS7 TDM channel Hi All, I am working on Signaling Gateway which also supports MEGACO commands to pr= ovidie Media Gateway functionality. When MGC sends MEGACO command , he specifiies the termination-id , how wil= l I determine that termination id mentioned in Megaco message will map to w= hich TDM channel id ? >From the spec, I got information that termination-id format will be choosen= by Media Gateway, Is it some kind of configuration which needs to be done in MG as well as in= MGC ? any response would be really appriciared !! thanks a lot. Best Regards, Kapil --_000_5F7BCCF5541B7444830A2288ABBEBC962189F4827CFRMRSSXCHMBSD_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

See e.g. H.248 profile specification from=20 ETSI:

TS 183 002 for access gateways

ES 283 024 for trunking gateways

=3D> sections on termination names

From: megaco-bounces@ietf.org=20 [mailto:megaco-bounces@ietf.org] On Behalf Of Kapil gupta
Sent= :=20 Mittwoch, 13. Juni 2012 05:30
To: megaco@ietf.org
Subject:<= /B>=20 [Megaco] MEGACO Message Termination-Id mapping to SS7 TDM=20 channel

Hi All,

I am working on Signaling Gateway which also supports MEGACO comm= ands=20 to providie Media Gateway functionality.

When MGC sends MEGACO command , he specifiies the termination-id= ,=20 how will I determine that termination id mentioned in Megaco message w= ill=20 map to which TDM channel id ?

From the spec, I got information that termination-id format will be ch= oosen=20 by Media Gateway,

Is it some kind of configuration which needs to be done in MG as well = as in=20 MGC ?

any response would be really appriciared !!

thanks a lot.

Best Regards,

Kapil
--_000_5F7BCCF5541B7444830A2288ABBEBC962189F4827CFRMRSSXCHMBSD_-- From tom.taylor.stds@gmail.com Wed Jun 13 08:26:51 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 BF01121F85C5 for ; Wed, 13 Jun 2012 08:26:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 8mZuDBFd5-vm for ; Wed, 13 Jun 2012 08:26:51 -0700 (PDT) Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3D63821F8592 for ; Wed, 13 Jun 2012 08:26:51 -0700 (PDT) Received: by obbeh20 with SMTP id eh20so1196084obb.31 for ; Wed, 13 Jun 2012 08:26:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=Sy4N74h+9hrWjFzPY8rE10VDeEGYb/g/Bv8h3mEvHTU=; b=jXDgaOhWKUIUUWXUZptfs7lht8WSfNTfzfJRjKC1JekK+j1DYE4MA0FZ/Z3DTbaYki n5kO4A92nn5G5JTQozVwV4hZta6Wa5ubCZF/EgMGYAnhKPWCwAzgqL6gyiX+Si7PFz1X uOE7htolUcG2qM9IaKz2bEgRe0pVMqSgKt1RlcsCeTgz3OZWlkLO2MlNgsIBvO80cr04 Adx5cMaieDq95uKgbxkDer3quKDG7pNDVQwOMzf+lqXNtkrvNvmPKYmSdQD2iEBX7fap MGEhMTV6SZ82z5B6MNA7ACe5+Ne66D23e1J8O7cIiYKtn0gviJlG0cIiKLvx4K0CP8lW LGOQ== Received: by 10.182.2.193 with SMTP id 1mr25123457obw.46.1339601210705; Wed, 13 Jun 2012 08:26:50 -0700 (PDT) Received: from [127.0.0.1] (dsl-173-206-85-206.tor.primus.ca. [173.206.85.206]) by mx.google.com with ESMTPS id s10sm2168431obo.16.2012.06.13.08.26.49 (version=SSLv3 cipher=OTHER); Wed, 13 Jun 2012 08:26:49 -0700 (PDT) Message-ID: <4FD8B138.1030901@gmail.com> Date: Wed, 13 Jun 2012 11:26:48 -0400 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: "Schwarz, Albrecht (Albrecht)" References: <5F7BCCF5541B7444830A2288ABBEBC962189F4827C@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> In-Reply-To: <5F7BCCF5541B7444830A2288ABBEBC962189F4827C@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 120613-0, 13/06/2012), Outbound message X-Antivirus-Status: Clean Cc: "megaco@ietf.org" , Kapil gupta Subject: Re: [Megaco] MEGACO Message Termination-Id mapping to SS7 TDM channel 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, 13 Jun 2012 15:26:51 -0000 ... But the short answer is that yes, coordinated configuration of MG and MGC is necessary. On 13/06/2012 3:01 AM, Schwarz, Albrecht (Albrecht) wrote: > See e.g. H.248 profile specification from ETSI: > TS 183 002 for access gateways > ES 283 024 for trunking gateways > => sections on termination names > > ________________________________ > From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of Kapil gupta > Sent: Mittwoch, 13. Juni 2012 05:30 > To: megaco@ietf.org > Subject: [Megaco] MEGACO Message Termination-Id mapping to SS7 TDM channel > > Hi All, > > I am working on Signaling Gateway which also supports MEGACO commands to providie Media Gateway functionality. > > When MGC sends MEGACO command , he specifiies the termination-id , how will I determine that termination id mentioned in Megaco message will map to which TDM channel id ? > >> From the spec, I got information that termination-id format will be choosen by Media Gateway, > > Is it some kind of configuration which needs to be done in MG as well as in MGC ? > > any response would be really appriciared !! > > thanks a lot. > > Best Regards, > Kapil > > > > > _______________________________________________ > Megaco mailing list > Megaco@ietf.org > https://www.ietf.org/mailman/listinfo/megaco