Share via

RTCIF_ Constants

  • Article

The RTCIF_ constants are initialization flags for RTC clients.

  • RTCIF_DISABLE_MEDIA
    0x00000001
    Media streams are disabled upon initialization.

    **RTC 1.0 and 1.01:  **This constant is not supported.

  • RTCIF_DISABLE_UPNP
    0x00000002
    UPNP is disabled upon initialization.

    **RTC 1.0 and 1.01:  **This constant is not supported.

  • RTCIF_ENABLE_SERVER_CLASS
    0x00000004
    This flag does the following:

    • 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.

    **RTC 1.0 and 1.01:  **This constant is not supported.

  • RTCIF_DISABLE_STRICT_DNS
    0x00000002
    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.

    **RTC 1.0 and 1.01:  **This constant is not supported.

  • RTCIF_DISABLE_UNAUTH_WATCHERS_AND_ROAMING
    0x00000010
    The RTC Client API discards all unauthenticated watchers and does not subscribe to any roaming sessions.

    **RTC 1.0, 1.01, and 1.2:  **This constant is not supported.

  • RTCIF_DISABLE_UNAUTH_SESSIONS
    0x00000020
    The RTC Client API drops any unauthenticated INVITE, MESSAGE, and OPTION requests.

    **RTC 1.0, 1.01, and 1.2:  **This constant is not supported.

  • RTCIF_SUPPORT_FORKING
    0x00000040
    This flag specifies that the application can accept a forked session request. For more information about application requirements for forking, see Accepting a Forked Session Request.

    **RTC 1.0, 1.01, and 1.2:  **This constant is not supported.

Requirements

Redistributable: Requires Rtcdll.dll on Windows 2000, Windows XP, and Windows Server 2003.
Header: Declared in Rtccore.h.