Profile Requirements
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
Profiles manage RTC Client API settings. For more information about profiles, see Using XML Profiles, RTC Client API Provisioning, IRTCClientProvisioning, and IRTCProfile.
The following is a summary of the XML profile and ITSP requirements for each session type.
| Session type | Profile |
|---|---|
Windows Embedded CE-SIP client |
Specifies an outgoing proxy server or ITSP if one is used to set up the call. If the URI is an IP address or machine name, a profile is not required; a direct communication link is established. |
Windows Embedded CE-phone |
Required to locate the SIP proxy server and gateway. An ITSP or third-party server can be used to locate the gateway, or the gateway can be specified in the profile. |
Sessions that use service providers or third-party servers require XML profiles.
An Internet Telephony Service Provider (ITSP) or a third-party corporate-deployed server provides telephony services over the Internet. The service provider supplies the gateway to the PSTN network for a Windows Embedded CE-phone session or initiates a phone-phone call.
The force profile flag in the IRTCClient::CreateSession method specifies a profile for multiple service providers or messaging sessions with various profiles.
The third-party corporate-deployed server is stored in the profile under the SIP server element.
The ITSP is listed under the provider element.
Before these profiles are used, they must be enabled and registered on the server with the IRTCClientProvisioning::EnableProfile method.