RTC Extensibility API Interfaces
11/30/2006
The following table shows the RTC Extensibility API interfaces with a description of the purpose of each.
| Programming element | Description |
|---|---|
This interface adds privacy support for all SIP traffic for an IRTCClient. It implements a subset of RFC 3323, RFC 3324, and 3325. |
|
This interface enables applications to create new subscriptions. Applications can access this interface by calling QueryInterface on an IRTCClient object. This interface is intended for C and C++ applications. |
|
This interface adds privacy support for all SIP traffic for an IRTCSession. It implements a subset of RFC 3323, RFC 3324, and 3325. Settings for the session object will override any settings for the parent IRTCClient object. |
|
This interface represents the RTC Subscription object, which represents a SIP SUBSCRIBE dialog. It can be queried for state and can resubscribe/unsubscribe from a service. |
|
This interface represents the RTC Subscription Notification Event object. This object is sent after receiving an incoming SIP NOTIFY message, which corresponds to a custom subscription (IRTCSubscription). |
|
This interface represents the RTC Subscription State Change Event object. This object is a notification event concerning the status of a SUBSCRIBE transaction. It is completely analogous to IRTCSessionStateChangeEvent. |