Session Initiation Protocol (SIP) Registration Extensions

[MS-SIPREGE]: Session Initiation Protocol (SIP) Registration Extensions

Intellectual Property Rights Notice for Open Specifications Documentation § Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. § Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. § No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

§ Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. § Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks. § Fictitious Names. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.

1 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it.

2 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Revision Summary Revision Revision Date History Class Comments

4/4/2008 0.1 Initial version

4/25/2008 0.2 Revised and edited technical content

6/27/2008 1.0 Revised and edited technical content

8/15/2008 1.01 Revised and edited technical content

12/12/2008 2.0 Revised and edited technical content

2/13/2009 2.01 Revised and edited technical content

3/13/2009 2.02 Revised and edited technical content

7/13/2009 2.03 Major Revised and edited the technical content

8/28/2009 2.04 Editorial Revised and edited the technical content

11/6/2009 2.05 Minor Revised and edited the technical content

2/19/2010 2.06 Editorial Revised and edited the technical content

3/31/2010 2.07 Major Updated and revised the technical content

4/30/2010 2.08 Editorial Revised and edited the technical content

6/7/2010 2.09 Minor Updated the technical content

6/29/2010 2.10 Editorial Changed language and formatting in the technical content.

7/23/2010 2.10 No Change No changes to the meaning, language, or formatting of the technical content.

9/27/2010 3.0 Major Significantly changed the technical content.

11/15/2010 3.0 No Change No changes to the meaning, language, or formatting of the technical content.

12/17/2010 3.0 No Change No changes to the meaning, language, or formatting of the technical content.

3/18/2011 3.1 Minor Clarified the meaning of the technical content.

6/10/2011 3.1 No Change No changes to the meaning, language, or formatting of the technical content.

1/20/2012 4.0 Major Significantly changed the technical content.

4/11/2012 4.0 No Change No changes to the meaning, language, or formatting of the technical content.

7/16/2012 4.0 No Change No changes to the meaning, language, or formatting of the technical content.

10/8/2012 5.0 Major Significantly changed the technical content.

2/11/2013 5.1 Minor Clarified the meaning of the technical content.

7/30/2013 5.2 Minor Clarified the meaning of the technical content.

11/18/2013 5.2 No Change No changes to the meaning, language, or formatting of the technical content.

2/10/2014 5.2 No Change No changes to the meaning, language, or formatting of the technical content.

4/30/2014 5.3 Minor Clarified the meaning of the technical content.

7/31/2014 6.0 Major Significantly changed the technical content.

10/30/2014 6.1 Minor Clarified the meaning of the technical content.

9/4/2015 7.0 Major Significantly changed the technical content.

4 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Introduction The Session Initiation Protocol (SIP) Registration Extensions protocol specifies proprietary extensions to Session Initiation Protocol (SIP) registration procedures. It also defines a provisioning protocol to enable SIP clients to obtain server provisioning data from SIP servers compliant to this specification. It is expected that the provisioning protocol sequence is performed during the client bootstrap process and that the data obtained is used for subsequent protocol operations attempted on the network. Sections 1.8, 2, and 3 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in [RFC2119]. Sections 1.5 and 1.9 are also normative but do not contain those terms. All other sections and examples in this specification are informative.

Glossary The following terms are specific to this document: 200 OK: A response to indicate that the request has succeeded. 403 Forbidden: A response that indicates that a protocol server understood but denies a request. access control list (ACL): A list of access control entries (ACEs) that collectively describe the security rules for authorizing access to some resource; for example, an object or set of objects. address book: A collection of Address Book objects, each of which are contained in any number of address lists. address book file: A file that contains a set of address book contact records. address-of-record: A Session Initiation Protocol (SIP) URI that specifies a domain with a location service that can map the URI to another URI for a user, as described in [RFC3261]. Augmented Backus-Naur Form (ABNF): A modified version of Backus- Naur Form (BNF), commonly used by Internet specifications. ABNF notation balances compactness and simplicity with reasonable representational power. ABNF differs from standard BNF in its definitions and uses of naming rules, repetition, alternatives, order-independence, and value ranges. For more information, see [RFC5234]. authentication: The act of proving an identity to a server while providing key material that binds the identity to subsequent communications. base URL: A URL that is specified for a web resource to convert all relative URLs in that resource to absolute URLs. A base URL ends with either a file name, such as http://www.example.com/sample.htm, or a slash, such as http://www.example.com/subdir/. See also absolute URL. bot: A structured HTML comment that is processed by a front-end web server when the containing document is opened by or saved to the server. Also referred to as web bot.

5 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Common Intermediate Format (CIF): A picture format, described in the H.263 standard, that is used to specify the horizontal and vertical resolutions of pixels in YCbCr sequences in video signals. Content-Type header: A message header field whose value describes the type of data that is in the body of the message. delegate: A user or resource that has permissions to act on behalf of another user or resource. delegator: A user or resource for which another user or resource has permission to act on its behalf. dialog: A peer-to-peer Session Initiation Protocol (SIP) relationship that exists between two user agents and persists for a period of time. A dialog is established by SIP messages, such as a 2xx response to an INVITE request, and is identified by a call identifier, a local tag, and a remote tag. endpoint: A device that is connected to a computer network. endpoint identifier (EPID): A unique identifier of a Session Initiation Protocol (SIP) endpoint. It is formed by combining the value of an epid parameter in a From or To header field with the address-of-record in the corresponding header field. Focus Factory: A component that is responsible for creating, managing, and deleting conferences. fully qualified domain name (FQDN): An unambiguous domain name (2) that gives an absolute location in the Domain Name System's (DNS) hierarchy tree, as defined in [RFC1035] section 3.1 and [RFC2181] section 11. Globally Routable User Agent URI (GRUU): A URI that identifies a user agent and is globally routable. A URI possesses a GRUU property if it is useable by any user agent client (UAC) that is connected to the Internet, routable to a specific user agent instance, and long-lived. header field: A component of a Session Initiation Protocol (SIP) message header, as described in [RFC3261]. Hypertext Transfer Protocol (HTTP): An application-level protocol for distributed, collaborative, hypermedia information systems (text, graphic images, sound, video, and other multimedia files) on the World Wide Web. Hypertext Transfer Protocol Secure (HTTPS): An extension of HTTP that securely encrypts and decrypts web page requests. In some older protocols, “Hypertext Transfer Protocol over Secure Sockets Layer” is still used (Secure Sockets Layer has been deprecated). For more information, see [SSL3] and [RFC5246]. in-band provisioning: A process in which a protocol client obtains configuration information from a protocol server. Internet Protocol version 4 (IPv4): An Internet protocol that has 32-bit source and destination addresses. IPv4 is the predecessor of IPv6. Internet Protocol version 6 (IPv6): A revised version of the Internet Protocol (IP) designed to address growth on the Internet. Improvements

6 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 include a 128-bit IP address size, expanded routing capabilities, and support for authentication and privacy. Kerberos: An authentication system that enables two parties to exchange private information across an otherwise open network by assigning a unique key (called a ticket) to each user that logs on to the network and then embedding these tickets into messages sent by the users. For more information, see [MS-KILE]. location profile: A definition of an environment where local numbers can be resolved to identifiers that either route to unique enterprise users or form unique numbers in a public telephone network, as defined by the International Telecommunications Union (ITU) recommendation. meeting console: The abbreviated name for the Microsoft Office Communications Live Meeting Console software. Messaging Application Programming Interface (MAPI): A messaging architecture that enables multiple applications to interact with multiple messaging systems across a variety of hardware platforms. ms-diagnostics header: A header that is added to a Session Initiation Protocol (SIP) response, BYE request, or CANCEL request to convey troubleshooting information. ms-diagnostics-public header: A header that is added to a Session Initiation Protocol (SIP) response, BYE request, or CANCEL request to convey troubleshooting information. Unlike the ms-diagnostics header, the ms-diagnostics-public header does not contain a "source" parameter. Multipurpose Internet Mail Extensions (MIME): A set of extensions that redefines and expands support for various types of content in email messages, as described in [RFC2045], [RFC2046], and [RFC2047]. NOTIFY: A method that is used to notify a Session Initiation Protocol (SIP) client that an event requested by an earlier SUBSCRIBE method has occurred. The notification optionally provides details about the event. NT LAN Manager (NTLM) Authentication Protocol: A protocol using a challenge-response mechanism for authentication in which clients are able to verify their identities without sending a password to the server. It consists of three messages, commonly referred to as Type 1 (negotiation), Type 2 (challenge) and Type 3 (authentication). For more information, see [MS-NLMP]. public IM connectivity: The ability of a protocol server deployment to interoperate with a public instant messaging (IM) provider. public switched telephone network (PSTN): Public switched telephone network is the voice-oriented public switched telephone network. It is circuit-switched, as opposed to the packet-switched networks. QoE Monitoring Server: A server that collects and processes Quality of Experience (QoE) metrics. Real-Time Transport Protocol (RTP): A network transport protocol that provides end-to-end transport functions that are suitable for applications

7 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 that transmit real-time data, such as audio and video, as described in [RFC3550]. REGISTER: A Session Initiation Protocol (SIP) method that is used by an SIP client to register the client address with an SIP server. security association (SA): A simplex "connection" that provides security services to the traffic carried by it. See [RFC4301] for more information. server: A replicating machine that sends replicated files to a partner (client). The term "server" refers to the machine acting in response to requests from partners that want to receive replicated files. Session Initiation Protocol (SIP): An application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. SIP is defined in [RFC3261]. Simple Mail Transfer Protocol (SMTP): A member of the TCP/IP suite of protocols that is used to transport Internet messages, as described in [RFC5321]. SIP message: The data that is exchanged between Session Initiation Protocol (SIP) elements as part of the protocol. An SIP message is either a request or a response. SIP protocol client: A network client that sends Session Initiation Protocol (SIP) requests and receives SIP responses. An SIP client does not necessarily interact directly with a human user. User agent clients (UACs) and proxies are SIP clients. SIP registrar: A Session Initiation Protocol (SIP) server that accepts REGISTER requests and places the information that it receives from those requests into the location service for the domain that it handles. SIP request: A Session Initiation Protocol (SIP) message that is sent from a user agent client (UAC) to a user agent server (UAS) to call a specific operation. SIP response: A Session Initiation Protocol (SIP) message that is sent from a user agent server (UAS) to a user agent client (UAC) to indicate the status of a request from the UAC to the UAS. site: A group of related pages and data within a SharePoint site collection. The structure and content of a site is based on a site definition. Also referred to as SharePoint site and web site. SUBSCRIBE: A Session Initiation Protocol (SIP) method that is used to request asynchronous notification of an event or a set of events at a later time. subscription: The result of a SUBSCRIBE request from a Session Initiation Protocol (SIP) element. survivable mode: A mode that enables a protocol client to access basic voice services if some server or network resources are unavailable. Transmission Control Protocol (TCP): A protocol used with the Internet Protocol (IP) to send data in the form of message units between computers over the Internet. TCP handles keeping track of the individual

8 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 units of data (called packets) that a message is divided into for efficient routing through the Internet. Transport Layer Security (TLS): A security protocol that supports confidentiality and integrity of messages in client and server applications communicating over open networks. TLS supports server and, optionally, client authentication by using X.509 certificates (as specified in [X509]). TLS is standardized in the IETF TLS working group. See [RFC4346]. Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986]. Uniform Resource Locator (URL): A string of characters in a standardized format that identifies a document or resource on the World Wide Web. The format is as specified in [RFC1738]. user agent: An HTTP user agent, as specified in [RFC2616]. user agent client (UAC): A logical entity that creates a new request, and then uses the client transaction state machinery to send it. The role of UAC lasts only for the duration of that transaction. In other words, if a piece of software initiates a request, it acts as a UAC for the duration of that transaction. If it receives a request later, it assumes the role of a user agent server (UAS) for the processing of that transaction. virtual directory: An HTTP URL that represents the root of a location where content can be published administratively. Voice over IP (VoIP): The use of the Internet Protocol (IP) for transmitting voice communications. VoIP delivers digitized audio in packet form and can be used to transmit over intranets, extranets, and the Internet. Windows Installer (.msi) file: A package file that contains the instructions and data required to install an application on a Windows- based computer. Every package contains at least one .msi file. The .msi file contains the installer database, a summary information stream, and possibly one or more transforms and internal source files. XML document: A document object that is well formed, as described in [XML], and might be valid. An XML document has a logical structure that is composed of declarations, elements, comments, character references, and processing instructions. It also has a physical structure that is composed of entities, starting with the root, or document, entity. XML schema definition (XSD): The World Wide Web Consortium (W3C) standard language that is used in defining XML schemas. Schemas are useful for enforcing structure and constraining the types of data that can be used validly within other XML documents. XML schema definition refers to the fully specified and currently recommended standard for use in authoring XML schemas.

9 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.

References Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata.

Normative References We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact [email protected]. We will assist you in finding the relevant information. [IETFDRAFT-OUGRUAUSIP-10] Rosenberg, J., "Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP)", draft-ietf-sip-gruu-10, July 2006, http://tools.ietf.org/id/draft-ietf-sip- gruu-10.txt

[MS-ABS] Microsoft Corporation, "Address Book File Structure".

[MS-AVEDGEA] Microsoft Corporation, "Audio Video Edge Authentication Protocol".

[MS-CONMGMT] Microsoft Corporation, "Connection Management Protocol".

[MS-DLX] Microsoft Corporation, "Distribution List Expansion Protocol".

[MS-E911WS] Microsoft Corporation, "Web Service for E911 Support Protocol".

[MS-OCER] Microsoft Corporation, "Client Error Reporting Protocol".

[MS-PRES] Microsoft Corporation, "Presence Protocol".

[MS-QoE] Microsoft Corporation, "Quality of Experience Monitoring Server Protocol".

[MS-RGSWS] Microsoft Corporation, "Response Group Service Web Service Protocol".

[MS-SIPAE] Microsoft Corporation, "Session Initiation Protocol (SIP) Authentication Extensions".

[MS-SIPRE] Microsoft Corporation, "Session Initiation Protocol (SIP) Routing Extensions".

[MS-SIP] Microsoft Corporation, "Session Initiation Protocol Extensions".

10 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, http://www.rfc- editor.org/rfc/rfc2119.txt

[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and Schooler, E., "SIP: Session Initiation Protocol", RFC 3261, June 2002, http://www.ietf.org/rfc/rfc3261.txt

[RFC3265] Roach, A. B., "Session Initiation Protocol (SIP)-Specific Event Notification", RFC 3265, June 2002, http://www.ietf.org/rfc/rfc3265.txt

[RFC950] Mogul, J., and Postel, J., "Internet Standard Subnetting Procedure", STD 5, RFC 950, August 1985, http://www.rfc-editor.org/rfc/rfc950.txt

Informative References [RFC5234] Crocker, D., Ed., and Overell, P., "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008, http://www.rfc- editor.org/rfc/rfc5234.txt

Overview This protocol is an extension of the original Session Initiation Protocol (SIP). This protocol defines registration extensions to the SIP protocol. These extensions are described in detail in section 3.1. This protocol also defines a protocol to retrieve provisioning and configuration information from a server compliant to this specification. This protocol is also referred to as in-band provisioning. These extensions are described in detail in section 3.3.

Relationship to Other Protocols This protocol depends on SIP. This protocol is invoked as an extension of SIP. This protocol depends on all of the protocols on which the SIP specification depends. In addition, this protocol depends on contacts and group subscription described in [MS-SIP] section 2.2.4, and self-subscription described in [MS- PRES] section 2.2.2.3.

Prerequisites/Preconditions This protocol assumes that both the SIP protocol clients and the server support SIP. The prerequisites for this protocol are the same as the prerequisites described in [MS-SIP] section 1.5.

This protocol is applicable when both the SIP protocol clients and the server support SIP and depend upon the use of one or more of the enhancements offered by SIP extensions.

Versioning and Capability Negotiation This protocol does not have protocol versioning. Instead, explicit capability negotiation is done as specified in this section by using the Supported header (section 2.2.1.5) to indicate support of various features. Using the Supported header is the standard SIP mechanism of doing capability negotiation.

Vendor-Extensible Fields None.

Standards Assignments None.

Transport A user agent client (UAC) that supports this protocol MUST use Session Initiation Protocol (SIP) over Transmission Control Protocol (TCP) or Transport Layer Security (TLS), as specified in [RFC3261], for Internet Protocol version 4 (IPv4)/ Internet Protocol version 6 (IPv6) <1> to exchange SIP messages with the SIP registrar.

Message Syntax This protocol relies on the SIP message format, as specified in [RFC3261] section 7. This protocol uses the REGISTER request and response, as specified in [RFC3261] section 10, for a UAC to register a binding. This protocol defines new option tags for the Supported header field and also adds new headers to be used with REGISTER requests and responses. This protocol defines a new Event header to be used with REGISTER requests and responses. This protocol also uses the NOTIFY request specified in [RFC3265] section 4.4.5 to remove the binding, or deregister, from the SIP registrar. This protocol defines a new token to be used as the event-type in the Event header field and a new Multipurpose Internet Mail Extensions (MIME) type in the Content-Type header field, as specified in [RFC3261] section 20.15, in the NOTIFY request. This protocol uses the SUBSCRIBE request and response specified in [RFC3265] section 4.4.3 to obtain in-band provisioning configuration information from the server.

Extensions to REGISTER Requests and Responses

SIP REGISTER Request Format The SIP REGISTER request is constructed using the rules specified in [RFC3261] section 10 and the following extensions. Zero or one Event header MAY be present in a REGISTER request. If an Event header is present, it MUST have the value "registration". This creates an implicit subscription for sending the registration state-change notifications specified in [RFC3265] section 7.2.1. The UAC SHOULD add the option tags defined in section 2.2.1.5 to the Supported header field in the REGISTER request. The UAC MAY add at most one ms-keep-alive header field, as specified in [MS-CONMGMT] section 2.2.1, in the REGISTER request. The constructed REGISTER request MUST also conform to the rules specified in Section 3.4 of [MS-SIPRE].

13 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 SIP REGISTER Response Format The SIP REGISTER response is constructed using the rules specified in [RFC3261] section 10 and the following extensions. The REGISTER 200 OK response MAY contain an ms-keep-alive header field, as specified in [MS-CONMGMT] section 2.2.1. The REGISTER 200 response constructed by the SIP registrar SHOULD contain either: § Zero ms-keep-alive header fields, as specified in [MS-CONMGMT] section 2.2.1. § One ms-keep-alive header field, as specified in [MS-CONMGMT] section 2.2.1. The registrar SHOULD add a presence-state header constructed using the rules specified in section 2.2.1.4. The registrar MUST add a Server header using the rules specified in section 2.2.1.9. The registrar MUST add a Contact header using the rules specified in [RFC3261] section 8.1.1.8.

ms-keep-alive Header Field Syntax The syntax and the use of the ms-keep-alive header are specified in [MS- CONMGMT] section 2.2.1.

Presence-State Header Field Syntax This protocol defines a new Presence-State header field. The Augmented Backus-Naur Form (ABNF), as defined in [RFC5234], syntax for the Presence-State header field<2> is as follows:

presence-state = "presence-State" HCOLON presence-state-value

presence-state-value = register-action[SEMI primary-cluster-state [SEMI user-services- state-unavailable] ]

primary-cluster-state = "primary-cluster-type" EQUAL primary-cluster-type-value SEMI cluster-connection-type-state

primary-cluster-type-value = ""central"" / ""remote""

cluster-connection-type-state = "is-connected-to-primary" EQUAL yes-no-value

yes-no-value = ""yes"" / ""no""

user-services-state-unavailable = "user-services-state=unavailable"

The ABNF syntax for the Presence-State header<3> field is as follows:

14 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 presence-state = "presence-State" HCOLON presence-state-value

presence-state-value = "register-action"

The SIP registrar MAY add at most one Presence-State header field in the 200 response to the REGISTER request.

Supported Header Field Extensions This protocol extends the Supported header field for the REGISTER request with the following new option tags. adhoclist: The UAC SHOULD add this option tag in the Supported header field in the REGISTER request if the UAC supports batched subscribe requests, as specified in [MS-SIP] section 3.3.4.1. com.microsoft.msrtc.presence: The UAC SHOULD add this option tag in the Supported header field in the REGISTER request if the UAC supports the Presence Protocol, as specified in [MS-SIP] section 3.2.4.1. msrtc-event-categories: The UAC SHOULD add this option tag in the Supported header field in the REGISTER request if the UAC supports the Presence Protocol, as specified in [MS-PRES] section 2.2.2.4.1. gruu-10: Used by the UAC for requesting the Globally Routable User Agent URI (GRUU) specified in [IETFDRAFT-OUGRUAUSIP-10] section 6. The UAC SHOULD add this option tag in the Supported header field in the REGISTER request. ms-forking: This tag is deprecated and SHOULD NOT be sent in requests. ms-userservices-state-notification: The UAC SHOULD<4> add this option tag in the Supported header field in the REGISTER request if the UAC supports survivable mode registration, which is registration without the availability of the service that handles the Presence Protocol specified in [MS- PRES] section 1. ms-cluster-failover: The UAC SHOULD<5> add this option tag to the Supported header field in the REGISTER request if the UAC supports serial processing of contact headers in decreasing q-value order, as specified in [RFC3261] section 10.2. The ABNF, as defined in [RFC5234], syntax listing specified in [RFC3261] section 25.1 is extended as follows:

Supported = ( "Supported" / "k" ) HCOLON ["adhoclist" / "com.microsoft.msrtc.presence" / "msrtc-event-categories" / "gruu-10" / "ms-userservices-state-notification" / "ms-cluster- failover" / option-tag *(COMMA option-tag)]

Ms-Subnet Header Field Syntax This protocol defines a new Ms-Subnet header field.<6> The ABNF, as defined in [RFC5234], syntax for the Ms-Subnet header field is as follows: Ms-Subnet = "ms-subnet" HCOLON ms-subnet-value

The ABNF for IPv4address is specified in [RFC3261] section 25.1. The UAC SHOULD add, at most, one Ms-Subnet header field in the REGISTER request to the SIP registrar.<7>

Ms-Device-Info Header Field Syntax This protocol defines a new Ms-Device-Info header field<8>. The ABNF syntax, as defined in [RFC5234], for the Ms-Device-Info header field is as follows:

Ms-Device-Info = "Ms-Device-Info" HCOLON ms-device-info-value

Ms-device-info-value = mac-info COMMA vendor-info COMMA version-info

mac-info = "MAC" EQUAL mac-addr

mac-addr = ^(([a-fA-F0-9]{2}-){5})([a-fA-F0-9]{2})$|^(([a-fA-F0-9]{2}-){7})([a-fA-F0-9]{2})$

vendor-info = "vendor" EQUAL pvalue

version-info = "version" EQUAL token

The ABNF for pvalue and token is specified in [RFC3261] section 25.1. The UAC SHOULD add, at most, one Ms-Device-Info header field in the REGISTER request to the SIP registrar.<9>

P-Preferred-Registrar Header Field Syntax This protocol defines a new P-Preferred-Registrar header field.<10> The ABNF syntax, as defined in [RFC5234], for the P-Preferred-Registrar header field is as follows:

p-preferred-registrar = "p-preferred-registrar" HCOLON preferred-registrar-value

preferred-registrar-value = addr-spec

The ABNF for addr-spec is specified in [RFC3261] section 25.1. The SIP registrar SHOULD add, at most, one P-Preferred-Registrar header field in the NOTIFY to the UAC.<11>

Extensions to Server Header The Server header is specified in [RFC3261] section 20.35. Implementations conformant with this specification SHOULD<12> set the value of the Server header to the literal string "RTC/4.0". The ABNF, as defined in [RFC5234], for the Server header specified in [RFC3261] section 25.1 is restricted as follows:

Server = "Server" HCOLON "RTC/4.0" / "RTC/3.5" / "RTC/3.0"

16 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Extensions to Contact Header Implementations SHOULD NOT use a wildcard Contact in REGISTER requests for modifying all registrar bindings. This is a deviation from what is specified in [RFC3261] section 8.1.1.8, which allows wildcard Contacts with Expires: 0 header to be used for removing all bindings.

Deregister NOTIFY Request Format The deregister NOTIFY request does not define a new event package, in the context of what is specified in [RFC3265], or a new subscription event package. Instead, the following Event and Content-Type headers are defined to identify the deregister NOTIFY, in the context of what is specified in [RFC3265] section 7.1.2 and section 7.2.1.

subscription-state Header The deregister NOTIFY MUST add exactly one subscription-state header field with terminated value and expires parameter value of zero.

Registration-Notify Event Header The SIP registrar MUST send the deregister NOTIFY request with exactly one Event header field with "registration-notify" as the event-type. This protocol defines this new event-type "registration-notify". This event type does not define a new event package, in the context of what is specified in [RFC3265] section 2. The presence of a subscription-state header field does not imply the use of any subscription event package. It is used in conjunction with the extensions defined in section 2.2.1.11.3 and section 2.2.1.11.4, primarily as the identifying features of a deregister NOTIFY.

Content-Type Header The SIP registrar MUST send the deregister NOTIFY request with text/registration-event as the MIME type in the Content-Type header field, as specified in [RFC3261] section 20.15.

Ms-Diagnostics-Public Header When generating this NOTIFY, the SIP registrar SHOULD add exactly one ms- diagnostics-public header, as specified in [MS-OCER] section 2.2.1.2. The ErrorId field values are given in section 2.2.1.13.

Survivable Mode NOTIFY Request Format The survivable mode NOTIFY request<13> does not define a new event package, as specified in [RFC3265], or a new subscription event package. Instead the following Event and Content-Type headers are defined to identify the survivable mode NOTIFY, as specified in [RFC3265] section 7.1.2 and section 7.2.1.

subscription-state Header

17 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 The survivable mode NOTIFY MUST add exactly one subscription-State header field with an active value and an expires parameter value of the time remaining on the registration.

Registration-Notify Event Header The SIP registrar MUST send the survivable mode NOTIFY request with exactly one Event header field with "registration-notify" as the event-type, as defined in section 2.2.1.11.2.

Content-Type Header The SIP registrar MUST send the survivable mode NOTIFY request with "text/registration-event" as the MIME in the Content-Type header field. For more information, see [RFC3265] section 20.15.

text/registration-event Message Body The message body MUST be set to one of the following values, depending on the event that triggered the NOTIFY. White spaces, both leading and trailing, SHOULD be ignored by the UAC. deregistered;event=unregistered: This is used by the SIP registrar if it unregisters an endpoint because of policy. For example, this is used when other endpoints of the same user have registered and the registrar decides to unregister the oldest endpoint. The ms- diagnostics-public ErrorId for this event is 4140. For more information, see [MS-OCER] section 7. deregistered;event=rejected: This is used by the registrar if the user is disabled for SIP communication. For example, this can happen if the administrator decides to lock the user's account. The ms-diagnostics-public ErrorId for this event is 4141. For more information, see [MS- OCER] section 7. deregistered;event=deactivated: This is used by the registrar to indicate that the service is temporarily unavailable for this user. For example, the user could be in the process of being moved from one server to another server by the administrator. The ms-diagnostics-public ErrorId for this event is 4142. For more information, see [MS- OCER] section 7. deregistered;event=userservices-unavailable<14>: This is used by the registrar if it unregisters or rejects an endpoint when the presence service for the user is unavailable and the endpoint does not support survivable mode registrations. The ms-diagnostics-public ErrorId for this event is 4165. For more information, see [MS- OCER] section 7. deregistered;event=preferred-registrar-change<15>: This is used by the registrar to indicate that the registrar for the endpoint has changed. The P-Preferred-Registrar header, as defined in section 2.2.1.8, specifies the new registrar for the endpoint (5). The ms-diagnostics-public ErrorId for this event is 4166 or 4167. For more information, see [MS-OCER] section 7.

18 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 registered;event=userservices-unavailable<16>: Used by the registrar to indicate that the UAC is in survivable mode. UACs SHOULD indicate support for survivable mode registration via the ms-userservices-state-notification Supported header described in section 2.2.1.5. The ms-diagnostics-public ErrorId for this event is 4165.

In-band Provisioning Messages A UAC requests the provisioning configuration that it is interested in by sending an in-band provisioning request. The server responds with the provisioning data for each of the groups listed in the request.

In-band Provisioning Request 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.

19 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 In-band Provisioning Response The 200 SUBSCRIBE response is used to send the in-band provisioning configuration body if the UAC indicates support for the ms-piggyback-first- notify extension, as specified in [MS-SIP] section 3.4.4.1. If the UAC does not indicate support for this extension, the in-band provisioning response is sent using a NOTIFY request. In either case, the 200 SUBSCRIBE or NOTIFY response SHOULD be constructed according to the procedures specified in [RFC3265] section 3.2.2, with the following extensions: § The Event header is set to "vnd-microsoft-provisioning-v2". § The Content-Type header is set to "application/vnd-microsoft-roaming- provisioning-v2+xml". § This subscription does not establish a dialog, so the Expires header is added with a value of zero. § The body is a valid application/vnd-microsoft-roaming-provisioning- v2+xml document, as described in section 2.2.2.4. A detailed response example is given in section 4.2.2.

Data Model for application/vnd-microsoft-roaming-provisioning-v2+xml Documents This is an XML document, and unless otherwise specified, all elements have a cardinality of 1 and are required.

Data Model for Requests

provisioningGroupList

|-- provisioningGroup

The following XML schema definition (XSD) <20> fragment defines the requirements to which a provisioningGroupList XML document SHOULD conform.

provisioningGroupList: A list of available provisioningGroup elements. provisioningGroup: A set of configuration data requested by the sending entity. The name attribute indicates the type of configuration data being requested. The following valid values are defined for the name attribute: § ServerConfiguration: Global Server Configuration and Provisioning Data. § meetingPolicy: Global Conferencing Policy Data, which is used for multi- party conferencing. § ucPolicy: Global Unified Communications Policy Data. § publicationGrammar: Grammar describing the publication of presence information, including presence containers and membership information based on rules defined by server administrators. § userSetting: User-specific configuration data. § endpointConfiguration: Client endpoint-specific configuration data. It controls the behavior of specific features of the client.<21> § locationPolicy: Location related configuration applied to users.<22> § mediaConfiguration: Media-related configuration data.<23> § presencePolicyV2: Presence-related configuration data.<24> § privacyPublicationGrammar: Privacy-related grammar describing presence containers and membership information based on rules defined by server administrators. <25> § publicProviders: Data on currently supported public providers.<26> The following XSD schema<27> fragment defines the requirements to which a provisioningGroupList XML document SHOULD conform.

Data Model for Responses

provisionGroupList

|-- provisionGroup

The XSD schema for a response provisionGroupList XML document is specified in section 2.2.2.4. provisionGroupList:A list of available provisionGroup elements. provisionGroup: A set of configuration data owned by a particular entity or service indicated by the name attribute. The following valid values are defined for the name attribute: § ServerConfiguration: Global Server Configuration and Provisioning Data. § meetingPolicy: Global Conferencing Policy Data, which is used for multi- party conferencing. § ucPolicy: Global Unified Communications Policy Data. § publicationGrammar: Grammar describing the publication of presence information, including presence containers and membership information based on rules defined by server administrators.<28> § userSetting: User-specific configuration data.<29>

22 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 § endpointConfiguration: Client endpoint-specific configuration data. It controls the behavior of specific features of the client.<30> § locationPolicy: Location-related configuration applied to users.<31> § mediaConfiguration: Media-related configuration data.<32> § presencePolicyV2: Presence-related configuration data.<33> § privacyPublicationGrammar: Privacy-specific grammar describing presence containers and membership information based on rules defined by server administrators.<34> § publicProviders: Data on currently supported public providers.<35> The provisionGroup lists an arbitrary sequence of elements applicable to that entity. The data model is given in the following sections for all the groups.

Data Model for ServerConfiguration provisionGroup Unless specified otherwise, all the properties are required and have a cardinality of 1.<36>

provisionGroup (name='ServerConfiguration')

|-- absWebServiceEnabled

|-- lisInternalUrl

|-- absInternalServerUrl

|-- absExternalServerUrl

|-- abwqInternalUrl

|-- abwqExternalUrl

|-- dlxInternalUrl

|-- dlxExternalUrl

|-- dlxEnabled

|-- updatesServerInternalUrl

|-- updatesServerExternalUrl

|-- updatesServerEnabled

|-- organization

|-- helpdeskInternalUrl

|-- helpdeskExternalUrl

|-- consoleDownloadInternalUrl

|-- consoleDownloadExternalUrl

|-- ucPortRangeEnabled

|-- ucMinMediaPort

|-- ucMinSipDynamicPort

|-- ucMaxSipDynamicPort

|-- ucMinAudioPort

|-- ucMaxAudioPort

|-- ucMinVideoPort

|-- ucMaxVideoPort

|-- ucMinAppSharingPort

|-- ucMaxAppSharingPort

|-- ucMinFileTransferPort

|-- ucMaxFileTransferPort

|-- ucPC2PCAVEncryption

|-- ucMaxVideoRateAllowed

|-- qosEnabled

|-- enableInCallQoS

|-- inCallQoSIntervalSeconds

|-- ucDiffServVoice

|-- ucVoice802_1p

|-- ucEnforcePinLock

|-- ucMinPinLength

|-- ucPhoneTimeOut

|-- ucExchangeMWIPoll

|-- ucEnableSIPSecurityMode

|-- ucEnableUserLogging

|-- loggingLevel

|-- enableBWPolicyCheck

|-- poolUri

|-- mrasUri

|-- qosUri

|-- callParkServerUri

|-- responseGroupServiceInternalURL

|-- responseGroupServiceInternalAgentURL

|-- responseGroupServiceExternalAgentURL

|-- botSipUriForTestCall

|-- cwaInternalUri

|-- cwaExternalUri

|-- ucLocationProfile

|-- focusFactoryUri

|-- voiceMailUri

This provision group example follows the behavior described in endnote <37>.

provisionGroup (name='ServerConfiguration')

|-- ucMaxVideoRateAllowed

|-- absInternalServerUrl

|-- absExternalServerUrl

|-- absWebServiceEnabled

|-- ucPC2PCAVEncryption

|-- organization

|-- consoleDownloadInternalUrl

|-- consoleDownloadExternalUrl

|-- helpdeskInternalUrl

|-- helpdeskExternalUrl

|-- dlxInternalUrl

|-- dlxExternalUrl

|-- dlxEnabled

|-- ucDiffServVoice

|-- ucVoice802_1p

|-- ucEnforcePinLock

|-- ucMinPinLength

|-- ucPhoneTimeOut

|-- ucEnableSIPSecurityMode

|-- ucEnableUserLogging

|-- updatesServerInternalUrl

|-- updatesServerExternalUrl

|-- updatesServerEnabled

|-- ucPortRangeEnabled

|-- ucMinMediaPort

|-- ucMaxMediaPort

|-- ucMinSipDynamicPort

|-- ucMaxSipDynamicPort

|-- qosEnabled

|-- enableInCallQoS

|-- inCallQoSIntervalSeconds

|-- ucLocationProfile

|-- mrasUri

|-- qosUri

|-- callControlServerUri

|-- poolUri

|-- cwaInternalUri

|-- cwaExternalUri

|-- focusFactoryUri

|-- voiceMailUri

The following XSD schema fragment defines the requirements to which a ServerConfiguration provisionGroup element XML document MUST conform.

ucMaxVideoRateAllowed: Maximum video rate that the UAC endpoints are to use. The maximum video rate MUST be one of the following defined values: § default: Maximum resolution of VGA-600K. § HD720P-1.5M: Maximum resolution of HD720P. High definition, with a resolution of 1280x720. § VGA-600K: Maximum resolution of VGA, 640x480, 25 fps. § CIF-250K<38>: Maximum resolution of Common Intermediate Format (CIF). CIF has a resolution of 352x288, 15 fps.

29 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 absInternalServerUrl: The URI where the Address Book Service can be reached within the enterprise. This SHOULD be a Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) URI pointing to the virtual directory in which the Address Book Service places the address book files, as specified in [MS-ABS] section 2.2. absExternalServerUrl: The URI where the Address Book Service can be reached through the public internet. This SHOULD be an HTTPS URI pointing to the virtual directory where the Address Book Service places the Address Book files, as specified in [MS-ABS] section 2.2. ucPC2PCAVEncryption: Specifies whether encryption is required for Computer to Computer Audio-Video Sessions. ucPC2PCAVEncryption MUST be one of the following defined values: § SupportEncryption: Encryption is optional. § RequireEncryption: Encryption is required. § DoNotSupportEncryption: Encryption is not required. organization: The name of the organization. consoleDownloadInternalUrl<39>: The URI from which the meeting console can be downloaded within the enterprise. This SHOULD be an HTTP URI. For example:

"http://r.office.fabrikam.com/r/rlidOCS?clid=1033&p1=livemeeting"

consoleDownloadExternalUrl<40>: The URI from which the meeting console can be downloaded through the public internet. This SHOULD be an HTTP URI. For example:

"http://r.office.fabrikam.com/r/rlidOCS?clid=1033&p1=livemeeting"

helpdeskInternalUrl<41>: The URI for the organization’s help desk within the enterprise. This SHOULD be an HTTP URI. helpdeskExternalUrl<42>: The URI for the organization’s help desk through the public internet. This SHOULD be an HTTP URI. dlxInternalUrl: The URI for the Group Expansion Web Service component within the enterprise. This SHOULD be an HTTPS URI pointing to the Group Expansion Web Service, as specified in [MS-DLX] section 2. dlxExternalUrl: The URI for the Group Expansion Web Service component through the public internet. This SHOULD be an HTTPS URI pointing to the Group Expansion Web Service, as specified in [MS-DLX] section 2. dlxEnabled: Indicates whether the Group Expansion Web Service is available. The value MUST be "true" or "false". ucDiffServVoice: Ignored. ucVoice802_1p: Ignored. ucEnforcePinLock: Ignored. ucMinPinLength: Ignored. ucPhoneTimeOut: Ignored.

30 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 ucEnableUserLogging:<43> Indicates whether logging needs to be enabled on the user computer to record client behavior. The value SHOULD be "true" or "false". ucExchangeMWIPoll: Ignored. ucEnableSIPSecurityMode: The security mode for the client. The value MUST be "High", "Medium", or "Low". updatesServerInternalUrl: Ignored. updatesServerExternalUrl: Ignored. updatesServerEnabled: Ignored. ucPortRangeEnabled:<44> Indicates whether the port ranges sent by the server need to be used by the client for media and signaling. The value SHOULD be "true" or "false". ucMinMediaPort:<45> The minimum of the range of dynamically-allocated ports that the client can use to transmit audio and video data using Real- Time Transport Protocol (RTP). ucMaxMediaPort:<46> The maximum of the range of dynamically- allocated ports that the client can use to transmit audio and video data using RTP. ucMinSipDynamicPort:<47> The minimum of the range of dynamically- allocated ports that the client can use to transmit signaling data using SIP. ucMaxSipDynamicPort:<48> The maximum of the range of dynamically- allocated ports that the client can use to transmit signaling data using SIP. qosEnabled:<49> Optional. Ignored. ucLocationProfile: The location profile for voice call features. This is used by the extensions described in [MS-SIPRE] section 2.2.8. mrasUri: The URI of the Media Relay Authentication Service (MRAS), as specified in [MS-AVEDGEA] section 2.2.3.1.2. This MUST be a SIP URI that can be used to address the MRAS Service. qosUri: The URI of the Media QoE Monitoring Server, as described in [MS-QoE] section 1.3. This MUST be a SIP URI that can be used to address the QoE Service. callControlServerUri:<50> Ignored. poolUri:<51> Ignored. cwaInternalUri:<52> The URI for the organization’s phone conferencing dial-in information page, accessible internally. This SHOULD be an HTTP(S) URI. cwaExternalUri:<53> The URI for the organization’s phone conferencing dial-in information page, accessible externally. This SHOULD be an HTTP(S) URI. focusFactoryUri: The User’s Conferencing Focus Factory. This is required for creating conferences. This MUST be a SIP URI. voiceMailUri: The user’s voice mail URI. This is required for sending messages to voice mail. This MUST be a SIP URI that can be used to route to the user’s voice mail. The syntax is described in [MS-SIPRE] section 2.2.3.

31 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 responseGroupServiceInternalURL:<54> The Uniform Resource Locator (URL) for the Response Group Service Web Service within the enterprise. This MUST be an HTTPS URL pointing to the Response Group Service Web Service, as specified in [MS-RGSWS]. responseGroupServiceExternalURL:<55> The URL for the Response Group Service Web Service through the public internet. This MUST be an HTTPS URL pointing to the Response Group Service Web Service, as specified in [MS-RGSWS]. responseGroupServiceInternalAgentURL:<56> The URL of a webpage containing information about the Response Group Service within the enterprise. This SHOULD be an HTTPS URL. responseGroupServiceExternalAgentURL:<57> The URL of a webpage containing information about the Response Group Service through the public internet. This SHOULD be an HTTPS URL. absWebServiceEnabled: Ignored. abwqExternalURL:<58> The Address Book Web Query URL. This is accessible through the public internet. This SHOULD be an HTTPS URI pointing to the Group Expansion Web Service, as specified in [MS-DLX] section 2. abwqInternalURL:<59> The Address Book Web Query URL. This is accessible inside the enterprise/intranet. This SHOULD be an HTTPS URI pointing to the Group Expansion Web Service, as specified in [MS-DLX] section 2. botSipUriForTestCall:<60> The SIP URI of the test bot that is available to the user for a test call. callParkServerUri:<61> The URI for the call park server that clients can connect to. enableBWPolicyCheck:<62> Boolean value that indicates whether the system is provisioned for bandwidth management. lisInternalUrl:<63> The URL of the Location Information Service, as specified in [MS-E911WS] section 3.1, which is accessible from inside the enterprise/intranet. loggingLevel:<64> The logging level on the client. ucMinAppSharingPort:<65> Minimum port used by Application Sharing. ucMaxAppSharingPort:<66> Maximum port used by Application Sharing. ucMinAudioPort:<67> Minimum port used by Audio. ucMaxAudioPort:<68> Maximum port used by Audio. ucMinFileTransferPort:<69> Minimum port used for File Transfer. ucMaxFileTransferPort:<70> Maximum port used for File Transfer. This is for P2P File Transfers only. ucMinVideoPort:<71> Minimum port used by Video. ucMaxVideoPort:<72> Maximum port used by Video.

32 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 requireFIPSCompliantMedia:<73> Boolean value that requires the client to be FIPS compliant in all audio video conversations if present, and has the value of "true". hybridConfigServiceInternalUrl:<74> The internal URL of a web service used to enable media bypass, E911, call park, and call center services for hybrid voice users. hybridConfigServiceExternalUrl:<75> The external URL of a web service used to enable media bypass, E911, call park, and call center services for hybrid voice users. enableInCallQos: <76> Whether the client will send in-call QoS metrics (value is set to "true"), or not ("false"). inCallQoSIntervalSeconds: <77> The number of seconds in the minimum time interval between sending one in-call QoS metric and sending the next. For a detailed example, see section 4.2.2.

Data Model for meetingPolicy provisionGroup

provisionGroup (name=’meetingPolicy’)

|-- instance

| |- property

| | |- name

The following XSD schema fragment defines the requirements a meetingPolicy provisionGroup element XML document MUST conform to.

instance: A single instance is specified within the meetingPolicy provisionGroup, listing a set of properties applicable for the user requesting the configuration. Property: A single policy setting. The name attribute specifies the property name. Values are Boolean, unless otherwise specified. AllowIPAudio: Specifies whether IP Audio functionality is enabled on the client. For example:

true

AllowIPVideo: Specifies whether IP Video functionality is enabled on the client. For example:

true

EnableDataCollaboration: Specifies whether Data Collaboration functionality is enabled on the client. For example:

true

Name:<78> Optional, ignored. ColorDepth:<79> Optional, ignored. AllowACP:<80> Optional, ignored. RetainPPTForExternalMeeting:<81> Retain PowerPoint slides for external meeting. MeetingSize:<82> Maximum number of attendees allowed in meetings.

34 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 AllowAppSharingForExternalMeeting:<83> Allow application sharing in external meetings. AllowPresenterToRecord:<84> Allow meeting presenter to record meeting. EnableAppDesktopSharing:<85> Specifies whether the client is allowed to share the desktop. For example:

true

EnablePSTNConferencing:<86> Enable conferencing audio call over a public switched telephone network (PSTN) network. TrustedConferencingPinRequired:<87> Require that trusted conferencing PIN be specified to join the conference. AllowAnnotations: Boolean value that allows participants to make annotations on top of PowerPoint content, as well as all whiteboarding content. AllowAnonymousParticipants: Boolean value that allows anonymous participants to join the meeting. AllowExternalUserControl: Boolean value that allows anonymous and federated users to control an application sharing session. AllowExternalUserRecording: Boolean value that allows external users to record meetings organized by this user. It works if AllowRecording is "true". AllowExternalUsersToSaveContent: Boolean value that allows anonymous and federated users to save content shared in a data sharing session. AllowFileTransfer: Boolean value that allows multi-party file transfer in a meeting. AllowParticipantControl: Boolean value that allows or prevents the user from sharing control with anyone when they are screen sharing. This applies regardless of who started/organized the conference. AllowRecording: Boolean value that allows recording on meetings organized by this user. If "true", the AllowExternalUserRecording policy applies to external users. EnableP2PFileTransfer: Enable P2P file transfer between two users during a meeting. MaxConferenceVideoResolution: Set the maximum resolution for video conferencing. Allowed values are "CIF" or "VGA". AllowedAppDesktopSharingLevel: Enables application and desktop sharing during web conferencing for users having this policy. AllowUserToScheduleMeetingsWithAppSharing: Enables users to schedule meetings with Application sharing. Allowed values are "None", "SingleApplication", or "Desktop". AppSharingBitRate: Set the bit rate for Application sharing. AudioBitRate: Set the bit rate for Audio. FileTransferBitRate: Set the bit rate for File Transfer.

35 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 RequirePasscode:<88> Controls whether a pass code is required to join dial-in conferences. VideoBitRate:<89> Set the bit rate for Video. AllowPolls:<90> Enables the polling feature within a meeting. The value MUST be "true" or "false". EnableP2PRecording:<91> Enables recording of P2P conversations. The value MUST be "true" or "false". EnableP2PVideo:<92> Enables P2P video conversations. The value MUST be "true" or "false". For a detailed example, see section 4.2.2. EnableMultiViewJoin:<93> Enables multiple video channels in conferencing. The value MUST be "true" or "false". For a detailed example, see section 4.2.2. TotalReceiveVideoBitRate:<94> Sets the total video bit rate to be used for conferencing video. For a detailed example, see section 4.2.2. DisablePowerPointAnnotations:<95> Specifies whether the user has turned off PowerPoint annotations. AllowSharedNotes:<96> Enables users to take shared notes during a meeting. The value MUST be "true" or "false". For a detailed example, see section 4.2.2. AllowQna:<97> Enables the Question and Answer feature within a meeting. The value MUST be "true" or "false". This setting applies to the user who organizes the conference: if set to "false", no conference created by a user affected by this policy will allow the use of the Questions and Answers Manager. However, that user can make use of the Questions and Answers Manager in other conferences where polls are allowed. The default value is"true". AllowOfficeContent:<98> Enables the Office content (such as slide presentations) sharing feature within a meeting. The value MUST be "true" or "false". When set to "false", prevents users from using Office content in their conferences. EnableOnlineMeetingPromptForLyncResources: <99> Enables online meeting prompting: if set to "true", users will be prompted any time they schedule a meeting that includes invitees (such as a meeting room) that would benefit from having the meeting held online. The default value is "false".

Data Model for ucPolicy provisionGroup

provisionGroup (name=’ucPolicy’)

|-- instance

| |- property

| | |- element

36 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 The following XSD schema fragment defines the requirements to which a ucPolicy provisionGroup element XML document MUST conform.

instance: A single instance is specified within the ucPolicy provisionGroup, listing a set of properties applicable for the user requesting the configuration. property: Lists a single policy setting. The name attribute specifies the property name. Values are Boolean, specified in CDATA notation, unless otherwise specified. Some properties list a sequence of element sub- elements. AllowSimultaneousRinging: Whether simultaneous ringing, as described in [MS-SIPRE] section 3.9.5.1.2, support is enabled. For example:

Name: Optional, ignored. PhoneRouteUsages:<100> Optional, ignored. AllowCallForwarding: Turns off call forwarding to a phone number or contact. The user only has the option to forward to voice mail. enableBWPolicyOverride:<101> Boolean value that enables the user endpoint to bypass the BandWidth (BW) policy check, and only report BW utilization for an established session. EnableCallPark: Boolean value that allows specified clients and devices to park calls. EnableCallTransfer: Boolean value that enables the call transfer user interface on client. EnableDelegation: Boolean value that enables all client user interface entry points for call delegation. EnableMaliciousCallTrace: Boolean value that enables the malicious call trace functionality. EnableTeamCall: Boolean value that enables all client user interface entry points for the team call-group. UcEnabled: <102> Ignored. VoiceDeploymentMode: <103> String value that indicates to the client the type of public switched telephone network (PSTN)connectivity they are provisioned for. The value MUST be one of the following § OnPrem § Online § OnlineBasic § OnPremOnlineHybrid A detailed example is given in section 4.2.2.

Data Model for publicationGrammar provisionGroup

provisionGroup (name='publicationGrammar')

|-- containerManifestList

| |- minSupportedClientVersion

|- majorVersion

|- minorVersion

| |-- containerManifest

| | |-- containers

|-- container

|-- visible

|-- avoidRedundantMembers

|-- blocked

|-- members

|-- member

|- type

|- role

|- uri

|-- allowedContainers

|- type

|-- container

|- id

|-- defaultContainer

|- id

|-- occurrenceConstraint

|- type

|-- sourceNetworks

|-- sourceNetwork

|- type

|-- resolutionRules

|-- resolutionRule

|- type

|- role

|-- blockRules

|-- blockRule

|- type

|-- containers

|-- container

|- id

|-- sourceNetworks

|-- sourceNetwork

|- type

|-- minAvailability

|-- maxAvailability

|-- rolePrecedence

|-- rolePrecedenceEntry

|- type

|-- categoryPublicationManifest

|- minSupportedClientVersion

|- majorVersion

|- minorVersion

|-- publicationList

|-- publicationRule

|- ruleType

|- categoryName

|- containerId

|- preferredSelfConsumption

|-- categoryData

|-- instanceId

|- type

|- value

|-- expireType

|- expireTime

The following XSD schema fragment defines the requirements to which a publicationGrammar provisionGroup element XML document SHOULD<104> conform.

targetNamespace="http://schemas.microsoft.com/2006/09/sip/provisiongrouplist- notification" elementFormDefault="qualified"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns:ms="urn:microsoft-cpp-xml-serializer">

41 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 The publicationGrammar provisionGroup element contains the containerManifestList and categoryPublicationManifest XML documents, as shown in the example in section 4.2.2. The following XSD schema fragment defines the requirements to which the containerManifestList XML document SHOULD<105> conform.

targetNamespace="http://schemas.microsoft.com/2008/09/sip/ContainerManifest"

xmlns:tns="http://schemas.microsoft.com/2008/09/sip/ContainerManifest"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns:ct="http://schemas.microsoft.com/2006/09/sip/commontypes"

attributeFormDefault="unqualified"

elementFormDefault="qualified">

schemaLocation="commontypes.xsd"/>

minOccurs="1" maxOccurs="1"/>

minOccurs="0" maxOccurs="1"/>

The following XSD schema fragment defines the requirements to which the categoryPublicationManifest XML document SHOULD<106> conform.

xmlns:tns="http://schemas.microsoft.com/2008/09/sip/categoryPublicationManifest"

targetNamespace="http://schemas.microsoft.com/2008/09/sip/categoryPublicationManifest"

elementFormDefault="qualified" attributeFormDefault="unqualified">

List the possible value of instanceId type attribute

List the the possible value to define for categoryData

List the possible values of expiryTypeValues

If expiryType is defined as Time, expiryTime must be defined

expiryTime is only meaningful for expiryType Time

The following XSD schema fragment defines the schema for commontypes referred by the containerManifestList XSD schema.

targetNamespace="http://schemas.microsoft.com/2006/09/sip/commontypes"

xmlns:tns="http://schemas.microsoft.com/2006/09/sip/commontypes"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

elementFormDefault="qualified"

attributeFormDefault="unqualified"

maxOccurs="unbounded" namespace="##other"/>

The following XSD schema fragment defines the schema for commontypesForNewPublicationManifest referred by the categoryPublicationManifest XSD schema.

xmlns:ms="urn:microsoft-cpp-xml-serializer"

targetNamespace="http://schemas.microsoft.com/2006/09/sip/commontypes"

xmlns:tns="http://schemas.microsoft.com/2006/09/sip/commontypes"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

elementFormDefault="qualified"

attributeFormDefault="unqualified"

maxOccurs="unbounded" namespace="##other"/>

containerManifestList: A list of all containerManifests available. containerManifest: Manifest that provides the list of containers and members. The UAC SHOULD create containers and its members based on the constraints defined in the manifest. majorVersion (optional): Ignored. minorVersion (optional): Ignored. minSupportedClientVersion (optional): The minimum version of the UAC that consumes the container manifest. containers: The wrapper for the list of container elements. container: Each container element describes a container. § id (required): Unsigned short integer that uniquely identifies a container. § Visible (optional):<107> Container attribute that, when "true", designates the container as a member of the set of containers identified with allowed containers type set to "visibleContainers". UAC also interprets containers that set the Visible attribute to "true" as containers that are displayed in its access level view. § avoidRedundantMembers (optional): This string indicates if a container can have redundant membership. For example, redundancy occurs when a domain, as well as a user who is in that domain, are associated with a container. The value MUST be "true" or "false". The UAC SHOULD clean up redundant members from containers if the setting is "true". § blocked (optional): Ignored. members: The wrapper for the list of member elements. member: Describes a container member. type (optional): This string value specifies the type of the member. The following values are defined: § user: A SIP URI. § domain: A SIP domain. § sameEnterprise: All users from the same enterprise.

63 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 § federated: All federated users. § publicCloud: All public cloud users. § everyone: All users. § singleIdentityUser: A user who has just one SIP uri for that particular identity. PIC contacts that have more than one SIP uri that belong to the identity should not be processed using this rule. role (optional): This string value specifies the role of the member. Note that container members matching to a member by role attribute take precedence over the corresponding match to member by type attribute. The following values are defined: § delegate: A user entity currently configured as a delegate for the local user. § buddy:<108> A user entity currently a member of the local user’s buddy list. allowedContainers: List of containers to which the member MAY be added. § type (required): The type attribute is a string that describes the access control element. The following values are defined: § custom: The list of containers is specified within the allowedContainers element. visibleContainers:<109> The list of containers for the member are the subset of child elements of the containers element with the Visible attribute set to "true". § container (optional): This element specifies the container to which the member MAY be added. There MAY be more than one element. The list of containers is specified when the type is "custom". § id (required): This unsigned short integer uniquely identifies a container. § defaultContainer (optional): The default container to which the member MAY be added if the constraint is not satisfied for the member. § id (required): An unsigned integer that gives the container identifier. occurrenceConstraint (optional): The mandatory membership occurrence rate the related type or role member is present in. § type (required): A string that gives the number of occurrences mandated for the given type or role. The value MUST be "zero", "one" or "zeroOrOne". § When "Zero", a given container MUST have zero members of the related type or role. This value SHOULD be ignored by a UAC. § When "One", a given container MUST have one member of the related type or role. § When "zeroOrOne", a given container MAY have no members of the related type or role or it MAY have one member of a related type or role. It MUST NOT have more than one member of a related type or role. sourceNetworks (optional): A wrapper for the optional list of source networks to which the member belongs to satisfy the constraint. sourceNetwork: Describes a source network.

64 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 § type (required): A string that describes the source network. The following values are defined: § sameEnterprise: All users from the same enterprise. § federated: All federated users. § publicCloud: All public cloud users. resolutionRules (optional): A wrapper for the optional list of resolution rules that are applied if the constraint is not satisfied for the member. resolutionRule: Describes a resolution rule. § type (required): The type attribute is a string that describes the resolution rule. The following values are defined: § removeFromContainer: The member is removed from the container if the constraint is not satisfied for the member. § moveToDefaultContainer: The member is moved to the default container if the constraint is not satisfied for the member. § forceRole: The member is forced into the role specified by the role element. § role (optional): A string that describes the role the member is forced into when the constraint is not satisfied for the member. This attribute is set when the type attribute has the value "forceRole". Possible values for the role attribute are "delegate" and "buddy". blockRules (optional): The wrapper for the list of blockRule elements. blockRule: Describes a blockRule element. § type (required): The type attribute is a string that describes the actions that are blocked. The following values are defined: § invites: Invites are blocked when the rule matches. § subscriberPrompt: Subscriber prompts are blocked when the rule matches. § containers (optional): The actions from the members of specified containers are blocked. § sourceNetworks (optional): The actions from the members of specified source networks are blocked. § maxAvailability (optional): Defines the upper bound of the availability range of the publisher for which this rule applies. § minAvailability (optional): Defines the lower bound of the availability range of the publisher for which this rule applies. rolePrecedence (optional): The wrapper for the list of rolePrecedenceEntry elements that define the order of precedence for roles when a member maps to multiple roles. rolePrecedenceEntry: Describes a role. § type (required): A string that specifies a role. The possible values are "delegate" and "buddy". categoryPublicationManifest: Manifest that describes the list of presence publication rules. minSupportedClientVersion (optional): The minimum version of the UAC that consumes the category publication manifest.

65 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 majorVersion (optional): Ignored. minorVersion (optional): Ignored. publicationList: A wrapper for publicationRules. publicationRule: The rules for the publication of a category in a given container. § ruleType (required): This string value specifies the type of the rule. The following values are defined: § bootstrap: Rule that seeds initial presence data. § transformation: Rule that modifies the presence data before publication according to XSL transformation defined in the categoryData element. § cleanup: Rule that un-publishes existing presence data. § categoryName (required): The name of the target category to which the publication rule applies. § containerID (required): The identifier of the target container to which the publication rule applies. § instance: Ignored. § preferredSelfConsumption (optional): Indicates that the containerId specified in the rule is a preferred container for consuming presence data of the category specified in the same rule. § categoryData: The XSL if the ruleType is "transformation". Empty content indicates that no transformation MUST be applied. Contains the XML to be published if the ruleType is "bootstrap". § expireType (optional): Specifies the lifetime of the publication. § type (required): A string that specifies the rules for expiring the publication. The following values are defined: § endpoint: The publication lives as long as the publishing endpoint stays registered. § user: The publication lives as long as the publishing user stays registered from at least one endpoint. § static: The publication never expires. § time: The publication expires if it is not refreshed within a certain period of time. § expireTime (optional): Specifies the lifetime of the publication when expireType is set to "time". This value is required when type is "time". instanceId (optional): This element allows different instances of the same category to be published to the same container. For example, a publisher might use two different endpoints to publish the same category to the same container, yet these publications will be treated by the server as distinct publications if they use different instanceIds. For a detailed example, see section 4.2.2.

Data Model for userSetting provisionGroup The userSetting provisionGroup is specified as follows.

provisionGroup (name='userSetting')

|-- disableFileTransfer

|-- ucUserLocationProfile

|-- commonAreaPhone

The following XSD schema fragment defines the requirements to which a userSetting provisionGroup element XML document SHOULD<110> conform.

disableFileTransfer:<111> Specifies whether file transfer is disabled. The value SHOULD be "true" or "false". ucUserLocationProfile: Supplies the location profile for voice call features. This is used by the extensions described in [MS-SIPRE] section 2.2.8.

67 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 commonAreaPhone: Specifies whether the client is a Common Area phone. The value MUST be "true" or "false". For a detailed example, see section 4.2.2.

Data Model for endpointConfiguration provisionGroup The endpointConfiguration provisionGroup is as follows.<112>

provisionGroup (name=’endpointConfiguration’)

|-- ShowRecentContacts

|-- ShowManagePrivacyRelationships

|-- MaxPhotoSizeKB

|-- DisableMusicOnHold

|-- AttendantSafeTransfer

|-- MusicOnHoldAudioFile

|-- CustomLinkInErrorMessages

|-- CustomStateUrl

|-- DisablePoorDeviceWarnings

|-- DisablePoorNetworkWarnings

|-- BlockConversationFromFederatedContacts

|-- CalendarStatePublicationInterval

|-- EnableCallLogAutoArchiving

|-- EnableAppearOffline

|-- EnableConversationWindowTabs

|-- EnableEventLogging

|-- EnableFullScreenVideoPreviewDisabled

|-- EnableSQMData

|-- EnableTracing

|-- EnableURL

|-- EnableIMAutoArchiving

|-- DisableEmailComparisonCheck

|-- DisableCalendarPresence

|-- DisableEmoticons

|-- DisableFederatedPromptDisplayName

|-- DisableHandsetOnLockedMachine

|-- DisableHtmlIm

|-- DisableInkIM

|-- DisableRTFIM

|-- DisableSavingIM

|-- DisableMeetingSubjectAndLocation

|-- DisableOneNote12Integration

|-- DisableOnlineContextualSearch

|-- DisablePhonePresence

|-- DisablePICPromptDisplayName

|-- DisablePresenceNote

|-- PhotoUsage

|-- AbsUsage

|-- AllowUnencryptedFileTransfer

|-- AutoDiscoveryRetryInterval

|-- ConferenceIMIdleTimeout

|-- DGRefreshInterval

|-- ExcludedContactFolders

|-- IMWarning

|-- MapiPollInterval

|-- MaximumNumberOfContacts

|-- NotificationForNewSubscribers

|-- PlayAbbrDialTone

|-- SearchPrefixFlags

|-- TabURL

|-- WebServicePollInterval

|-- DisableFeedsTab

|-- EnableEnterpriseCustomizedHelp

|-- CustomizedHelpUrl

|-- DisableContactCardOrganizationTab

|-- HotdeskingTimeout

|-- SPSearchInternalUrl

|-- SPSearchExternalUrl

|-- SPSearchCenterInternalUrl

|-- SPSearchCenterExternalUrl

|-- EnableExchangeDelegateSyncUp

|-- EnableContactSync

|-- ShowSharepointPhotoEditLink

|-- EnableVOIPCallDefault

|-- MaximumDGsAllowedInContactList

|-- ImLatencySpinnerDelay

|-- ImLatencyErrorThreshold

|-- EnableMediaRedirection

|-- P2PAppSharingEncryption

|-- HelpEnvironment

|-- RateMyCallAllowCustomUserFeedback

|-- RateMyCallDisplayPercentage

|-- imLatencySpinnerDelay

|-- imLatencyErrorThreshold

|-- EnableHighPerformanceP2PAppSharing

|-- EnableHighPerformanceConferencingAppSharing

|-- TracingLevel

|-- EnableServerConversationHistory

|-- EnableSkypeUI

|-- CallViaWorkEnabled

|-- UseAdminCallbackNumber

|-- AdminCallbackNumber

The following XSD schema fragment defines the requirements to which an endpointConfiguration provisionGroup element XML document SHOULD conform.

ShowRecentContacts: Ignored. AbsUsage: Specifies whether the user MAY use an Address Book Service (as specified in [MS-ABS]) web query, download a file, or either one for accessing an address book. Values include "WebSearchAndFileDownload", "WebSearchOnly", or "FileDownloadOnly". AllowUnencryptedFileTransfer: Allows unencrypted files to be transferred. MusicOnHoldAudioFile: Optional, ignored. DisableMusicOnHold: Optional, ignored. AttendantSafeTransfer: Optional, ignored. AutoDiscoveryRetryInterval: How frequently to retry autodiscovery if it fails. BlockConversationFromFederatedContacts: This policy prevents external contacts from inviting users to IM or Audio-Video conversations unless they are in the user’s High Presence level. High Presence means that

71 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 they are in the ALLOW access control list (ACL) of the user. In addition, it blocks messages that are not part of a session from reaching the user. CalendarStatePublicationInterval: How frequently data loaded from the calendar is published, in seconds. ConferenceIMIdleTimeout: Amount of time a user MAY sit in an IM-only conference without sending or receiving an IM. When the timeout occurs, the user automatically leaves the IM conference. CustomizedHelpUrl: Determines the root URL to be used when passing help parameters to the customized Help system of the enterprise. CustomLinkInErrorMessages: Custom link pointing users to an enterprise-hosted extranet site from the error messages. CustomStateUrl: URL to an XML file containing custom Presence states. DGRefreshInterval: Timing period, in seconds, for refreshing the Distribution Group. DisableCalendarPresence: Disables loading Free/Busy data from Messaging Application Programming Interface (MAPI) or web services. Also disables publication of free/busy data. DisableContactCardOrganizationTab: Removes the contact card organization tab from the UI. DisableEmailComparisonCheck: Disables the e-mail comparison check; normally, if the e-mail client profile’s email-id does not match the Simple Mail Transfer Protocol (SMTP) address received from the e-mail server<113>, any personal information management (PIM) integration<114> is disabled. This policy is disabled by default. DisableEmoticons: Prevents emoticons being shown in instant messages. DisableFederatedPromptDisplayName: The display name of federated, non-public IM connectivity, contacts in the notification dialog. DisableFeedsTab: Indicates whether the feed environment is shown in the UI. If this setting is enabled, the feed environment and the feed tab are removed from the UI. DisableFreeBusyInfo: Indicates whether free/busy information is published. If this setting is enabled, free/busy information is not published. DisableHandsetOnLockedMachine: When the PC is locked, this setting does not allow calls to or from the handset. DisableHtmlIm: Disables HTML instant messages. DisableInkIM: Ignored. DisableMeetingSubjectAndLocation: Indicates whether the meeting subject and location information is published. DisableOneNote12Integration: Specifies whether planning and note- taking software integration with the instant-messaging client is enabled.<115> DisableOnlineContextualSearch: Disables online searches for related conversations. This disables both the automatic population of previous logs, and the ability to start a contextual search for conversation related to

72 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 emails. This only affects users who are using an e-mail client<116> in online mode. DisablePhonePresence: When this policy is enabled, phone call states are not published as part of the presence information. DisablePICPromptDisplayName: The display name of public IM connectivity contacts in the notification dialog. DisablePoorDeviceWarnings: Disables poor device warnings that appear during the first run, in the tuning wizard, in the main UI, and in the conversation window at the endpoint. DisablePoorNetworkWarnings: Disables poor network warnings that appear during the conversation at the endpoint. DisablePreCallNetworkDiagnostics: Disables poor network warnings that appear during the conversation at the endpoint. DisablePresenceNote: Disables the loading of the OOF (out of office) message from MAPI or web services. Also disables the publication of OOF messages. DisableRTFIM: Indicates that rich text MUST NOT be allowed for IM. DisableSavingIM: Prevents users from saving instant messages. EnableAppearOffline: Controls the appear offline entry points on the client. The value MUST be "true" or "false". EnableCallLogAutoArchiving: When enabled, the client always archives call logs. When disabled, the client never archives call logs. EnableConversationWindowTabs: Enables the web browser in the conversation window. EnableEnterpriseCustomizedHelp: Determines whether the enterprise wants the default online help system or uses a completely customized help system. EnableEventLogging: Turns on UCCP event logging for the client. EnableExchangeDelegateSyncUp: When this is enabled, the delegate’s information is retrieved from the calendar, with author and editor rights on the boss's calendar. EnableFullScreenVideoPreviewDisabled: Enables full screen video with the correct aspect ratio and disables video preview for all client video calls. EnableHotdesking: Specifies whether hotdesking is enabled for a common area phone. Only phones with the common area phone device type make use of this setting. EnableIMAutoArchiving: When this policy is enabled, the client always archives IM conversations. When it is disabled, the client never archives IM conversations. When this policy is not set, the user controls archiving of IM conversations. EnableSQMData: Enables collection of software quality metrics. EnableTracing: Turns on tracing for the client; primarily for use by customer support and the OC team to assist customer problem solving. EnableURL: Allows hyperlinks in instant messages.

73 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 ExcludedContactFolders: This policy is used for excluding contact folders from being imported into the client search results. HotdeskingTimeout: The common area phone operating in hotdesking mode uses this setting to determine when to log the user out and revert to common area mode if the user has been inactive for the hotdeskingTimeout period. This setting is only made use of by phones with the common area device type and the enableHotdesking setting set to "true". IMWarning: Allows the administrator to configure the initial text that appears in the instant messaging area when a conversation window is opened. MapiPollInterval: The frequency, in minutes, of loading calendar data from the MAPI provider. MaximumNumberOfContacts: Maximum number of contacts users are allowed to have. MaxPhotoSizeKB: Maximum size of an individual photo that a client MAY download. NotificationForNewSubscribers: Notifications are shown unless the user has selected otherwise in the options dialog. PhotoUsage: Whether client endpoints display photos of each type. Valid values are "NoPhoto", "PhotosFromADOnly", and "AllPhotos". PlayAbbrDialTone: Changes the length of the dial tone from a 30-second dial tone to a fading, 3-second dial tone. SearchPrefixFlags: A DWORD value whose bits represent the decision of which address book attribute to index into the prefix search tree. These bits are as follows (from low to high): § Bit 0: Primary e-mail. § Bit 1: Alias. § Bit 2: All emails. § Bit 3: Company. § Bit 4: Display name. § Bit 5: First name. § Bit 6: Last name. ShowManagePrivacyRelationships: Controls whether the "view by" menu in the contact list shows or hides "manage privacy relationships" (previously known as access level management view).Valid values are "true" and "false". SPSearchCenterExternalUrl: The site search center external URL is used to enable the site link in the expert search results. This URL represents the search center outside the enterprise network of the search service specified in the ExpertSearchExternalURL. If this setting is blank, there is no link to the site server at the bottom of the search results.

SPSearchCenterInternalUrl: The site search center internal URL is used to enable the site link in the expert search results. This URL represents the search center within the enterprise network of the search service specified

74 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 in the ExpertSearchInternalURL. If this setting is blank, there is no link to the site server at the bottom of the search results. SPSearchExternalUrl: The site external URL is used to enable expert search capabilities If the client is connected to the server outside of the enterprise network. If the URL is blank or invalid, none of the expert search capabilities and UI are enabled. SPSearchInternalUrl: The site internal URL is used to enable expert search capabilities if the client is connected to the server inside of the enterprise network. If the URL is blank or invalid, none of the expert search capabilities and UI are enabled. TabURL: URL for the XML file from which the tab definitions are loaded. WebServicePollInterval: The frequency, in minutes, of loading calendar data from a web services provider. EnableContactSync: Determines whether the client synchronizes contacts into the e-mail server contacts store.<117> The value MUST be "true" or "false". ShowSharepointPhotoEditLink: Determines whether the client shows the site link to edit their photo. The value MUST be "true" or "false". EnableVOIPCallDefault: Determines whether the client chooses Voice over IP (VoIP) call as the default calling method instead of a PSTN call when click to call is used. The value MUST be "true" or "false". MaximumDGsAllowedInContactList: Determines the number of distribution groups allowed in the contact list of the client. The type for this is unsigned integer. EnableMediaRedirection: Enables an enterprise-grade audio/video experience.<118> HelpEnvironment: Specifies the help documentation that the client shows to the user. P2PAppSharingEncryption: An integer value that specifies the encryption mode for application sharing sessions between clients. § 0 : Supported § 1 : Enforced § 2 : Not Supported TracingLevel:<119> Controls the tracing level on the client. This with EnableTracing controls tracing, if EnableTracing is not set then this attribute controls the level of tracing and the user can change the tracing level, if EnableTracing is set then the user cannot change the tracing level and the tracing level is determined by the value of this attribute. This string attribute MUST have one of the following values. § Off § Light § Full RateMyCallAllowCustomUserFeedback: <120> Whether the call rating dialog should include a free form text field, where user can provide custom feedback (value set to "true"), or not ("false").

75 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 RateMyCallDisplayPercentage: <121> An integer percentage value between 0 and 100 that indicates the percentage of calls for which call rating information is requested from the user at the end of a call. A value of 0 specifies to never request call rating information. A value of 100 specifies requesting call rating information at the end of every call. The default value is 10, specifying requesting call rating information for 1 call out of every 10 calls. ImLatencySpinnerDelay: <122> The amount of time in milliseconds to wait before showing the spinner in the client when IM delivery is delayed. ImLatencyErrorThreshold: <123> An integer value in milliseconds. If the IM latency is above this threshold the client will submit a CER. EnableServerConversationHistory: <124> Whether to allow the IM server to record the conversation history for this user. EnableHighPerformanceP2PAppSharing: <125> Whether to enable high frame rate application sharing in a two-party conversation. To enable the best experience, this setting SHOULD be enabled on both the sharer and viewer. When this setting is enabled, the actual frame rate is determined by the AppSharingBitRate setting. If the AppSharingBitRate is less than or equal to 2000, then the frame rate is calculated as 2.5 frames per second. If the AppSharingBitRate is between 2000 and 4000, the frame rate is calculated as 4 frames per second. If the AppSharingBitRate is between 4000 and 8000, then the frame rate is calculated as 6 frames per second. If the AppSharingBitRate is between 8000 and 12000, then the frame rate is calculated as 8 frames per second. If the AppSharingBitRate is greater than 12000, then the frame rate is calculated as 10 frames per second. The default is "false", indicating a default frame rate of 2.5 frames per second. EnableHighPerformanceConferencingAppSharing: <126> Whether to enable high frame rate application sharing in a multi-party (conference) conversation. Note that when enabled, this may have a performance impact on the application sharing conference server, possibly resulting in degraded performance if the server is heavily loaded. To enable the best experience, the setting SHOULD be enabled on both the sharer and viewer. When this setting is enabled, the actual frame rate is determined by the AppSharingBitRate setting. If the AppSharingBitRate is less than or equal to 2000, then the frame rate is calculated as 2.5 frames per second. If the AppSharingBitRate is between 2000 and 4000, the frame rate is calculated as 4 frames per second. If the AppSharingBitRate is between 4000 and 8000, then the frame rate is calculated as 6 frames per second. If the AppSharingBitRate is between 8000 and 12000, then the frame rate is calculated as 8 frames per second. If the AppSharingBitRate is greater than 12000, then the frame rate is calculated as 10 frames per second. The default is "false", indicating a default frame rate of 2.5 frames per second EnableSkypeUI: <127> Whether the client should display a Lync-style or Skype-style user interface. When set to "true", the client should display a Skype-style interface; when set to "false", the client should display a Lync-

76 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 style interface. If this setting is absent, the client can choose in an implementation-specific manner. CallViaWorkEnabled: <128> Whether to enable or disable a user for CallViaWork functionality. AdminCallBackNumber: <129> An administrator-specified callback phone number for a specific user. UseAdminCallbackNumber: <130> Whether to force the user to use their AdminCallbackNumber as their callback phone number. When set to "true", the AdminCallbackNumber must be configured. When set to "false", user has the ability to specify their own callback phone number in addition to the administrator-specified AdminCallbackNumber. For a detailed example, see section 4.2.2.

Data Model for locationPolicy provisionGroup The locationPolicy provisionGroup follows the behavior described in product behavior note <131>.

provisionGroup (name=’locationPolicy’)

|-- propertyEntryList

| |-- property

| | |- name

The following XSD schema fragment defines the requirements to which a locationPolicy provisionGroup element XML document SHOULD conform.

EnhancedEmergencyServicesEnabled: If "true", the client acquires location information and sends PIDF-LO with an emergency call. The value MUST be "true" or "false". LocationPolicyTagID: If this element is present, the client MUST insert this value into the PIDF-LO of every emergency call. [MS-SIPRE] section 3.17.5.2 specifies the usage of this field in detail. LocationRequired: Triggers the client to request alternate location sources from the user if the lisInternalUrl (section 2.2.2.5.1) is not populated or the Location Information Service does not return a location. Valid values are "yes", "no", or "disclaimer". § "yes" – triggers the client to show an alert indicator and text about entering a location. § "no" – do nothing. § "disclaimer"– show an alert indicator and text about entering a location, and if the user clicks through then show the EmergencyServiceDisclaimer (section 2.2.2.5.7). UseLocationForE911Only: If "true", the location is sent only in a 911 call. The value MUST be "true" or "false". PstnUsage: Ignored. EmergencyDialString: The dial string or URI that triggers the client to send PIDF-LO and initiates the E911-related UI capability. EmergencyDialMask: Dial strings or URIs that, if entered by a user, are translated into the emergency dial string. If there are multiple values, they are separated by a semicolon (;). For example, a European employee, while visiting the United States, might dial 112 in an emergency and this property helps route the call correctly. NotificationUri: URIs that the emergency notification will be sent to. The notification URI MAY be one SIP URI or list of comma separated SIP URIs. Group and DL URIs are not supported. ConferenceUri: URI of the person or group that is conferenced-in in the emergency call. ConferenceMode: Toggle setting of one-way or two-way audio for an emergency conference. Valid values are "oneway" or "twoway". EmergencyServiceDisclaimer: Text entered by the administrator for the client to display an emergency services disclaimer if it could not fetch a

78 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 location from the Location Information Service, as specified in [MS- E911WS] section 3.1.4.1. LocationRefreshInterval: The interval in hours for Location Information Service requests from the client. For a detailed example, see section 4.2.2.

Data Model for mediaConfiguration provisionGroup

provisionGroup (name=’mediaConfiguration’)

|-- propertyEntryList

| |-- property

| | |- name

The following XSD schema fragment defines the requirements to which a mediaConfiguration provisionGroup element XML document SHOULD conform.<132>

bypassEnabled: Specifies whether bypass is enabled for this deployment. The value MUST be "true" or "false". internalBypassMode: If bypass is enabled for this deployment, specifies whether bypass is enabled for internal users. externalBypassMode: If bypass is enabled for this deployment, specifies whether bypass is enabled for outside users. bypassId: If bypass is enabled for this deployment, specifies the Bypass identifier to be used if the deployment is configured for "alwaysBypass", or the default Bypass identifier to use if no Bypass identifier is returned as a result of region or site matching. For a detailed example, see section 4.2.2.

Data Model for presencePolicyV2 provisionGroup The presencePolicyV2 provisionGroup is specified as follows.<133>

provisionGroup (name='presencePolicyV2')

|-- propertyEntryList

| |-- property

| | |- name

The following XSD schema fragment defines the requirements to which a presencePolicyV2 provisionGroup element XML document MUST conform.

propertyEntryList: A single propertyEntryList element is specified within the presencePolicyV2 provisionGroup, and lists a set of presence- related settings. property: A single presence setting. The name attribute specifies the property name. Values are specified in CDATA notation. The following properties MUST be present. EnablePrivacyMode: Indicates whether privacy mode is enabled on the server. The value MUST be "true" or "false". AutoInitiateContacts: Specifies whether the first-run automatic population of the contact list needs to be enabled on the client. The value MUST be "true" or "false". PublishLocationDataDefault: Specifies whether clients need to publish location data by default. The value MUST be "true" or "false". DisplayPublishedPhotoDefault: Specifies whether the user’s published photo is displayed by the client by default. The value MUST be "true" or "false". PersonalNoteHistoryDepth: The maximum number of child note elements stored in the single NoteHistory instance that MAY be published in a container at any given time. The value is an unsigned integer. SubscribeToCollapsedDG: Specifies whether the client needs to subscribe to presence information of distribution group members when collapsed in the UI. For a detailed example, see section 4.2.2.

81 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Data Model for privacyPublicationGrammar provisionGroup

provisionGroup (name='privacyPublicationGrammar')

|-- containerManifestList

| |- minSupportedClientVersion

|- majorVersion

|- minorVersion

| |-- containerManifest

| | |-- containers

|-- container

|- id

|-- visible

|-- avoidRedundantMembers

|-- blocked

|-- members

|-- member

|- type

|- role

|- uri

|-- allowedContainers

|- type

|-- container

|- id

|-- defaultContainer

|- id

|-- occurrenceConstraint

|- type

|-- sourceNetworks

|-- sourceNetwork

|- type

|-- resolutionRule

|- type

|- role

|-- blockRules

|-- blockRule

|- type

|-- containers

|- type

|-- container

|- id

|-- sourceNetworks

|-- sourceNetwork

|- type

|-- minAvailability

|-- maxAvailability

|-- rolePrecedence

|-- rolePrecedenceEntry

|- type

The following XSD schema fragment defines the requirements to which a privacyPublicationGrammar provisionGroup element XML document SHOULD<134> conform.

83 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 targetNamespace="http://schemas.microsoft.com/2006/09/sip/provisiongrouplist- notification" elementFormDefault="qualified"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns:ms="urn:microsoft-cpp-xml-serializer">

The privacyPublicationGrammar provisionGroup element contains the containerManifestList XML document, as shown in the example in section 4.2.2. The following XSD schema fragment defines the requirements to which the containerManifestList XML document SHOULD<135> conform.

targetNamespace="http://schemas.microsoft.com/2008/09/sip/ContainerManifest"

xmlns:tns="http://schemas.microsoft.com/2008/09/sip/ContainerManifest"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns:ct="http://schemas.microsoft.com/2006/09/sip/commontypes"

elementFormDefault="qualified">

schemaLocation="commontypes.xsd"/>

minOccurs="1" maxOccurs="1"/>

minOccurs="0" maxOccurs="1"/>

The following XSD schema fragment defines the schema for commontypes referred by the containerManifestList XSD schema.

targetNamespace="http://schemas.microsoft.com/2006/09/sip/commontypes"

xmlns:tns="http://schemas.microsoft.com/2006/09/sip/commontypes"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

elementFormDefault="qualified"

attributeFormDefault="unqualified"

maxOccurs="unbounded" namespace="##other"/>

containerManifestList: A list of all containerManifests available. containerManifest: A manifest that provides the list of containers and members. The UAC SHOULD create containers and its members based on the constraints defined in the manifest. majorVersion (optional): Ignored. minorVersion (optional): Ignored. minSupportedClientVersion (optional): The minimum version of the UAC that can use the container manifest. containers: The wrapper for the list of container elements. container: Each container element describes a container. § id (required): This unsigned short integer uniquely identifies a container. § Visible (optional): Container attribute which, when "true", designates the container as a member of the set of containers identified with allowed containers type equal to "visibleContainers". The UAC also interprets this attribute as those containers that are displayed in its access level view. § avoidRedundantMembers (optional): This string indicates whether a container MAY have redundant membership. For example, redundancy

100 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 occurs when a domain, as well as a user who is in that domain, are associated with a container. The value MUST be "true" or "false". The UAC SHOULD clean up redundant members from containers if the setting is "true". § blocked (optional): Ignored. members: The wrapper for the list of member elements. member: Describes a container member. type (optional): This string value specifies the type of the member. The following values are defined: § user: A SIP URI. § domain: A SIP domain. § sameEnterprise: All users from the same enterprise. § federated: All federated users. § publicCloud: All public cloud users. § everyone: All users. § singleIdentityUser: A user who has just one SIP uri for that particular identity. PIC contacts that have more than one SIP uri that belong to the identity should not be processed using this rule. role (optional): This string value specifies the role of the member. Note that container members matching to a member by role attribute take precedence over the corresponding match to member by type attribute. The following values are defined: § delegate: A user entity currently configured as a delegate for the local user. § buddy: A user entity currently a member of the local user’s buddy list. allowedContainers: The list of containers to which the member MAY be added. § type (required): A string that describes the access control element. The following values are defined: § custom: The list of containers is specified within the allowedContainers element. § visibleContainers: The list of containers for the member are the same as the subset of child elements of the containers element with the Visible element set to "true". § container (optional): The container to which the member MAY be added. There MAY be more than one element. The list of containers is specified when the type is "custom." § id (required): This unsigned short integer uniquely identifies a container. defaultContainer (optional): The default container to which the member MAY be added if the constraint is not satisfied for the member. § id (required): An unsigned integer that is the container identifier. occurrenceConstraint (optional): The mandatory membership occurrence rate the related type or role the member is present in.

101 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 § type (required): A string that gives the number of occurrences mandated for the given type or role in a given container. The value MUST be "zero", "one", or "zeroOrOne". § When "Zero", a given container MUST have zero members of the related type or role. This value SHOULD be ignored by a UAC. § When "One", a given container MUST have one member of the related type or role. § When "zeroOrOne", a given container MAY have no members of the related type or role or it MAY have one member of a related type or role. It MUST NOT have more than one member of a related type or role. sourceNetworks (optional): A wrapper for the optional list of source networks to which the member belongs to satisfy the constraint. sourceNetwork: Describes a source network. § type (required): A string that describes the source network. The following values are defined: § sameEnterprise: All users from the same enterprise. § federated: All federated users. § publicCloud: All public cloud users. resolutionRules (optional): A wrapper for the optional list of resolution rules that are applied if the constraint is not satisfied for the member. resolutionRule: Describes a resolution rule. § type (required): The type attribute is a string that describes the resolution rule. The following values are defined: § removeFromContainer: The member is removed from the container if the constraint is not satisfied for the member. § moveToDefaultContainer: The member is moved to the default container if the constraint is not satisfied for the member. § forceRole: The member is forced into the role specified by the role element. § role (optional): A string that describes the role the member is forced into when the constraint is not satisfied for the member. This attribute is set when the type attribute has the value "forceRole". Possible values for the role attribute are "delegate" and "buddy". blockRules (optional): The wrapper for the list of blockRule elements. blockRule: Describes a blockRule element. § type (required): The type attribute is a string that describes the actions that are blocked. The following values are defined: § invites: Invites are blocked when the rule matches. § subscriberPrompt: Subscriber prompts are blocked when the rule matches. § containers (optional): The actions from the members of specified containers are blocked. § sourceNetworks (optional): The actions from the members of specified source networks are blocked.

102 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 § maxAvailability (optional): Defines the upper bound of the availability range of the publisher for which this rule applies. § minAvailability (optional): Defines the lower bound of the availability range of the publisher for which this rule applies. rolePrecedence (optional): The wrapper for the list of rolePrecedenceEntry elements that defines the order of precedence for roles when a member maps to multiple roles. rolePrecedenceEntry: Describes a role. § type (required): A string that specifies a role. The possible values are "delegate" and "buddy". For a detailed example, see section 4.2.2.

Data Model for persistentChatConfiguration provisionGroup

provisionGroup (name=’persistentChatConfiguration’)

| |-- propertyEntryList

| |-- property

| | |- name

The following XSD schema fragment defines the requirements to which a persistentChatConfiguration provisionGroup element XML document SHOULD conform.<136>

DefaultPersistentChatPoolUri: Specifies the default persistent chat pool URI for the client to connect to. EnablePersistentChat: Specifies whether persistent chat is enabled for the client. The value MUST be "true" or "false". PersistentChatPoolUris: Specifies the URIs of all the persistent chat pools that the client can connect to, separated by a single whitespace. PersistentChatWebManagerUriInt: Specifies the internally accessible URI that serves the chat room management Web application.<137> This URI SHOULD be used by the client to connect to the Web application when signed on from inside the network. PersistentChatWebManagerUriExt: Specifies the externally accessible URI that serves the chat room management Web application.<138>. This URI SHOULD be used by the client to connect to the Web application when signed on from outside the network. For a detailed example, see section 4.2.2.

Data Model for publicProviders provisionGroup

provisionGroup (name=’publicProviders’)

| |-- propertyEntryList

| |-- property[name="publicProviders"]

| | |-- CDATA

| | | |-- PublicProviders

The following XSD schema fragment defines the requirements to which a publicProviders provisionGroup element XML document SHOULD conform.<139>

The following XSD schema fragment defines the requirements to which a publicProviders PublicProviders element XML document SHOULD conform.<140>

Name: The name of the public provider. ProxyFqdn: Specifies the fully qualified domain name (FQDN) that is used for presence requests for this public provider. IconUrl: Specifies the URL of an icon the client uses to graphically indicate the location of contacts. NameDecorationDomain: Specifies an FQDN the client displays for the public provider. NameDecorationRoutingDomain: Specifies an FQDN to be used to transform the user name of a public provider in the form of username@domain into username(domain)@NameDecorationRoutingDomain as its SIP URI. NameDecorationExcludedDomainList: Specifies a comma-separated list of FQDNs. Protocol clients that attempt to route users from public providers belonging to one of the domains on this list are routed without the name transformation described in the preceding paragraph.

Basic Registration The SIP registrar accepts SIP REGISTER requests, processes them, and responds to them as specified in [RFC3261], with the additional extensions defined as follows. The basic end-to-end call-flow is shown in the following diagram.

Figure 1: Basic register call flow

Client Role The UAC registers and refreshes a binding with the SIP registrar as specified in [RFC3261] section 10. The UAC SHOULD select endpoint identifier (EPID) and SIP.INSTANCE endpoint identifiers, as described in [MS-SIPRE] section 3.2. The UAC MUST have exactly one active REGISTER dialog as specified in [RFC3261] for the selected endpoint identifier (EPID). As part of the registration process, the UAC MUST establish and maintain a security association (SA) with the registrar using the NT LAN Manager (NTLM) Authentication Protocol or the Kerberos authentication protocol, as specified in [MS-SIPAE] section 3.2.

Abstract Data Model This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This protocol does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this protocol. The UAC SHOULD keep the following state: § Epid: A string that is a part of the SIP endpoint identifier. The format and generation of Epid are described in [MS-SIPRE] section 3.2.3.1. § SIP.INSTANCE: A string that is a part of the SIP endpoint identifier. The format and generation of SIP.INSTANCE are described in [MS-SIPRE] section 3.2. § GRUU: A string that is part of the SIP endpoint identifier. It is generated by the SIP registrar and persisted on the client. The format and generation of GRUU are described in [MS-SIPRE] section 3.4.

107 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 § Presence-Service-Available:<141> A Boolean that is generated by the registrar and persisted on the client, and is updated as described in section 3.1.1.5.1. § Primary-Cluster-Type:<142> An identifier associated with the UAC that is generated by the registrar and persisted on the client, and is updated as described in section 3.1.1.5.1. § Is-Connected-to-Primary:<143> A Boolean flag associated with the UAC that is generated by the registrar and persisted on the client, and is updated as described in section 3.1.1.5.1.

Timers The UAC SHOULD start and maintain a SIP registration refresh timer, as specified in [RFC3261] section 10.2.4. If the UAC specifies support for ms-keep-alive, as specified in [MS- CONMGMT] section 2.2.1, it SHOULD maintain a whitespace keep-alive timer for sending whitespaces, as specified in [MS-CONMGMT] section 2.2.2.

Initialization The UAC instance MUST generate an EPID and a SIP.INSTANCE value before sending any REGISTER request, as described in [MS-SIPRE] section 3.3.3.1.

Higher-Layer Triggered Events Except as specified in the following subsections, processing rules follow [RFC3261] section 10.1.

Constructing the Outgoing SIP REGISTER Request The UAC MUST construct the outgoing SIP REGISTER request, as specified in section 2.2.1.1. It MUST then insert the Epid and SIP.INSTANCE values in the REGISTER request, as specified in [MS-SIPRE] section 3.2 and [MS-SIPRE] section 3.2. The UAC SHOULD insert a User-Agent header as specified in section 3.4.1.5.1. The UAC SHOULD discover its subnet address and insert an Ms-Subnet header. The UAC MUST populate the Ms-Subnet header by discovering the IP Subnet Address, as specified in [RFC950], of the TCP connection over which the SIP REGISTER Request will be sent. The UAC SHOULD insert a Ms-Device-Info header as specified in section 2.2.1.7. The UAC MUST populate the Ms-Device-Info header by discovering the following: § The MAC address, which is the physical address of the network interface over which the SIP REGISTER request will be sent. § The version, which is a literal string that describes the version of the UAC. § The vendor identifier, which is a literal string that identifies the manufacturer of the UAC.

108 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 It MUST then send the SIP REGISTER request and process the response as specified in the following subsection.

Message Processing Events and Sequencing Rules Except as specified in the following subsections, the processing rules follow the procedures specified in [RFC3261] section 10.2.7.

Processing the SIP REGISTER Response The UAC SHOULD extract the contact GRUU returned by the SIP registrar and use it subsequently as specified in [IETFDRAFT-OUGRUAUSIP-10] section 8. The UAC MUST retrieve the registration expiry timer value, as specified in [RFC3261] section 10, from the SIP REGISTER response. It MUST then set the registration expiry timer value less than the value specified in the 200 OK response to the REGISTER request. The UAC SHOULD process the ms-keep-alive header, as specified in [MS- CONMGMT] section 2.2.1, returned by the registrar as specified in [MS- CONMGMT] section 3.4.5, and use it to initialize the keep-alive timer. If a Presence-State header field is present in the 200 success response, the UAC MUST take the following additional actions: § If the value of Register-Action is "added" or "fixed", and if the REGISTER operation is for the purpose of refreshing a binding instead of adding a new binding, the UAC MUST treat this as a registration failure and all existing dialogs SHOULD be considered terminated. The UAC SHOULD restart registration. § If the value of Primary-Cluster-Type is "central", the UAC SHOULD<144> treat this as an indication of the user being provisioned on a server at a central site and MUST update the Primary-Cluster-Type field to "central". If the value is "remote", the UAC MUST treat this as an indication that the user is being provisioned at a remote site and MUST update the Primary- Cluster-Type field to "remote". § If the value of Is-Connected-to-Primary is "yes", the UAC SHOULD<145> treat the endpoint as being connected to the user’s primary server and MUST update the Is-Connected-to-Primary field to "true". If the value is "no", the UAC MUST<146> treat the endpoint as not being connected to the user’s primary server and MUST update the Is-Connected-to-Primary field to "false". § If the value of user-services-state is "unavailable", the UAC SHOULD<147> set the Presence-Service-Available field to "false". § If user-services-state is NOT present, the UAC SHOULD<148> set the Presence-Service-Available field to "true". After the UAC receives a 200 response for the first REGISTER it sent, the UAC SHOULD attempt to establish a contact or group subscription, as specified in [MS-SIP] section 3.3, and SHOULD attempt to establish a self-subscription, as specified in [MS-PRES] section 3.3, to retrieve the user's contact and group information and published presence information.

109 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 If the Presence-Service-Available field is set to "false", the UAC SHOULD<149> treat itself to be in survivable mode and SHOULD NOT attempt to establish any subscription except a self-subscription, as specified in [MS- PRES] section 3.3. If the self-subscription fails to establish, the UAC is not able to retrieve the published presence information, and the UAC SHOULD<150> remove the binding by sending a REGISTER request with Expiry value of 0, as specified in [RFC3261] section 10.2.2. If the contact or group subscription fails, contacts and groups information is not available. If the self-subscription fails to establish and the UAC is not in survivable mode, the UAC SHOULD<151> retry the self-subscription at a randomized interval. If, however, the self-subscription fails to establish while the UAC is in survivable mode, it SHOULD<152> wait for the retry until the end of survivable mode, as indicated by a response to a future REGISTER with the Presence-Service- Available field set to "false", as described in the preceding paragraphs. This protocol does not mandate how implementations operate on the Primary- Cluster-Type and Is-Connected-to-Primary fields as long as their external behavior is consistent with that described in this protocol.

Timer Events The UAC SHOULD refresh the registration whenever the registration expiry timer fires, as specified in [RFC3261] section 10.2.4. The UAC MUST use the same TCP connection that it sent the dialog-creating REGISTER request through for sending registration refresh requests. The UAC SHOULD periodically send whitespaces whenever the keep-alive timer fires, as specified in [MS-CONMGMT] section 3.4.5.4.

Other Local Events None.

Server Role

Abstract Data Model This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This protocol does not mandate that implementations adhere to this model, as long as their external behavior is consistent with that described in this protocol. The registrar SHOULD keep the following states for each UAC: § SIP Endpoint identifier: An identifier for a UAC. It MAY be a structure with the combination of an EPID, as described in [MS-SIPRE] section 3.2, a SIP.INSTANCE, as described in [MS-SIPRE] section 3.2, and a GRUU, as described in [MS-SIPRE] section 3.4.

110 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 § Routable: A Boolean flag that is set to "true" whenever a valid registration is associated with the UAC, and is set to "false" whenever the registration associated with the UAC ceases to exist. § Presence-Service-Available:<153> A Boolean flag that is set to "true" when the presence service associated with the user is available, and is set to "false" whenever the presence service associated with the user is unavailable. § Primary-Cluster-Type:<154> An identifier for the user associated with the UAC that is set to "central" if the user’s home server is located in a central site, and is set to "remote" if the user’s home server is located in a remote site. § Is-Connected-to-Primary:<155> A Boolean flag that is set to "true" when the server accepting the registration is the user’s home server, and is set to "false" when the server accepting the registration is not the user’s home server. § Supports survivable mode:<156> A Boolean flag that is set to "true" when the UAC indicates support for registration without the availability of the presence component, as defined in section 2.2.1.5, and is set to "false" when the UAC does not support registration without the availability of the presence component.

Timers The SIP registrar SHOULD keep a registration timer for each binding. The registration expiry timer value is exchanged as specified in [RFC3261] section 10. The registrar MUST specify an expiry value for the binding of no less than 30 seconds. When the registrar receives a REGISTER request for a binding, the registrar MUST refresh the registration expiration timer for the associated binding.

Initialization None.

Higher-Layer Triggered Events The message validation rules for processing an incoming REGISTER request follow the procedures specified in [RFC3261] section 10.3 as well as [MS- SIPRE] sections 3.4 and 3.5.

Message Processing Events and Sequencing Rules Except as specified in the following subsections, the processing rules follow the procedures specified in [RFC3261] section 10.3 and [IETFDRAFT- OUGRUAUSIP-10] section 7.1.2.1.

Processing the REGISTER Request

111 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 The SIP registrar MUST establish and maintain an SA with the UAC using the NTLM or the Kerberos authentication protocol, as specified in [MS-SIPAE] section 3.2. When the SA is established, the registrar MUST validate the request according to the rules specified in section 2.2.1.1. If the validation fails after the registrar inspects the REGISTER request headers, as specified in [RFC3261] section 8.2.2, the registrar SHOULD reject the request with an appropriate error response, as specified in [RFC3261] section 8.2.2. The outgoing SIP error response SHOULD include an ms- diagnostics header or an ms-diagnostics-public header, as described in [MS- OCER] section 2.2.1. The ErrorId to be included in these headers is also listed in the following table. Special error responses are shown in the following table. SIP response code ErrorId Reason

400 4010 Missing endpoint identifier (Epid and SIP.INSTANCE).

489 4055 Event header is not set to "registration".

421 2057 Supported header does not have gruu-10, but msrtc-event- categories is present. The registrar retrieves the Epid and SIP.INSTANCE value from the REGISTER request. The registrar tries to find an existing SIP endpoint with an identifier that contains an identical Epid and SIP.INSTANCE. If none is found, this is a new binding for a new UAC. The registrar generates a GRUU as described in [MS-SIPRE] section 2.2.3, and stores the EPID, SIP.INSTANCE, and GRUU in a new SIP endpoint identifier. It then processes the request and, if the request is accepted, it SHOULD set the Routable field of the SIP endpoint identifier to "true". If the registrar finds an existing SIP endpoint identifier, this is either a REGISTER refresh or a new REGISTER for the same endpoint. In either case, the registrar processes the request as specified in [RFC3261] section 10.3. If it accepts the request, it SHOULD set the Routable field of the SIP endpoint identifier to "true". The server replaces bindings using SIP.INSTANCE as the primary key. If the Supports survivable mode field for the UAC is set to "false" and Presence Service Available is "false", the registrar SHOULD<157> reject the request with a 503 Service Unavailable, as specified in [RFC3261] Section 21.5.4. The ms-diagnostics-public ErrorId SHOULD be set to "4164". If the UAC supports survivable mode, the registrar SHOULD<158> notify the endpoint if the Presence-Service-Available transitions from "true" to "false" using a NOTIFY with the userservices-unavailable event, as defined in section 2.2.1.13. The registrar SHOULD<159> retrieve the MAC address, version and vendor identifier from the Ms-Device-Info header in the REGISTER request. The

112 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 information stored in the Ms-Device-Info header SHOULD be used by the server to track the devices that are communicating with it. The 200 OK response for the REGISTER request is generated as specified in [RFC3261] section 10.3, and the following additional rules: § The registrar retrieves the GRUU from the SIP endpoint identifier and returns the GRUU as specified in [IETFDRAFT-OUGRUAUSIP-10] section 8.2 in the response to the REGISTER request. § In addition, the registrar SHOULD insert a Presence-State header field into the 200 response to the REGISTER request. § The value of the Register-Action field of the Presence- State header is generated as follows: § If the REGISTER created a new SIP endpoint (5), the value is "added". § If the REGISTER adds a new binding to an existing SIP endpoint and the Routable field changed from "false" to "true" during processing, the value is "fixed". § If the REGISTER refreshes an existing binding for an existing SIP endpoint (5), the value is "refreshed". § The Primary-Cluster-Type<160> field of the Presence- State header is generated as follows. § If the Primary-Cluster-Type field is set to "central", the value is "central". § If the Primary-Cluster-Type field is set to "remote", the value is "remote". § The Is-Connected-To-Primary<161> field of the Presence-State header is generated as follows. § If the Is-Connected-To-Primary field is "true", the value is "yes". § If the Is-Connected-To-Primary field is "false", the value is "no". § The user-services-state<162> field of the Presence- State header is generated as follows. § The user-services-state field is set to "unavailable" if the Presence-Service-State field is set to "false". § The user-services-state field of the Presence-State header SHOULD NOT be set if the Presence-Service- State field is set to true. The registrar MAY perform additional actions based on the version of the UAC, as described in section 3.4.2.5.

Timer Events When the SIP registrar's expiry timer for a binding expires, the registrar MUST remove the binding and clear any state related to the binding. If the routable field was previously set to "true", it SHOULD be changed to "false". If the

113 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 keep-alive timer specified in [MS-CONMGMT] section 3.4.5.2 fires, the binding SHOULD be removed.

Other Local Events None.

Removing a Binding from the Registrar The SIP registrar SHOULD send a deregister NOTIFY to the UAC if it becomes necessary to remove a binding prematurely for any reason. Some of the reasons when this MAY happen are illustrated by the following examples, which are described in section 2.2.1.13. § The registrar enforces a quota on the number of endpoints from which a user MAY be registered. If this quota is exceeded, the registrar might use a policy of deregistering the oldest endpoint. In this case, the message body is set to "unregistered". § The administrator disables the user for policy reasons, such as when a user leaves the organization. In such cases, the registrar might automatically deregister all the endpoints (5) of the user when the policy change is applied. The message body is set to "rejected". § The user is being moved across servers. This is possible if the system supports the notion of a dedicated "home server" for each user. In such cases, when the user is moved across servers (2), the existing endpoints (5) in the previous server (2) might be automatically deregistered. The message body is set to "deactivated". § The user is being moved across registrars. This is possible if the system supports the notion of a dedicated "home registrar" for each user. In such cases, when the user is moved across registrars, the existing endpoints in the previous registrar might be automatically deregistered. The message body is set to "preferred-registrar-change". The P-Preferred-Registrar header indicates the new home registrar for the user.<163> § The service responsible for presence of a user is unavailable and the endpoint has not indicated support for survivable mode. In such cases, the endpoints (5) that do not indicate support are automatically deregistered. The message body is set to "userservices-unavailable".<164> Note: These reasons are illustrative and the list of examples is not comprehensive. When the registrar deregisters an endpoint (5), it SHOULD send a deregister NOTIFY to the UAC indicating that the registration has terminated.

Client Role This section follows the behavior described in endnote <165>.

Abstract Data Model None.

Initialization None.

Higher-Layer Triggered Events None.

Message Processing Events and Sequencing Rules This section follows the behavior described in endnote <166>. No extra sequencing rules beyond those specified in [RFC3261] section 10.2.2 are required, except when a P-Preferred-Registrar header is present in the NOTIFY. If the P-Preferred-Registrar header is present, the UAC SHOULD attempt to register with the SIP registrar specified in the P-Preferred- Registrar header.

Server Role

Abstract Data Model None.

Timers None.

Initialization None.

Higher-Layer Triggered Events The SIP registrar SHOULD send a deregister NOTIFY to the UAC if it becomes necessary to remove a binding prematurely for any reason. If the registrar deregisters an endpoint and a NOTIFY is sent, it MUST construct the NOTIFY request as specified in the following subsection.

Constructing the Outgoing Deregister NOTIFY Request The outgoing deregister NOTIFY request is first constructed using the rules specified in section 2.2.1.11. It MUST be sent only to the UAC that is being deregistered, and hence it MUST use the same local and remote tags as those specified in [RFC3261] section 12 and the call-id and local CSeq of the last REGISTER transaction sent from the deregistered UAC, as specified in [RFC3265] section 3.3.4 and [RFC3261] section 10.3.

115 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Message Processing Events and Sequencing Rules The processing rules follow the procedures specified in [RFC3261] section 10.3, [RFC3265] section 4.4.8, and [IETFDRAFT-OUGRUAUSIP-10] section 7.1.2. A binding SHOULD be considered terminated when the registration expiry timer or the keep-alive timer fires, as specified in section 3.1.2.6. In this case, the SIP registrar MAY do either of the following options: § Expire the registration binding, but keep the SIP endpoint identifier, as defined in section 3.1.2.1, with routable state set to "false". This is useful when the registrar keeps additional state associated with the SIP endpoint that is independent of the binding itself. With this option, when a subsequent re-registration is received for the expired endpoint, the Presence-State header SHOULD contain a Register-Action field with the value "fixed". § Expire the registration binding and remove the SIP endpoint identifier, as defined in section 3.1.2.1. With this option, when a subsequent re- registration is received for the expired endpoint, the Presence-State header SHOULD contain a Register-Action field with the value "added".

Timer Events None.

Other Local Events None.

Obtaining Provisioning Information

Client Role The UAC sends an in-band provisioning request listing all the configuration groups in which it is interested. It then waits for a response and extracts the various configuration parameters for each of the groups listed in the response. Example call flows are given in section 4.2.

Abstract Data Model None.

Timers None.

Initialization None.

116 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Higher-Layer Triggered Events Unless specified otherwise, the message processing rules follow the procedures specified in [RFC3265] section 4.4.6. The user agent constructs an in-band provisioning request using the syntax rules given in section 2.2.2.1 and populates it with the body specified in section 2.2.2.4. It then sends the SUBSCRIBE requests using the procedures specified in [RFC3265] section 3.1.4.

Message Processing Events and Sequencing Rules Depending on the provisioning groups requested, the client processes the response as described in section 2.2.2.5.

Timer Events None.

Other Local Events None.

Server Role

Abstract Data Model None.

Timers None.

Initialization None.

Higher-Layer Triggered Events Except as specified in the following subsection, processing rules follow the procedures specified in [RFC3265] section 4.4.6.

Processing the Incoming SUBSCRIBE Request On receiving an in-band provisioning request, the server parses and validates the SIP headers using the rules specified in section 2.2.2.1. The server then validates the request body using the rules specified in section 2.2.2.4. If either of these validations fails, the server SHOULD reject the request with an appropriate SIP response, or as per the rules specified in [RFC3265] section 3.1.6.3 and [RFC3261] section 8.2.6. The server SHOULD then extract the provisioning groups listed in the request. It SHOULD then construct the response XML, as specified in section 2.2.2.5, listing each supported provisioning group and the parameters within the group. All mandatory parameters MUST be populated.

117 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 The server SHOULD then generate the SUBSCRIBE response as specified in section 2.2.2.2.

Message Processing Events and Sequencing Rules None.

Timer Events None.

Other Local Events None.

Automatically Updating Client to a Server Compatible Version

Client Role The UAC provides version information to enable version checks on the server. The following sections specify how the version information is constructed by the UAC.

Abstract Data Model None.

Timers None.

Initialization None.

Higher-Layer Triggered Events None.

Message Processing Events and Sequencing Rules

Construction of User-Agent header The UAC includes a User-Agent header when it sends a REGISTER request. The User-Agent header, as specified in [RFC3261] section 20.41, is constructed per the ABNF, as defined in [RFC5234], specified in [RFC3261] section 24.1. The ABNF is as follows:

User-Agent = "User-Agent" HCOLON server-val *(LWS server-val)

server-val = product / comment

product = token [SLASH product-version]

The UAC constructs the product-version using the following ABNF:

product-version = Major-version "." Minor-version "." Build-number "." Qfe-number

Major-version = 1*DIGIT

Minor-version = 1*DIGIT

Build-number = 4*DIGIT

QfeNumber = 1*DIGIT

Following is an example of a User-Agent header as constructed by a UAC:

User-Agent: UCCAPI/3.5.6889.0 OC/3.5.6889.0

Construction of Dynamic URL This section follows the behavior described in the product behavior note <167>. In the cases where a dynamic URL is sent back, as described in section 3.4.2.5.8 and section 3.4.2.5.9, the user agent constructs an HTTPS URL based on the base URL by adding the following possible parameters: § lang: The language of the UAC that needs to be installed. Possible values are the values specified in the first and third columns of the table in section 3.4.1.5.3. § arch: The architecture of the UAC that needs to be installed. Possible values are "x32" and "x64". § flavor: The flavor of the UAC that needs to be installed. Possible values are the following: § pm: Per computer. § pu: Per user. § Build: The type of build that needs to be installed. Possible values are the following: § fre: A free or retail build. § chk: A checked or debug build. The following is an example of the Warning header that contains the base HTTPS URI:

Warning: 312 lcs.microsoft.com "https://fabrikam.com/AutoUpdate/Int/Handler/update.aspx? folder=OCv3.1"

The following is an example of the URL a UAC might construct from the preceding base HTTPS URI to download a newer UAC:

Warning: 312 lcs.microsoft.com https://fabrikam.com/AutoUpdate/Int/Handler/update.aspx? folder=OCv3.1&lang=en-us&arch=x32&flavor=pu&build=fre

119 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Possible Values for lang Parameter The following table provides the possible values for the lang parameter described in section 3.4.1.5.2. Language code Language Language code Language af Afrikaans sq Albanian ar-sa Arabic (Saudi Arabia) ar-iq Arabic (Iraq) ar-eg Arabic (Egypt) ar-ly Arabic (Libya) af Afrikaans sq Albanian ar-sa Arabic (Saudi Arabia) ar-iq Arabic (Iraq) ar-eg Arabic (Egypt) ar-ly Arabic (Libya) ar-dz Arabic (Algeria) ar-ma Arabic (Morocco) ar-tn Arabic (Tunisia) ar-om Arabic (Oman) ar-ye Arabic (Yemen) ar-sy Arabic (Syria) ar-jo Arabic (Jordan) ar-lb Arabic (Lebanon) ar-kw Arabic (Kuwait) ar-ae Arabic (U.A.E.) ar-bh Arabic (Bahrain) ar-qa Arabic (Qatar)

Eu Basque bg Bulgarian

Be Belarusian ca Catalan zh-tw Chinese (Taiwan) zh-cn Chinese (PRC) zh-hk Chinese (Hong Kong zh-sg Chinese (Singapore) SAR)

Hr Croatian cs Czech

Da Danish nl Dutch (Standard) nl-be Dutch (Belgium) en English en-us English (United States) en-gb English (United Kingdom) en-au English (Australia) en-ca English (Canada) en-nz English (New Zealand) en-ie English (Ireland) en-za English (South Africa) en-jm English (Jamaica)

En English (Caribbean) en-bz English (Belize) en-tt English (Trinidad) et Estonian

Fo Faeroese fa Persian

Fi Finnish fr French (Standard) fr-be French (Belgium) fr-ca French (Canada) fr-ch French (Switzerland) fr-lu French (Luxembourg)

Gd Scottish Gaelic (United gd-ie Irish (Ireland) Kingdom)

De German (Standard) de-ch German (Switzerland) de-at German (Austria) de-lu German (Luxembourg) de-li German el Greek (Liechtenstein)

120 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Language code Language Language code Language

He Hebrew hi Hindi

Hu Hungarian is Icelandic

Id Indonesian it Italian (Standard) it-ch Italian (Switzerland) ja Japanese

Ko Korean ko Korean (Johab)

Lv Latvian lt Lithuanian

Mk Macedonian (FYROM) ms Malaysian

Mt Maltese no Norwegian (Bokmal)

No Norwegian (Nynorsk) pl Polish pt-br Portuguese (Brazil) pt Portuguese (Portugal)

Rm Rhaeto-Romanic ro Romanian ro-mo Romanian (Republic of ru Russian Moldova) ru-mo Russian (Republic of sz Sami (Lappish) Moldova)

Sr Serbian (Cyrillic) sr Serbian (Latin)

Sk Slovak sl Slovenian

Sb Sorbian es Spanish (Spain) es-mx Spanish (Mexico) es-gt Spanish (Guatemala) es-cr Spanish (Costa Rica) es-pa Spanish (Panama) es-do Spanish (Dominican es-ve Spanish Republic) (Venezuela) es-co Spanish (Colombia) es-pe Spanish (Peru) es-ar Spanish (Argentina) es-ec Spanish (Ecuador) es-cl Spanish (Chile) es-uy Spanish (Uruguay) es-py Spanish (Paraguay) es-bo Spanish (Bolivia) es-sv Spanish (El Salvador) es-hn Spanish (Honduras) es-ni Spanish (Nicaragua) es-pr Spanish (Puerto Rico)

Sx Sutu sv Swedish sv-fi Swedish (Finland) th Thai

Ts Tsonga tn Tswana

Tr Turkish uk Ukrainian

Ur Urdu ve Venda

Vi Vietnamese xh Xhosa

Ji Yiddish zu Zulu

Timer Events None.

Server Role

Abstract Data Model None.

Timers None.

Initialization None.

Higher-Layer Triggered Events None.

Message Processing Events and Sequencing Rules The server can provide a way for the administrator to configure versions of the UAC that it supports and the actions that could be taken based on the version of the UAC. The server can also provide a way to configure the location to download a newer client that implements a compatible version of a UAC. A client is a desktop application that acts on behalf of a user as a UAC. For the purposes of this discussion, a client is a UAC. A client is identified by the UAC version specified in the SIP request generated by the client, as specified in section 3.4.1.5.1. Based on the version of the UAC, it is possible for the administrator to configure the following: § Allow client: In the case of a compatible UAC version, the server SHOULD allow the client to register with the server. § Allow clients with static URL: In the case of a deprecated compatible UAC version, the server SHOULD allow the client to register with the server and provide static information to the client and network location where another version of the client can be downloaded. § Block client with a prompt: In the case of an incompatible UAC version, the server (2) SHOULD reject the client with an error and include a prompt that can be displayed on the client indicating that its UAC version is incompatible with the server (2). § Block client with static URL: In the case of an incompatible UAC version, the server SHOULD reject the client with an error and provide static information to the client pertaining to the location from which a compatible version of the client can be downloaded. § Block client with dynamic URL: In the case of an incompatible UAC version, the server (2) SHOULD<168> reject the client with an error and provide location information to the client indicating where to download a

122 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 newer client. In this case, the client SHOULD also be able to specify which version of the UAC needs to be downloaded. For example, a language- specific version of a UAC can be automatically downloaded as a newer version of the client. § Block clients with upgrade: In the case of an incompatible UAC version, the server SHOULD reject the client with an error and include a non- localized, non-displayable message in a warning header indicating that an upgrade tool needs to be used to upgrade. § Allow client and provide a dynamic URL to download a newer version of client: In the case where the server supports a UAC version, but needs to recommend that the client upgrade to a client that implements a newer version of the UAC, the server SHOULD allow the UAC to register with the server and provide location information to the client where to download a newer client. In this case, the UAC SHOULD<169> also be able to specify which version of the client needs to be downloaded, for example by language, and automatically download a newer version of the client. This is discussed in more detail in the following sections.

Processing Incoming REGISTER Request The client includes the version of the UAC it is running in the format described in section 3.4.1.5 in the User-Agent header, as specified in [RFC3261] section 20.41, of the REGISTER request. When the server (2) receives this request from a client, it SHOULD retrieve the UAC version from the value of the User- Agent header. Based on the configuration on the server (2) that specifies the versions of the UAC that are compatible with the server (2), the server (2) can respond in one of the following ways: § It SHOULD respond with a 200 OK response code, as specified in [RFC3261] section 7.2, if the UAC version is compatible with the server (2). The server (2) SHOULD include a Warning header, as specified in [RFC3261] section 7.3.1, which could provide more information to the client with regard to the location where a compatible version of the client could be downloaded. § It SHOULD respond with a 403 Forbidden response code, as specified in [RFC3261] section 7.2, if the UAC version is incompatible with the server (2). In this case, the server (2) SHOULD include a Warning header, as specified in [RFC3261], section 7.3.1, which could provide more information to the client with regard to the location where a compatible version of the client could be downloaded. Following is the ABNF, as defined in [RFC5234], for a Warning header, as specified in [RFC3261] section 25.1.

Warning = "Warning" HCOLON warning-value *(COMMA warning-value)

warning-value = warn-code SP warn-agent SP warn-text

warn-code = 3DIGIT

warn-agent = hostport / pseudonym

123 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 ; the name or pseudonym of the server adding

; the Warning header, for use in debugging

warn-text = quoted-string

Sections 3.4.2.5.2 through 3.4.2.5.9 describe these response codes in more detail.

Sending 200 OK response (Action: Allow client) If the request is valid and the version specified in the User-Agent header is supported, the server SHOULD allow processing of the REGISTER request and respond with a 200 OK REGISTER response.

Sending 403 Forbidden response (Action: Block client with prompt) If the server determines that it does not support the version specified in the User-Agent header, and if the action that is configured for the client is to prompt, such as when there is no location configured to download newer clients, the server SHOULD respond with a 403 Forbidden error. In this case, the server SHOULD include a Warning header, as specified in [RFC3261] section 7.3.1. The value of the Warning header MUST be constructed as follows: § Warn-code is set to the value 310. § Warn-agent is set to the value "lcs.microsoft.com". § Warn-text is set to the quoted string "You are currently not using the recommended version of the client". The following is an example of a Warning header:

Warning: 310 lcs.microsoft.com "You are currently not using the recommended version of the client"

Sending 403 Forbidden response (Action: Block client with static URL) If the server determines that it does not support the version specified in the User-Agent header, it SHOULD respond with a 403 Forbidden error. If the action configured for the version of the UAC is to block and respond with a static location to download a newer client, the server SHOULD include a Warning header, as specified in [RFC3261] section 7.3.1. The value of the Warning header MUST be constructed as follows: § Warn-code is set to the value 311. § Warn-agent is set to the value "lcs.microsoft.com". § Warn-text is set to the static location information that is configured for this version of the UAC. Typically, the client prompts the user to go to this location to download a newer version of the client. This information is an HTTP or HTTPS URI where the client version can be downloaded. The following is an example of this Warning header.

Warning: 311 lcs.microsoft.com http://fabrikam.com

124 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Sending 200 OK response (Action: Allow clients with static URL) This section follows the behavior described in product behavior note <170>. If the server determines that it can support the version specified in the User- Agent header, it SHOULD allow processing of the REGISTER request and respond with a 200 OK response if the processing succeeds. If the action configured for the version of the UAC is to allow and respond with a static location to download a newer client, the server SHOULD include a Warning header, as specified in [RFC3261] section 7.3.1. The value of the Warning header MUST be constructed as follows: § Warn-code is set to the value 313. § Warn-agent is set to the value "lcs.microsoft.com". § Warn-text is set to the static location information that is configured for this version of the UAC. Typically, the client prompts the user to go to this location to download a newer version of the client. This information is an HTTP or HTTPS URI where the client version can be downloaded. The following is an example of this Warning header.

Warning: 313 lcs.microsoft.com http://fabrikam.com

Sending 403 Forbidden response (Action: Block clients with upgrade) This section follows the behavior described in product behavior note <171>. If the server determines that it does not support the version specified in the User-Agent header, it SHOULD respond with a 403 Forbidden error. If the action configured for the version of the UAC is to block and respond with an upgrade notification hinting to the client to upgrade from an upgrade service, the server SHOULD include a Warning header, as specified in [RFC3261] section 7.3.1. The value of the Warning header MUST be constructed as follows: § Warn-code is set to the value 314. § Warn-agent is set to the value "lcs.microsoft.com". § Warn-text is set to the quoted string "Check Microsoft Update for the newest version." The following is an example of this Warning header.

Warning: 314 lcs.microsoft.com "Check Microsoft Update for the newest version."

Sending 200 OK response (Action: Allow clients with upgrade) This section follows the behavior described in product behavior note <172>. If the server determines that it can support the version specified in the User- Agent header, it SHOULD allow processing of the REGISTER request and respond with a 200 OK response if the processing succeeds. If the action configured for the version of the UAC is to allow and respond with an upgrade notification hinting to the client to upgrade from an upgrade service, the server SHOULD include a Warning header, as specified in [RFC3261] section 7.3.1. The value of the Warning header MUST be constructed as follows: § Warn-code is set to the value 314.

125 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 § Warn-agent is set to the value "lcs.microsoft.com". § Warn-text is set to the quoted string "Check Microsoft Update for the newest version." The following is an example of this Warning header.

Warning: 314 lcs.microsoft.com "Check Microsoft Update for the newest version."

Sending 403 Forbidden response (Action: Block client with dynamic URL) This section follows the behavior described in product behavior note <173>. If the server determines that it does not support the version specified in the User-Agent header, it SHOULD respond with a 403 Forbidden error. If the action configured for the version of the client is to block and respond with a dynamic location to download a newer client, the response SHOULD include a Warning header, as specified in [RFC3261] section 7.3.1. The value of the Warning header MUST be constructed as follows: § Warn-code is set to the value 312. § Warn-agent is set to the value "lcs.microsoft.com". § Warn-text is set to the base location to download a newer version of the client. This location is an HTTPS URI and points to a webpage. The URI MUST contain a parameter with the name folder. The server constructs a path relative to this base location, as described in section 3.4.1.5.2. The installers are either Windows Installer (.msi) file or .msp file. The client can automatically install a newer version of the client from this location. The following is an example of a Warning header with a base HTTPS URL that is sent back in the response.

Warning: 312 lcs.microsoft.com "https://fabrikam.com/AutoUpdate/Int/Handler/update.aspx? folder=OCv3.1

Sending 200 OK response (Action: Allow client with dynamic URL) This section follows the behavior described in product behavior note <174>. If the server determines that it can support the version specified in the User- Agent header, it SHOULD allow processing of the REGISTER request and respond with a 200 OK response if the processing succeeds. If the action configured for the version of the client is to respond with a dynamic location, such as when an upgrade of the client is recommended, the server SHOULD include a Warning header, as specified in [RFC3261] section 7.3.1. The value of the Warning header MUST be constructed as follows: § Warn-code is set to the value 312. § Warn-agent is set to the value "lcs.microsoft.com". § Warn-text is set to the base location to download a newer version of the client. This location is an HTTPS URI and points to a webpage. The URI MUST contain a parameter with the name folder. The server constructs a path relative to this base location, as described in section 3.4.1.5.2. The installers are either Windows Installer (.msi) files or .msp files. The client can automatically install a newer version of the client from this location.

126 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 The following is an example of a Warning header with a base HTTPS URL that is sent back in the response.

Warning: 312 lcs.microsoft.com "https://fabrikam.com/AutoUpdate/Int/Handler/update.aspx? folder=OCv3.1

Timer Events None.

Other Local Events None.

Notifying the Client of Survivable Mode This section follows the behavior described in product behavior note <175>.

Server Role None.

Abstract Data Model None.

Timers None.

Initialization None.

Higher-Layer Triggered Events The SIP registrar SHOULD send a NOTIFY to the UAC if it changes the state of the Presence-Service-Available field described in section 3.1.2.1 from "true" to "false". If the registrar notifies an endpoint and a NOTIFY is sent, it MUST construct the NOTIFY request as specified in the following subsection.

Constructing the Survivable Mode NOTIFY Request The outgoing NOTIFY request is first constructed using the rules specified in section 2.2.1.12. It MUST be sent only to the UAC that is being notified, and hence it MUST use the same local and remote tags, as specified in [RFC3261] section 12, and the call-id and local CSeq of the last REGISTER transaction sent from the UAC being notified, as specified in [RFC3265] section 3.3.4 and [RFC3261] section 10.3.

Message Processing Events and Sequencing Rules None.

Other Local Events None.

Registration

Basic Registration In the following example, user [email protected] registers with the SIP registrar server. This is the first endpoint to register. The call flow is shown in the following diagram.

Figure 2: Basic registration call flow

The authentication challenge that is typically part of the registration sequence is not shown here.

Via: SIP/2.0/TLS 10.1.2.50:4237

Max-Forwards: 70

From: ;tag=2d0be03279;epid=492a7ce35f

To:

Call-ID: 74c55d45a6ee404680aa55c8fe126f11

CSeq: 3 REGISTER

Contact: ;methods="INVITE, MESSAGE, INFO, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER, BENOTIFY";proxy=replace; +sip.instance=""

User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)

Authorization: NTLM qop="auth", realm="SIP Communications Service", targetname="ocs.fabrikam.com", gssapi- data="TlRMTVNTUAADAAAAGAAYAHoAAAAYABgAkgAAAAoACgBIAAAAEAAQAFIAAAAYABgAYgAAABAAEACqAAAAVYKQQg UCzg4AAAAPTgBUAEQARQBWAHMAVQBuAGsAYQByAGEAbgBTAEEATgBLAEEAUgBBAE4ALQBEAEUAVgDnJVs84fE59ziCDe cY7XprbBXcdABFbpbnJVs84fE59ziCDecY7XprbBXcdABFbpZwMLke/elE9fi69enePNxU", opaque="99052D67", version=3

Supported: gruu-10, adhoclist, msrtc-event-categories

Supported: ms-cluster-failover

Supported: ms-userservices-state-notification

ms-keep-alive: UAC;hop-hop=yes

ms-subnet: 10.1.2.1

Content-Length: 0

The server responds with a 200 OK response and includes the GRUU contact URI to be used in subsequent dialog initiating requests, as follows.

SIP/2.0 200 OK

ms-keep-alive: UAS; tcp=no; hop-hop=yes; end-end=no; timeout=300

Authentication-Info: NTLM rspauth="0100000000636F6E9575D2297F8F5EF3", srand="168CE345", snum="1", opaque="99052D67", qop="auth", targetname="ocs.fabrikam.com", realm="SIP Communications Service"

From: ;tag=2d0be03279;epid=492a7ce35f

To: ;tag=0D08337B2339766A952BC5B9D8E0A41A

Call-ID: 74c55d45a6ee404680aa55c8fe126f11

CSeq: 3 REGISTER

Via: SIP/2.0/TLS 10.1.2.50:4237;received=10.54.78.109;ms-received-port=4237;ms-received- cid=10A0D00

Contact: ;expires=7200;+sip.instance="";gruu="sip:[email protected];opaque=user:epid:HT07tI-f3F-fdDyic8rblwAA;gruu"

Expires: 7200

presence-state: register-action="added";primary-cluster-type="central";is-connected-to- primary="yes"

Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft- roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft- provisioning-v2

