Subject: RE: [Megaco] Query

From: "Tom-PT Taylor"<[email-masked]>
Date: Fri, 26 Apr 2002 09:47:34 -0400

Hi.  Answers below, marked with [PTT].

-----Original Message-----
From: Suman Choudhary [mailto:[email-masked]]
Sent: Tuesday, April 30, 2002 11:29 PM
To: [email-masked]
Subject: [Megaco] Query

Hi All,

When termination goes out of service, MGW will inform MGC
with the following parameters.
 
Context ID = Contexts / Null / All
Termination ID = Termination(s)
Service Change Reason = Transmission failure / Termination malfunctioning / 
                                        Loss of lower layer connectivity /
Termination taken out of service
Service Change Method = Graceful / Forced
Is wildcarding of terminations allowed in this transaction. ?

[PTT] Yes, and it will often be needed.

If context ID is ALL, should MGC assume that all terminations in all active
contexts are out of service ??

[PTT] Only if the terminationID is also ALL.  Otherwise it would be the
termination(s) designated by the terminationID, provided they are in active
contexts.  Other people may want to comment on this interpretation.

What if the context id is NULL ?

[PTT] It is valid to report that a termination in the NULL context is out of
service.  Where we get problems is when you are not sure whether the
termination is in the acti
 
Can the MGW send this message even for ephemeral terminations ?

[PTT] Yes, it can.  There has been some debate over what this means.  At a
minimum, it means that no traffic is flowing through the termination.
Probably the MGC should subtract it and, if possible, create a replacement.

Thanx in advance,
Suman

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco