Subject: Re: ServiceChange

From: Madhu Babu <[email-masked]>
Date: Fri, 28 Jan 2000 08:33:28 +0530

This sounds good. This implies that when terminations are taken out-of-service
the descriptors present at MG will be having values prior to receiving/sending
ServiceChange.

This implies that when a termination is out-of-service, its the responsiblity of
MGC to
update the descriptors at MG ( SInce the termination have gone out-of-service
when the termination is either in context. or NULL context).

Tom-PT Taylor <[email-masked]> on 01/28/2000 02:22:29 AM

Please respond to Tom-PT Taylor <[email-masked]>

To:   [email-masked]
cc:    (bcc: Madhu B Babu/HSS)

Subject:  Re: ServiceChange

Brian has stated this very clearly, but I'll head off one small doubt.  If
the MGC issues a ServiceChange (restart) for the the termination and it can
be recovered (i.e. hasn't lost its bearer), the MG should act on the
command.  If the termination cannot be recovered the MG should reject the
command with error return.

> -----Original Message-----
> From: Rosen, Brian [SMTP:[email-masked]]
> Sent: Thursday, January 27, 2000 10:52 AM
> To:   [email-masked]
> 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".
> >