This documentation is archived and is not being maintained.

Peer-to-Peer Sessions

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.

A peer-to-peer session supports exactly two Microsoft Office Communications Server clients. The two clients can be custom clients or a combination of custom client and Microsoft Office Communicator client. The topics in this section build on the topics found in the Performing Essential Session Tasks section. You should review that section before continuing on.

This section discusses the unique characteristics of each of the following session types.

  • UCC_SESSION_TYPE.UCCST_INSTANT_MESSAGING
  • UCC_SESSION_TYPE.UCCST_AUDIO_VIDEO
  • UCC_SESSION_TYPE.UCCST_CONFERENCE
  • UCC_SESSION_TYPE.UCCST_APPLICATION

The audio/video session discussion introduces the concept of the media channel. Media channels provides full support for streaming media. With Unified Communications Client API, the client can configure the media devices used in audio/video sessions. For information about configuring media devices, see Configuring Media Devices. For more information about the media channel, see Terminology.

Unified Communications API Client is designed to use a public switch telephone network (PSTN) telephone or UC-enabled telephone plus a webcam to provide input/output for audio and video data. When using a PSTN telephone, the application is actually making telephone calls through a private branch exchange (PBX). For more information, see Managing Telephone Calls.

The audio/video modality can be used with a peer-to-peer session such as one from a Microsoft Office Communicator client to custom client session, or a conference involving a mix of custom clients, an Office Communicator client, and Microsoft RoundTable sessions where multiple users share a single endpoint.

Show: