rfc3015.txt

RFC 的详细文档！

   and when the Termination is taken out of the call it is in.

   Multimedia gateways may process multiplexed media streams.  For
   example, Recommendation H.221 describes a frame structure for
   multiple media streams multiplexed on a number of digital 64 kbit/s
   channels.  Such a case is handled in the connection model in the
   following way.  For every bearer channel that carries part of the
   multiplexed streams, there is a Termination.  The Terminations that
   source/sink the digital channels are connected to a separate
   Termination called the multiplexing Termination. This Termination
   describes the multiplex used (e.g. how the H.221 frames are carried
   over the digital channels used).  The MuxDescriptor is used to this
   end.  If multiple media are carried, this Termination contains
   multiple StreamDescriptors. The media streams can be associated with
   streams sourced/sunk by other Terminations in the Context.

   Terminations may be created which represent multiplexed bearers, such
   as an ATM AAL Type 2 bearer.  When a new multiplexed bearer is to be
   created, an ephemeral termination is created in a context established
   for this purpose.  When the termination is subtracted, the
   multiplexed bearer is destroyed.

6.2.1 Termination Dynamics

   The protocol can be used to create new Terminations and to modify
   property values of existing Terminations.  These modifications
   include the possibility of adding or removing events and/or signals.
   The Termination properties, and events and signals are described in





Cuervo, et al.              Standards Track                    [Page 16]

RFC 3015              Megaco Protocol Version 1.0          November 2000


   the ensuing sections. An MGC can only release/modify terminations and
   the resources that the termination represents which it has previously
   seized via, e.g., the Add command.

6.2.2 TerminationIDs

   Terminations are referenced by a TerminationID, which is an arbitrary
   schema chosen by the MG.

   TerminationIDs of physical Terminations are provisioned in the Media
   Gateway. The TerminationIDs may be chosen to have structure.  For
   instance, a TerminationID may consist of trunk group and a trunk
   within the group.

   A wildcarding mechanism using two types of wildcards can be used with
   TerminationIDs.  The two wildcards are ALL and CHOOSE.  The former is
   used to address multiple Terminations at once, while the latter is
   used to indicate to a media gateway that it must select a Termination
   satisfying the partially specified TerminationID.  This allows, for
   instance, that a MGC instructs a MG to choose a circuit within a
   trunk group.

   When ALL is used in the TerminationID of a command, the effect is
   identical to repeating the command with each of the matching
   TerminationIDs.  Since each of these commands may generate a
   response, the size of the entire response may be large.  If
   individual responses are not required, a wildcard response may be
   requested.  In such a case, a single response is generated, which
   contains the UNION of all of the individual responses which otherwise
   would have been generated, with duplicate values suppressed.  For
   instance, given a Termination Ta with properties p1=a, p2=b and
   Termination Tb with properties p2=c, p3=d, a UNION response would
   consist of a wildcarded TerminationId and the sequence of properties
   p1=a, p2=b,c and p3=d.  Wildcard response may be particularly useful
   in the Audit commands.

   The encoding of the wildcarding mechanism is detailed in Annexes A
   and B.

6.2.3 Packages

   Different types of gateways may implement Terminations that have
   widely differing characteristics.  Variations in Terminations are
   accommodated in the protocol by allowing Terminations to have
   optional Properties, Events, Signals and Statistics implemented by
   MGs.





Cuervo, et al.              Standards Track                    [Page 17]

RFC 3015              Megaco Protocol Version 1.0          November 2000


   In order to achieve MG/MGC interoperability, such options are grouped
   into Packages, and a Termination realizes a set of such Packages.
   More information on definition of packages can be found in section
   12.  An MGC can audit a Termination to determine which Packages it
   realizes.

   Properties, Events, Signals and Statistics defined in Packages, as
   well as parameters to them, are referenced by identifiers (Ids).
   Identifiers are scoped. For each package, PropertyIds, EventIds,
   SignalIds, StatisticsIds and ParameterIds have unique name spaces and
   the same identifier may be used in each of them.  Two PropertyIds in
   different packages may also have the same identifier, etc.

