Re: OutOfService vs Inactive

Javi,

> Christian,
> > the MGC can't change OutOfService to InService.
> 
> When MGC  sends to MG a serviceChange command with method Forced or 
> Graceful and reason 905 (Out Of Service), MGC requests to MG 
> to put out 
> of service the indicated terminations. Is not it?
[Raju]
Right. There are several reasons why a termination can be out of service(OOS).
Take a look at "H.248.8 : Gateway control protocol: Error code and service change reason description"
http://www.itu.int/rec/T-REC-H.248.8-200708-I/en

Following are some of the relevant ones:

        904 Termination malfunctioning
        905 Termination taken out of service
        906 Loss of lower layer connectivity (e.g. downstream sync)
        907 Transmission Failure

MGC can put a termination OOS and bring it back INS later.
Please see "F.4.1.2 ServiceChange Method Behaviour on Physical Terminations" of:
http://www.itu.int/rec/T-REC-H.248.1-200509-I/en


However, if the termination is OOS due to 904/906/907 reason codes then MGC 
obviously can't bring it INS.

Regards
Raju

> 
> Regards,
> 
> Javi
> 
> >
> > Regards, Christian
> >
> > On 10/12/2011 11:44 PM, Javi wrote:
> >> In a termination *with**a single stream*, which is the 
> >> differencebetween?:
> >>
> >> (a) TerminationState{ServiceStates=OutOfService}
> >>
> >> (b) Media{ LocalControl { StreamMode=Inactive } }
> >>
> >> Regards,
> >>
> >> Javi
> >>
> >>
> >> _______________________________________________
> >> Megaco mailing list
> >> [email protected]
> >> https://www.ietf.org/mailman/listinfo/megaco
> > _______________________________________________
> > Megaco mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/megaco
> >
> 
> _______________________________________________
> Megaco mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/megaco
>