Re: Failover

Peer-to-peer synchronization (& notification) protocols between primary
and secondary H.248 entities (e.g. MG_primary to MG_secondary,
MGC_primary to MGC_secondary, MGC_primary to MGC_2nd,secondary, etc) are
OUT OF SCOPE of H.248.
See also H.Sup7.

This limits such type of changeover scenarios, you got in mind, to
"intra-vendor failovers" (e.g. all primary and secondary entities from
the same manufactures). Inter-vendor failovers would require an
agreement on a common interface.

Please note that this is not limiting other, well-known changeover
scenarios. They may be all provided in inter-vendor environments ...

 

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Javi
> Sent: Montag, 19. Oktober 2009 13:22
> To: [email protected]
> Subject: [Megaco] Failover
> 
> When an optional secondary unit of a MG detects a maintenance 
> or failure outage of the primary MG unit and the primary is 
> unable to notify the MGC of the failure, the secondary MG 
> shall send a ServiceChange Command to the MGC with 
> ServiceChangeMethod "Failover"
> 
> How does secundary MG detects that primary MG is failing?, 
> may primary MG sends any command warning about it?
> 
> Javi
> _______________________________________________
> Megaco mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/megaco
>