Subject: RE: Properties

From: "Michael Brown" <[email-masked]>
Date: Wed, 28 Feb 2001 14:07:02 -0500

Right, that's what I was saying. The quote from 7.1.8 only applies to
Local/Remote and hence only SDP or Native Tag values.
 
Michael

-----Original Message-----
From: Rosen, Brian [mailto:[email-masked]]
Sent: Wednesday, February 28, 2001 1:26 PM
To: Brown, Michael [NC1:GW10:EXCH]; Megaco (E-mail)
Subject: RE: Properties

I don't think that you would not get a Media descriptor return unless you
used CHOOSE,
regardless of "mandatory yet not present" properties.  If you did use
CHOOSE,
then such mandatory properties would be returned.
 
Brian

-----Original Message-----
From: Michael Brown [mailto:[email-masked]]
Sent: Wednesday, February 28, 2001 12:08 PM
To: Megaco (E-mail)
Subject: RE: Properties

I think this is the source of confusion on the suggested behavior is due to
the following statement about the Local/Remote Descriptors.
 
Section 7.1.8 states
 
The MG SHALL include additional properties and their values in its response
if these properties are mandatory yet not  present in the requests made by
the MGC (e.g., by specifying  detailed video encoding parameters where the
MGC only specified the payload type).

Just to be clear, this statement applies only to Local/Remote Descriptors
and actually refers to "properties" in the sense of returned SDP or Native
Tag values and not properties as defined in packages in other descriptors.
So, for the example where the returned values are from the LocalControl
Descriptor, the CHOOSE must be specified.

Another case where overloaded usage of the term property can cause
confusion.

Michael 

-----Original Message-----
From: Rosen, Brian [mailto:[email-masked]]
Sent: Tuesday, February 27, 2001 1:37 PM
To: Younts, Randy [NCRTP:3Z90:EXCH]; Megaco (E-mail)
Subject: RE: Properties

Properties can change value for a variety of reasons
    Because the MGC set a value in an Add, Move, or Modify command
    Because an internal event or state change occurred in the MG
    Because an external state or signal connected to the MG changed
 
The current value of a property is returned in a descriptor, what ever the
reason
the descriptor was returned.  Just because the value changed does not mean
that the
descriptor will be returned.  The descriptor is returned because:
    The MGC used CHOOSE
    The MGC used Audit
    Statistics is returned by default on a Subtract
    Service is returned by ServiceChange
 
Since your example did not use CHOOSE, Media would NOT be returned from
your example.
 
Brian

-----Original Message-----
From: Randy Younts [mailto:[email-masked]]
Sent: Tuesday, February 27, 2001 9:58 AM
To: Megaco (E-mail)
Subject: Properties

Can properties have their values changed in the reply to a command?  In
section 6.2.4, it states, "In some cases, descriptors are returned as output
from a command."  It sounds like property negotiation.  The following
message flow was suggested to me.  I am under the impression that property
values can only be read by auditing for them.  Which is correct.

MEGACO/1 [47.174.64.80]:2944 
Transaction=11 { 
 Context=- { 
     Modify=TP2 { 
         Media { 
             LocalControl { 
                 mta/mtapt = 1 
                 mta/cfg   = lp 
} } } } } 

MEGACO/1 [47.140.7.191]:2427 
Reply=11 { 
 Context=- { 
     Modify=TP2 { 
         Media { 
             LocalControl { 
                 mta/mtapt = 1 
                 mta/splitCap = NSFS 
                 mta/monCap   = No 
} } } } } 

   Two roads diverged in a wood, and I- 
   I took the one less traveled by, 
   And that has made all the difference. 
                         -Robert Frost 
-------------------------------------------- 
  
W. Randy Younts      GWC Protocols 
NORTEL NETWORKS      Dept. 3Z90 
35 Davis Dr.         Voice: (919) 991-2014 
RTP, NC  27709       ESN: 351-2014