Re: Uniqueness of context ID

"Schwarz Albrecht" <[email protected]>
Newsgroups gmane.ietf.megaco
Message-ID <F4562D4585113D42AC08DC47FDEC49B001E10856@FRVELSMBS23.ad2.ad.alcatel.com>
Like to add:
there is a unique name space of ContextID values because there is a
single CA (H.248 Control Association) between a pair of MGC and MG
entities.
(Please note that there is not any difference between a physical or
virtual MG, - there's just one CA.)



> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Raphael Tryster
> Sent: Mittwoch, 20. Mai 2009 07:58
> To: Priya Krishnan; [email protected]
> Subject: Re: [Megaco] Uniqueness of context ID
> 
> Yes.  It is actually quite likely to occur if multiple MGs 
> initialize at the same time and all start assigning context 
> IDs from 1.
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Priya Krishnan
> Sent: Wednesday, 20 May 2009 8:47 AM
> To: [email protected]
> Subject: [Megaco] Uniqueness of context ID
> 
> 
> Hi,
> 
> A context ID is unique within a physical MGW. But when we 
> access a context report at MGC [example a MSS] can we 
> identify any report at MSS using only context ID.
> 
> My thinking is since MGC connects to many MGW, it might have 
> similar context IDs with multiple MGWs. Example there could 
> be a context ID 2 with MGW 1 and context ID 2 with MGW 4. In 
> that case to identify a particular context related info we 
> might need a combination of virtual MGW address and context 
> ID. Is this understanding right? please clarify.
> 
> Thanks and Regards
> Geetha
> 
> 
>       
> _______________________________________________
> Megaco mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/megaco
> _______________________________________________
> Megaco mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/megaco
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.