SIP
Click on the red underlined text to get to the source
... Directory Services Architecture for Non-Standard Protocols
Because SIP is an IETF standard, the contents of H.350 and H.350.4 ...
... gatekeeper. In SIP, this entity is a SIP Proxy Server. Note that
not all signalling protocols use a call server.
...
... that point to the associated commObjects, for example, to a user's
H.323 conferencing station and SIP IP phone. Note that multiple
instances of commURI need not point to the same commObject directory.
...
... endpoint (H.323 endpoint or SIP user agent or other
protocol endpoint) and all their aliases ...
... architecture
for multimedia conferencing using SIP. In particular, it defines an
LDAP schema to represent SIP User Agents ...
... SIP. In particular, it defines an
LDAP schema to represent SIP User Agents (UAs) on the network and
...
... 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 lookups ...
... 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
...
... endpoint information for endpoints using
SIP into existing enterprise directories and white pages.
...
... 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 Rec. H.350 ...
... attributetypes: (0.0.8.350.1.1.6.1.1
NAME 'SIPIdentitySIPURI'
DESC 'Universal Resource Indicator of the SIP UA'
EQUALITY caseExactMatch ...
... Uniform Resource Identifier that identifies a communication
resource in SIP. Usually contains a user name and a host name and is
...
... Notes
This URI may institute SIP or SIPS (secure). In the event that
SIPS is instituted, the URI must reflect that it is using SIPS as
...
... SIPS is instituted, the URI must reflect that it is using SIPS as
opposed to SIP. See Examples below.
Semantics
...
... Example applications for which this attribute would be useful
Online representation of most current listing of a user's
SIP(S) UA.
Example
...
... UA.
Example
SIPIdentitySIPURI: sip:alice@foo.com // SIP example
SIPIdentitySIPURI: sip:alice@152.2.158.212 // SIP example
...
... SIPIdentitySIPURI: sip:alice@foo.com // SIP example
SIPIdentitySIPURI: sip:alice@152.2.158.212 // SIP example
SIPIdentitySIPURI: sips:bob@birmingham.edu // SIPS example
...
... attributetypes: (0.0.8.350.1.1.6.1.3
NAME 'SIPIdentityProxyAddress'
DESC 'Specifies the location of the SIP Proxy'
EQUALITY caseIgnoreIA5Match ...
... Permissible values (if controlled)
Notes
SIP User Agents are not REQUIRED to use a proxy, but will in
many cases.
...
... as the basis for HTTP Digest in RFC 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop), any SIP servers supporting
RFC 2617draft must ensure backward compatibility ...
... HTTP Digest Authentication in RFC 2543(-> 3265prop | 3264prop | 3263prop | 3262prop | 3261prop), any SIP
servers supporting HTTP Digest Authentication ...
... user@proxy.domain portion of the SIP URI. In that case it may not be
necessary to populate this attribute.
Semantics ...
... Notes
This attribute does not represent a data element found in SIP.
SIP itself does not support distinctions in service ...
... element found in SIP.
SIP itself does not support distinctions in service levels. Instead,
this attribute provides a mechanism for the storage of service level ...
... attributetypes: (0.0.8.350.1.1.6.1.1
NAME 'SIPIdentitySIPURI'
DESC 'Universal Resource Indicator of the SIP UA'
EQUALITY caseExactMatch ...
... attributetypes: (0.0.8.350.1.1.6.1.3
NAME 'SIPIdentityProxyAddress'
DESC 'Specifies the location of the SIP Proxy'
EQUALITY caseIgnoreIA5Match ...
... credentials where appropriate. It should be noted
that both H.323 and SIP support shared secret authentication (H.235
...
... The userSMIMECertificate attribute is defined in RFC 2798 (section
2.8) as a part of inetOrgPerson. The SIP user agent's X.509
certificate can be stored in this attribute. When the certificate is
...
... Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261prop, June 2002. ...
... Rosenberg, J. and H. Schulzrinne, "Session Initiation Protocol (SIP): Locating SIP Servers", RFC 3263prop, June 2002. ...
... Rosenberg, J. and H. Schulzrinne, "Session Initiation Protocol (SIP): Locating SIP Servers", RFC 3263prop, June 2002. ...