RTCIF_

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

Windows Mobile Not SupportedWindows Embedded CE Supported

8/28/2008

These constants are initialization flags for RTC clients. The following table shows the initialization flags.

Value Description

RTCIF_DISABLE_MEDIA = 0x00000001

Media streams are disabled upon initialization.

RTCIF_DISABLE_STRICT_DNS = 0x00000008

The RTC Client API will not use the strict DNS name format to locate the server in the IRTCClientProvisioning::GetProfile method. For example, if the user's URI is someone@example.com and the transport is TLS, the DNS SRV lookup must return sip.example.com. This is the default behavior. This behavior is disabled by passing the RTCIF_DISABLE_STRICT_DNS flag when initializing the client with the IRTCClient2::InitializeEx method. When this flag is used, the server allows the someone.example.com format of the FQDN.

RTCIF_DISABLE_UPNP = 0x00000002

UPnP streams are disabled upon initialization.

RTCIF_ENABLE_SERVER_CLASS = 0x00000004

This flag disables the following functionality:

  • The Internet Connection Firewall (ICF) is disabled for SIP traffic.
  • Requests to refresh the presence status of the buddy with the IRTCBuddy2::Refresh method will not be throttled. By default, the RTC Client API throttles these requests to the server.
  • The RTC Client API will not attempt to reconnect sessions that are disconnected due to a change in the IP address on the client machine. By default, the RTC Client API will attempt to reconnect any existing SIP session when the IP address of the client machine changes. The IP address of the client machine can change when a wireless connection is interrupted, a network connection is disconnected, or a network interface is switched on a machine that has multiple NICs.

RTCIF_ENABLE_SYMMETRIC_UDP_SIGNALING = 0x00000100

SIP traffic will be sent and received from the same port number for any given SIP dialog. This flag is required for RTC to communicate through certain NAT scenarios.

RTCIF_PREFER_STATIC_PORT_FOR_SYMMETRIC_UDP = 0x00000200

When choosing a symmetric port number with which to start a new SIP dialog, the RTC Client API will choose the static port (5060) over the dynamic listen port. This flag is required for RTC to communicate through certain NAT scenarios.

To enable symmetric UDP signaling this flag and RTCIF_ENABLE_SYMMETRIC_UDP_SIGNALING must be set.

RTCIF_SEND_SDP_IN_PROVISIONAL_RESPONSES = 0x00000400

When sending a provisional response, the RTC Client will include an SDP message. This is required to enable early media scenarios when the early media negotiation needs to be processed in SIP Provisional responses.

RTCIF_TRUST_NETWORK_ASSERTED_IDENTITY = 0x00001000

Applies to Windows Embedded CE 6.0 R2

Indicates that the SIP client should always use the value from P-Asserted-Identity instead of the value in the FROM header. If this flag is not set, the SIP client should use the P-Asserted-Identity value only if the message is signed by a trusted authority.

Requirements

Header rtccore.h
Windows Embedded CE Windows CE .NET 4.2 and later

See Also

Reference

RTC Client API Constants
IRTCClient2::InitializeEx
IRTCClientProvisioning::GetProfile