Share via


IRTCSessionDescriptionManager::EvaluateSessionDescription

Other versions of this page are also available for the following:

Windows Mobile Not SupportedWindows Embedded CE Supported

8/28/2008

This method evaluates the session description for the supplied content type and body of a SIP INVITE request. The application decides to accept or reject the request. This method can be called on any incoming session.

Syntax

HRESULT EvaluateSessionDescription(
  BSTR bstrContentType,
  BSTR bstrSessionDescription,
  VARIANT_BOOL* pfApplicationSession
);

Parameters

  • bstrContentType
    [in] The content type for the response to the INVITE request. The content type is application-specific. Applications should ensure that the called party is able to decipher the content type of the session description.
  • bstrSessionDescription
    [in] The session description for the response to the INVITE request.
  • pfApplicationSession
    [in, out] Pointer to VARIANT_TRUE if the application decides to accept the INVITE request, and VARIANT_FALSE otherwise.

Return Value

This method can return an RTC_E_ constant.

The following table shows an additional possible return value.

Value Meaning

E_INVALIDARG

The pfApplicationSession parameter is not a valid pointer, or the bstrContentType or bstrSessionDescription parameter is not valid.

Remarks

This method is required when the Client object has been initialized using the IRTCClient::Initialize or IRTCClient2::InitializeEx method without specifying the RTCIF_DISABLE_MEDIA flag.

This method allows the application to handle negotiations for a session. The application can choose to handle session negotiations for several reasons, for example, when the application wants to include media stacks that are not supported by the RTC Client API.

The method is a callback. The application is strongly recommended to return from this method immediately and not run a windows message pump when the method is called.

The content type is application-specific. Applications should ensure that the called party is able to decipher the content type of the session description.

Requirements

Header rtccore.h, rtccore.idl
Library uuid.lib
Windows Embedded CE Windows CE .NET 4.2 and later

See Also

Reference

IRTCSessionDescriptionManager
IRTCClient::Initialize
IRTCClient2::InitializeEx