| Previous | Next |
| RTC_E_STATUS_NOT_ACCEPTABLE_HERE | RTC_E_STATUS_SERVER_NOT_IMPLEMENTED |
RTC_E_STATUS_SERVER_INTERNAL_ERROR
The Real-time Communications (RTC) Client API is a set of COM interfaces and methods designed to create PC-PC, PC-phone, phone-phone audio/video calls, or text-only Instant Messaging (IM) sessions over the Internet. Application sharing and whiteboard can also be added to PC-PC sessions. Presence information is used to track the location of buddies (or contacts) for communication purposes. This information is available through the RTC Client API on a SIP registrar server.
The RTC Client API:
- Supports multiparty phone-phone calls
- Uses SIP-based signaling and presence communications
- Integrates with the Microsoft® Office RTC proxy and registrar server
- Supports provisioning with ITSPs or third-party corporate-deployed servers
- Integrates signals over IP and PSTN networks
RTC Client API Version 1.2
A number of fundamental additions to the RTC core API have been added to support roaming and logical grouping functionality, as well as user search behaviors. These additions and changes will be denoted specifically.
RTC Client API Version 1.3
Enhanced MPOP support, additional client security options, marshalling support, and support for new Microsoft® Office Live Communications Server features have been added.
What's New in RTC
RTC Version 1.0 delivered basic SIP-based real-time communications functionality for the development of content-streaming client applications.
RTC Version 1.01 provides extensions for the application to provide IP port and address mappings for clients situated behind a Network Address Translator (NAT).
RTC Version 1.2 offers the following functional additions on top of the 1.0 specification:
- Improved multiple service connection support.
- SIP-based user search behaviors.
- Support for logical buddy groupings.
- Support for contact roaming behavior. Roaming functionality is a SIP extension, and not a component of standard SIP services.
- Support for event handling of the SIP INFO request.
- Support for custom presence properties.
- Support for ACL-based contact access.