
From sumantgupta@gmail.com  Thu Jan  5 02:17:26 2012
Return-Path: <sumantgupta@gmail.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 6943C21F8625 for <megaco@ietfa.amsl.com>; Thu,  5 Jan 2012 02:17:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=0.930,  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 uhCLk5knOsAJ for <megaco@ietfa.amsl.com>; Thu,  5 Jan 2012 02:17:26 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id A6E4621F85E0 for <megaco@ietf.org>; Thu,  5 Jan 2012 02:17:25 -0800 (PST)
Received: by bkbzs8 with SMTP id zs8so80536bkb.31 for <megaco@ietf.org>; Thu, 05 Jan 2012 02:17:24 -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=vfJXmixeVbTB9sSS78BGl6gYlivaobXarpLRQKqN9y8=; b=BxZvz92n2+tDcPcpH/tzHJYbkIpJN88xYsrBU5OgYO+P1Ng88Yh/t7la5d6ZPRL8oi k+s7WiYPDzilXGcUK7rVALkjv+RlZCVaQWWIcq1ykU9j4D19LFKVJFHEb8hreCvcc/jO a+1pAurFmeNjkOaYwZQCuOTYSQNfy1EQQ3n3I=
MIME-Version: 1.0
Received: by 10.204.148.216 with SMTP id q24mr488783bkv.129.1325758644690; Thu, 05 Jan 2012 02:17:24 -0800 (PST)
Received: by 10.204.62.208 with HTTP; Thu, 5 Jan 2012 02:17:24 -0800 (PST)
Date: Thu, 5 Jan 2012 15:47:24 +0530
Message-ID: <CAFty30VHCBq-v0Ln6KKsp-1HrwxWKP8OsUp3fwaF1Zc4BmeZmQ@mail.gmail.com>
From: Sumant Gupta <sumantgupta@gmail.com>
To: megaco@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Megaco] MGCP-Query regarding Connection id and call id?
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: Thu, 05 Jan 2012 10:21:38 -0000

Can somebody help in providing info that how can a single callid could
have 2 more or connections associated with it?

Some text i have found:

A call is identified by its call ID, which is created by the MGC when
establishing a new call. Call ID is a hexadecimal string with a
maximum length of 32 characters. Call ID is unique within the MGC. Two
or more connections can have the same call ID if they belong to the
same call.

Looking for response?

