User Settings (Windows CE 5.0)
The following user settings are used for phone-to-phone sessions and define the information required by the third-party server. For more information about the XML schema that defines these settings, see RTC Client API XML Schema.
account
The user account ID with the third-party server or the Internet Telephony Service Provider (ITSP).allowedauth
The authentication methods allowed by the client application.The authentication types available are described in the RTCAU_ constants.
This value for this attribute should be a subset of the following authentication methods:
- Basic
- Digest
- NTLM
- Kerberos
- Logoncred
If the allowedauth attribute is the empty string (""), the RTC Client API will not respond to any authentication challenge from the SIP server.
If neither the allowedauth attribute nor the auth attribute of the <sipsrv> tag is present in the XML profile, the default value of this allowedauth attribute is "NTLM | Kerberos."
The application can choose to alter the default value of this attribute by calling the IRTCProfile2::AllowedAuth method.
Note The NTLM and Kerberos authentication methods are supported only under the TCP and TLS transport types.
name
The user's display name that the client application should use.password
A character string that the third-party server or ITSP uses to authenticate the user.The XML language reserves a set of characters that have special meaning in the language. If reserved characters are used in the password listed in the profile, the password fails.
For example, &, <, and > are reserved in XML and should not be used in the XML profile.
Security Note The password is temporarily cached in memory in clear text, which can pose a brief security risk.
realm
The protection space used in the Authorization header when making a SIP request. This is used by the ITSPs to outsource their services to another carrier.This attribute is required when authentication is enabled on the SIP server and the authentication used is Basic.
This attribute is not mandatory for Digest, NTLM, and Kerberos authentication methods.
If the attribute is not present in the XML profile and the application does not set a value for the realm using the IRTCProfile2::Realm method, the realm received from the SIP server in the first SIP 401 or 407 challenge response is used.
If the value of this attribute is set by the application and a 401 or 407 authentication challenge response contains a different realm value, the response is rejected.
uri
The user's SIP URI. The uri attribute of the <user> tag in the XML profile document must be prefixed with sip:.
See Also
RTC Client API XML Schema | IRTCProfile2::AllowedAuth | IRTCProfile2::Realm | Client Settings | Provider Settings | Provision Settings | Session Settings | SIP Server Settings
Send Feedback on this topic to the authors