Sumant Gupta | 5 Jan 2012 11:17
Picon

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?
Tom Taylor | 5 Jan 2012 15:05
Picon

Re: MGCP-Query regarding Connection id and call id?

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 <at> ietf.org
> https://www.ietf.org/mailman/listinfo/megaco
>
Sumant Gupta | 5 Jan 2012 17:06
Picon

Re: 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 <at> 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?
(Continue reading)

Favicon

Re: MGCP-Query regarding Connection id and call id?

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 procedures which are orthogonal to H.248. and H248 does not mandate any
specific call control application in MGC. Context-id is selected by MG and multiple terminations 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 terminations on multiple MGs controlled by same MGC. So same call id can have multiple
contexts in an MGC.

-Arindam 

-----Original Message-----
From: megaco-bounces <at> ietf.org [mailto:megaco-bounces <at> ietf.org] On Behalf Of Sumant Gupta
Sent: Thursday, January 05, 2012 5:17 AM
To: megaco <at> 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
(Continue reading)

Favicon

Re: MGCP-Query regarding Connection id and call id?

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 <at> ietf.org [mailto:megaco-bounces <at> ietf.org] On Behalf Of Sumant Gupta
Sent: Thursday, January 05, 2012 11:06 AM
To: Tom Taylor
Cc: megaco <at> 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.

(Continue reading)

itz me | 12 Jan 2012 11:26
Picon

MG sends a Service Change request for ROOT terminal only and not to individual terminals while association creation

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
>
itz me | 12 Jan 2012 11:45
Picon

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

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

Gmane