Supported: adhoclist

Server: RTC/3.0

Supported: msrtc-event-categories

Content-Length: 0

Basic Unregistration The user unregisters from the SIP registrar by sending a REGISTER request with an Expires: 0 header, as follows.

Via: SIP/2.0/TLS 10.1.2.50:4237

Max-Forwards: 70

To:

Call-ID: 74c55d45a6ee404680aa55c8fe126f11

CSeq: 3 REGISTER

Contact: ;methods="INVITE, MESSAGE, INFO, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER, BENOTIFY";proxy=replace; +sip.instance=""

User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)

Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft- roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft- provisioning-v2

Supported: gruu-10, adhoclist, msrtc-event-categories

ms-keep-alive: UAC;hop-hop=yes

Event: registration

Expires: 0

Content-Length: 0

The server responds with a 200 OK response, terminating the registration.

SIP/2.0 200 OK

ms-keep-alive: UAS; tcp=no; hop-hop=yes; end-end=no; timeout=300

Authentication-Info: NTLM rspauth="0100000000636F6E9575D2297F8F5EF3", srand="168CE345", snum="1", opaque="99052D67", qop="auth", targetname="ocs.fabrikam.com", realm="SIP Communications Service"

From: ;tag=2d0be03279;epid=492a7ce35f

To: ;tag=0D08337B2339766A952BC5B9D8E0A41A

Call-ID: 74c55d45a6ee404680aa55c8fe126f11

CSeq: 3 REGISTER

Via: SIP/2.0/TLS 10.1.2.50:4237;received=10.54.78.109;ms-received-port=4237;ms-received- cid=10A0D00

Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft- roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft- provisioning-v2

Supported: adhoclist, msrtc-event-categories

Server: RTC/3.0

Content-Length: 0

Deregistration If the server deregisters a user's endpoint because of policy, it sends a deregister NOTIFY, as follows. Note that such deregistrations are usually triggered by server (2) policies, such as endpoint (5) quota enforcement.

NOTIFY sip:10.1.2.178:4126;transport=tls;ms-opaque=9a9503bcdb;ms-received-cid=600 SIP/2.0

Via: SIP/2.0/TLS 10.1.2.178:5061;branch=z9hG4bKD948963B.BFDD97BF;branched=FALSE;ms-ts="Wed, 06 Feb 2008 00:41:50 GMT 0"

Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFFCC4C8119E16FEC024B25E89E96BA0865", srand="AA69CAF1", snum="9", opaque="28CE6668", qop="auth", targetname="sip/ocs.fabrikam.com", realm="SIP Communications Service"

Max-Forwards: 70

Content-Length: 27

From: ;tag=25498F391570ACE435E286F873E6AACC

To: sip:[email protected]>;tag=7c503117ea;epid=90e62db136

Call-ID: 6d7b09278d574162a4ef50c25e4e5051

CSeq: 1 NOTIFY

Content-Type: text/registration-event

Event: registration-notify

subscription-state: terminated;expires=0

ms-diagnostics-public: 4141;reason="User disabled"

deregistered;event=rejected

Survivable Mode Notify If the presence service for a UAC becomes unavailable and the UAC has indicated support for survivable mode, the server sends a NOTIFY.

NOTIFY sip:10.1.2.178:4126;transport=tls;ms-opaque=9a9503bcdb;ms-received-cid=600 SIP/2.0

Via: SIP/2.0/TLS 10.1.2.178:5061;branch=z9hG4bKD948963B.BFDD97BF;branched=FALSE;ms-ts="Wed, 06 Feb 2008 00:41:50 GMT 0"

Content-Length: 41

From: ;tag=25498F391570ACE435E286F873E6AACC

To: sip:[email protected]>;tag=7c503117ea;epid=90e62db136

Call-ID: 6d7b09278d574162a4ef50c25e4e5051

CSeq: 1 NOTIFY

Content-Type: text/registration-event

Event: registration-notify

Subscription-state: active;expires=900

ms-diagnostics-public: 4165;reason="User Services Pool is unavailable."

registered;event=userservices-unavailable

Notify for Registrar Change If the system supports a dedicated "home registrar" and the user is being moved across registrars, the server sends a NOTIFY.

NOTIFY sip:10.1.2.178:4126;transport=tls;ms-opaque=9a9503bcdb;ms-received-cid=600 SIP/2.0

Via: SIP/2.0/TLS 10.1.2.178:5061;branch=z9hG4bKD948963B.BFDD97BF;branched=FALSE;ms-ts="Wed, 06 Feb 2008 00:41:50 GMT 0"

Max-Forwards: 70

Content-Length: 41

From: ;tag=25498F391570ACE435E286F873E6AACC

To: sip:[email protected]>;tag=7c503117ea;epid=90e62db136

Call-ID: 6d7b09278d574162a4ef50c25e4e5051

CSeq: 25 NOTIFY

Content-Type: text/registration-event

Event: registration-notify

Subscription-state: terminated;expires=0

P-Preferred-Registrar:

ms-diagnostics-public: 4166;reason="Preferred Registrar Change."

133 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 deregistered;event=preferred-registrar-change

In-band Provisioning The UAC sends an in-band provisioning request to the server. The server responds to the request and generates a notification with the in-band provisioning data. The following example assumes support for piggyback- notifications, as described in [MS-SIP] section 3.4, where the response document is returned in the 200 OK SUBSCRIBE response itself. This is shown in the following diagram.

Figure 3: In-band provisioning call flow

Client to Server Request In the following request, user [email protected] sends an application/vnd- microsoft-roaming-provisioning-v2+xml request to the server, requesting all supported provisioning groups.

SUBSCRIBE sip:[email protected] SIP/2.0

Via: SIP/2.0/TLS 172.24.32.149:53990

Max-Forwards: 70

From: ;tag=77399b3fb7;epid=e48fdaa231

To:

Call-ID: dcb605d5e73e44ccbe84dbe4886d210f

CSeq: 1 SUBSCRIBE

Contact:

User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Communicator 2010)

Event: vnd-microsoft-provisioning-v2

Accept: application/vnd-microsoft-roaming-provisioning-v2+xml

Supported: com.microsoft.autoextend

Supported: ms-benotify

Supported: ms-piggyback-first-notify

Expires: 0

Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="224773FA", targetname="sip/clientmainse.fabrikam.com", crand="571d3235", cnum="4", response="040400ffffffffff0000000000000000d2a625d0f476403d15d58285"

Content-Type: application/vnd-microsoft-roaming-provisioning-v2+xml

Content-Length: 625

Server to Client Response In the following response, the server responds with the data for all requested provisioning groups.

SIP/2.0 200 OK

Contact:

Proxy-Authentication-Info: Kerberos qop="auth", opaque="224773FA", srand="84924759", snum="4", rspauth="040401ffffffffff00000000000000001516d27bd2ddfb27246db52a", targetname="sip/clientmainse.fabrikam.com", realm="SIP Communications Service", version=4

Content-Length: 52146

From: "Alice";tag=77399b3fb7;epid=e48fdaa231

Call-ID: dcb605d5e73e44ccbe84dbe4886d210f

CSeq: 1 SUBSCRIBE

Via: SIP/2.0/TLS 172.24.32.149:53990;ms-received-port=53990;ms-received-cid=914800

Expires: 0

Content-Type: application/vnd-microsoft-roaming-provisioning-v2+xml

Event: vnd-microsoft-provisioning-v2

subscription-state: terminated;expires=0

ms-piggyback-cseq: 1

Supported: ms-benotify, ms-piggyback-first-notify

true

false

true

AllPhotos

WebSearchAndFileDownload

true

180

http://my/_vti_bin/search.asmx

http://msw/searchcenter/pages/peopleresults.aspx

true

false

1500

true

http://octop

http://Oly11- ocg.exchange.corp.microsoft.com/trdin

https://comodf.microsoft.com/trd/

[email protected]

http://vote/scenarios/communicator/dogfood.aspx? &Site=2b08429f-4651-4901-af51-1d0ca5bca2b7

http://www.microsoft.com/communicator

df-mqd-dcs-01

true

user-tagid

yes

false

119

112;100

sip:[email protected]

Your company policy requires you to set a location. If you do not set a location emergency services will not be able to locate you in an emergency. Please set a location.

false

1500

false

Light

true

4251111111

true

Any

Off

true

Desktop

true

false

true

VGA

true

Desktop

false

200

2000

true

6000

false

true

false

true

false

true

false

true

11999

9000

false

true

false

true

11999

9000

6900 urgent-interruptions-only 6900 8999 ]]>

]]>

18500 ]]>

]]>

https://clientmainse.fabrikam.com:443/locationinformation/liservice.svc

https://clientmainse.fabrikam.com:443/abs/handler

https://clientmainse.fabrikam.com:4443/abs/handler

https://clientmainse.fabrikam.com:443/groupexpansion/service.svc

https://clientmainse.fabrikam.com:4443/groupexpansion/service.svc

https://clientmainse.fabrikam.com:443/groupexpansion/service.svc

https://clientmainse.fabrikam.com:4443/groupexpansion/service.svc

true

https://clientmainse.fabrikam.com:443/RequestHandler/ucdevice.upx< /updatesServerInternalUrl>

https://clientmainse.fabrikam.com:4443/RequestHandlerExt/ucdevice. upx

true

false

5350

5389

7100

7102

5350

5389

5350

5389

5350

5389

5350

5389

RequireEncryption

VGA-600K

false

true

High

Medium

true

sip:[email protected];gruu;opaque=srvr:HomeServer:5duhvIdz_FOh to7rkSU2gAAA

sip:[email protected];gruu;opaque=srvr:MRAS:lvmY26x3w1WbYUtP iviXXgAA

sip:[email protected];gruu;opaque=srvr:QoS:N7bgtXm_dla- s17uU81BIwAA

sip:[email protected];gruu;opaque=srvr:Microsoft.Rtc .Applications.Cps:4H28w6olDlm9KG3nl5tyBQAA

https://clientmainse.fabrikam.com:443/RgsClients/AgentServi ce.svc

https://clientmainse.fabrikam.com:4443/RgsClients/AgentServ ice.svc

https://clientmainse.fabrikam.com:443/RgsClients/Tab.a spx

https://clientmainse.fabrikam.com:4443/RgsClients/Tab. aspx

sip:[email protected];gruu;opaque=srvr:Microsoft. Rtc.Applications.TestBot:Hzhw8lv8gF-49c74fEDnRgAA

DefaultProfile

sip:[email protected];gruu;opaque=app:conf:focusfactory

sip:[email protected];opaque=app:voicemail

false

DefaultPolicy

true

false

true

OnPrem

false

DefaultProfile

true

sip:[email protected];gruu;opaque=srvr:GroupChat:k_7TLwJGsVy7jWMyTAtJcwAA

sip:[email protected];gruu;opaque=srvr:GroupChat:k_7TLwJGsVy7jWMyTAtJcwAA sip:[email protected];gruu;opaque=srvr:GroupChat: l_7TLwJGsVy7jWMyTAtJcwBB

https://pool0.fabrikam.com:123/PersistentChat/RM

https://ext.fabrikam.com:1234/PersistentChat/RM

< /PublicProviders>]]>

Client-to-Server Delegated Provisioning Request In the following request, user [email protected] sends an application/vnd- microsoft-roaming-provisioning-v2+xml request to the server on behalf of his delegator [email protected].

SUBSCRIBE sip:[email protected] SIP/2.0

Via: SIP/2.0/TLS 172.24.32.149:53990

Max-Forwards: 70

From: ;tag=77399b3fb7;epid=e48fdaa231

To: sip:[email protected]

p-session-on-behalf-of: sip:[email protected]

Call-ID: dcb605d5e73e44ccbe84dbe4886d210f

CSeq: 1 SUBSCRIBE

Contact:

User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Communicator 2010)

Event: vnd-microsoft-provisioning-v2

Accept: application/vnd-microsoft-roaming-provisioning-v2+xml

Supported: com.microsoft.autoextend

Supported: ms-benotify

Proxy-Require: ms-benotify

Supported: ms-piggyback-first-notify

Expires: 0

Content-Type: application/vnd-microsoft-roaming-provisioning-v2+xml

Content-Length: 625

Automatically Updating Client to a Server-Compatible Version

Processing Incoming Register Request The following example is a typical REGISTER request with a User-Agent header specifying the UAC version.

From: ;tag=90a265ed3f;epid=a0ae9e6cb0

To:

CSeq: 1 REGISTER

Call-ID: 6b2dec5dfd9a4eaf90180bb2f8f699ea

Via: SIP/2.0/TLS 10.2.50.42:1649

Max-Forwards: 70

Contact: ;methods="INVITE, MESSAGE, INFO, OPTIONS, BYE, CANCEL, NOTIFY, ACK, REFER, BENOTIFY";proxy=replace; +sip.instance=""

User-Agent: UCCAPI/3.5.6890.0 OC/3.5.6890.0 (Microsoft Office Communicator 2007 R2)

Supported: gruu-10, adhoclist, msrtc-event-categories

ms-keep-alive: UAC;hop-hop=yes

Event: registration

Content-Length: 0

162 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Sending 200 OK Response (Action: Allow client) The following code is an example of a 200 OK REGISTER response sent back when the server allows the UAC.

SIP/2.0 200 OK

From: ;tag=90a265ed3f;epid=a0ae9e6cb0

To:

CSeq: 1 REGISTER

Call-ID: 6b2dec5dfd9a4eaf90180bb2f8f699ea

ms-keep-alive: UAS; tcp=no; hop-hop=yes; end-end=no; timeout=300

Proxy-Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF9964699C1D00E6ACA44AEBD821D187D2", srand="9F9AB255", snum="1", opaque="B3762FF0", qop="auth", targetname="sip/ABC.fabrikam.com", realm="SIP Communications Service"

Via: SIP/2.0/TLS 10.2.50.42:1649;ms-received-port=1649;ms-received-cid=100

Contact: ;expires=7200;+sip.instance="";gruu="sip:[email protected];opaque=user:epid:QJJYwWDmT1mos0tV81j LwQAA;gruu"

Expires: 7200

presence-state: register-action="added";primary-cluster-type="central";is-connected-to- primary="yes"

Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft- roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft- provisioning-v2

Supported: adhoclist

Server: RTC/3.5

Supported: msrtc-event-categories

Content-Length: 0

Sending 403 Forbidden Response (Action: Block Client with Prompt) The following code is an example of a 403 Forbidden response sent back when the server blocks the client. In this case, the UAC displays a prompt to the user indicating that the version of the client needs to be updated.

SIP/2.0 403 Forbidden

From: ;tag=90a265ed3f;epid=a0ae9e6cb0

To: sip:[email protected]

CSeq: 1 REGISTER

Proxy-Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF553E0C6CD0DF29D9C9DF1A9132706429", srand="E7D4FFEC", snum="1", opaque="F2225600", qop="auth", targetname=" sip/ABC.fabrikam.com ", realm="SIP Communications Service"

Via: SIP/2.0/TLS 10.2.50.42:1656;ms-received-port=1656;ms-received-cid=100

Warning: 310 lcs.microsoft.com "You are currently not using the recommended version of the client"

ms-diagnostics: 17002;reason="Invalid Request";source="DB19- LCT.Production.cdmedia.tv";appName="ClientVersionFilter"

Content-Length: 0

Sending 403 Forbidden Response (Action: Block Client with Static URL) The following code is an example of a 403 Forbidden response sent back when the server blocks the client. In this case, the user can get the newer version of the client from the following link specified in the Warning header.

https://fabrikam.com/ClientUpdate.html

SIP/2.0 403 Forbidden

From: ;tag=90a265ed3f;epid=a0ae9e6cb0

To: sip:[email protected]

CSeq: 1 REGISTER

Call-ID: 6b2dec5dfd9a4eaf90180bb2f8f699ea

Via: SIP/2.0/TLS 10.2.50.42:1656;ms-received-port=1656;ms-received-cid=100

Warning: 311 lcs.microsoft.com "https://fabrikam.com/ClientUpdate.html"

ms-diagnostics: 17002;reason="Invalid Request";source="DB19- LCT.Production.cdmedia.tv";appName="ClientVersionFilter"

Content-Length: 0

Sending 403 Forbidden Response (Action: Block Client with Dynamic URL) The following code is an example of a 403 Forbidden response sent back when the server blocks the client. In this case, the client uses the dynamic URL to construct the following URL, and then automatically downloads a newer version of the client.

164 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 https://server.vdomain.com/AutoUpdate/Int/Handler/update.aspx?folder=OCv3.1&lang=en- us&arch=x32&flavor=pu&build=chk

SIP/2.0 403 Forbidden

From: ;tag=90a265ed3f;epid=a0ae9e6cb0

To: sip:[email protected]

CSeq: 1 REGISTER

Call-ID: 6b2dec5dfd9a4eaf90180bb2f8f699ea

Via: SIP/2.0/TLS 10.2.50.42:1656;ms-received-port=1656;ms-received-cid=100

Warning: 312 lcs.microsoft.com "https://fabrikam.com/ClientUpdate/update.aspx?folder=OCv3.1"

ms-diagnostics: 17002;reason="Invalid Request";source="DB19- LCT.Production.cdmedia.tv";appName="ClientVersionFilter"

Content-Length: 0

Sending 200 OK Response (Action: Allow Client with Dynamic URL) The following code is an example of a 200 OK response sent back. In this case, the client uses the dynamic URL to construct the following URL, and then downloads a newer version of the client.

https://server.vdomain.com/AutoUpdate/Int/Handler/update.aspx?folder=OCv3.1&lang=en- us&arch=x32&flavor=pu&build=chk

SIP/2.0 200 OK

From: ;tag=90a265ed3f;epid=a0ae9e6cb0

To: sip:[email protected]

CSeq: 1 REGISTER

Call-ID: 6b2dec5dfd9a4eaf90180bb2f8f699ea

ms-keep-alive: UAS; tcp=no; hop-hop=yes; end-end=no; timeout=300

Proxy-Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF104A8EDFA12CC095AAA663DF55824DCB", srand="5E058A82", snum="1", opaque="E0DA4F74", qop="auth", targetname="sip/DB19- LCT.Production.cdmedia.tv", realm="SIP Communications Service"

Via: SIP/2.0/TLS 10.2.50.42:1699;ms-received-port=1699;ms-received-cid=200

Contact: ;expires=7200;+sip.instance="";gruu="sip:[email protected];opaque=user:epid:QJJYwWDmT1mos0tV81jLwQAA;gruu"

presence-state: register-action="added";primary-cluster-type="central";is-connected-to- primary="yes"

Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft- roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft- provisioning-v2

Supported: adhoclist

Server: RTC/3.5

Supported: msrtc-event-categories

Warning: 312 lcs.microsoft.com "https://fabrikam.com/Client

/update.aspx?folder=OCv3.1"

ms-diagnostics: 17002;reason="Invalid Request";source="DB19- LCT.Production.cdmedia.tv";appName="ClientVersionFilter"

Content-Length: 0

Sending 200 OK Response (Action: Allow Clients with Upgrade) The following code is an example of a 200 OK response sent back when the server allows the client. In this case, the client connections to an update service to find the latest version.

SIP/2.0 200 OK

From: ;tag=90a265ed3f;epid=a0ae9e6cb0

To: sip:[email protected]

CSeq: 1 REGISTER

Call-ID: 6b2dec5dfd9a4eaf90180bb2f8f699ea

Via: SIP/2.0/TLS 10.2.50.42:1656;ms-received-port=1656;ms-received-cid=100

Warning: 314 lcs.microsoft.com "Check Microsoft Update for the newest version.";appName="ClientVersionFilter"

Content-Length: 0

Sending 403 Forbidden (Action: Block Clients with Upgrade) The following code is an example of a 403 Forbidden response sent back when the server blocks the client. In this case, the client connections to an update service to find the latest version.

SIP/2.0 403 Forbidden

To: sip:[email protected]

CSeq: 1 REGISTER

Call-ID: 6b2dec5dfd9a4eaf90180bb2f8f699ea

Via: SIP/2.0/TLS 10.2.50.42:1656;ms-received-port=1656;ms-received-cid=100

Warning: 314 lcs.microsoft.com "Check Microsoft Update for the newest version.";appName="ClientVersionFilter"

Content-Length: 0

Sending 200 OK Response (Action: Allow Client with Static URL) The following code is an example of a 200 OK REGISTER response sent back by the server. In this case, the user can get the newer version of the client from the following link specified in the Warning header.

https://fabrikam.com/ClientUpdate.html

SIP/2.0 200 OK

From: ;tag=90a265ed3f;epid=a0ae9e6cb0

To: sip:[email protected]

CSeq: 1 REGISTER

Call-ID: 6b2dec5dfd9a4eaf90180bb2f8f699ea

ms-keep-alive: UAS; tcp=no; hop-hop=yes; end-end=no; timeout=300

Via: SIP/2.0/TLS 10.2.50.42:1699;ms-received-port=1699;ms-received-cid=200

Contact: ;expires=7200;+sip.instance="";gruu="sip:[email protected];opaque=user:epid:QJJYwWDmT1mos0tV81jLwQAA;gruu"

Expires: 7200

presence-state: register-action="added";primary-cluster-type="central";is-connected-to- primary="yes"

Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft- roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft- provisioning-v2

Server: RTC/3.5

Supported: msrtc-event-categories

