Objects and Interfaces
The Communications Service relies on the RTC API, which offers a set of COM interfaces and methods that can be used in custom applications.
The following list describes the general characteristics of the RTC API.
- Uses SIP-based signaling and presence communications.
- Integrates with the Microsoft .NET SIP proxy and registrar server.
- Supports provisioning with ITSPs or third-party corporate-deployed servers.
- Integrates signals over TCP/IP and PSTN networks.
The following table shows the primary RTC communication objects and their interface definitions.
| Object | Interface | Description |
|---|---|---|
| Client | IRTCClient | Sets the session types and parameters. |
| Session | IRTCSession | Supports all session types and represents the entity that creates or receives audio calls or IM sessions. |
| Participant | IRTCParticipant | Retrieves a participant's name, URI, and state. |
| Buddy | IRTCBuddy | Handles buddy information for the presence feature. |
| Watcher | IRTCWatcher | Handles watcher information for the presence feature. |
| Profile | IRTCProfile | Retrieves profile information. |
The following illustration shows how these objects are created.
.gif)
Last updated on Saturday, April 10, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.