Re: [Megaco] Re: Descriptor state after out of service

[Tom Taylor <taylor@nortelnetworks.com>]

You have me a bit confused here.  ServiceChange simply changes the state of the 
termination -- did you mean that the same Action would contain a Subtract, if issued 
by the MGC?

Christian Groves wrote:
> G'Day,
>
> I think you should concentrate more on the method associated with the service
> change that put the termination into the Out of Service state. The result of
> Forced or Graceful will be that terminations are subtracted - thus if subtracted
> the descriptors will be affected according to H.248.1 sect 7.2.3.
>
> Christian
>
> Tom Taylor wrote:
>
> > I don't believe the ServiceChange action does anything to the descriptors on its
> > own.  It is up to the MGC to reset them if necessary.  I do have the feeling that we
> > might want to analyze the situation and possibly refine it.
> >
> > Harry Suede wrote:
> >
> > > Hi list, Tom
> > >
> > > PL ignore my previous mail. By mistake I have written "out of service" in place of "in service" in the last line.
> > >
> > > What is the state of descriptor of a termination in a non-null context when termination is put "out of service" by MGC or MG? Does the descriptor remain on termination database but inactivated or does they are total flushed. Thus if this termination is put "in service" by MGC or MG then what will be the state of descriptor i.e. they are reapply/reactivated on the termination or not.
> > >
> > > regards
> > > harry
> > _______________________________________________
> > Megaco mailing list
> > Megaco@ietf.org
> > https://www1.ietf.org/mailman/listinfo/megaco
_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco