SIP Server Settings

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

• Windows Embedded CE 6.0 R3

8/28/2008

The following SIP server settings specify which servers are available.

You can specify multiple sets of server settings.

For more information about the XML schema that defines these settings, see RTC Client API XML Schema.

• addr
  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 overrides the default port for sessions using this 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 version 1.0, 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 large.

  If the allowedauth attribute of the <user> tag is present in the profile, the auth attribute is ignored.

  To specify the NTLM and Kerberos authentication methods, use the allowedauth attribute of the <user> tag.

  Security Note:

  The Basic authentication method contains a security risk because the credentials can be viewed in the network path. This method is not recommended for use in RTC communications without careful consideration of the risk involved. Someone could intercept information by replacing the SIP server. This would result in forwarding SIP requests to erroneous servers. Therefore, the application should 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.

• protocol
  The transport that should be used to connect to the server.

  Possible values are TCP, UDP, and TLS.

  Security Note:
  Someone could intercept information by replacing the SIP server. This 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.

  Available options are PC-PC, and IM (text messaging).

  For each form of communication, first-party or third-party must also be specified.

  A first-party call is initiated by the client; a third-party call is initiated by another computer.

  For more information about session types, see Session Information and RTC_SESSION_TYPE.

See Also

Reference

RTC Client API XML Schema

Concepts

Client Settings
Provider Settings
Provision Settings
Session Settings