Terminology (Unified Communications Managed API version 1.0)

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

• Bootstrapper
  A setup application that can be configured to install all of the components required by an application onto a target computer. The bootstrapper (also called an application chainer) can determine whether prerequisites for an application are installed, and if not, can download and install them.

• Connection
  Physical connection over the wire to carry packets across networks. In the Unified Communications Managed API version 1.0 SDK, a connection can use either TCP or TLS transport.

  Microsoft Office Communications Server 2007 supports two types of connections: client and server. A server connection requires the use of Mutual TLS (MTLS) transport. In addition, the server must be in the list of trusted servers on the server running Office Communications Server 2007.

• Connection manager
  Designates Unified Communications Managed API version 1.0 functionality that allows a middle-tier application to optimize the performance of server-to-server SIP communications by limiting the number of outgoing connections established with a destination tuple. After the maximum number of authorized outgoing TCP or TLS connections to a given Destination Tuple is reached, connections are shared in a round robin fashion across the Realtime endpoints of Unified Communications Managed API version 1.0.

  There are two types of connection manager:

  1. client (more secure as it does not listen on incoming connections)
  2. server (better performance as it has the ability to listen on a specified port as well as perform server throttling)

• Destination Tuple
  A destination tuple represents information needed to connect to a remote computer. It usually consists of the FQDN or IP address of the remote computer, the remote port, and the transport protocol.

• Endpoint ID
  Endpoint ID is a Microsoft specific identifier assigned to an endpoint. For example, the Endpoint ID used at registration helps Office Communications Server 2007 distinguish the endpoints of a given user. Endpoint ID is being deprecated in favor of GRUU.

• GRUU
  Globally Routable User Agent URI (GRUU) is defined in the SIP Internet-Draft, "Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP)" (draft-ietf-sip-gruu-09). GRUU is meant to represent an endpoint (registered or not) in the Unified Communications infrastructure.

• Media description
  Description of media capabilities carried as the message body of a SIP request. The media description is indifferent to the offer-answer model used by the application.

• Media negotiation
  Exchange of media description involving one party making an offer, another presenting an answer.

• MTLS
  Mutual Transport Layer Security. A standard protocol that is used to provide secure Web communications on the Internet or intranets. It enables clients to authenticate servers or, optionally, servers to authenticate clients. It also provides a secure channel by encrypting communications. See "TLS" later in this topic.

• Page-mode messaging
  Page mode messaging consists of sending SIP requests (INFO, Message, SERVICE) outside a SIP dialog from a real-time endpoint implementation. For example, you can use it to send Alerts or Notifications to custom clients built on top of Unified Communications Managed API version 1.0.

• Publication
  Designates the action of publishing data into a Microsoft Office Communications Server 2007 SQL data store. In the Unified Communications infrastructure, a publication is done by using a SERVICE request.

• Realtime endpoint
  Designates a Unified Communications Managed API version 1.0 class that represents an identifiable endpoint. Each such endpoint is uniquely identified by a URI and an endpoint ID, a GRUU URI, or a SIP instance. A real-time endpoint can be a SipEndpoint or a SipPeerToPeerEndpoint.

• SDP
  Session Description Protocol, an Internet standard (RFC 2327).

• SignalingSession
  SignalingSession designates a Unified Communications Managed API version 1.0 class that represents a long-lived SIP session (based on RFC 3261) initiated by an INVITE method. A SignalingSession is considered outbound if the initial INVITE originates locally, and inbound if the initial INVITE is consumed.

• SIP
  Session Initiation Protocol, an Internet standard (RFC 3261).

• SIP proxy server
  A SIP server that can receive SIP requests and forward them to the intended recipient.

• Subscription
  See "subscription session" later in this topic.

• Subscription session
  A long-lived session used to receive notifications such as for Presence when a target presentity publishes data updates.

• TLS
  Transport Layer Security. A standard protocol that is used to provide secure Web communications on the Internet or intranets. It enables clients to authenticate servers or, optionally, servers to authenticate clients. It also provides a secure channel by encrypting communications. See "MTLS" earlier in this topic.

See Also

Concepts

Unified Communications Managed API version 1.0 Architecture
Unified Communications Managed API version 1.0 Object Model
Unified Communications Managed API version 1.0 Application Scenarios
Development Guide for Unified Communications Managed API version 1.0