Call Class
Represents a basic call to handle an SDP offer/answer based invite session.
Inheritance Hierarchy
System..::..Object
Microsoft.Rtc.Collaboration..::..Call
Microsoft.Rtc.Collaboration.AudioVideo..::..AudioVideoCall
Microsoft.Rtc.Collaboration..::..InstantMessagingCall
Namespace: Microsoft.Rtc.Collaboration
Assembly: Microsoft.Rtc.Collaboration (in Microsoft.Rtc.Collaboration.dll)
Syntax
'Declaration
Public MustInherit Class Call
'Usage
Dim instance As Call
public abstract class Call
Remarks
The SDP offer/answer inside a MIME body is also supported by this call.
This is a base class for a call to handle specific media types. For example, InstantMessagingCall or AudioVideoCall are examples of specific calls that are designed to handle specific media types. However, there are operations and behaviors that are generally common among all these call types. The base call provides features and support for handling these common operations so that a derived class can leverage these features to implement specific scenarios. A "call" cannot exist by itself. A "call" always belongs to a "conversation". A conversation is either two party or conference based multi-party communication. A conversation can also be multi-modal (having calls supporting different media types). Since the context of the communication is implicit in the conversation, a call does not need to know the remote target address in general. If the conversation is hosted in an MCU which is already part of the conference, the conversation might have multiple remote participants and hence many calls. These calls are targeted towards different remote participants and hence the call must support targeting specific remote participants. When the application wants to terminate the media associated with a call, a call can expose the flow associated with the call when it is accepted or established. The media flow is the primary way to consume media associated with the call. If an application is not interested in terminating media locally or is not interested in using default media providers, it can create its own media provider to handle the specific media. This is considered to be an advanced usage scenario.
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.