Subject: Re: ServiceChange

From: Sachin Mittal <[email-masked]>
Date: Mon, 31 Jan 2000 13:13:53 +0530

Can we add the text "If a command other than Subtract (or ServiceChange) was
received on a
termination that is out of service, an error should be returned." somewhere in
the document.

"Rosen, Brian" <[email-masked]> on 01/27/2000 09:21:55 PM

Please respond to "Rosen, Brian" <[email-masked]>

To:   [email-masked]
cc:    (bcc: Sachin Mittal/HSS)

Subject:  Re: ServiceChange

I believe the MG should do what the MGC says.

The MGC is responsible for making the state consistent, and this
means getting the Subtract through.

A termination could be out of service, but still in a context,
and would be under failure conditions.  The MGC must run the
Subtract command to get the state reasonable.

If a command other than Subtract (or ServiceChange) was received on a
termination that is out of service, an error should be returned.

Brian

> -----Original Message-----
> From: Madhu Babu [mailto:[email-masked]]
> Sent: Thursday, January 27, 2000 5:00 AM
> To: [email-masked]
> Subject: ServiceChange
>
>
> When a termination is marked out-of-service through
> ServiceChange command
> using graceful/ forced ServiceChangeMethod, and MGC has not
> yet sent Subtract
> command for that termination, what is the processing
> associated at MG when
> second
> ServiceChange command arrives with Restart method. Should it
> be removed from
> context or disallow second ServiceChange command?
>
> There is no text in Version 13  mentioning that when
> terminations are brought
> back
> to service using Restart ServiceChange command, what the
> context of the
> terminations
> will be. Version 11 did mention this as "the Termiantions are
> assumed to now not
> be
> associated with any Context".
>