Re: [Megaco] MGC and virtual MG

[Ron Ho <ron.ho.megaco at gmail.com>]

Thanks for the clarification. So one MGC can control multiple MGs. Does the MGC need multiple mid, one for each MG? Or the MGC needs one only mid and every MGs send to the same MGC using the same mid of the MGC?

On Fri, Sep 18, 2009 at 4:13 PM, Tom Taylor <tom.taylor at rogers.com> wrote:

You should be able to control multiple virtual MG from one MGC instance if you need to. I can see a simple use case for this, where the normal MGC for one of the virtual MGs has failed and an MGC controlling another virtual MG takes its place. I am sure there are other applications.

And yes, you can multiplex control associations for multiple virtual MGs over the same physical connection. You would have to take some care not to clear down the connection just because one virtual MG is doing a restart.

Ron Ho wrote:

Hi All,

I am confused about how virtual MG is bound to MGC. For a physical MG, it
can be partitioned into multiple virtual MGs. I am confused about how these
virtual MGs bind to the MGC. Do we need one-to-one mapping between MGC and
MG? In order words, I need as many virtual MGC to connect to the virtual MG.


Can I have a single MGC having multiple virtual MGs registered into it? Do I
need multiple MGC identities? (e.g. different MGC mid for each pairing with
a virtual MG) Or just one MGC mid which can be used to connect to different
virtual MG (each virtual MG has it own mid)?

How is the addressing need to be done? I understand that binding between MGC
and MG is established by a Control Association using mid which is
independent of the physical interface used. Does it mean that I can have one
IP address/port in MGC and one IP address/port in MG while having multiple
binding connections between the MGC and the virtual MG?

I am really confused.

Many thanks,
Ron

------------------------------------------------------------------------

_______________________________________________
Megaco mailing list
Megaco at ietf.org
https://www.ietf.org/mailman/listinfo/megaco