UNLIMITED FREE ACCESS TO THE WORLD'S BEST IDEAS

SUBMIT
Already an Engineering360 user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your Engineering360 Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

ITU-T H.350.4

Directory services architecture for SIP

active, Most Current
Buy Now
Organization: ITU-T
Publication Date: 1 May 2011
Status: active
Page Count: 24
scope:

This Recommendation1 describes a lightweight directory access protocol (LDAP) directory services architecture for multimedia conferencing using a session initiation protocol (SIP). In particular, it defines an LDAP schema to represent SIP user agents (UAs) on the network and associate those endpoints with users.

This Recommendation is intended to supplement the CommObject directory architecture as discussed in [ITU-T H.350], and is not intended to be used as a stand-alone architecture. The implementation of this LDAP schema, together with the use of the ITU-T H.350 CommObject architecture, facilitates the integration of SIP user agents and conferencing devices into the existing enterprise directories; thus allowing the user to perform white page lookups and access clickable dialling supported by SIP devices. The primary reasons for implementing this schema include those listed in [ITU-T H.350] (the CommObject class definition) as they apply specifically to the use of SIP UAs, and to facilitate vendors making SIP services more readily available to their users.

The scope of this Recommendation includes recommendations for the architecture to integrate endpoint information for endpoints using SIP into the existing enterprise directories and white pages.

The scope of this Recommendation does not include normative methods for the use of the LDAP directory itself or the data it contains. The purpose of the schema is not to represent all possible data elements in the SIP protocol, but rather to represent the minimal set required to accomplish the design goals enumerated in [ITU-T H.350].

Note that SIP provides well-defined methods for discovering registrar addresses and locating users on the network. Some of the attributes defined here are intended for more trivial or manual implementations and may not be needed for all applications. For example, SIPIdentityRegistrarAddress and SIPIdentityAddress may not be needed for many applications, but are included here for completeness. Thus, SIPIdentitySIPURI is the primary attribute of interest that will be served out, especially for white page directory applications.

Extending the schema

The SIPIdentity classes may be extended as necessary for specific implementations. See the base [ITU-T H.350] for a discussion on schema extension.

1 This Recommendation includes an electronic attachment containing a text file with a schema configuration for SIPIdentity.

Document History

ITU-T H.350.4
May 1, 2011
Directory services architecture for SIP
This Recommendation1 describes a lightweight directory access protocol (LDAP) directory services architecture for multimedia conferencing using a session initiation protocol (SIP). In particular, it...
August 1, 2003
Directory services architecture for SIP
A description is not available for this item.

References

Advertisement