Share via

2.2.2.1 In-band Provisioning Request

  • Article

The SUBSCRIBE request is constructed according to the procedures specified in [RFC3265] section 4.4.3. To request in-band provisioning information, the following additional rules SHOULD be followed.

  • The To-Uri of the request is set to the user's SIP address-of-record.

  • The From-Uri is the same as the To-Uri if the user does a self-request for provisioning<17>.

  • The From-Uri is the delegate’s URI if the request is done by a delegate on behalf of the delegator. If the From-Uri is a delegate’s URI, there MUST be a p-session-on-behalf-of header that equals the delegator’s URI. The To-Uri is set as a delegator’s URI. The authorization logic when delegation is used is described in [MS-SIPAE].<18>

  • When the request is made by a server entity that does not have a SIP address-of-record, the server MUST set the host portion of the To-Uri and the From-Uri to its own fully qualified domain name (FQDN) and MUST NOT include the user portion for both. The server entity initiating this request SHOULD be trusted to send this request via some out-of-band mechanism.<19>

  • The Event header is set to "vnd-microsoft-provisioning-v2" to identify this as an in-band provisioning request.

  • The Accept header is set to"application/vnd-microsoft-roaming-provisioning-v2+xml". Implementations SHOULD reject a request with a 406 response if the Accept header is not set to this value.

  • The Content-Type header is set to "application/vnd-microsoft-roaming-provisioning-v2+xml".

  • An Expires header is added with a value of "0" because this subscription does not establish a dialog.

  • No Require headers are present in the request.

  • Optional Supported headers MAY be present in the request, as specified in [MS-SIP] section 3.1.4.2 and [MS-PRES] section 2.2.2.4.1 for SUBSCRIBE requests.

  • The body is a valid application/vnd-microsoft-roaming-provisioning-v2+xml document.

For a detailed request example, see section 4.2.1.