Share via


SIP Server Settings

The SIP server settings specify which servers are available. You can use multiple sets of server settings.

Parameters

  • Address
    The host name of the server. The port can also be specified in this address by using the format sip.microsoft.com:1234. This port will override the default port for sessions using this profile.

  • Protocol
    The transport that should be used to connect to the server. Possible values are TCP, UDP, and TLS.

    Note  It is possible for someone to intercept information by replacing the SIP server, which would result in forwarding SIP requests to erroneous servers. The application should therefore ensure that a means to authenticate the server is enabled. For the application to authenticate the server, the Kerberos authentication method should be enabled and the TLS transport type must be specified in the profile.

  • Auth
    The form of authentication that should be used. If authentication is Basic, the transport must be TLS for security reasons. For RTC Client API versions 1.0 and 1.01, the supported authentication methods are Basic and Digest. The NTLM and Kerberos authentication methods are supported under the RTC Client API version 1.2. The transport recommended for these methods is TCP because the packet sizes can be quite large.

    If the user/allowedauth tag is present in the profile, the auth tag is ignored. To specify the NTLM and Kerberos authentication methods, use the user/allowed auth tag.

    The Basic authentication method contains a security risk because the credentials can be viewed along the network path. This method is not recommended for use in RTC communications without careful consideration of the risk involved. For more information, see Authentication.

    Note  It is possible for someone to intercept information by replacing the SIP server, which would result in forwarding SIP requests to erroneous servers. The application should therefore ensure that a means to authenticate the server is enabled. For the application to authenticate the server, the Kerberos authentication method should be enabled and the TLS transport type must be specified in the profile.

  • Role
    The role of the server. The possible values are Proxy and Registrar.

  • Session
    The session types that a server can support. The available options are PC-PC, PC-phone, phone-phone, and IM. For each form of communication, the party (either first-party or third-party) must also be specified. A first-party call is initiated by the client and a third-party call is initiated by another computer.

    See Session Information and RTC_SESSION_TYPE for more information on session types and enumerations.

See Also

XML Schema