Warning: 313 lcs.microsoft.com "https://fabrikam.com/ClientUpdate.html"

ms-diagnostics: 17002;reason="Invalid Request";source="DB19- LCT.Production.cdmedia.tv";appName="ClientVersionFilter"

Content-Length: 0

Security Considerations for Implementers These extensions have the same security considerations as those natively defined for SIP. In addition, an SA is required to be established and maintained between the UAC and the SIP registrar using the NTLM or the Kerberos authentication protocol, as described in [MS-SIPAE] section 3.2.

Index of Security Parameters None.

169 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Appendix A: Product Behavior The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs. § Microsoft Office Communications Server 2007 § Microsoft Office Communicator 2007 § Microsoft Office Communications Server 2007 R2 § Microsoft Office Communicator 2007 R2 § Microsoft Lync Server 2010 § Microsoft Lync 2010 § Microsoft Lync Server 2013 § Microsoft Lync Client 2013/Skype for Business § Microsoft Skype for Business Server 2015 § Microsoft Skype for Business 2016 Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition. Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription. <1> Section 2.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync 2010, Lync Server 2010: IPv6 is not supported. <2> Section 2.2.1.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <3> Section 2.2.1.4: Supported in Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only. <4> Section 2.2.1.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <5> Section 2.2.1.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <6> Section 2.2.1.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

170 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <7> Section 2.2.1.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <8> Section 2.2.1.7: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <9> Section 2.2.1.7: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <10> Section 2.2.1.8: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <11> Section 2.2.1.8: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <12> Section 2.2.1.9: Office Communications Server 2007: Server header value is the literal string "RTC/3.0". Office Communications Server 2007 R2: Server header value is the literal string "RTC/3.5". <13> Section 2.2.1.12: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <14> Section 2.2.1.13: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This message body is not supported. <15> Section 2.2.1.13: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This message body is not supported. <16> Section 2.2.1.13: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <17> Section 2.2.2.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <18> Section 2.2.2.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <19> Section 2.2.2.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <20> Section 2.2.2.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

171 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <21> Section 2.2.2.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <22> Section 2.2.2.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <23> Section 2.2.2.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <24> Section 2.2.2.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <25> Section 2.2.2.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <26> Section 2.2.2.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync 2010: This behavior is not supported. <27> Section 2.2.2.4: Supported in Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only. <28> Section 2.2.2.5: Office Communications Server 2007, Office Communicator 2007: The response is a server error, based on an incompatible UAC version. <29> Section 2.2.2.5: Office Communications Server 2007, Office Communicator 2007: The response is a server error, based on an incompatible UAC version. <30> Section 2.2.2.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <31> Section 2.2.2.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <32> Section 2.2.2.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <33> Section 2.2.2.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <34> Section 2.2.2.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <35> Section 2.2.2.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync 2010: This behavior is not supported.

172 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <36> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. Office Communications Server 2007 R2, Office Communicator 2007 R2: Only the following properties are supported:

|-- lisInternalUrl

|-- absInternalServerUrl

|-- absExternalServerUrl

|-- abwqInternalUrl

|-- abwqExternalUrl

|-- dlxInternalUrl

|-- dlxExternalUrl

|-- dlxEnabled

|-- updatesServerInternalUrl

|-- updatesServerExternalUrl

|-- updatesServerEnabled

|-- organization

|-- consoleDownloadInternalUrl

|-- consoleDownloadExternalUrl

|-- ucPortRangeEnabled

|-- ucMinMediaPort

|-- ucMaxMediaPort

|-- ucMinSipDynamicPort

|-- ucMaxSipDynamicPort

|-- ucMinAudioPort

|-- ucMaxAudioPort

|-- ucMinVideoPort

|-- ucMaxVideoPort

|-- ucMinAppSharingPort

|-- ucMaxAppSharingPort

|-- ucMinFileTransferPort

|-- ucMaxFileTransferPort

|-- ucPC2PCAVEncryption

|-- qosEnabled

|-- enableInCallQoS

|-- inCallQoSIntervalSeconds

|-- ucDiffServVoice

|-- ucVoice802_1p

|-- ucEnforcePinLock

|-- ucMinPinLength

|-- ucPhoneTimeOut

|-- ucExchangeMWIPoll

|-- ucEnableSIPSecurityMode

|-- ucEnableUserLogging

|-- loggingLevel

|-- enableBWPolicyCheck

|-- poolUri

|-- mrasUri

|-- qosUri

|-- callParkServerUri

|-- responseGroupServiceInternalURL

|-- responseGroupServiceExternalURL

|-- responseGroupServiceInternalAgentURL

|-- responseGroupServiceExternalAgentURL

|-- botSipUriForTestCall

|-- cwaInternalUri

|-- cwaExternalUri

|-- ucLocationProfile

|-- focusFactoryUri

|-- voiceMailUri

<37> Section 2.2.2.5.1: Supported in Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only.

174 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <38> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This value is not supported. <39> Section 2.2.2.5.1: Supported in Office Communicator 2007, Office Communicator 2007 R2 only. <40> Section 2.2.2.5.1: Supported in Office Communicator 2007, Office Communicator 2007 R2 only. <41> Section 2.2.2.5.1: Supported in Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only. <42> Section 2.2.2.5.1: Supported in Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only. <43> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <44> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <45> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <46> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <47> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <48> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <49> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <50> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <51> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <52> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <53> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <54> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <55> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <56> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

175 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <57> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <58> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <59> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <60> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <61> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <62> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <63> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <64> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <65> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <66> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <67> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <68> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <69> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <70> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <71> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

176 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <72> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <73> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <74> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <75> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <76> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <77> Section 2.2.2.5.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <78> Section 2.2.2.5.2: Supported in Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only. <79> Section 2.2.2.5.2: Supported in Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only. <80> Section 2.2.2.5.2: Supported in Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only. <81> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: Optional/Ignored. <82> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: Optional/Ignored. <83> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: Optional/Ignored. <84> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: Optional/Ignored.

177 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <85> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007: A UAC sending a request with this parameter receives a server error, based on an incompatible UAC version. <86> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: Optional/Ignored. <87> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: Optional/Ignored. <88> Section 2.2.2.5.2: Supported in Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only. <89> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <90> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <91> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <92> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <93> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <94> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <95> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <96> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <97> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

178 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <98> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <99> Section 2.2.2.5.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <100> Section 2.2.2.5.3: Supported in Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2 only. <101> Section 2.2.2.5.3: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <102> Section 2.2.2.5.3: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <103> Section 2.2.2.5.3: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <104> Section 2.2.2.5.4: Office Communications Server 2007, Office Communicator 2007: The ProvisionGroupType and ProvisionGroup element are not supported. <105> Section 2.2.2.5.4: Office Communications Server 2007, Office Communicator 2007: This structure is not supported. <106> Section 2.2.2.5.4: Office Communications Server 2007, Office Communicator 2007: This structure is not supported. <107> Section 2.2.2.5.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: Ignored. <108> Section 2.2.2.5.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <109> Section 2.2.2.5.4: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: visibleContainers: The list of containers for the member is the same as the visible list of containers present in the containers element. <110> Section 2.2.2.5.5: Office Communications Server 2007, Office Communicator 2007: This behavior is not supported. <111> Section 2.2.2.5.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

179 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <112> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This value is not supported. <113> Section 2.2.2.5.6: Supported by Microsoft Outlook 2010 or Microsoft Outlook 2010 Service Pack 1 (SP1) with Lync Server 2010, or Microsoft Outlook 2013 with Lync Server 2013 only. <114> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <115> Section 2.2.2.5.6: Supported by Microsoft OneNote 2010 with Lync Server 2010 only. <116> Section 2.2.2.5.6: Supported by Outlook 2010, Outlook 2010 SP1, and Outlook 2013 only. <117> Section 2.2.2.5.6: Supported by Microsoft Exchange Server 2013 only. <118> Section 2.2.2.5.6: This setting applies only to Lync Server 2013 when Lync Client 2013/Skype for Business is deployed in a Virtualized Environment. When enabled, this setting dictates that Lync Server 2013 connects with the Lync Client 2013/Skype for Business Virtualization Plugin (if deployed on the access device) to provide the user with a high-quality audio and video experience. <119> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <120> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <121> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <122> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <123> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <124> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported.

180 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <125> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <126> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <127> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <128> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <129> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <130> Section 2.2.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This value is not supported. <131> Section 2.2.2.5.7: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <132> Section 2.2.2.5.8: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <133> Section 2.2.2.5.9: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <134> Section 2.2.2.5.10: Office Communications Server 2007, Office Communicator 2007: A UAC sending a request that includes this element receives a server error, based on an incompatible UAC version. <135> Section 2.2.2.5.10: Office Communications Server 2007, Office Communicator 2007: A UAC sending a request that includes this element receives a server error, based on an incompatible UAC version. <136> Section 2.2.2.5.11: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <137> Section 2.2.2.5.11: Supported by the Lync Server 2013 Persistent Chat Room Management Web Application only.

181 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <138> Section 2.2.2.5.11: Supported by the Lync Server 2013 Persistent Chat Room Management Web Application only. <139> Section 2.2.2.5.12: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <140> Section 2.2.2.5.12: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2, Lync Server 2010, Lync 2010: This behavior is not supported. <141> Section 3.1.1.1: Office Communicator 2007, Office Communicator 2007 R2: This behavior is not supported. <142> Section 3.1.1.1: Office Communicator 2007, Office Communicator 2007 R2: This behavior is not supported. <143> Section 3.1.1.1: Office Communicator 2007, Office Communicator 2007 R2: This behavior is not supported. <144> Section 3.1.1.5.1: Office Communicator 2007, Office Communicator 2007 R2: This behavior is not supported. <145> Section 3.1.1.5.1: Office Communicator 2007, Office Communicator 2007 R2: This behavior is not supported. <146> Section 3.1.1.5.1: Office Communicator 2007, Office Communicator 2007 R2: This behavior is not supported. <147> Section 3.1.1.5.1: Office Communicator 2007, Office Communicator 2007 R2: This behavior is not supported. <148> Section 3.1.1.5.1: Office Communicator 2007, Office Communicator 2007 R2: This behavior is not supported. <149> Section 3.1.1.5.1: Office Communicator 2007: This behavior is not supported. <150> Section 3.1.1.5.1: Office Communicator 2007: This behavior is supported. <151> Section 3.1.1.5.1: Office Communicator 2007: This behavior is not supported. <152> Section 3.1.1.5.1: Office Communicator 2007: This behavior is not supported. <153> Section 3.1.2.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported. <154> Section 3.1.2.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported. <155> Section 3.1.2.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported. <156> Section 3.1.2.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported. <157> Section 3.1.2.5.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported.

182 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 <158> Section 3.1.2.5.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported. <159> Section 3.1.2.5.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported. <160> Section 3.1.2.5.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported. <161> Section 3.1.2.5.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported. <162> Section 3.1.2.5.1: Office Communications Server 2007, Office Communications Server 2007 R2: This behavior is not supported. <163> Section 3.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <164> Section 3.2: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <165> Section 3.2.1: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <166> Section 3.2.1.5: Office Communicator 2007, Office Communicator 2007 R2: This behavior is not supported. <167> Section 3.4.1.5.2: Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is only supported in this version. <168> Section 3.4.2.5: Office Communications Server 2007: This behavior is not supported. <169> Section 3.4.2.5: Office Communications Server 2007: This behavior is not supported. <170> Section 3.4.2.5.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <171> Section 3.4.2.5.6: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <172> Section 3.4.2.5.7: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported. <173> Section 3.4.2.5.8: Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is only supported in this version. <174> Section 3.4.2.5.9: Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is only supported in these versions. <175> Section 3.5: Office Communications Server 2007, Office Communicator 2007, Office Communications Server 2007 R2, Office Communicator 2007 R2: This behavior is not supported.

183 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 Change Tracking This section identifies changes that were made to this document since the last release. Changes are classified as New, Major, Minor, Editorial, or No change. The revision class New means that a new document is being released. The revision class Major means that the technical content in the document was significantly revised. Major changes affect protocol interoperability or implementation. Examples of major changes are: § A document revision that incorporates changes to interoperability requirements or functionality. § The removal of a document from the documentation set. The revision class Minor means that the meaning of the technical content was clarified. Minor changes do not affect protocol interoperability or implementation. Examples of minor changes are updates to clarify ambiguity at the sentence, paragraph, or table level. The revision class Editorial means that the formatting in the technical content was changed. Editorial changes apply to grammatical, formatting, and style issues. The revision class No change means that no new technical changes were introduced. Minor editorial and formatting changes may have been made, but the technical content of the document is identical to the last released version. Major and minor changes can be described further using the following change types: § New content added. § Content updated. § Content removed. § New product behavior note added. § Product behavior note updated. § Product behavior note removed. § New protocol syntax added. § Protocol syntax updated. § Protocol syntax removed. § New content added due to protocol revision. § Content updated due to protocol revision. § Content removed due to protocol revision. § New protocol syntax added due to protocol revision. § Protocol syntax updated due to protocol revision. § Protocol syntax removed due to protocol revision. § Obsolete document removed. Editorial changes are always classified with the change type Editorially updated. Some important terms used in the change type descriptions are defined as follows: § Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces.

184 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 § Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire. The changes made to this document are listed in the following table. For more information, please contact [email protected]. Major Tracking number (if applicable) and Section change (Y Change type description or N)

2.2.2.5.1 Data Model for Content ServerConfiguration Removed unused element names. N removed. provisionGroup

Added product behavior notes to specify behaviors that are not supported by Office New product 2.2.2.5.2 Data Model for Communications Server 2007, Office Y behavior note meetingPolicy provisionGroup Communicator 2007, Lync Server 2010, and added. Lync 2010.

Added product behavior note to specify behavior that is not supported by Office New product 2.2.2.5.3 Data Model for Communications Server 2007, Office Y behavior note ucPolicy provisionGroup Communicator 2007, Lync Server 2010, and added. Lync 2010.

Added product behavior notes to specify 2.2.2.5.6 Data Model for values that are not supported by Office New product endpointConfiguration Communications Server 2007, Office Y behavior note provisionGroup Communicator 2007, Lync Server 2010, and added. Lync 2010. Index A block with prompt 113 block with static URL 113 Abstract data model process request 112 automatic client update server client 83 abstract data model 87 server 87 higher-layer triggered events 87 basic registration initialization 87 client 73 local events 91 server 76 messaging processing 87 provisioning sequencing rules 87 client 81 timer events 91 server 82 timers 87 remove binding from registrar client 79 server 80 B survivable mode server 91 Basic registration Applicability 13 client 73 Automatic client update abstract data model 73 client higher-layer triggered events 74 abstract data model 83 initialization 74 higher-layer triggered events 83 local events 76 initialization 83 message processing 74 local events 87 sequencing rules 74 messaging processing 83 timer events 76 overview 83 timers 74 sequencing rules 83 example 93 timer events 87 overview 73 timers 83 server example abstract data model 76 200 OK response higher-layer triggered events 77 allow 112 initialization 77 allow with dynamic URL 114 local events 79 allow with static URL 115 message processing 77 403 Forbidden response sequencing rules 77 block with dynamic URL (section 4.3.5 113, timer events 78 section 4.3.7 114, section 4.3.8 115) timers 76

185 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 unregistration Deregister example 94 example 95 Basic unregistration messages 17 example 94 E C Examples Capability negotiation 13 automatic client update Change tracking 129 200 OK response Client allow 112 automatic client update allow with dynamic URL 114 abstract data model 83 allow with static URL 115 higher-layer triggered events 83 403 Forbidden response initialization 83 block with dynamic URL (section 4.3.5 113, local events 87 section 4.3.7 114, section 4.3.8 115) message processing 83 block with prompt 113 overview 83 block with static URL 113 sequencing rules 83 process request 112 timer events 87 basic registration 93 timers 83 basic unregistration 94 basic registration 73 deregistration 95 abstract data model 73 in-band provisioning 96 higher-layer triggered events 74 client to server request 96 initialization 74 delegated request 111 local events 76 server to client response 97 message processing 74 registrar change notify 95 sequencing rules 74 survivable mode notify 95 timer events 76 Extensions to REGISTER Requests and Responses timers 74 message Provisioning deregister NOTIFY request 17 abstract data model 81 extensions to Contact header 17 higher-layer triggered events 81 extensions to Server header 17 initialization 81 header field extensions 15 local events 82 ms-keep-alive header field 15 message processing 81 Ms-Subnet header field syntax 16 overview 81 P-Preferred-Registrar header field 17 sequencing rules 81 Presence-State header field 15 timer events 81 SIP REGISTER request 14 timers 81 SIP REGISTER response 14 remove binding from registrar survivable mode NOTIFY request 18 abstract data model 79 text/registration-event message 18 higher-layer triggered events 80 initialization 79 F message processing 80 overview 79 Fields - vendor-extensible 13 sequencing rules 80 timers 79 G D Glossary 8 Data model - abstract automatic client update H client 83 server 87 Higher-layer triggered events basic registration automatic client update server 76 client 83 provisioning server 87 client 81 basic registration server 82 client 74 remove binding from registrar server 77 client 79 provisioning server 80 client 81 survivable mode server 82 server 91 remove binding from registrar Data model – abstract client 80 basic registration server 80 client 73 survivable mode

186 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 server 92 remove binding from registrar client 80 I server 80 server initialization 82 Implementer - security considerations 117 local events 82 In-band provisioning timer events 82 example 96 Messages client to server request 96 Extensions to REGISTER Requests and Responses delegated request 111 deregister NOTIFY request 17 server to client response 97 extensions to Contact header 17 In-band Provisioning Messages message (section 2.2.2 extensions to Server header 17 19, section 2.2.2.3 20) header field extensions 15 request 19 ms-keep-alive header field 15 data model 20 Ms-Subnet header field syntax 16 response 20 P-Preferred-Registrar header field 17 data model 22 Presence-State header field 15 Index of security parameters 117 SIP REGISTER request 14 Informative references 13 SIP REGISTER response 14 Initialization survivable mode NOTIFY request 18 automatic client update text/registration-event message 18 client 83 In-band Provisioning Messages 19 server 87 application/vnd-microsoft-roaming-provisioning- basic registration v2+xml document client 74 data model 20 server 77 request 19 provisioning data model 20 client 81 response 20 server 82 data model 22 remove binding from registrar syntax 14 client 79 transport 14 server 80 survivable mode server 92 N Introduction 8 Normative references 12 L O Local events automatic client update Overview (synopsis) 13 client 87 server 91 P basic registration client 76 Parameters - security index 117 server 79 Preconditions 13 provisioning Prerequisites 13 client 82 Product behavior 118 server 82 Provisioning remove binding from registrar client server 81 abstract data model 81 higher-layer triggered events 81 M initialization 81 overview 81 Message processing timers 81 automatic client update example 96 client 83 client server 87 delegated request 111 basic registration request 96 client 74 server server 77 response 97 client messages 19 initialization 81 server local events 82 abstract data model 82 timer events 81 higher-layer triggered events 82 provisioning initialization 82 client 81 timers 82 server 82

187 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 R sequencing rules 87 timer events 91 timers 87 References 12 basic registration informative 13 abstract data model 76 normative 12 higher-layer triggered events 77 Registrar initialization 77 example 95 local events 79 messages 17 message processing 77 removing a binding sequencing rules 77 overview 79 timer events 78 Registration timers 76 example provisioning basic registration 93 abstract data model 82 basic unregistration 94 higher-layer triggered events 82 deregistration 95 initialization 82 notify for registrar change 95 local events 82 survivable mode notify 95 message processing 82 Relationship to other protocols 13 sequencing rules 82 Remove binding from registrar timer events 82 client timers 82 abstract data model 79 remove binding from registrar higher-layer triggered events 80 abstract data model 80 initialization 79 higher-layer triggered events 80 message processing 80 initialization 80 overview 79 local events 81 sequencing rules 80 message processing 80 timers 79 sequencing rules 80 overview 79 timer events 81 server timers 80 abstract data model 80 survivable mode higher-layer triggered events 80 abstract data model 91 initialization 80 higher-layer triggered events 92 local events 81 initialization 92 message processing 80 timers 92 sequencing rules 80 Standards assignments 13 timer events 81 Survivable mode timers 80 example 95 messages 18 S overview 91 server Security abstract data model 91 implementer considerations 117 higher-layer triggered events 92 parameter index 117 initialization 92 Sequencing rules timers 92 automatic client update Syntax 14 client 83 server 87 T basic registration client 74 Timer events server 77 automatic client update client client 87 initialization 81 server 91 provisioning basic registration client 81 client 76 server 82 server 78 remove binding from registrar provisioning client 80 client 81 server 80 server 82 server remove binding from registrar initialization 82 server 81 Server Timers automatic client update automatic client update abstract data model 87 client 83 higher-layer triggered events 87 server 87 initialization 87 basic registration local events 91 client 74 message processing 87

188 / 189 [MS-SIPREGE] - v20150904 Session Initiation Protocol (SIP) Registration Extensions Copyright © 2015 Microsoft Corporation Release: September 4, 2015 server 76 client 74 provisioning server 77 client 81 provisioning server 82 client 81 remove binding from registrar server 82 client 79 remove binding from registrar server 80 client 80 survivable mode server 80 server 92 survivable mode Tracking changes 129 server 92 Transport 14 Triggered events V automatic client update client 83 Vendor-extensible fields 13 server 87 Versioning 13 basic registration