6.2.4 Termination Properties and Descriptors

   Terminations have properties.  The properties have unique
   PropertyIDs.  Most properties have default values, which are
   explicitly defined in this standard or in a package (see Section 12)
   or set by provisioning.  If not provisioned otherwise, all
   descriptors except TerminationState and LocalControl default to
   empty/"no value" when a Termination is first created or returned to
   the null Context.  The default contents of the two exceptions are
   described in sections 7.1.5 and 7.1.7.

   There are a number of common properties for Terminations and
   properties specific to media streams. The common properties are also
   called the termination state properties.  For each media stream,
   there are local properties and properties of the received and
   transmitted flows.

   Properties not included in the base protocol are defined in Packages.
   These properties are referred to by a name consisting of the
   PackageName and a PropertyId.  Most properties have default values
   described in the Package description. Properties may be read- only or
   read/write.  The possible values of a property may be audited, as can
   their current values.  For properties that are read/write, the MGC
   can set their values.  A property may be declared as "Global" which
   has a single value shared by all terminations realizing the package.
   Related properties are grouped into descriptors for convenience.

   When a Termination is Added to a Context, the value of its read/write
   properties can be set by including the appropriate descriptors as
   parameters to the Add command.  Properties not mentioned in the
   command retain their prior values.  Similarly, a property of a
   Termination in a Context may have its value changed by the Modify
   command.  Properties not mentioned in the Modify command retain their
   prior values. Properties may also have their values changed when a




Cuervo, et al.              Standards Track                    [Page 18]

RFC 3015              Megaco Protocol Version 1.0          November 2000


   Termination is moved from one Context to another as a result of a
   Move command.  In some cases, descriptors are returned as output from
   a command.

   The following table lists all of the possible Descriptors and their
   use.  Not all descriptors are legal as input or output parameters to
   every command.












































Cuervo, et al.              Standards Track                    [Page 19]

RFC 3015              Megaco Protocol Version 1.0          November 2000


   +------------------+-----------------------------------------------+
   | Descriptor Name  | Description                                   |
   |------------------|-----------------------------------------------|
   | Modem            | Identifies modem type and properties          |
   |                  | when applicable.                              |
   | Mux              | Describes multiplex type for multimedia       |
   |                  | terminations (e.g. H.221, H.223, H.225.0)     |
   |                  | and Terminations forming the input mux.       |
   | Media            | A list of media stream specifications         |
   |                  | (see 7.1.4).                                  |
   | TerminationState | Properties of a Termination (which can be     |
   |                  | defined in Packages) that are not stream      |
   |                  | specific.                                     |
   | Stream           | A list of remote/local/localControl           |
   |                  | descriptors for a single stream.              |
   | Local            | Contains properties that specify the media    |
   |                  | flows that the MG receives from the remote    |
   |                  | entity.                                       |
   | Remote           | Contains properties that specify the media    |
   |                  | flows that the MG sends to the remote entity. |
   | LocalControl     | Contains properties (which can be defined in  |
   |                  | packages) that are of interest between the MG |
   |                  | and the MGC.                                  |
   | Events           | Describes events to be detected by the MG and |
   |                  | what to do when an event is detected.         |
   | EventBuffer      | Describes events to be detected by the MG     |
   |                  | when Event Buffering is active.               |
   | Signals          | Describes signals and/or actions to be        |
   |                  | applied (e.g. Busy Tone) to the Terminations. |
   | Audit            | In Audit commands, identifies which           |
   |                  | information is desired.                       |
   | Packages         | In AuditValue, returns a list of Packages     |
   |                  | realized by Termination.                      |
   | DigitMap         | Defines patterns against which sequences of a |
   |                  | specified set of events are to be matched so  |
   |                  | they can be reported as a group rather than   |
   |                  | singly.                                       |
   | ServiceChange    | In ServiceChange, what, why service change    |
   |                  | occurred, etc.                                |
   | ObservedEvents   | In Notify or AuditValue, report of events     |
   |                  | observed.                                     |
   | Statistics       | In Subtract and Audit, Report of Statistics   |
   |                  | kept on a Termination.                        |
   +------------------------------------------------------------------+







Cuervo, et al.              Standards Track                    [Page 20]

RFC 3015              Megaco Protocol Version 1.0          November 2000


6.2.5 Root Termination

   Occasionally, a command must refer to the entire gateway, rather than
   a termination within it.  A special TerminationID, "Root" is reserved
   for this purpose.  Packages may be defined on Root.  Root thus may
   have properties, events and statistics (signals  are not appropriate
   for root).  Accordingly, the root TerminationID may appear in:

   *  a Modify command - to change a property or set an event
   *  a Notify command - to report an event
   *  an AuditValue return - to examine the values of properties and
      statistics implemented on root
   *  an AuditCapability - to determine what properties of root are
      implemented
   *  a ServiceChange - to declare the gateway in or out of service.

   Any other use of the root TerminationID is an error.

7. COMMANDS

   The protocol provides commands for manipulating the logical entities
   of the protocol connection model, Contexts and Terminations.

   Commands provide control at the finest level of granularity supported
   by the protocol.  For example, Commands exist to add Terminations to
   a Context, modify Terminations, subtract Terminations from a Context,