From tom.taylor.stds@gmail.com  Thu Jan  5 06:05:52 2012
Return-Path: <tom.taylor.stds@gmail.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 B0A9921F882D for <megaco@ietfa.amsl.com>; Thu,  5 Jan 2012 06:05:52 -0800 (PST)
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=[AWL=0.000,  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 RMJFjB9zUPzm for <megaco@ietfa.amsl.com>; Thu,  5 Jan 2012 06:05:52 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2B82B21F882B for <megaco@ietf.org>; Thu,  5 Jan 2012 06:05:52 -0800 (PST)
Received: by yhjj72 with SMTP id j72so138491yhj.31 for <megaco@ietf.org>; Thu, 05 Jan 2012 06:05:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=EzRq8kAhZ41Lp2DcR14eepU/dNkbcK1QpeuSKocRypQ=; b=aED5eGLLD3PgBBGSDAMEkgt7EuxTWFwPD5dzaXsJiPbRsE0KfOONw9S6AZNjr/RsnR cWhPLoHdgzr8T8aRKdh5Ra6VzhnDOu7xDr7fgKxDNJQmkJQkvGaKQfClUg2mrBei+z96 KXHSciKo3gc9olpi0lZBkVzaWD7F/coGto2R8=
Received: by 10.236.161.197 with SMTP id w45mr1598808yhk.96.1325772351756; Thu, 05 Jan 2012 06:05:51 -0800 (PST)
Received: from [192.168.2.17] (bas4-ottawa10-1088918650.dsl.bell.ca. [64.231.148.122]) by mx.google.com with ESMTPS id j16sm23082922anm.9.2012.01.05.06.05.50 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 05 Jan 2012 06:05:51 -0800 (PST)
Message-ID: <4F05AE3E.90409@gmail.com>
Date: Thu, 05 Jan 2012 09:05:50 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Sumant Gupta <sumantgupta@gmail.com>
References: <CAFty30VHCBq-v0Ln6KKsp-1HrwxWKP8OsUp3fwaF1Zc4BmeZmQ@mail.gmail.com>
In-Reply-To: <CAFty30VHCBq-v0Ln6KKsp-1HrwxWKP8OsUp3fwaF1Zc4BmeZmQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: megaco@ietf.org
Subject: Re: [Megaco] MGCP-Query regarding Connection id and call id?
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: Thu, 05 Jan 2012 14:05:52 -0000

A conference call?

On 05/01/2012 5:17 AM, Sumant Gupta wrote:
> Can somebody help in providing info that how can a single callid could
> have 2 more or connections associated with it?
>
> Some text i have found:
>
> A call is identified by its call ID, which is created by the MGC when
> establishing a new call. Call ID is a hexadecimal string with a
> maximum length of 32 characters. Call ID is unique within the MGC. Two
> or more connections can have the same call ID if they belong to the
> same call.
>
> Looking for response?
> _______________________________________________
> Megaco mailing list
> Megaco@ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>

From sumantgupta@gmail.com  Thu Jan  5 08:06:21 2012
Return-Path: <sumantgupta@gmail.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 C2D0E21F8817 for <megaco@ietfa.amsl.com>; Thu,  5 Jan 2012 08:06:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.967
X-Spam-Level: 
X-Spam-Status: No, score=-2.967 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599, J_CHICKENPOX_46=0.6, 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 E4x9ip9BmSjd for <megaco@ietfa.amsl.com>; Thu,  5 Jan 2012 08:06:20 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF8721F8688 for <megaco@ietf.org>; Thu,  5 Jan 2012 08:06:20 -0800 (PST)
Received: by eaak10 with SMTP id k10so567461eaa.31 for <megaco@ietf.org>; Thu, 05 Jan 2012 08:06:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yBbzKYZ4PEy8zpsR/YmhOwBHZapT8C9ppQsoejtPEYg=; b=FhCzk9B8V49IL9BR9YfJaedpW0ZVSilQgP2PYBK4oq151/IlOeiSZpYH8o1DEuRSoo nsp0jQv/qu2ZN/s3Kv0gV5W3cnjCa8VlVqRudwHLANBzaIksL0odyGzEdciO9jNfrwT1 EAvcmvu9DqoEVI+bfQSts6BXvpf8EEZGMsEFI=
MIME-Version: 1.0
Received: by 10.204.156.207 with SMTP id y15mr957065bkw.93.1325779578749; Thu, 05 Jan 2012 08:06:18 -0800 (PST)
Received: by 10.204.62.208 with HTTP; Thu, 5 Jan 2012 08:06:18 -0800 (PST)
In-Reply-To: <4F05AE3E.90409@gmail.com>
References: <CAFty30VHCBq-v0Ln6KKsp-1HrwxWKP8OsUp3fwaF1Zc4BmeZmQ@mail.gmail.com> <4F05AE3E.90409@gmail.com>
Date: Thu, 5 Jan 2012 21:36:18 +0530
Message-ID: <CAFty30XmkPZ06nVFGUu8cijO-CLwG4NHhxaVsXL36jjH5R183A@mail.gmail.com>
From: Sumant Gupta <sumantgupta@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: megaco@ietf.org
Subject: Re: [Megaco] MGCP-Query regarding Connection id and call id?
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: Thu, 05 Jan 2012 16:06:21 -0000

I have seen a sample trace of 3way call.Following is the flow,please
correct me if i am wrong:

A dials B first a 2way call is established and the details of this
call are say call id value from Call agent comes as 1 and connection
id generated by endpoint   is 10

Now A presses flash hook

Now A dials C and 2way call is established and the details of this
call are say call id value from Call agent comes as  2 and connection
id generated by endpoint   is 11

A presses flash hook again.Call agent changes the Connection mode
parameter to "conference" via the MDCX
command for entity A and a conference call is established b/s the 3 parties.

Here different connection id  is used during the conf. call.

Regards
Sumant

On Thu, Jan 5, 2012 at 7:35 PM, Tom Taylor <tom.taylor.stds@gmail.com> wrote:
> A conference call?
>
>
> On 05/01/2012 5:17 AM, Sumant Gupta wrote:
>>
>> Can somebody help in providing info that how can a single callid could
>> have 2 more or connections associated with it?
>>
>> Some text i have found:
>>
>> A call is identified by its call ID, which is created by the MGC when
>> establishing a new call. Call ID is a hexadecimal string with a
>> maximum length of 32 characters. Call ID is unique within the MGC. Two
>> or more connections can have the same call ID if they belong to the
>> same call.
>>
>> Looking for response?
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>
>

From arindam.bhattacharjee@alcatel-lucent.com  Thu Jan  5 08:28:01 2012
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 0A89621F85BF for <megaco@ietfa.amsl.com>; Thu,  5 Jan 2012 08:28:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 P1wVoVP1YpAR for <megaco@ietfa.amsl.com>; Thu,  5 Jan 2012 08:28:00 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 54C6421F84DE for <megaco@ietf.org>; Thu,  5 Jan 2012 08:27:55 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id q05GRpgI020356 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 5 Jan 2012 10:27:51 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q05GRjfJ008946 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 5 Jan 2012 10:27:51 -0600
Received: from USNAVSXCHMBSA2.ndc.alcatel-lucent.com ([135.3.39.124]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Thu, 5 Jan 2012 10:27:49 -0600
From: "Bhattacharjee, Arindam (Arindam)" <arindam.bhattacharjee@alcatel-lucent.com>
To: Sumant Gupta <sumantgupta@gmail.com>, "megaco@ietf.org" <megaco@ietf.org>
Date: Thu, 5 Jan 2012 10:27:48 -0600
Thread-Topic: [Megaco] MGCP-Query regarding Connection id and call id?
Thread-Index: AczLk9FiqJ/O7tDhTa6yAKOZq+oQ4gAMcmoQ
Message-ID: <703C56B521385C4C9091299BE82357B7EFE956BA@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
References: <CAFty30VHCBq-v0Ln6KKsp-1HrwxWKP8OsUp3fwaF1Zc4BmeZmQ@mail.gmail.com>
In-Reply-To: <CAFty30VHCBq-v0Ln6KKsp-1HrwxWKP8OsUp3fwaF1Zc4BmeZmQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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.11
Subject: Re: [Megaco] MGCP-Query regarding Connection id and call id?
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: Thu, 05 Jan 2012 16:28:01 -0000

Hi,
Not sure if question related to Megaco or H248. H248 does not discuss about=
 call id of  MGC. Call id is there in SIP or similar call control procedure=
s which are orthogonal to H.248. and H248 does not mandate any specific cal=
l control application in MGC. Context-id is selected by MG and multiple ter=
minations can be in a context. Context id should not be confused or used as=
 call-id in MGC, since for example a call with a call id may be having term=
inations on multiple MGs controlled by same MGC. So same call id can have m=
ultiple contexts in an MGC.
=20
-Arindam=20

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of=
 Sumant Gupta
Sent: Thursday, January 05, 2012 5:17 AM
To: megaco@ietf.org
Subject: [Megaco] MGCP-Query regarding Connection id and call id?

Can somebody help in providing info that how can a single callid could
have 2 more or connections associated with it?

Some text i have found:

A call is identified by its call ID, which is created by the MGC when
establishing a new call. Call ID is a hexadecimal string with a
maximum length of 32 characters. Call ID is unique within the MGC. Two
or more connections can have the same call ID if they belong to the
same call.

Looking for response?
_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www.ietf.org/mailman/listinfo/megaco

From arindam.bhattacharjee@alcatel-lucent.com  Thu Jan  5 08:34:37 2012
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 ACE6521F8804 for <megaco@ietfa.amsl.com>; Thu,  5 Jan 2012 08:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_46=0.6, 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 HgY66rTd1MQX for <megaco@ietfa.amsl.com>; Thu,  5 Jan 2012 08:34:36 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9946621F87FF for <megaco@ietf.org>; Thu,  5 Jan 2012 08:34:36 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q05GYZiI001897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 5 Jan 2012 10:34:35 -0600 (CST)
Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q05GYZtE013257 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 5 Jan 2012 10:34:35 -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, 5 Jan 2012 10:34:35 -0600
From: "Bhattacharjee, Arindam (Arindam)" <arindam.bhattacharjee@alcatel-lucent.com>
To: Sumant Gupta <sumantgupta@gmail.com>, Tom Taylor <tom.taylor.stds@gmail.com>
Date: Thu, 5 Jan 2012 10:34:17 -0600
Thread-Topic: [Megaco] MGCP-Query regarding Connection id and call id?
Thread-Index: AczLxAEHoBuGVQYbSleVDa3U1qQUuwAA6EmA
Message-ID: <703C56B521385C4C9091299BE82357B7EFE956C6@USNAVSXCHMBSA2.ndc.alcatel-lucent.com>
References: <CAFty30VHCBq-v0Ln6KKsp-1HrwxWKP8OsUp3fwaF1Zc4BmeZmQ@mail.gmail.com> <4F05AE3E.90409@gmail.com> <CAFty30XmkPZ06nVFGUu8cijO-CLwG4NHhxaVsXL36jjH5R183A@mail.gmail.com>
In-Reply-To: <CAFty30XmkPZ06nVFGUu8cijO-CLwG4NHhxaVsXL36jjH5R183A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-puzzleid: {042E542B-B343-48BC-8BC1-CEBBCEBA34CF}
x-cr-hashedpuzzle: Clgy D9Gm E5GE GPWI KJ28 K2c6 MGvC O00f RJjc RtEQ UbQV YoI0 ZG1i ZhQP bq2K eXoP; 3; bQBlAGcAYQBjAG8AQABpAGUAdABmAC4AbwByAGcAOwBzAHUAbQBhAG4AdABnAHUAcAB0AGEAQABnAG0AYQBpAGwALgBjAG8AbQA7AHQAbwBtAC4AdABhAHkAbABvAHIALgBzAHQAZABzAEAAZwBtAGEAaQBsAC4AYwBvAG0A; Sosha1_v1; 7; {042E542B-B343-48BC-8BC1-CEBBCEBA34CF}; YQByAGkAbgBkAGEAbQAuAGIAaABhAHQAdABhAGMAaABhAHIAagBlAGUAQABhAGwAYwBhAHQAZQBsAC0AbAB1AGMAZQBuAHQALgBjAG8AbQA=; Thu, 05 Jan 2012 16:34:17 GMT; UgBFADoAIABbAE0AZQBnAGEAYwBvAF0AIABNAEcAQwBQAC0AUQB1AGUAcgB5ACAAcgBlAGcAYQByAGQAaQBuAGcAIABDAG8AbgBuAGUAYwB0AGkAbwBuACAAaQBkACAAYQBuAGQAIABjAGEAbABsACAAaQBkAD8A
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: "megaco@ietf.org" <megaco@ietf.org>
Subject: Re: [Megaco] MGCP-Query regarding Connection id and call id?
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: Thu, 05 Jan 2012 16:34:37 -0000

I think your question is probably related to MGCP not Megaco.

Some one with MGCP expertise may be able to help you.

-Arindam

-----Original Message-----
From: megaco-bounces@ietf.org [mailto:megaco-bounces@ietf.org] On Behalf Of=
 Sumant Gupta
Sent: Thursday, January 05, 2012 11:06 AM
To: Tom Taylor
Cc: megaco@ietf.org
Subject: Re: [Megaco] MGCP-Query regarding Connection id and call id?

I have seen a sample trace of 3way call.Following is the flow,please
correct me if i am wrong:

A dials B first a 2way call is established and the details of this
call are say call id value from Call agent comes as 1 and connection
id generated by endpoint   is 10

Now A presses flash hook

Now A dials C and 2way call is established and the details of this
call are say call id value from Call agent comes as  2 and connection
id generated by endpoint   is 11

A presses flash hook again.Call agent changes the Connection mode
parameter to "conference" via the MDCX
command for entity A and a conference call is established b/s the 3 parties=
.

Here different connection id  is used during the conf. call.

Regards
Sumant

On Thu, Jan 5, 2012 at 7:35 PM, Tom Taylor <tom.taylor.stds@gmail.com> wrot=
e:
> A conference call?
>
>
> On 05/01/2012 5:17 AM, Sumant Gupta wrote:
>>
>> Can somebody help in providing info that how can a single callid could
>> have 2 more or connections associated with it?
>>
>> Some text i have found:
>>
>> A call is identified by its call ID, which is created by the MGC when
>> establishing a new call. Call ID is a hexadecimal string with a
>> maximum length of 32 characters. Call ID is unique within the MGC. Two
>> or more connections can have the same call ID if they belong to the
>> same call.
>>
>> Looking for response?
>> _______________________________________________
>> Megaco mailing list
>> Megaco@ietf.org
>> https://www.ietf.org/mailman/listinfo/megaco
>>
>
_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www.ietf.org/mailman/listinfo/megaco

From prekgupta@gmail.com  Thu Jan 12 02:26:55 2012
Return-Path: <prekgupta@gmail.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 BFE2021F8597 for <megaco@ietfa.amsl.com>; Thu, 12 Jan 2012 02:26:55 -0800 (PST)
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=[AWL=0.001,  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 Htpe9LCMFww9 for <megaco@ietfa.amsl.com>; Thu, 12 Jan 2012 02:26:55 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 41D0821F8596 for <megaco@ietf.org>; Thu, 12 Jan 2012 02:26:55 -0800 (PST)
Received: by vcbfk13 with SMTP id fk13so1437160vcb.31 for <megaco@ietf.org>; Thu, 12 Jan 2012 02:26:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=sIHIeLr4mttFSVk/jZrAy/JU22dq70el7rgqx/WejzE=; b=GQ/It78sdOo1rCuH+59dSEOD0YLXZKfcYwhXEWr5Kf6bgFepONUSs/LAGJox9+zp+a oi4txBWw7/WRjlUAX+jwBQoUWQg7yQ6TZALWEL2HvnKwQLmM5QTZhA7hRMMY4ydZfbqD 47qo/kWINec/9NYjsVBYJ84QogfuV/R1A6OhQ=
MIME-Version: 1.0
Received: by 10.220.226.193 with SMTP id ix1mr1595240vcb.57.1326364014623; Thu, 12 Jan 2012 02:26:54 -0800 (PST)
Received: by 10.220.224.133 with HTTP; Thu, 12 Jan 2012 02:26:54 -0800 (PST)
In-Reply-To: <CAMaBYnd9Vr627En6LBeZRsxqpw5YZnaXw1j6vXEsCBusGBiKuw@mail.gmail.com>
References: <CAMaBYnd9Vr627En6LBeZRsxqpw5YZnaXw1j6vXEsCBusGBiKuw@mail.gmail.com>
Date: Thu, 12 Jan 2012 15:56:54 +0530
Message-ID: <CAMaBYnfOvRsGUgYZqZSDGN3t4XAO-VOh29OTkyjDxtZd0a_++g@mail.gmail.com>
From: itz me <prekgupta@gmail.com>
To: megaco@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Megaco] MG sends a Service Change request for ROOT terminal only and not to individual terminals while association creation
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: Thu, 12 Jan 2012 10:26:55 -0000

Hi

In the following scenario:
1.	MG sends initial Service Change request to ROOT.
2.	MG receives successful reply from MGC.
3.	MGC now sends the Service change request as follows:
ROOT{Services{VERSION=1,Method=Forced, Reason="905 Termination taken
out of service"
4.	MG receives service change confirmation from MGC.
5.	MG gives 401 protocol error.


 Hi All


 Can MG configure the association with out sending service change request
>  on ROOT such that Service change Requests can be sent to individual
> terminals later.
> In current architecture, MG sends a Service Change request for ROOT
> terminal only and not to individual terminals while association creation.
>
>
>
> Regards,
> Preksha
>

From prekgupta@gmail.com  Thu Jan 12 02:45:13 2012
Return-Path: <prekgupta@gmail.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 06F7121F8526 for <megaco@ietfa.amsl.com>; Thu, 12 Jan 2012 02:45:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.57
X-Spam-Level: 
X-Spam-Status: No, score=-3.57 tagged_above=-999 required=5 tests=[AWL=0.029,  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 23h4T0DzSXV1 for <megaco@ietfa.amsl.com>; Thu, 12 Jan 2012 02:45:12 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 179B321F84B6 for <megaco@ietf.org>; Thu, 12 Jan 2012 02:45:12 -0800 (PST)
Received: by vcbfk13 with SMTP id fk13so1448445vcb.31 for <megaco@ietf.org>; Thu, 12 Jan 2012 02:45:11 -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=KlhDS8JLRe5mcAK7PxYTzyOt1kGSEfK7XbLY/N5lOFo=; b=HgQVyumwOmswkNXgOKOkVepIG0g8PC2sIrqbWwSM+AhV4TMiHpFuzm2c8qYvN62feR eJ7oT8ysht55WjfVTjtLR4Pj3zGbOgqHUoJHZ0b57yfA0Rde6CpJBCBUjppa8Oqq04Ek lIRCcmEepbOKDdpZbsWym4YW0IyWu6OLvX4jE=
MIME-Version: 1.0
Received: by 10.220.148.133 with SMTP id p5mr1695977vcv.32.1326365111410; Thu, 12 Jan 2012 02:45:11 -0800 (PST)
Received: by 10.220.224.133 with HTTP; Thu, 12 Jan 2012 02:45:11 -0800 (PST)
Date: Thu, 12 Jan 2012 16:15:11 +0530
Message-ID: <CAMaBYnejsCOqjXRMsZAx0C4Lt0yySMcTK7hsLvrHtFs0-nydiA@mail.gmail.com>
From: itz me <prekgupta@gmail.com>
To: megaco <megaco@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Megaco] Shall MG accept the confirmation for SVC request sent for ROOT termination with method forced and reason 905 Termination taken oos after initial association creation
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: Thu, 12 Jan 2012 10:45:13 -0000

Hi

In the following scenario :
At step 5 shall MG accept the confirmation for SVC request sent for
ROOT termination with method forced and reason 905 Termination taken
oos :

Scenario
1.	MG sends initial Service Change request to ROOT.
2.	MG receives successful reply from MGC.
3.	MGC now sends the Service change request as follows:
ROOT{Services{VERSION=1,Method=Forced, Reason="905 Termination taken
out of service"
4.	MG receives service change confirmation from MGC.
5.	MG gives 401 protocol error and does not accepts the SVC confirm


-Preksha
