Windows Embedded CE-SIP client, Windows Embedded CE-phone, or Messaging Sessions
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
This sample profile shows how to provision a client for Windows Embedded CE-SIP client, Windows Embedded CE-phone, and messaging sessions.
The profile contains user information, such as account, password, and URI.
The access control element defines the domain for which the user is provisioned.
The SIP proxy address, transport protocol, and authorization are listed in the sipsrv element.
<provision key="de500844-e074-47fd-9e53-a51d63e5f51d"
name="Amun">
<user account="1234567"
password="notfornow"
uri="someone@example.com" />
<accesscontrol domain="myserver.microsoft.com"
sig="unique signature provided by Microsoft" />
<sipsrv addr="amun1.myserver.microsoft.com"
protocol="UDP"
auth="digest"
role="proxy">
<session party="first" type="pc2pc" />
<session party="first" type="im" />
</sipsrv>
<sipsrv addr="amun1.myserver.microsoft.com"
protocol="UDP"
auth="digest"
role="registrar" />
</provision>