architecture
Click on the red underlined text to get to the source
... created the H.350 series of Recommendations that specify
directory services architectures in support of multimedia
conferencing protocols. The goal of the architecture is to
...
... directory services architectures in support of multimedia
conferencing protocols. The goal of the architecture is to
'directory enable' multimedia conferencing so that these services ...
...
H.350 architectures are not intended to change the operation of
multimedia conferencing protocols in any way. Rather, they are meant
...
... In the H.350 series, Recommendation H.350 specifies the base
architecture and object classes, while subordinate Recommendations
specify elements ...
... H.323
H.350.2 - Directory Services Architecture for H.235
H.350.3 - Directory Services Architecture ...
... Directory Services Architecture for H.235
H.350.3 - Directory Services Architecture for H.320
H.350.4 - Directory Services Architecture ...
... Directory Services Architecture for H.320
H.350.4 - Directory Services Architecture for SIP
H.350 ...
... Technology may provide the email address, etc. For the purposes
of this architecture, it is assumed that an enterprise directory
is accessible via LDAP ...
...
This Recommendation describes a directory services architecture for
multimedia conferencing using LDAP ...
... H.350 should be viewed not as an authoritative
endpoint configuration architecture, but rather one tool that can
...
... endpoint has a unique configuration.
This architecture uses a generic object class, called commObject, to
represent attributes common to any video or voice ...
... object class.
There are two basic components in the architecture. The commURI
object is a class whose only purpose is to link ...
... canonical data sources in order to reduce redundant
administrative processes and ensure information accuracy. The
following design criteria are established for this architecture. The
architecture will:
...
... following design criteria are established for this architecture. The
architecture will:
1) enable endpoint ...
... applications. For example 'modelNumber', and 'accountNumber' are
examples of attributes that are not defined in the Recommendation but
may be useful if implemented. Adding attributes to this architecture
must be done in a way that does not break compatibility with this
...
... This Recommendation describes an LDAP directory services architecture
for multimedia conferencing using SIP ...
...
This Recommendation is intended to supplement the CommObject
directory architecture as discussed in ITU-T Rec. H.350, and not
...
... ITU-T Rec. H.350, and not
intended to be used as a stand-alone architecture. The
implementation of this LDAP schema, together with the use of the
...
... LDAP schema, together with the use of the
H.350 CommObject architecture, facilitates the integration of SIP
User Agents and conferencing devices into existing Enterprise
Directories, thus allowing the user to perform white page ...
...
The scope of this Recommendation includes recommendations for the
architecture to integrate endpoint information for endpoints using
...
... boundaries of standards bodies, research networks, academia and
private industry in order to produce an architecture that works
toward integrating multimedia conferencing deployments ...
... IETF and ITU-T were drawn from
extensively, and the architecture is meant to serve all communities.
This work developed out of the Video Conferencing Middleware
...
... working group, a joint effort of Internet2
(www.internet2.edu) and the Video Development Initiative
(www.vide.net). The architecture was developed in response to
deployment challenges discovered in the ViDeNet
...
...
H.350 does not alter the security architectures of any particular
protocol. However, it does offer a standardized place to store
authentication ...
... ITU-T Recommendation H.350, "Directory services architecture for multimedia conferencing", 2003. ...
... ITU-T Recommendation H.350.5, "Directory services architecture for Non-Standard Protocols", 2003. ...
... ITU-T Recommendation H.350.6, "Directory services architecture for Call Forwarding and Preferences", 2004. ...